SOLO-5013

PortForwardMissingSoloError

Description

Thrown when a configured port-forward is not present; the message names the component, its id, and the local-to-pod port mapping. solo expects each configured port-forward to be active so the component is reachable, so this means it is missing — for example it was never established or was dropped. It is retryable, since re-establishing the port-forward often succeeds.

Troubleshooting Steps

1. Check port-forward status: solo deployment diagnostics connections –deployment
2. Re-establish port forwards: solo consensus node start
3. Verify the pod is running: kubectl get pods -n