Troubleshooting Guide¶
A structured guide for diagnosing and resolving issues across Omnia deployment, provisioning, Kubernetes, Slurm, storage, authentication, and telemetry workflows. Each entry follows a consistent Symptom > Cause > Resolution format so you can quickly identify the problem and apply the fix.
Troubleshooting Approach¶
When you encounter an issue, follow this general diagnostic flow:
-
Check logs first. Most issues leave a clear trace in the logs. For comprehensive logging information, see Log Management.
-
Verify prerequisites. Many failures stem from unmet prerequisites (missing packages, wrong OS version, misconfigured networks). Re-check the Prerequisites Checklist for your deployment path.
-
Inspect container and service status. Verify that OIM containers and services are running:
Execution context: OIM host
podman ps --format 'table {{.Names}}\t{{.Status}}' -
Check the current OpenCHAMI services. Use the
ochamiCLI for SMD inventory and systemd for the Fabrica boot and metadata services:Execution context: OIM
ochami smd component get ochami smd service status systemctl is-active boot-service metadata-service tokensmith -
Search this section. Browse the topic-specific pages below or use your browser's search (Ctrl+F) to find your symptom.
Troubleshooting Topics¶
Repository Manager module¶
Repository mirroring and synchronization issues - Pulp operations, package downloads, container registry sync
| Topic | Description |
|---|---|
| Local Repository and Pulp Issues | Pulp container operations, repository synchronization, and package downloads |
Image Build Manager module¶
Image building and S3 storage issues - OS image creation, MinIO uploads, architecture-specific builds
| Topic | Description |
|---|---|
| Image Build Manager Issues | OS image creation, architecture-specific builds, and S3 or MinIO operations |
Discovery module¶
Node discovery and mapping file generation issues - OME integration, PXE mapping file creation
| Topic | Description |
|---|---|
| Discovery Issues | OME integration and PXE mapping file generation |
Orchestrator module¶
Slurm, Kubernetes, networking, storage, and authentication issues - Node provisioning, cluster configuration
| Topic | Description |
|---|---|
| Orchestrator Issues | General Orchestrator module issues |
| Provisioning Issues | Node provisioning and PXE boot issues |
| Slurm Issues | Slurm job scheduling and configuration issues |
| Kubernetes Issues | Kubernetes service cluster issues |
| OpenCHAMI Issues | OpenCHAMI provisioning stack issues |
| Authentication Issues | LDAP and authentication issues |
| Kernel Version Override | Kernel version management issues |
Telemetry module¶
Monitoring and metrics collection issues - iDRAC telemetry, LDMS samplers, Kafka, VictoriaMetrics, VictoriaLogs
| Topic | Description |
|---|---|
| Telemetry Issues | iDRAC telemetry, LDMS samplers, Kafka, VictoriaMetrics, and VictoriaLogs |
BuildStreaM module¶
GitOps-based CI/CD pipeline issues - BuildStreaM execution, GitLab integration, catalog validation
| Topic | Description |
|---|---|
| BuildStreaM Issues | BuildStreaM pipeline stage failures, API registration, and catalog parsing |
Utils module¶
Helper utilities issues - Backup, install, and prepare operations
| Topic | Description |
|---|---|
| Utils Issues | Backup, install, and prepare operations |
Cross-module issues¶
| Topic | Description |
|---|---|
| General | OIM issues, OpenCHAMI certificates, system recovery, InfiniBand, and Ansible Vault errors |
| Known Limitations | Current limitations, constraints, and known issues |
Tip
If you cannot resolve an issue using this guide, open an issue on the Omnia GitHub repository with the relevant log output and a description of your environment.