SOLO-5032

BlockNodeNotReadySoloError

Description

Thrown when a deployed block node does not become ready; the message names the release and wraps the underlying failure in cause. solo waits for the block node pods to reach a Ready state, so this means that wait did not succeed. It is retryable, since a block node that is merely slow to start often becomes ready on a later attempt; a persistent failure points to a crash-looping or misconfigured block node.

Troubleshooting Steps

1. Check block node pod status: kubectl get pods -A | grep
2. Describe pods for readiness probe failures: kubectl describe pods -A -l app.kubernetes.io/instance=
3. Check solo logs: tail -n 100 ~/.solo/logs/solo.log