-
Notifications
You must be signed in to change notification settings - Fork 667
Pods get stuck in ContainerCreating #2822
Comments
The last "connection refused" is:
and the weave-kube container starts right after that:
|
To clarify, the issue is that the pod sits in "ContainerCreating" state, and I cannot see anything in those logs to explain why. I'm going to edit the issue description as "node can't connect to 127.0.0.1:6784" is just a transient state before it all gets going |
After much investigating via Slack, the problem was traced here:
The "waiting for IP range grant from peers" status indicates that Weave Net's IPAM believes that all the IP address space is owned by other nodes in the cluster, but actually none of those nodes are able to be contacted at the moment. So the underlying cause is #2797 |
Thank you, Bryan, for all the assistance in tracking down this issue yesterday. Here's my workaround. Big red warnings:
|
Thanks, @rlnrln. Going to close this as a duplicate. |
Please help me , i am trying to use weave networking solution my k8 cluster. but i am getting below errors. vagrant@master-1: ============================ =============== kubelet.service - Kubernetes Kubelet Jan 10 04:35:53 worker-1 kubelet[17379]: E0110 04:35:53.787040 17379 pod_workers.go:190] Error syncing pod ed5aa617-713c-11ec-9aa3-0229e0c3be ==============================
vagrant@master-1:~$ kubectl describe pod weave-net-2vdr7 -n kube-system Normal Scheduled 17h default-scheduler Successfully assigned kube-system/weave-net-2vdr7 to worker-1 I dont understand what else to check . Anybody please help me. i want to set up k8 cluster i my laptop first so i will practise and will clear CKA exam. |
Kubernetes 1.5.2, created with Kops 1.5.0 alpha 4.
Complete logs from recently rebooted node.
kubelet logs
kube-weave logs
Scheduling deployment of prometheus:
The text was updated successfully, but these errors were encountered: