SOLO-4064
BackupConfigMapKeyMissingSoloError — Validation
BackupConfigMapKeyMissingSoloError
| Code | SOLO-4064 |
| Category | Validation |
| Ownership | Infrastructure |
| Retryable | No |
Description
Thrown when the backup ConfigMap does not contain a required key; the message names the missing key. solo reads specific keys from the backup ConfigMap during restore, so this means the ConfigMap exists but is missing data it needs — indicating an incomplete or unexpected backup source.
Troubleshooting Steps
- Check solo logs: tail -n 100 ~/.solo/logs/solo.log
- Verify the Kubernetes ConfigMap contains the expected data
- Re-export the backup to regenerate the ConfigMap: solo config ops backup