-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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
Pod fail to start as /sys/fs/cgroup/devices/kubepods.slice/kubepods-burstable.slice doesn't exist #123459
Comments
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/sig node
this version is not in support |
@trashadewan, it is difficult to fix the issue without repro step. Can you provide any repro steps or logs? /triage needs-information |
@trashadewan Can you provide the repro steps? |
I wasn't able to reproduce the issue at all
Upgraded to 22.04 and since then didn't see the issue
Sent from Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Sivakajan Sivaparan ***@***.***>
Sent: Tuesday, March 12, 2024 2:02:56 AM
To: kubernetes/kubernetes ***@***.***>
Cc: Trasha Dewan ***@***.***>; Mention ***@***.***>
Subject: Re: [kubernetes/kubernetes] Pod fail to start as /sys/fs/cgroup/devices/kubepods.slice/kubepods-burstable.slice doesn't exist (Issue #123459)
@trashadewan<https://github.com/trashadewan> Can you provide the repro steps?
—
Reply to this email directly, view it on GitHub<#123459 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABYYS3FNPKJW7CWTXRMLKW3YX3AEBAVCNFSM6AAAAABDV4SIOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJRGA4DMNJYHE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
If there's no reproducer, and folks haven't caught it on newer versions, then I'm inclined to /close please reopen if you hit this on a supported k8s version |
@haircommander: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What happened?
Pod failed to start with the following issue:
Warning FailedCreatePodContainer 29m kubelet unable to ensure pod container exists: failed to create container for [kubepods burstable pod71ab4a03-d88b-4cbb-bd26-41c5b0ce3663] : Timeout waiting for systemd to create kubepods-burstable-pod71ab4a03_d88b_4cbb_bd26_41c5b0ce3663.slice
What did you expect to happen?
The pod to be successfully created and complete after running.
How can we reproduce it (as minimally and precisely as possible)?
I am unsure. once i reboot the node, the issue is resolved and the pods can start on it.
Anything else we need to know?
When i see logs from journalctl -u kubelet:
I see a lot of pods logs like below:
Kubernetes version
Cloud provider
OS version
The text was updated successfully, but these errors were encountered: