Closed zeitler closed 6 days ago
This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.
This issue was closed because it became stale and did not receive further updates. If the issue is still affecting you, please re-open it, or file a fresh Issue with updated information.
What did you do to encounter the bug? Clean install and it simply dont start. Already installed in another cluster, never had issues
What did you expect? The statefulSet gets up and running
What happened instead? First member fails to start
Screenshots
Operator Information
Kubernetes Cluster Information
Additional context Looked in host
/var/log/*.log
and nothing relevant Used ctr utility and didn't found much, but also don't know that well how to explore it Asked for help in https://github.com/rancher/rke2/discussions/6102; Tried remove node from cluster and add it again, didn't work Forced installation in other nodes, didn't work Already installed operator with helm, and downloaded git repo installing it from there; didn't work Removed all crds, roles, etc; didn't workDeleted and installed again, operator logs:
And it keep going like this
No logs or exec into any container
Our first impression is that kubelet it's not being allowed to mount the emptyDir folders. Also stated by Brandond, rke2 maintainer. But I don't know where and how to look for it and fix it