⚠️ Homebrew support is being deprecated.
Solo will stop publishing updates to Homebrew after August 31, 2026.
Install via
npm install -g @hiero-ledger/solo@latest instead.
See System Readiness for full install instructions.SOLO-5073
ClusterRoleCheckFailedSoloError — System
ClusterRoleCheckFailedSoloError
| Code | SOLO-5073 |
| Category | System |
| Ownership | Infrastructure |
| Retryable | No |
Description
Thrown when solo cannot check whether a Kubernetes ClusterRole exists; the message names the role and wraps the underlying failure in cause. solo queries for ClusterRoles before installing or relying on them, so this means the lookup failed — for example the Kubernetes API was unreachable or the current user lacks permission to read ClusterRoles.
Troubleshooting Steps
- Check solo logs: tail -n 100 ~/.solo/logs/solo.log
- Verify RBAC permissions: kubectl get clusterroles
- Inspect cluster state: kubectl get pods -A