SOLO-5081

PodNotReadySoloError

Description

Thrown when a pod matching the expected labels was found but never reached the required phase or readiness condition before solo stopped waiting; the message names the pod, its last observed phase, and a per-container summary (readiness, restart count, and any waiting/terminated reason). This is distinct from the pod-not-found errors: the pod exists, but something is keeping it from becoming ready — most commonly a failing startup or readiness probe, a crash-looping container, or an unreachable dependency the container’s health check verifies. It is retryable because readiness is often only delayed; if it persists, inspect the pod rather than the scheduler.

Troubleshooting Steps

1. Describe the pod for probe failures and events: kubectl describe pod -n
2. Check container logs, including the previous run: kubectl logs -n –previous
3. If the readiness probe checks a dependency (e.g. a mirror node or database), verify that dependency is healthy
4. Check PVC/PV binding and volume attach events: kubectl get pvc -n ; kubectl describe pvc -n
5. Review solo logs: tail -n 100 ~/.solo/logs/solo.log