OIM Logs

Caution

It is not recommended to delete the below log files or the directories they reside in.

Note

If you want log files for specific playbook execution, ensure to use the cd command to move into the specific directory before executing the playbook. For example, if you want local repo logs, ensure to enter cd local_repo before executing the playbook. If the directory is not changed, all the playbook execution log files will be consolidated and provided as part of omnia logs located in /opt/omnia/log/core/playbooks.

Cluster Log Collection

Omnia provides a one-shot log collection playbook for gathering cluster logs from Kubernetes and Slurm nodes for debugging and support handoff. For detailed information on log collection, see ../Omnia/log_collector.

Usage

To collect logs from the cluster, execute the following commands:

ssh omnia_core
cd omnia/log_collector
ansible-playbook collect.yml

Collection modes

  • Full mode (default): Collects all logs from target nodes

ansible-playbook collect.yml

  • Curated support mode: Excludes temporary and stale log files

ansible-playbook collect.yml --tags curated_support

Output artifacts

  • Workspace: /opt/omnia/collector_logs

  • Bundle: omnia_logs_<YYYYMMDD-HHMMSS>.tar.gz

  • Metadata: metadata.json (included in bundle)

  • Checksum: .sha256 file for integrity verification

Prerequisites

  • PXE mapping file must exist at /opt/omnia/input/project_default/pxe_mapping_file.csv

  • Nodes must be reachable from OIM

Omnia playbook and container logs

The following table provides an overview of the various Omnia log files, their locations, and their purposes for monitoring.

Location

Purpose

/opt/omnia/log/core/playbooks/discovery.log

Discovery logs

/opt/omnia/log/core/playbooks/local_repo.log

Local Repository logs

/opt/omnia/log/core/playbooks/prepare_oim.log

Prepare OIM Logs

/opt/omnia/log/core/playbooks/provision.log

Provision Logs

/opt/omnia/log/core/playbooks/scheduler.log

Scheduler Logs

/opt/omnia/log/core/playbooks/telemetry.log

Telemetry logs

/opt/omnia/log/core/playbooks/utils.log

Utility logs

/opt/omnia/log/core/playbooks/credential_utility.log

Credential utility logs

/opt/omnia/log/openchami/*log

OpenCHAMI playbook logs

/opt/omnia/log/pulp/*log

Pulp container logs

/opt/omnia/log/local_repo/*log

Local repo logs

/opt/omnia/log/core/container/*log

Core container logs

/opt/omnia/log/core/playbooks/validation_omnia_project_default.log

Omnia input validation report logs

/opt/omnia/log/core/playbooks/input_validation.log

Omnia input validation playbook logs

/opt/omnia/log/core/playbooks/gitlab_build_stream.log

GitLab BuildStreaM logs

/opt/omnia/log/build_stream/

BuildStreaM container log path

Note

The BuildStreaM and GitLab log paths are available inside the BuildStreaM container.

Logs of Individual Podman Containers in OIM

  1. To view the containers running on OIM, run the following command:

    podman ps -a

    The following table shows the status of Omnia containers running on the OIM:

Podman Logs

CONTAINER ID

IMAGE

COMMAND

CREATED

STATUS

PORTS

NAMES

622106c0238a

localhost/omnia_core:2.2

47 hours ago

Up 47 hours

2222/tcp

omnia_core

db34394920dc

localhost/omnia_auth:1.0

/bin/sh -c mkdi…

47 hours ago

Up 47 hours

0.0.0.0:389->389/tcp, 0.0.0.0:636->636/tcp

omnia_auth

b7b115c7f9b9

docker.io/pgsty/minio:RELEASE.2026-04-17T00-00-00Z

server /data –co…

47 hours ago

Up 47 hours

0.0.0.0:9000-9001->9000-9001/tcp

minio-server

09f03324e100

docker.io/pulp/pulp:3.80

/init

44 hours ago

Up 44 hours

0.0.0.0:2225->2225/tcp, 80/tcp

pulp

d0b76ac340c7

docker.io/library/postgres:16

postgres

44 hours ago

Up 44 hours

5432/tcp

omnia_postgres

0608aa923b7c

docker.io/dellhpcomniaaisolution/omnia_build_stream:1.1

44 hours ago

Up 44 hours

omnia_build_stream

1a53264391a3

docker.io/library/registry:3.1.0

/etc/distribution…

44 hours ago

Up 44 hours

0.0.0.0:5000->5000/tcp

registry

c23f11155bfa

docker.io/library/postgres:11.5-alpine

postgres

39 hours ago

Up 39 hours

5432/tcp

postgres

c76102a85d8b

ghcr.io/openchami/local-ca:v0.2.6

/step-ca.sh

39 hours ago

Up 39 hours

9000/tcp

step-ca

33f7ea6c1f6c

docker.io/oryd/hydra:v2.3

serve -c /etc/con…

39 hours ago

Up 39 hours

hydra

887920fb9b04

ghcr.io/openchami/smd:v2.19.3

/smd

39 hours ago

Up 39 hours

27779/tcp

smd

fbb6a89d671c

ghcr.io/openchami/opaal:v0.3.12

/opaal/opaal serv…

39 hours ago

Up 39 hours

opaal-idp

fb69e07e8a6c

ghcr.io/openchami/bss:v1.32.2

/bin/sh -c /usr/l…

39 hours ago

Up 39 hours

27778/tcp

bss

6b9d12699af9

ghcr.io/openchami/opaal:v0.3.12

/opaal/opaal logi…

39 hours ago

Up 39 hours

opaal

dee68167385c

ghcr.io/openchami/cloud-init:v1.3.0

/usr/local/bin/cl…

39 hours ago

Up 39 hours

cloud-init-server

1986ae05d933

cgr.dev/chainguard/haproxy:latest

haproxy -f /usr/l…

39 hours ago

Up 39 hours

0.0.0.0:8081->80/tcp, 0.0.0.0:8443->443/tcp

haproxy

3bdafb383a38

ghcr.io/openchami/coresmd:v0.4.3

/coredhcp

39 hours ago

Up 39 hours

coresmd-coredhcp

ef6db14ebaca

ghcr.io/openchami/coresmd:v0.4.3

/coredns

39 hours ago

Up 39 hours

coresmd-coredns

  1. To view the logs from a specific container, run the following command:

    podman logs <container name>

  2. Alternatively, if the container is managed as a systemd service, you can view the logs using the following command:

    journalctl -xeu <container name>

Logs of Individual K8s Containers on Service Cluster

  1. A list of namespaces and their corresponding pods can be obtained using:

    kubectl get pods -A

  2. Get a list of containers for the pod in question using:

    kubectl get pods <pod_name> -o jsonpath='{.spec.containers[*].name}'

  3. Once you have the namespace, pod and container names, run the below command to get the required logs:

    kubectl logs pod <pod_name> -n <namespace> -c <container_name>

If you have any feedback about Omnia documentation, please reach out at omnia.readme@dell.com.