I have 3 nodes. Previously when one node was down, the other two were ready.But when I deploy a pod, they were not scheduled to any of the node. I am even unable to find the kubeletlog too on the node.
On Friday, May 20, 2016 at 4:05:07 PM UTC-7, Daniel Smith wrote: > > > ... "type":"Ready","status":"Unknown", ... > > NAME STATUS AGE > > 10.241.1.36 NotReady 13d > > Your node is actually not ready, it's not phoning home and node-controller > marked it as unknown, which means pods won't be scheduled to it. > > I cannot tell the status of your other nodes from the data you provide. I > also can't tell if there's space on them for another pod. All I can say is > that nothing will be scheduled to the node for which you give info. You can > probably look in its /var/log/kubelet.log to see why it can't phone home. > > Stackoverflow may be a better forum for this sort of question. > > On Fri, May 20, 2016 at 12:27 PM, shri devops <[email protected] > <javascript:>> wrote: > >> I was trying to deploy pods in my Kubernetes environment. I have 1 Master >> and 3 Minions. Two other minions status are active and one minion is not >> ready. When I create pods, the pod status is pending. When look into >> describing the pod, there is no IP on which minion it is created and the >> reason says "failed scheduling no nodes available to schedule pods". >> >> Here I am using chef recipe to create a pod. I have not created any >> replication controllers. >> >> Please help me with it. I have posted my logs of that particular node >> >> [root@infckubmtrd01 ~]# kubectl --v=10 get node 10.241.1.36 >> I0520 12:12:50.976495 23094 round_trippers.go:267] curl -k -v -XGET -H >> "Accept: application/json, */*" -H "User-Agent: kubectl/v1.2.0 >> (linux/amd64) kubernetes/738b760" http://localhost:8080/api >> I0520 12:12:50.980308 23094 round_trippers.go:286] GET >> http://localhost:8080/api 200 OK in 3 milliseconds >> I0520 12:12:50.980323 23094 round_trippers.go:292] Response Headers: >> I0520 12:12:50.980334 23094 round_trippers.go:295] Content-Length: >> 32 >> I0520 12:12:50.980341 23094 round_trippers.go:295] Content-Type: >> application/json >> I0520 12:12:50.980346 23094 round_trippers.go:295] Date: Fri, 20 >> May 2016 19:12:50 GMT >> I0520 12:12:50.980395 23094 request.go:870] Response Body: { >> "versions": [ >> "v1" >> ] >> } >> I0520 12:12:50.980868 23094 round_trippers.go:267] curl -k -v -XGET -H >> "Accept: application/json, */*" -H "User-Agent: kubectl/v1.2.0 >> (linux/amd64) kubernetes/738b760" http://localhost:8080/apis >> I0520 12:12:50.981162 23094 round_trippers.go:286] GET >> http://localhost:8080/apis 200 OK in 0 milliseconds >> I0520 12:12:50.981184 23094 round_trippers.go:292] Response Headers: >> I0520 12:12:50.981190 23094 round_trippers.go:295] Content-Type: >> application/json >> I0520 12:12:50.981195 23094 round_trippers.go:295] Date: Fri, 20 >> May 2016 19:12:50 GMT >> I0520 12:12:50.981200 23094 round_trippers.go:295] Content-Length: >> 18 >> I0520 12:12:50.981217 23094 request.go:870] Response Body: { >> "groups": [] >> } >> I0520 12:12:50.981563 23094 round_trippers.go:267] curl -k -v -XGET -H >> "Accept: application/json, */*" -H "User-Agent: kubectl/v1.2.0 >> (linux/amd64) kubernetes/738b760" >> http://localhost:8080/api/v1/nodes/10.241.1.36 >> I0520 12:12:50.983398 23094 round_trippers.go:286] GET >> http://localhost:8080/api/v1/nodes/10.241.1.36 200 OK in 1 milliseconds >> I0520 12:12:50.983412 23094 round_trippers.go:292] Response Headers: >> I0520 12:12:50.983417 23094 round_trippers.go:295] Content-Type: >> application/json >> I0520 12:12:50.983423 23094 round_trippers.go:295] Date: Fri, 20 >> May 2016 19:12:50 GMT >> I0520 12:12:50.983428 23094 round_trippers.go:295] Content-Length: >> 1088 >> I0520 12:12:50.983463 23094 request.go:870] Response Body: >> {"kind":"Node","apiVersion":"v1","metadata":{"name":"10.241.1.36","selfLink":"/api/v1/nodes/ >> 10.241.1.36 >> ","uid":"1cb818e0-13c9-11e6-abcd-42010af10121","resourceVersion":"477002","creationTimestamp":"2016-05-06T20:28:37Z","labels":{" >> kubernetes.io/hostname":"10.241.1.36"}},"spec":{"externalID":"10.241.1.36"},"status":{"capacity":{"cpu":"1","memory":"3789388Ki","pods":"40"},"conditions":[{"type":"Ready","status":"Unknown","lastHeartbeatTime":"2016-05-20T07:29:43Z","lastTransitionTime":"2016-05-20T07:30:24Z","reason":"NodeStatusUnknown","message":"Kubelet >> >> stopped posting node >> status."}],"addresses":[{"type":"LegacyHostIP","address":"10.241.1.36"},{"type":"InternalIP","address":"10.241.1.36"}],"daemonEndpoints":{"kubeletEndpoint":{"Port":10250}},"nodeInfo":{"machineID":"c4f107c86c4d9771e87b30e2645799cd","systemUUID":"B77DAB52-2FFA-573C-E4E8-C45A44923D50","bootID":"5e0bcb61-1611-4941-823a-bf51532823bb","kernelVersion":"3.10.0-327.13.1.el7.x86_64","osImage":"CentOS >> >> Linux 7 >> (Core)","containerRuntimeVersion":"docker://1.9.1","kubeletVersion":"v1.2.0","kubeProxyVersion":"v1.2.0"}}} >> NAME STATUS AGE >> 10.241.1.36 NotReady 13d >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Containers at Google" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/google-containers. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
