SOLO-5006

PodNotFoundSoloError

Description

Thrown when solo queries Kubernetes for the pod backing a consensus node alias and the lookup returns no pod; the message names the alias. solo needs the pod to run commands, copy files, or check status on a node, so this fires when no pod matches the expected labels in the namespace. Because pod scheduling is asynchronous, it can appear briefly during startup before the pod exists, which is why it is retryable; if it persists, the pod failed to schedule or start, was evicted, or the node was never deployed. This is the base error for the component-specific variants (explorer, relay, mirror-node, block-node, and Postgres pod-not-found errors).

Troubleshooting Steps

1. Check pod status: kubectl get pods -n -l solo.hedera.com/node-name=
2. Describe the pod for events: kubectl describe pod -n -l solo.hedera.com/node-name=
3. A StatefulSet whose claim cannot be provisioned never creates its pod; check PVC/PV binding: kubectl get pvc,pv -n
4. Check the storage class and its provisioner: kubectl get storageclass
5. Review solo logs: tail -n 100 ~/.solo/logs/solo.log