Engineering Logs for Troubleshooting & Debugging
AMD GPU CLI Argument Parsing Failure During Disaster Recovery Problem Description (Symptoms and Impact) During automated disaster‑recovery runs on AMD GPU clusters, the recovery scripts invoke ROCm utilities such as rocm-smi, rocminfo, and rocm-bandwidth-test. The scripts abort with parsing errors, causing the scheduler (e.g., Slurm) to mark all GPUs as unavailable. Typical log excerpts are: … Read more
Problem – Collection Creation Failure During Canary Deployment on AMD MI210 Nodes During a rolling canary deployment of a new AI model on a Kubernetes cluster that contains AMD Instinct MI210 accelerators, pods repeatedly terminate with the following error: [2026-06-27 10:12:34] ERROR: Failed to create collection: ROCm runtime version 5.5 does not match driver version 5.6 … Read more
Problem – Frequent Pod Evictions on AMD GPU Nodes During Disaster Recovery During disaster‑recovery (DR) drills the AI training platform experiences a surge of concurrent training jobs. On clusters that use AMD MI250X GPUs the kubelet repeatedly evicts pods with the reason=OutOfmemory condition. Typical symptoms observed: Pods transition to Evicted status within minutes of the … Read more
Problem – PVC Stuck in Pending on an AMD GPU‑Enabled Cluster In a Kubernetes cluster where nodes are provisioned with AMD GPUs (ROCm), AI workloads that require GPU‑accelerated storage often create a PersistentVolumeClaim (PVC). Operators observe that the PVC never transitions to Bound and remains in the Pending phase despite the presence of storage back‑ends … Read more
Problem: Batch Ingestion Fails on AMD GPU in an Air‑Gapped Environment In a secure, air‑gapped compute cluster the nightly AI batch‑ingestion pipeline aborts with errors indicating missing ROCm runtime components. Typical log excerpts look like: Traceback (most recent call last): File “/opt/pipeline/ingest.py”, line 42, in import torch ImportError: libamdhip64.so: cannot open shared object file: No … Read more