Lab3.4 step16, pod pending
after run step 16, the pod not running, it is pending
You guys could you help me to fix it?
student@master:~$ kubectl get deploy,pod
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/nginx 0/1 1 0 32m
NAME READY STATUS RESTARTS AGE
pod/nginx-d46f5678b-ttzhl 0/1 Pending 0 16m
pod/nginx-f89759699-t9qr9 0/1 Pending 0 32m
thanks
Comments
-
Hi @Jingze_Ma,
Running the following command may reveal why your pods are in a pending state:
kubectl describe pod <pending-pod-name>
At the bottom of the output you will see an
Events
section, that is where you may find those clues.Regards,
-Chris0 -
@chrispokorni said:
Hi @Jingze_Ma,Running the following command may reveal why your pods are in a pending state:
kubectl describe pod <pending-pod-name>
At the bottom of the output you will see an
Events
section, that is where you may find those clues.Regards,
-ChrisHi @chrispokorni ,
thanks for your reply, I tried run this command, in the Events section, I saw:
"
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 6s (x880 over 21h) default-scheduler 0/1 nodes are available: 1 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.
"
Could you please give me any advice what should I do?
thanksJingze
0 -
@Jingze_Ma said:
@chrispokorni said:
Hi @Jingze_Ma,Running the following command may reveal why your pods are in a pending state:
kubectl describe pod <pending-pod-name>
At the bottom of the output you will see an
Events
section, that is where you may find those clues.Regards,
-ChrisHi @chrispokorni ,
thanks for your reply, I tried run this command, in the Events section, I saw:
"
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 6s (x880 over 21h) default-scheduler 0/1 nodes are available: 1 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.
"
Could you please give me any advice what should I do?
thanksJingze
@chrispokorni ,
fixed, thanks0 -
I hope it's ok that I append my problem here as my initial problem is exactly the same.
student@master:~$ kubectl get deployments,pod NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/nginx 0/1 1 0 29m NAME READY STATUS RESTARTS AGE pod/nginx-f89759699-mbt5v 0/1 ContainerCreating 0 29m
This is an overview about all my pods:
student@master:~$ kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE default nginx-f89759699-kgvkc 0/1 ContainerCreating 0 4m37s kube-system calico-kube-controllers-7dbc97f587-w4pkt 1/1 Running 1 13h kube-system calico-node-5ts9j 0/1 Completed 1 3h7m kube-system calico-node-hj89f 0/1 Running 1 13h kube-system coredns-66bff467f8-j6xtn 1/1 Running 1 14h kube-system coredns-66bff467f8-lk65s 1/1 Running 1 14h kube-system etcd-master 1/1 Running 1 14h kube-system kube-apiserver-master 1/1 Running 1 14h kube-system kube-controller-manager-master 1/1 Running 1 14h kube-system kube-proxy-qt6bm 1/1 Running 1 14h kube-system kube-proxy-r6f77 0/1 Error 1 3h7m kube-system kube-scheduler-master 1/1 Running 1 14h
student@master:~$ kubectl get nodes NAME STATUS ROLES AGE VERSION master Ready master 15h v1.18.1 worker Ready <none> 4h1m v1.18.1
When I check for errors of my pod 'nginx-f89759699-mbt5v' I see the following events:
Warning FailedCreatePodSandBox 3m17s (x117 over 28m) kubelet, worker Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create a sandbox for pod "nginx-f89759699-mbt5v": Error response from daemon: cgroup-parent for systemd cgroup should be a valid slice named as "xxx.slice"
I'm not sure what the error message means. Can anyone help me with that?
(I followed the lab guide to set up the Kubernetes cluster. I'm on a GCE environment, running Ubuntu 18.04.)
0 -
Hi @ctschacher,
It seems that some of your control plane pods - the two
calico
pods and of of thekube-proxy
pods are not ready. You could runkubectl -n kube-system describe pod <pod-name>
for the twocalico
pods and thekube-proxy
pod, and from theEvents
section of each output you may be able to determine why they are not ready.Then you could attempt to
delete
the twocalico
pods and allow the controller to re-create them for you - this method would ideally start them back up and resolve any glitches or minor dependency issues.Regards,
-Chris1 -
Ok, it seems that the problem is solved. All pods have READY 1/1 now. Thank you for your help!
I learnt a lesson: just check the events for every faulty pod. It sounds so simple and still I had not yet fully embraced it.One Calico pod said:
Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal SandboxChanged 2m35s (x2185 over 7h55m) kubelet, worker Pod sandbox changed, it will be killed and re-created.
And that reminded me that I've played around with different start options for the Docker runtime on my worker node. After I changed it to the same settings as my Master node and a restart of the pod (deletion) on the Master node, it was finally working.
0
Categories
- All Categories
- 219 LFX Mentorship
- 219 LFX Mentorship: Linux Kernel
- 793 Linux Foundation IT Professional Programs
- 354 Cloud Engineer IT Professional Program
- 179 Advanced Cloud Engineer IT Professional Program
- 82 DevOps Engineer IT Professional Program
- 147 Cloud Native Developer IT Professional Program
- 137 Express Training Courses
- 137 Express Courses - Discussion Forum
- 6.2K Training Courses
- 47 LFC110 Class Forum - Discontinued
- 71 LFC131 Class Forum
- 42 LFD102 Class Forum
- 226 LFD103 Class Forum
- 19 LFD110 Class Forum
- 38 LFD121 Class Forum
- 18 LFD133 Class Forum
- 7 LFD134 Class Forum
- 18 LFD137 Class Forum
- 71 LFD201 Class Forum
- 5 LFD210 Class Forum
- 5 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 2 LFD233 Class Forum
- 4 LFD237 Class Forum
- 24 LFD254 Class Forum
- 697 LFD259 Class Forum
- 111 LFD272 Class Forum
- 4 LFD272-JP クラス フォーラム
- 12 LFD273 Class Forum
- 149 LFS101 Class Forum
- 1 LFS111 Class Forum
- 3 LFS112 Class Forum
- 2 LFS116 Class Forum
- 4 LFS118 Class Forum
- LFS120 Class Forum
- 7 LFS142 Class Forum
- 5 LFS144 Class Forum
- 4 LFS145 Class Forum
- 3 LFS146 Class Forum
- 3 LFS147 Class Forum
- 1 LFS148 Class Forum
- 15 LFS151 Class Forum
- 2 LFS157 Class Forum
- 30 LFS158 Class Forum
- 7 LFS162 Class Forum
- 2 LFS166 Class Forum
- 4 LFS167 Class Forum
- 3 LFS170 Class Forum
- 2 LFS171 Class Forum
- 3 LFS178 Class Forum
- 3 LFS180 Class Forum
- 2 LFS182 Class Forum
- 5 LFS183 Class Forum
- 32 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 3 LFS201-JP クラス フォーラム
- 18 LFS203 Class Forum
- 134 LFS207 Class Forum
- 2 LFS207-DE-Klassenforum
- 1 LFS207-JP クラス フォーラム
- 302 LFS211 Class Forum
- 56 LFS216 Class Forum
- 52 LFS241 Class Forum
- 48 LFS242 Class Forum
- 38 LFS243 Class Forum
- 15 LFS244 Class Forum
- 2 LFS245 Class Forum
- LFS246 Class Forum
- 49 LFS250 Class Forum
- 2 LFS250-JP クラス フォーラム
- 1 LFS251 Class Forum
- 153 LFS253 Class Forum
- 1 LFS254 Class Forum
- 1 LFS255 Class Forum
- 9 LFS256 Class Forum
- 1 LFS257 Class Forum
- 1.3K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 119 LFS260 Class Forum
- 159 LFS261 Class Forum
- 42 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 24 LFS267 Class Forum
- 23 LFS268 Class Forum
- 30 LFS269 Class Forum
- LFS270 Class Forum
- 202 LFS272 Class Forum
- 2 LFS272-JP クラス フォーラム
- 1 LFS274 Class Forum
- 4 LFS281 Class Forum
- 9 LFW111 Class Forum
- 259 LFW211 Class Forum
- 181 LFW212 Class Forum
- 13 SKF100 Class Forum
- 1 SKF200 Class Forum
- 1 SKF201 Class Forum
- 796 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 103 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 758 Linux Distributions
- 82 Debian
- 67 Fedora
- 17 Linux Mint
- 13 Mageia
- 23 openSUSE
- 148 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 353 Ubuntu
- 468 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 93 Linux Security
- 78 Network Management
- 102 System Management
- 47 Web Management
- 63 Mobile Computing
- 18 Android
- 33 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 371 Off Topic
- 114 Introductions
- 174 Small Talk
- 22 Study Material
- 805 Programming and Development
- 303 Kernel Development
- 484 Software Development
- 1.8K Software
- 263 Applications
- 183 Command Line
- 3 Compiling/Installing
- 987 Games
- 317 Installation
- 97 All In Program
- 97 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)