SOLO-2017
ClusterResetFailedSoloError — Deployment
ClusterResetFailedSoloError
| Code | SOLO-2017 |
| Category | Deployment |
| Ownership | Infrastructure |
| Retryable | No |
Description
Thrown when solo cluster-ref config reset cannot tear down the cluster-level resources that setup installed (the solo-cluster-setup chart and its components); the underlying failure is wrapped in cause. It means the uninstall did not complete cleanly — for example a Helm release could not be removed, or the cluster API was unreachable mid-reset — so some resources may still be present. Inspect the remaining Helm releases and pods to see what was left behind.
Troubleshooting Steps
- Check solo logs: tail -n 100 ~/.solo/logs/solo.log
- Inspect cluster state: kubectl get pods -A
- Check Helm releases still present: helm list -A
- Re-run cluster reset: solo cluster-ref config reset