Closed
Description
Failure cluster 5442ad1006c2256556d9
Error text:
[FAILED] Error waiting for all pods to be running and ready: Timed out after 600.000s.
Expected all pods (need at least 0) in namespace "kube-system" to be running and ready (except for 0).
21 / 34 pods were running and ready.
Expected 9 pod replicas, 5 are Running and Ready.
Pods that were neither completed nor running:
<[]v1.Pod | len:13, cap:16>:
- metadata:
annotations:
cni.projectcalico.org/podIP: ""
cni.projectcalico.org/podIPs: ""
creationTimestamp: "2023-07-18T08:39:37Z"
generateName: coredns-55968cc89d-
labels:
k8s-app: kube-dns
pod-template-hash: 55968cc89d
managedFields:
Recent failures:
2023/7/20 04:35:04 ci-kubernetes-e2e-ubuntu-gce-network-policies
2023/7/19 22:35:07 ci-kubernetes-e2e-ubuntu-gce-network-policies
2023/7/19 16:35:04 ci-kubernetes-e2e-ubuntu-gce-network-policies
2023/7/19 10:35:02 ci-kubernetes-e2e-ubuntu-gce-network-policies
2023/7/19 04:34:03 ci-kubernetes-e2e-ubuntu-gce-network-policies
/kind failing-test
/sig node
see #119446.
There is a bug containerd/containerd#7836 in containerd that is fixed in v1.6.14. https://github.com/containerd/containerd/releases/tag/v1.6.14
The test here is using v1.6.12.
https://github.com/containerd/containerd/blob/main/RELEASES.md#kubernetes-supportKubernetes v1.27 supported containerd versions: 1.7.0+, 1.6.15+