SOLO-3062
GossipKeySecretCreationFailedSoloError — Component
GossipKeySecretCreationFailedSoloError
| Code | SOLO-3062 |
| Category | Component |
| Ownership | Infrastructure |
| Retryable | No |
Description
Thrown when solo cannot store a consensus node’s gossip keys as a Kubernetes secret; the message names the node alias. Gossip keys secure node-to-node communication and are mounted from a cluster secret, so this means that secret could not be created — for example the namespace is missing, a conflicting secret exists, or the Kubernetes API rejected the request.
Troubleshooting Steps
- Check solo logs: tail -n 100 ~/.solo/logs/solo.log
- Check existing secrets: kubectl get secrets -n
- Verify RBAC permissions allow secret creation in the namespace
- Re-run node setup: solo consensus node setup