question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

After upgrading to 21/stable all my pods fail to create

See original GitHub issue

Hi, I wanted to ask if anyone has tried to upgrade fron 19/stable to 21/stable and experienced the same issue, every single container faces the issue. (i for now downgraded to 20/stable and everything is working)

sofo@k8s-test-m:~$ kubectl get all --all-namespaces
NAMESPACE                  NAME                                                          READY   STATUS    RESTARTS   AGE
metallb-system             pod/speaker-qcj9x                                             0/1     Unknown   23         138d
kube-system                pod/calico-node-bs46g                                         0/1     Unknown   1          27d
metallb-system             pod/speaker-cn6nx                                             0/1     Unknown   29         160d
kube-system                pod/calico-node-62x6q                                         0/1     Unknown   1          27d
sofo@k8s-test-m:~$ kubectl -n metallb-system describe pod/speaker-qcj9x
Name:         speaker-qcj9x
Namespace:    metallb-system
Priority:     0
Node:         k8s-test-m/10.14.214.40
Start Time:   Sun, 13 Dec 2020 22:26:36 +0000
Labels:       app=metallb
              component=speaker
              controller-revision-hash=69f56bb877
              pod-template-generation=1
Annotations:  prometheus.io/port: 7472
              prometheus.io/scrape: true
Status:       Running
IP:           10.14.214.40
IPs:
  IP:           10.14.214.40
Controlled By:  DaemonSet/speaker
Containers:
  speaker:
    Container ID:  containerd://d56653f8ee10a407bd8383ebc2b0c9735a09bb6beba2ae9c49ec0500ce08a506
    Image:         metallb/speaker:v0.8.2
    Image ID:      docker.io/metallb/speaker@sha256:f1941498a28cdb332429e25d18233683da6949ecfc4f6dacf12b1416d7d38263
    Port:          7472/TCP
    Host Port:     7472/TCP
    Args:
      --port=7472
      --config=config
    State:          Terminated
      Reason:       Unknown
      Exit Code:    255
      Started:      Sun, 04 Apr 2021 03:45:28 +0000
      Finished:     Sat, 01 May 2021 20:46:47 +0000
    Ready:          False
    Restart Count:  23
    Limits:
      cpu:     100m
      memory:  100Mi
    Requests:
      cpu:     100m
      memory:  100Mi
    Environment:
      METALLB_NODE_NAME:   (v1:spec.nodeName)
      METALLB_HOST:        (v1:status.hostIP)
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from speaker-token-gwnsh (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  speaker-token-gwnsh:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  speaker-token-gwnsh
    Optional:    false
QoS Class:       Guaranteed
Node-Selectors:  beta.kubernetes.io/os=linux
Tolerations:     node-role.kubernetes.io/master:NoSchedule
                 node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                 node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                 node.kubernetes.io/network-unavailable:NoSchedule op=Exists
                 node.kubernetes.io/not-ready:NoExecute op=Exists
                 node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                 node.kubernetes.io/unreachable:NoExecute op=Exists
                 node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type     Reason                  Age                    From             Message
  ----     ------                  ----                   ----             -------
  Warning  NodeNotReady            27m                    node-controller  Node is not ready
  Warning  FailedCreatePodSandBox  22m (x4 over 24m)      kubelet          Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create containerd task: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:334: copying bootstrap data to pipe caused: write init-p: broken pipe: unknown
  Warning  FailedCreatePodSandBox  21m (x8 over 24m)      kubelet          Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create containerd task: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:338: getting the final child's pid from pipe caused: read init-p: connection reset by peer: unknown
  Normal   SandboxChanged          9m9s (x71 over 24m)    kubelet          Pod sandbox changed, it will be killed and re-created.
  Normal   SandboxChanged          2m22s (x9 over 3m52s)  kubelet          Pod sandbox changed, it will be killed and re-created.
  Warning  FailedCreatePodSandBox  2m22s (x9 over 3m51s)  kubelet          Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create containerd task: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:338: getting the final child's pid from pipe caused: read init-p: connection reset by peer: unknown
  Warning  FailedCreatePodSandBox  43s                    kubelet          Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create containerd task: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:334: copying bootstrap data to pipe caused: write init-p: broken pipe: unknown
  Normal   SandboxChanged          1s (x9 over 94s)       kubelet          Pod sandbox changed, it will be killed and re-created.
  Warning  FailedCreatePodSandBox  1s (x8 over 93s)       kubelet          Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create containerd task: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:338: getting the final child's pid from pipe caused: read init-p: connection reset by peer: unknown

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
ktsakalozoscommented, May 6, 2021

With the 1.21/stable channel should be updated with v1.21.1 release.

0reactions
Aaron-Rittercommented, Jul 11, 2021

@ktsakalozos do you have any news on the 1.21.1 release?

never mind, i did not see this: 1.21/stable: v1.21.1 2021-06-16 (2262) 191MB classic

Read more comments on GitHub >

github_iconTop Results From Across the Web

Configure Service Accounts for Pods - Kubernetes
You can only set the serviceAccountName field when creating a Pod, or in a template for a new Pod. You cannot update the...
Read more >
Troubleshooting installation and upgrade - IBM
Topology pods fail after a node or cluster restart. Symptom. Topology pods are not able to start up after an OpenShift node or...
Read more >
Learn why your EKS pod is stuck in the ContainerCreating state
My Amazon Elastic Kubernetes Service (Amazon EKS) pod is stuck in the ContainerCreating state with the error "failed to create pod sandbox".
Read more >
If your AirPods won't connect - Apple Support
To make sure that Bluetooth is on, choose Apple menu > System Settings, then click Bluetooth. If your AirPods are connected, make sure...
Read more >
How to Debug Kubernetes Pending Pods and Scheduling ...
Monitor kubernetes failed scheduling events pending pods in the datadog ... Kubernetes will create an event to mark when the node became ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found