SOLO-3089

NodeServiceNotFoundSoloError

Description

Thrown when solo cannot resolve the Kubernetes service for a specific consensus node; the message names the node alias. solo expects each node to expose a service it can reach, so this is raised when no matching service is found — typically because the node alias does not correspond to a deployed node, or the selected deployment or namespace does not contain it.

Troubleshooting Steps

1. Verify that node ‘’ exists in the deployment: solo deployment info
2. List all node services in the namespace: kubectl get svc -n
3. Check that the consensus node pod is running: kubectl get pods -n -l app=
4. Check solo logs for more context: tail -n 100 ~/.solo/logs/solo.log