SOLO-3091

GossipKeySecretRestoreFailedSoloError

Description

Thrown when solo cannot restore a consensus node’s gossip keys from its Kubernetes secret back to the local keys directory; the message names the node alias. When --debug is off the on-disk gossip keys are deleted after they are uploaded to the cluster, so later commands re-fetch them from the secret — this means that secret could not be read or did not contain the expected key files (for example the namespace or secret is missing, or the Kubernetes API rejected the request).

Troubleshooting Steps

1. Check solo logs: tail -n 100 ~/.solo/logs/solo.log
2. Confirm the gossip key secret exists: kubectl get secret network--keys-secrets -n
3. Verify RBAC permissions allow reading secrets in the namespace