-
Notifications
You must be signed in to change notification settings - Fork 275
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
After restart of pods, one of the Canal pod is getting a Init:CreateContainerConfigError #4742
Comments
|
Seeing this Init:CreateContainerConfigError on reboot of the nodes without cluster-reset. Pods don't come back clean.
|
The |
Appears to be an issue with the CNI config; containerd log says:
It seems to be upset that |
Would like @manuelbuil and @rbrtbnfgl to take a look at this as it seems related to canal's calico somehow. I suspect that what's happening is that:
I am curious if dropping the kubeconfig somewhere other than that directory might fix that. Unfortunately it looks like it's hardcoded to that path, so changing that may be a dead-end; we probably need to figure out where the |
1.27 shows the same error in the containerd log so maybe it's a red herring?
|
OK those are all red herrings; I'm not seeing anything new on the containerd side because the kubelet isn't even attempting to restart it. Setting
This appears to be a change in behavior (bug perhaps) in the 1.28 kubelet. I do see that it has successfully listed services, but for some reason it's not retrying the pod setup.
|
Closing as upstream issue. |
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
Describe the bug:
Steps To Reproduce:
The text was updated successfully, but these errors were encountered: