SOLO-3011

NodeNotReadySoloError

Description

Thrown when a consensus node does not reach the expected status within the allotted polling attempts; the message names the node alias, the expected status, and the attempt count (attempt/maxAttempts). solo polls node status while waiting for nodes to come up or change state, and raises this once the attempts are exhausted without the node reaching the expected status — for example the node is crash-looping, stuck during startup, or unable to join the network.

Troubleshooting Steps

1. Check node pod status: kubectl get pods -n -l solo.hedera.com/node-name=
2. View node logs: kubectl logs -n -l solo.hedera.com/node-name=
3. Review solo logs: tail -n 100 ~/.solo/logs/solo.log