SOLO-3008

BlockNodeConfigFailedSoloError

Description

Thrown when solo fails while building the block-nodes configuration; the underlying failure is wrapped in cause. solo generates the configuration that tells consensus nodes how to reach the block nodes, so this means that generation step failed — for example required connection details could not be resolved. It is retryable, since a transient resolution problem often clears on a later attempt.

Troubleshooting Steps

1. Check block node pod status: kubectl get pods -n -l block-node.hiero.com/type=block-node
2. Check network node pod status: kubectl get pods -n -l solo.hedera.com/type=network-node
3. Review solo logs: tail -n 100 ~/.solo/logs/solo.log
4. Verify the cluster is reachable: kubectl cluster-info –context