-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubelet restart: failed to initialize top level QOS containers: root container [kubepods] doesn't exist #7701
Comments
I forgot to attach the log.
Log of kubelet after starting by hand.
|
I seem to remember this has something to do with cgroupv2. I also wonder if it's an error coming from libcontainer. @kolyshkin does anything come to mind immediately? |
Another instance where this was observed while using cgroup v2 - kubernetes/kubernetes#122955 (comment) |
/assign |
I was able to observe this on latest openshift as well,
|
A friendly reminder that this issue had no activity for 30 days. |
https://github.com/openshift/machine-config-operator/pull/4217/files |
it does but it wasn't merged because I don't think we should delegate : openshift/machine-config-operator#4217 (comment) Basically: the problem is when kubelet creates the kubepods slice, it doesn't specify AllowedCPUs (which would enable the cpuset cgroup on the top-level), so systemd doesn't create it, and then the kubelet errors. though the fix won't be that simple I'm afraid. |
A friendly reminder that this issue had no activity for 30 days. |
What happened?
kubelet not autostart Power off the machine (cold).
What did you expect to happen?
Autostart kubelelt
How can we reproduce it (as minimally and precisely as possible)?
Debian 12.2 / 12.4
kernel - 6.1.0-17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linux
kubernetes v1.27.6 / v1.27.10 / v1.28.6
crio version 1.27.3 / 1.28.3
crun 1.9.2 / 1.13
Anything else we need to know?
I was unable to replicate the behavior on centos similar operating system and centos 8.x
When looking for information on the error was found:
https://github.innominds.com/kubernetes/kubernetes/issues/122681
#4035
k3s-io/k3s#6318
CRI-O and Kubernetes version
OS version
Additional environment details (AWS, VirtualBox, physical, etc.)
The text was updated successfully, but these errors were encountered: