ci-cri-containerd-e2e-cos-gce-reboot #1619938049183977472
Recent runs || View in Spyglass
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sdropping\sall\sinbound\spackets\sfor\sa\swhile\sand\sensure\sthey\sfunction\safterwards$'
[FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 06:12:33.422from ginkgo_report.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:10:14.025 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:10:14.025 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:10:14.025 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 06:10:14.025 Jan 30 06:10:14.025: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 06:10:14.026 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/30/23 06:10:14.155 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/30/23 06:10:14.238 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:10:14.318 (294ms) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 06:10:14.318 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 06:10:14.319 (0s) > Enter [It] each node by dropping all inbound packets for a while and ensure they function afterwards - test/e2e/cloud/gcp/reboot.go:136 @ 01/30/23 06:10:14.319 Jan 30 06:10:14.412: INFO: Getting bootstrap-e2e-minion-group-j5pg Jan 30 06:10:14.412: INFO: Getting bootstrap-e2e-minion-group-89rb Jan 30 06:10:14.412: INFO: Getting bootstrap-e2e-minion-group-jt1b Jan 30 06:10:14.456: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-89rb condition Ready to be true Jan 30 06:10:14.456: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-j5pg condition Ready to be true Jan 30 06:10:14.456: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-jt1b condition Ready to be true Jan 30 06:10:14.499: INFO: Node bootstrap-e2e-minion-group-jt1b has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:10:14.500: INFO: Node bootstrap-e2e-minion-group-j5pg has 4 assigned pods with no liveness probes: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-zckpq" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-bg4vb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-srxc6" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-jt1b" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Node bootstrap-e2e-minion-group-89rb has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-4glfd" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-89rb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.546: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 46.887351ms Jan 30 06:10:14.546: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.548: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb": Phase="Running", Reason="", readiness=true. Elapsed: 48.266927ms Jan 30 06:10:14.548: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.548: INFO: Pod "metadata-proxy-v0.1-zckpq": Phase="Running", Reason="", readiness=true. Elapsed: 48.644019ms Jan 30 06:10:14.548: INFO: Pod "metadata-proxy-v0.1-zckpq" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.548: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb": Phase="Running", Reason="", readiness=true. Elapsed: 48.246832ms Jan 30 06:10:14.548: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.548: INFO: Pod "metadata-proxy-v0.1-4glfd": Phase="Running", Reason="", readiness=true. Elapsed: 48.395319ms Jan 30 06:10:14.548: INFO: Pod "metadata-proxy-v0.1-4glfd" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.548: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:10:14.548: INFO: Getting external IP address for bootstrap-e2e-minion-group-89rb Jan 30 06:10:14.548: INFO: SSH "\n\t\tnohup sh -c '\n\t\t\tset -x\n\t\t\tsleep 10\n\t\t\twhile true; do sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT && break; done\n\t\t\twhile true; do sudo iptables -I INPUT 2 -j DROP && break; done\n\t\t\tdate\n\t\t\tsleep 120\n\t\t\twhile true; do sudo iptables -D INPUT -j DROP && break; done\n\t\t\twhile true; do sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT && break; done\n\t\t' >/tmp/drop-inbound.log 2>&1 &\n\t\t" on bootstrap-e2e-minion-group-89rb(34.168.49.142:22) Jan 30 06:10:14.549: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=true. Elapsed: 48.991799ms Jan 30 06:10:14.549: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.549: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:10:14.549: INFO: Getting external IP address for bootstrap-e2e-minion-group-jt1b Jan 30 06:10:14.549: INFO: SSH "\n\t\tnohup sh -c '\n\t\t\tset -x\n\t\t\tsleep 10\n\t\t\twhile true; do sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT && break; done\n\t\t\twhile true; do sudo iptables -I INPUT 2 -j DROP && break; done\n\t\t\tdate\n\t\t\tsleep 120\n\t\t\twhile true; do sudo iptables -D INPUT -j DROP && break; done\n\t\t\twhile true; do sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT && break; done\n\t\t' >/tmp/drop-inbound.log 2>&1 &\n\t\t" on bootstrap-e2e-minion-group-jt1b(34.83.145.21:22) Jan 30 06:10:14.549: INFO: Pod "metadata-proxy-v0.1-srxc6": Phase="Running", Reason="", readiness=true. Elapsed: 49.32294ms Jan 30 06:10:14.549: INFO: Pod "metadata-proxy-v0.1-srxc6" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.549: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg": Phase="Running", Reason="", readiness=true. Elapsed: 49.415697ms Jan 30 06:10:14.549: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.549: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: true. Pods: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:10:14.549: INFO: Getting external IP address for bootstrap-e2e-minion-group-j5pg Jan 30 06:10:14.549: INFO: SSH "\n\t\tnohup sh -c '\n\t\t\tset -x\n\t\t\tsleep 10\n\t\t\twhile true; do sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT && break; done\n\t\t\twhile true; do sudo iptables -I INPUT 2 -j DROP && break; done\n\t\t\tdate\n\t\t\tsleep 120\n\t\t\twhile true; do sudo iptables -D INPUT -j DROP && break; done\n\t\t\twhile true; do sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT && break; done\n\t\t' >/tmp/drop-inbound.log 2>&1 &\n\t\t" on bootstrap-e2e-minion-group-j5pg(34.82.243.144:22) Jan 30 06:10:15.067: INFO: ssh prow@34.83.145.21:22: command: nohup sh -c ' set -x sleep 10 while true; do sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT && break; done while true; do sudo iptables -I INPUT 2 -j DROP && break; done date sleep 120 while true; do sudo iptables -D INPUT -j DROP && break; done while true; do sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT && break; done ' >/tmp/drop-inbound.log 2>&1 & Jan 30 06:10:15.067: INFO: ssh prow@34.83.145.21:22: stdout: "" Jan 30 06:10:15.067: INFO: ssh prow@34.83.145.21:22: stderr: "" Jan 30 06:10:15.067: INFO: ssh prow@34.83.145.21:22: exit code: 0 Jan 30 06:10:15.067: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-jt1b condition Ready to be false Jan 30 06:10:15.072: INFO: ssh prow@34.168.49.142:22: command: nohup sh -c ' set -x sleep 10 while true; do sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT && break; done while true; do sudo iptables -I INPUT 2 -j DROP && break; done date sleep 120 while true; do sudo iptables -D INPUT -j DROP && break; done while true; do sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT && break; done ' >/tmp/drop-inbound.log 2>&1 & Jan 30 06:10:15.072: INFO: ssh prow@34.168.49.142:22: stdout: "" Jan 30 06:10:15.072: INFO: ssh prow@34.168.49.142:22: stderr: "" Jan 30 06:10:15.072: INFO: ssh prow@34.168.49.142:22: exit code: 0 Jan 30 06:10:15.072: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-89rb condition Ready to be false Jan 30 06:10:15.072: INFO: ssh prow@34.82.243.144:22: command: nohup sh -c ' set -x sleep 10 while true; do sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT && break; done while true; do sudo iptables -I INPUT 2 -j DROP && break; done date sleep 120 while true; do sudo iptables -D INPUT -j DROP && break; done while true; do sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT && break; done ' >/tmp/drop-inbound.log 2>&1 & Jan 30 06:10:15.072: INFO: ssh prow@34.82.243.144:22: stdout: "" Jan 30 06:10:15.072: INFO: ssh prow@34.82.243.144:22: stderr: "" Jan 30 06:10:15.072: INFO: ssh prow@34.82.243.144:22: exit code: 0 Jan 30 06:10:15.072: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-j5pg condition Ready to be false Jan 30 06:10:15.110: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:15.114: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:15.114: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:17.162: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:17.164: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:17.164: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:19.209: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:19.209: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:19.209: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:21.254: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:21.254: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:21.254: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:23.300: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:23.300: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:23.300: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:25.345: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:25.345: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:25.345: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:27.385: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:27.385: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:27.385: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:29.425: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:29.425: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:29.426: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:31.465: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:31.465: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:31.465: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:33.505: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:33.505: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:33.505: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:35.546: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:35.546: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:35.546: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:37.586: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:37.586: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:37.586: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:39.626: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:39.626: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:39.626: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:41.666: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:41.666: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:41.666: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:43.707: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:43.707: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:43.707: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:45.748: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:45.748: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:45.748: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:47.788: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:47.788: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:47.788: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:49.828: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:49.828: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:49.828: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:51.869: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:51.869: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:51.869: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:53.909: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:53.909: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:53.909: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:55.950: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:55.950: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:55.950: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:57.990: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:57.990: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:57.990: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:11:02.803: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:02.803: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:02.803: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:04.850: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:04.850: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:04.850: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:06.897: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:06.897: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:06.898: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:08.943: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:08.946: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:08.946: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:10.985: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:10.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:10.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:13.028: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:13.034: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:13.034: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:15.072: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:15.078: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:15.078: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:17.116: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:17.125: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:17.125: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:19.158: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:19.167: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:19.169: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:21.202: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:21.211: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:21.212: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:23.346: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:23.346: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:23.346: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:25.392: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:25.393: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:25.393: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:27.447: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:27.447: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:27.447: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:29.493: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:29.493: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:29.493: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:31.541: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:31.541: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:31.541: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:33.588: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:33.588: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:33.588: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:35.635: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:35.635: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:35.635: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:37.681: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:37.681: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:37.681: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:39.729: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:39.729: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:39.729: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:41.777: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:41.777: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:41.777: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:43.822: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:43.823: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:43.826: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:45.865: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:45.865: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:45.868: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:47.907: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:47.910: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:47.911: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:49.951: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:49.955: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:49.955: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:51.995: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:51.999: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:51.999: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:54.038: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:54.044: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:54.044: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:56.080: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:56.089: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:56.089: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:58.124: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:58.134: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:58.134: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:00.168: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:00.178: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:00.178: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:02.212: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:02.224: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:02.224: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:04.260: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:04.275: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:04.275: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:06.303: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:06.318: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:06.318: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:08.345: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:08.363: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:08.363: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:10.389: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:10.407: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:10.407: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:12.439: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:12.453: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:12.453: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:14.482: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:14.498: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:14.498: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:16.482: INFO: Node bootstrap-e2e-minion-group-j5pg didn't reach desired Ready condition status (false) within 2m0s Jan 30 06:12:16.499: INFO: Node bootstrap-e2e-minion-group-jt1b didn't reach desired Ready condition status (false) within 2m0s Jan 30 06:12:16.499: INFO: Node bootstrap-e2e-minion-group-89rb didn't reach desired Ready condition status (false) within 2m0s Jan 30 06:12:16.499: INFO: Node bootstrap-e2e-minion-group-89rb failed reboot test. Jan 30 06:12:16.499: INFO: Node bootstrap-e2e-minion-group-j5pg failed reboot test. Jan 30 06:12:16.499: INFO: Node bootstrap-e2e-minion-group-jt1b failed reboot test. Jan 30 06:12:16.499: INFO: Executing termination hook on nodes Jan 30 06:12:16.499: INFO: Getting external IP address for bootstrap-e2e-minion-group-89rb Jan 30 06:12:16.499: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-89rb(34.168.49.142:22) Jan 30 06:12:32.370: INFO: ssh prow@34.168.49.142:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 30 06:12:32.370: INFO: ssh prow@34.168.49.142:22: stdout: "+ sleep 10\n+ true\n+ sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT\n+ break\n+ true\n+ sudo iptables -I INPUT 2 -j DROP\n+ break\n+ date\nMon Jan 30 06:10:25 UTC 2023\n+ sleep 120\n+ true\n+ sudo iptables -D INPUT -j DROP\n+ break\n+ true\n+ sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT\n+ break\n" Jan 30 06:12:32.370: INFO: ssh prow@34.168.49.142:22: stderr: "" Jan 30 06:12:32.370: INFO: ssh prow@34.168.49.142:22: exit code: 0 Jan 30 06:12:32.370: INFO: Getting external IP address for bootstrap-e2e-minion-group-j5pg Jan 30 06:12:32.370: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-j5pg(34.82.243.144:22) Jan 30 06:12:32.899: INFO: ssh prow@34.82.243.144:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 30 06:12:32.899: INFO: ssh prow@34.82.243.144:22: stdout: "+ sleep 10\n+ true\n+ sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT\n+ break\n+ true\n+ sudo iptables -I INPUT 2 -j DROP\n+ break\n+ date\nMon Jan 30 06:10:25 UTC 2023\n+ sleep 120\n+ true\n+ sudo iptables -D INPUT -j DROP\n+ break\n+ true\n+ sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT\n+ break\n" Jan 30 06:12:32.899: INFO: ssh prow@34.82.243.144:22: stderr: "" Jan 30 06:12:32.899: INFO: ssh prow@34.82.243.144:22: exit code: 0 Jan 30 06:12:32.899: INFO: Getting external IP address for bootstrap-e2e-minion-group-jt1b Jan 30 06:12:32.899: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-jt1b(34.83.145.21:22) Jan 30 06:12:33.421: INFO: ssh prow@34.83.145.21:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 30 06:12:33.421: INFO: ssh prow@34.83.145.21:22: stdout: "+ sleep 10\n+ true\n+ sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT\n+ break\n+ true\n+ sudo iptables -I INPUT 2 -j DROP\n+ break\n+ date\nMon Jan 30 06:10:25 UTC 2023\n+ sleep 120\n+ true\n+ sudo iptables -D INPUT -j DROP\n+ break\n+ true\n+ sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT\n+ break\n" Jan 30 06:12:33.421: INFO: ssh prow@34.83.145.21:22: stderr: "" Jan 30 06:12:33.421: INFO: ssh prow@34.83.145.21:22: exit code: 0 [FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 06:12:33.422 < Exit [It] each node by dropping all inbound packets for a while and ensure they function afterwards - test/e2e/cloud/gcp/reboot.go:136 @ 01/30/23 06:12:33.422 (2m19.103s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:12:33.422 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 06:12:33.422 Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-27hpv to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} FailedMount: MountVolume.SetUp failed for volume "config-volume" : failed to sync configmap cache: timed out waiting for the condition Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 2.636021002s (2.636034032s including waiting) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container coredns Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container coredns Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container coredns Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: Get "http://10.64.3.7:8181/ready": dial tcp 10.64.3.7:8181: connect: connection refused Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: Get "http://10.64.3.12:8181/ready": dial tcp 10.64.3.12:8181: connect: connection refused Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-27hpv_kube-system(d5696a97-0c32-4875-8ac5-fdb1ce1816da) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: Get "http://10.64.3.14:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.14:8080/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-vtndh to bootstrap-e2e-minion-group-jt1b Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 1.034366695s (1.034389733s including waiting) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container coredns Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container coredns Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Stopping container coredns Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.3:8181/ready": dial tcp 10.64.2.3:8181: connect: connection refused Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.5:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-vtndh_kube-system(9c9e7a94-38c6-4663-8f82-43b74a199e59) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.6:8181/ready": dial tcp 10.64.2.6:8181: i/o timeout (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.6:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f: {replicaset-controller } FailedCreate: Error creating: insufficient quota to match these scopes: [{PriorityClass In [system-node-critical system-cluster-critical]}] Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-27hpv Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-vtndh Jan 30 06:12:33.470: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 1 Jan 30 06:12:33.470: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 2 from 1 Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container etcd-container Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container etcd-container Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container etcd-container Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe errored: rpc error: code = Unknown desc = failed to exec in container: container is in CONTAINER_EXITED state Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/etcd:3.5.7-0" already present on machine Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container etcd-container in pod etcd-server-bootstrap-e2e-master_kube-system(2ef2f0d9ccfe01aa3c1d26059de8a300) Jan 30 06:12:33.470: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_2e2da became leader Jan 30 06:12:33.470: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_7c8d0 became leader Jan 30 06:12:33.470: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_1ffa4 became leader Jan 30 06:12:33.470: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_b9c2e became leader Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-lsjtz to bootstrap-e2e-minion-group-jt1b Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 664.348201ms (664.364985ms including waiting) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Stopping container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Liveness probe failed: Get "http://10.64.2.4:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-sv2mg to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 2.45385434s (2.453864342s including waiting) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.5:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.19:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-vpdtl to bootstrap-e2e-minion-group-89rb Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 657.450417ms (657.460286ms including waiting) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Liveness probe failed: Get "http://10.64.1.5:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Failed: Error: failed to get sandbox container task: no running task found: task 38160c3af9302d8f890a71a78eed322e52a69e59da84d5a3ca773407ab029cd1 not found: not found Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-vpdtl_kube-system(73c6f815-a15e-4e7a-a972-20e282f676c0) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-sv2mg Jan 30 06:12:33.470: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-vpdtl Jan 30 06:12:33.470: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-lsjtz Jan 30 06:12:33.470: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-addon-manager Jan 30 06:12:33.470: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-addon-manager Jan 30 06:12:33.470: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-addon-manager Jan 30 06:12:33.470: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/addon-manager/kube-addon-manager:v9.1.6" already present on machine Jan 30 06:12:33.470: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 06:12:33.470: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-apiserver Jan 30 06:12:33.470: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Readiness probe failed: Get "https://127.0.0.1:443/readyz": dial tcp 127.0.0.1:443: connect: connection refused Jan 30 06:12:33.470: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/kube-controller-manager-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:12:33.470: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-controller-manager Jan 30 06:12:33.470: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-controller-manager Jan 30 06:12:33.470: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-controller-manager Jan 30 06:12:33.470: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container kube-controller-manager in pod kube-controller-manager-bootstrap-e2e-master_kube-system(4fc5a5aeac3c203e3876adb08d878c93) Jan 30 06:12:33.470: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_c4dee0f1-ebbd-431b-a4f5-cdaba3338ff1 became leader Jan 30 06:12:33.470: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_6a930d5c-d857-45d7-8821-ab6144cfb617 became leader Jan 30 06:12:33.470: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_52b92c73-5b92-4994-9104-bec143d48796 became leader Jan 30 06:12:33.470: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_24f84219-2bae-4a66-bead-e8bbaf2fb7a6 became leader Jan 30 06:12:33.470: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_24c1fd47-ae61-4e44-8476-8212cb452f58 became leader Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-dns-autoscaler-5f6455f985-bg4vb to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" in 2.01573763s (2.015748792s including waiting) Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container autoscaler Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container autoscaler Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container autoscaler Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" already present on machine Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container autoscaler in pod kube-dns-autoscaler-5f6455f985-bg4vb_kube-system(d17909b1-64e2-475c-a08b-b40ba36f6afa) Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985: {replicaset-controller } FailedCreate: Error creating: pods "kube-dns-autoscaler-5f6455f985-" is forbidden: error looking up service account kube-system/kube-dns-autoscaler: serviceaccount "kube-dns-autoscaler" not found Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985: {replicaset-controller } SuccessfulCreate: Created pod: kube-dns-autoscaler-5f6455f985-bg4vb Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler: {deployment-controller } ScalingReplicaSet: Scaled up replica set kube-dns-autoscaler-5f6455f985 to 1 Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-89rb_kube-system(a86edc08c98ce4fefed543ad485600a4) Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-j5pg_kube-system(adff6fb483f7c9e3d86fb4cb79733a2e) Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Stopping container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-jt1b_kube-system(87a78f5a508a69cfa60729c5d4dc7da6) Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/kube-scheduler-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-scheduler Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-scheduler Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container kube-scheduler in pod kube-scheduler-bootstrap-e2e-master_kube-system(5b3c0a3dad3d723f9e5778ab0a62849c) Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-scheduler Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe failed: Get "https://127.0.0.1:10259/healthz": dial tcp 127.0.0.1:10259: connect: connection refused Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_18ee2297-5499-4a10-b782-8bf60ef964f2 became leader Jan 30 06:12:33.470: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_959dc035-06e0-4f47-9fbb-6328d3119de5 became leader Jan 30 06:12:33.470: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_36535314-0b8e-4eff-a7de-1c139a5f4105 became leader Jan 30 06:12:33.470: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_8d92bf3b-8542-4829-90e1-576b213e261b became leader Jan 30 06:12:33.470: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_95bd1561-0f4e-420f-8860-23de9b4e3cb0 became leader Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {default-scheduler } Scheduled: Successfully assigned kube-system/l7-default-backend-8549d69d99-slz4q to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" in 2.282907597s (2.282919912s including waiting) Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container default-http-backend Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container default-http-backend Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.4:8080/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Container default-http-backend failed liveness probe, will be restarted Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99: {replicaset-controller } SuccessfulCreate: Created pod: l7-default-backend-8549d69d99-slz4q Jan 30 06:12:33.470: INFO: event for l7-default-backend: {deployment-controller } ScalingReplicaSet: Scaled up replica set l7-default-backend-8549d69d99 to 1 Jan 30 06:12:33.470: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container l7-lb-controller Jan 30 06:12:33.470: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container l7-lb-controller Jan 30 06:12:33.470: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "gcr.io/k8s-ingress-image-push/ingress-gce-glbc-amd64:v1.20.1" already present on machine Jan 30 06:12:33.470: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container l7-lb-controller in pod l7-lb-controller-bootstrap-e2e-master_kube-system(f922c87738da4b787ed79e8be7ae0573) Jan 30 06:12:33.470: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe failed: Get "http://10.138.0.2:8086/healthz": dial tcp 10.138.0.2:8086: connect: connection refused Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-4glfd to bootstrap-e2e-minion-group-89rb Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 743.096978ms (743.138916ms including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.911633038s (1.911644632s including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-4rnk7 to bootstrap-e2e-master Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 751.7056ms (751.711494ms including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Failed: Error: services have not yet been read at least once, cannot construct envvars Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.335358551s (2.33536641s including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Created: Created container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Started: Started container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Created: Created container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Started: Started container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-srxc6 to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 804.763467ms (804.774083ms including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.089844613s (2.089864707s including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-zckpq to bootstrap-e2e-minion-group-jt1b Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 842.219895ms (842.229354ms including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.054812451s (2.054822588s including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-4rnk7 Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-4glfd Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-zckpq Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-srxc6 Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-6764bf875c-vbxz7 to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} FailedMount: MountVolume.SetUp failed for volume "metrics-server-config-volume" : failed to sync configmap cache: timed out waiting for the condition Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 3.531930568s (3.532067103s including waiting) Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container metrics-server Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container metrics-server Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 1.812865403s (1.812874646s including waiting) Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container metrics-server-nanny Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container metrics-server-nanny Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container metrics-server Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container metrics-server-nanny Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-6764bf875c-vbxz7 Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulDelete: Deleted pod: metrics-server-v0.5.2-6764bf875c-vbxz7 Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-867b8754b9-s79bn to bootstrap-e2e-minion-group-89rb Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 1.367491088s (1.367525697s including waiting) Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container metrics-server Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container metrics-server Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 1.035914064s (1.035929902s including waiting) Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container metrics-server-nanny Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container metrics-server-nanny Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Readiness probe failed: Get "https://10.64.1.3:10250/readyz": dial tcp 10.64.1.3:10250: connect: connection refused Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Liveness probe failed: Get "https://10.64.1.3:10250/livez": dial tcp 10.64.1.3:10250: connect: connection refused Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Liveness probe failed: Get "https://10.64.1.3:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Readiness probe failed: Get "https://10.64.1.3:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container metrics-server Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container metrics-server-nanny Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Readiness probe failed: Get "https://10.64.1.4:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-867b8754b9-s79bn Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-v0.5.2-6764bf875c to 1 Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-v0.5.2-867b8754b9 to 1 Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled down replica set metrics-server-v0.5.2-6764bf875c to 0 from 1 Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {default-scheduler } Scheduled: Successfully assigned kube-system/volume-snapshot-controller-0 to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" in 1.683320982s (1.68333161s including waiting) Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container volume-snapshot-controller Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container volume-snapshot-controller Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container volume-snapshot-controller Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(694587fc-d43c-43bc-bbab-563d942a4f03) Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller: {statefulset-controller } SuccessfulCreate: create Pod volume-snapshot-controller-0 in StatefulSet volume-snapshot-controller successful < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:12:33.471 (49ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:12:33.471 Jan 30 06:12:33.471: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:12:33.532 (61ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 06:12:33.532 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 06:12:33.532 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:12:33.532 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:12:33.532 STEP: Collecting events from namespace "reboot-2856". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 06:12:33.532 STEP: Found 0 events. - test/e2e/framework/debug/dump.go:46 @ 01/30/23 06:12:33.573 Jan 30 06:12:33.615: INFO: POD NODE PHASE GRACE CONDITIONS Jan 30 06:12:33.615: INFO: Jan 30 06:12:33.663: INFO: Logging node info for node bootstrap-e2e-master Jan 30 06:12:33.707: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-master da42dd0c-bb3c-402f-847c-793de73fb287 1204 0 2023-01-30 06:04:10 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-1 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-master kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-1 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:10 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{},"f:unschedulable":{}}} } {kube-controller-manager Update v1 2023-01-30 06:04:27 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.0.0/24\"":{}},"f:taints":{}}} } {kube-controller-manager Update v1 2023-01-30 06:04:27 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kubelet Update v1 2023-01-30 06:09:37 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:10.64.0.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-master,Unschedulable:true,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:<nil>,},Taint{Key:node.kubernetes.io/unschedulable,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[10.64.0.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{1 0} {<nil>} 1 DecimalSI},ephemeral-storage: {{16656896000 0} {<nil>} 16266500Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3858370560 0} {<nil>} 3767940Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{1 0} {<nil>} 1 DecimalSI},ephemeral-storage: {{14991206376 0} {<nil>} 14991206376 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3596226560 0} {<nil>} 3511940Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:10 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:10 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:10 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:14 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.2,},NodeAddress{Type:ExternalIP,Address:34.145.121.12,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-master.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-master.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ceaf667f6b5e1324cd116eb2db802512,SystemUUID:ceaf667f-6b5e-1324-cd11-6eb2db802512,BootID:f3af49de-86af-4adc-82a1-ca040b706b59,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-apiserver-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:135961043,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:125279033,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:51eae8381dcb1078289fa7b4f3df2630cdc18d09fb56f8e56b41c40e191d6c83 registry.k8s.io/etcd:3.5.7-0],SizeBytes:101639218,},ContainerImage{Names:[registry.k8s.io/kube-scheduler-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:57551672,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[gcr.io/k8s-ingress-image-push/ingress-gce-glbc-amd64@sha256:5db27383add6d9f4ebdf0286409ac31f7f5d273690204b341a4e37998917693b gcr.io/k8s-ingress-image-push/ingress-gce-glbc-amd64:v1.20.1],SizeBytes:36598135,},ContainerImage{Names:[registry.k8s.io/addon-manager/kube-addon-manager@sha256:49cc4e6e4a3745b427ce14b0141476ab339bb65c6bc05033019e046c8727dcb0 registry.k8s.io/addon-manager/kube-addon-manager:v9.1.6],SizeBytes:30464183,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-server@sha256:b1389e7014425a1752aac55f5043ef4c52edaef0e223bf4d48ed1324e298087c registry.k8s.io/kas-network-proxy/proxy-server:v0.1.1],SizeBytes:21875112,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:12:33.707: INFO: Logging kubelet events for node bootstrap-e2e-master Jan 30 06:12:33.754: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-master Jan 30 06:12:33.833: INFO: konnectivity-server-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container konnectivity-server-container ready: true, restart count 0 Jan 30 06:12:33.833: INFO: kube-controller-manager-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container kube-controller-manager ready: true, restart count 5 Jan 30 06:12:33.833: INFO: etcd-server-events-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container etcd-container ready: true, restart count 0 Jan 30 06:12:33.833: INFO: kube-addon-manager-bootstrap-e2e-master started at 2023-01-30 06:03:43 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container kube-addon-manager ready: true, restart count 1 Jan 30 06:12:33.833: INFO: kube-apiserver-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container kube-apiserver ready: true, restart count 1 Jan 30 06:12:33.833: INFO: etcd-server-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container etcd-container ready: true, restart count 2 Jan 30 06:12:33.833: INFO: kube-scheduler-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container kube-scheduler ready: true, restart count 4 Jan 30 06:12:33.833: INFO: l7-lb-controller-bootstrap-e2e-master started at 2023-01-30 06:03:43 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container l7-lb-controller ready: true, restart count 5 Jan 30 06:12:33.833: INFO: metadata-proxy-v0.1-4rnk7 started at 2023-01-30 06:04:10 +0000 UTC (0+2 container statuses recorded) Jan 30 06:12:33.833: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:12:33.833: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:12:34.010: INFO: Latency metrics for node bootstrap-e2e-master Jan 30 06:12:34.010: INFO: Logging node info for node bootstrap-e2e-minion-group-89rb Jan 30 06:12:34.052: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-89rb 7a6374a4-18c6-4a29-8950-b11b5056de6e 1336 0 2023-01-30 06:04:12 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-2 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-minion-group-89rb kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-2 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.1.0/24\"":{}}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kubelet Update v1 2023-01-30 06:10:01 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status} {node-problem-detector Update v1 2023-01-30 06:10:03 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.1.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-minion-group-89rb,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.1.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815430144 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553286144 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.5,},NodeAddress{Type:ExternalIP,Address:34.168.49.142,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-89rb.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-89rb.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:a886a977671560a8ccd3c81c9111e6c4,SystemUUID:a886a977-6715-60a8-ccd3-c81c9111e6c4,BootID:2435cf70-73c9-4f65-bb5d-1b1f7ed9a49e,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:66988744,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[registry.k8s.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 registry.k8s.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[registry.k8s.io/autoscaling/addon-resizer@sha256:43f129b81d28f0fdd54de6d8e7eacd5728030782e03db16087fc241ad747d3d6 registry.k8s.io/autoscaling/addon-resizer:1.8.14],SizeBytes:10153852,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-agent@sha256:939c42e815e6b6af3181f074652c0d18fe429fcee9b49c1392aee7e92887cfef registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1],SizeBytes:8364694,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:12:34.052: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-89rb Jan 30 06:12:34.101: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-89rb Jan 30 06:12:34.212: INFO: kube-proxy-bootstrap-e2e-minion-group-89rb started at 2023-01-30 06:04:12 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.212: INFO: Container kube-proxy ready: false, restart count 3 Jan 30 06:12:34.212: INFO: metadata-proxy-v0.1-4glfd started at 2023-01-30 06:04:13 +0000 UTC (0+2 container statuses recorded) Jan 30 06:12:34.212: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:12:34.212: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:12:34.212: INFO: konnectivity-agent-vpdtl started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.212: INFO: Container konnectivity-agent ready: false, restart count 2 Jan 30 06:12:34.212: INFO: metrics-server-v0.5.2-867b8754b9-s79bn started at 2023-01-30 06:04:46 +0000 UTC (0+2 container statuses recorded) Jan 30 06:12:34.212: INFO: Container metrics-server ready: false, restart count 6 Jan 30 06:12:34.212: INFO: Container metrics-server-nanny ready: true, restart count 2 Jan 30 06:12:34.369: INFO: Latency metrics for node bootstrap-e2e-minion-group-89rb Jan 30 06:12:34.369: INFO: Logging node info for node bootstrap-e2e-minion-group-j5pg Jan 30 06:12:34.412: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-j5pg 77296218-aa10-476d-a138-052026f8f306 1359 0 2023-01-30 06:04:14 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-2 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-minion-group-j5pg kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-2 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.3.0/24\"":{}}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {node-problem-detector Update v1 2023-01-30 06:10:05 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-30 06:10:10 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:10.64.3.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-minion-group-j5pg,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.3.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815438336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553294336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.3,},NodeAddress{Type:ExternalIP,Address:34.82.243.144,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-j5pg.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-j5pg.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:00c00596a04cd69c19526ec9065fe3a0,SystemUUID:00c00596-a04c-d69c-1952-6ec9065fe3a0,BootID:8b0896f1-a065-4ffa-97fa-b74f7309fbf4,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:66988744,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[registry.k8s.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 registry.k8s.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[registry.k8s.io/sig-storage/snapshot-controller@sha256:823c75d0c45d1427f6d850070956d9ca657140a7bbf828381541d1d808475280 registry.k8s.io/sig-storage/snapshot-controller:v6.1.0],SizeBytes:22620891,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/cpa/cluster-proportional-autoscaler@sha256:fd636b33485c7826fb20ef0688a83ee0910317dbb6c0c6f3ad14661c1db25def registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4],SizeBytes:15209393,},ContainerImage{Names:[registry.k8s.io/autoscaling/addon-resizer@sha256:43f129b81d28f0fdd54de6d8e7eacd5728030782e03db16087fc241ad747d3d6 registry.k8s.io/autoscaling/addon-resizer:1.8.14],SizeBytes:10153852,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-agent@sha256:939c42e815e6b6af3181f074652c0d18fe429fcee9b49c1392aee7e92887cfef registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1],SizeBytes:8364694,},ContainerImage{Names:[registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64@sha256:7eb7b3cee4d33c10c49893ad3c386232b86d4067de5251294d4c620d6e072b93 registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11],SizeBytes:6463068,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:12:34.412: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-j5pg Jan 30 06:12:34.457: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-j5pg Jan 30 06:12:34.519: INFO: metadata-proxy-v0.1-srxc6 started at 2023-01-30 06:04:15 +0000 UTC (0+2 container statuses recorded) Jan 30 06:12:34.519: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:12:34.519: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:12:34.519: INFO: kube-dns-autoscaler-5f6455f985-bg4vb started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.519: INFO: Container autoscaler ready: false, restart count 4 Jan 30 06:12:34.519: INFO: coredns-6846b5b5f-27hpv started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.519: INFO: Container coredns ready: false, restart count 4 Jan 30 06:12:34.519: INFO: l7-default-backend-8549d69d99-slz4q started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.519: INFO: Container default-http-backend ready: true, restart count 2 Jan 30 06:12:34.519: INFO: volume-snapshot-controller-0 started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.519: INFO: Container volume-snapshot-controller ready: false, restart count 5 Jan 30 06:12:34.519: INFO: konnectivity-agent-sv2mg started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.519: INFO: Container konnectivity-agent ready: true, restart count 4 Jan 30 06:12:34.519: INFO: kube-proxy-bootstrap-e2e-minion-group-j5pg started at 2023-01-30 06:04:14 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.519: INFO: Container kube-proxy ready: true, restart count 3 Jan 30 06:12:34.689: INFO: Latency metrics for node bootstrap-e2e-minion-group-j5pg Jan 30 06:12:34.689: INFO: Logging node info for node bootstrap-e2e-minion-group-jt1b Jan 30 06:12:34.732: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-jt1b 9c9847ba-4388-4123-89c6-52ccc637e6c3 1337 0 2023-01-30 06:04:14 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-2 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-minion-group-jt1b kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-2 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.2.0/24\"":{}}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kubelet Update v1 2023-01-30 06:10:01 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status} {node-problem-detector Update v1 2023-01-30 06:10:03 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.2.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-minion-group-jt1b,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.2.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815438336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553294336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.4,},NodeAddress{Type:ExternalIP,Address:34.83.145.21,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-jt1b.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-jt1b.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:a84e7124d1b77ea5a363b5b4e806099f,SystemUUID:a84e7124-d1b7-7ea5-a363-b5b4e806099f,BootID:c2771298-b9a1-4721-be1f-55ff63f4a2d8,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:66988744,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-agent@sha256:939c42e815e6b6af3181f074652c0d18fe429fcee9b49c1392aee7e92887cfef registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1],SizeBytes:8364694,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:12:34.732: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-jt1b Jan 30 06:12:34.776: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-jt1b Jan 30 06:12:34.835: INFO: kube-proxy-bootstrap-e2e-minion-group-jt1b started at 2023-01-30 06:04:14 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.835: INFO: Container kube-proxy ready: true, restart count 3 Jan 30 06:12:34.835: INFO: metadata-proxy-v0.1-zckpq started at 2023-01-30 06:04:14 +0000 UTC (0+2 container statuses recorded) Jan 30 06:12:34.835: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:12:34.835: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:12:34.835: INFO: konnectivity-agent-lsjtz started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.835: INFO: Container konnectivity-agent ready: false, restart count 4 Jan 30 06:12:34.835: INFO: coredns-6846b5b5f-vtndh started at 2023-01-30 06:04:32 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.835: INFO: Container coredns ready: false, restart count 4 Jan 30 06:12:34.991: INFO: Latency metrics for node bootstrap-e2e-minion-group-jt1b END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:12:34.991 (1.459s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:12:34.991 (1.459s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:12:34.991 STEP: Destroying namespace "reboot-2856" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 06:12:34.991 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:12:35.035 (43ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:12:35.035 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:12:35.035 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sdropping\sall\sinbound\spackets\sfor\sa\swhile\sand\sensure\sthey\sfunction\safterwards$'
[FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 06:12:33.422from junit_01.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:10:14.025 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:10:14.025 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:10:14.025 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 06:10:14.025 Jan 30 06:10:14.025: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 06:10:14.026 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/30/23 06:10:14.155 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/30/23 06:10:14.238 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:10:14.318 (294ms) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 06:10:14.318 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 06:10:14.319 (0s) > Enter [It] each node by dropping all inbound packets for a while and ensure they function afterwards - test/e2e/cloud/gcp/reboot.go:136 @ 01/30/23 06:10:14.319 Jan 30 06:10:14.412: INFO: Getting bootstrap-e2e-minion-group-j5pg Jan 30 06:10:14.412: INFO: Getting bootstrap-e2e-minion-group-89rb Jan 30 06:10:14.412: INFO: Getting bootstrap-e2e-minion-group-jt1b Jan 30 06:10:14.456: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-89rb condition Ready to be true Jan 30 06:10:14.456: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-j5pg condition Ready to be true Jan 30 06:10:14.456: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-jt1b condition Ready to be true Jan 30 06:10:14.499: INFO: Node bootstrap-e2e-minion-group-jt1b has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:10:14.500: INFO: Node bootstrap-e2e-minion-group-j5pg has 4 assigned pods with no liveness probes: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-zckpq" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-bg4vb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-srxc6" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-jt1b" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Node bootstrap-e2e-minion-group-89rb has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-4glfd" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.500: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-89rb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:10:14.546: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 46.887351ms Jan 30 06:10:14.546: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.548: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb": Phase="Running", Reason="", readiness=true. Elapsed: 48.266927ms Jan 30 06:10:14.548: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.548: INFO: Pod "metadata-proxy-v0.1-zckpq": Phase="Running", Reason="", readiness=true. Elapsed: 48.644019ms Jan 30 06:10:14.548: INFO: Pod "metadata-proxy-v0.1-zckpq" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.548: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb": Phase="Running", Reason="", readiness=true. Elapsed: 48.246832ms Jan 30 06:10:14.548: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.548: INFO: Pod "metadata-proxy-v0.1-4glfd": Phase="Running", Reason="", readiness=true. Elapsed: 48.395319ms Jan 30 06:10:14.548: INFO: Pod "metadata-proxy-v0.1-4glfd" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.548: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:10:14.548: INFO: Getting external IP address for bootstrap-e2e-minion-group-89rb Jan 30 06:10:14.548: INFO: SSH "\n\t\tnohup sh -c '\n\t\t\tset -x\n\t\t\tsleep 10\n\t\t\twhile true; do sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT && break; done\n\t\t\twhile true; do sudo iptables -I INPUT 2 -j DROP && break; done\n\t\t\tdate\n\t\t\tsleep 120\n\t\t\twhile true; do sudo iptables -D INPUT -j DROP && break; done\n\t\t\twhile true; do sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT && break; done\n\t\t' >/tmp/drop-inbound.log 2>&1 &\n\t\t" on bootstrap-e2e-minion-group-89rb(34.168.49.142:22) Jan 30 06:10:14.549: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=true. Elapsed: 48.991799ms Jan 30 06:10:14.549: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.549: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:10:14.549: INFO: Getting external IP address for bootstrap-e2e-minion-group-jt1b Jan 30 06:10:14.549: INFO: SSH "\n\t\tnohup sh -c '\n\t\t\tset -x\n\t\t\tsleep 10\n\t\t\twhile true; do sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT && break; done\n\t\t\twhile true; do sudo iptables -I INPUT 2 -j DROP && break; done\n\t\t\tdate\n\t\t\tsleep 120\n\t\t\twhile true; do sudo iptables -D INPUT -j DROP && break; done\n\t\t\twhile true; do sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT && break; done\n\t\t' >/tmp/drop-inbound.log 2>&1 &\n\t\t" on bootstrap-e2e-minion-group-jt1b(34.83.145.21:22) Jan 30 06:10:14.549: INFO: Pod "metadata-proxy-v0.1-srxc6": Phase="Running", Reason="", readiness=true. Elapsed: 49.32294ms Jan 30 06:10:14.549: INFO: Pod "metadata-proxy-v0.1-srxc6" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.549: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg": Phase="Running", Reason="", readiness=true. Elapsed: 49.415697ms Jan 30 06:10:14.549: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" satisfied condition "running and ready, or succeeded" Jan 30 06:10:14.549: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: true. Pods: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:10:14.549: INFO: Getting external IP address for bootstrap-e2e-minion-group-j5pg Jan 30 06:10:14.549: INFO: SSH "\n\t\tnohup sh -c '\n\t\t\tset -x\n\t\t\tsleep 10\n\t\t\twhile true; do sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT && break; done\n\t\t\twhile true; do sudo iptables -I INPUT 2 -j DROP && break; done\n\t\t\tdate\n\t\t\tsleep 120\n\t\t\twhile true; do sudo iptables -D INPUT -j DROP && break; done\n\t\t\twhile true; do sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT && break; done\n\t\t' >/tmp/drop-inbound.log 2>&1 &\n\t\t" on bootstrap-e2e-minion-group-j5pg(34.82.243.144:22) Jan 30 06:10:15.067: INFO: ssh prow@34.83.145.21:22: command: nohup sh -c ' set -x sleep 10 while true; do sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT && break; done while true; do sudo iptables -I INPUT 2 -j DROP && break; done date sleep 120 while true; do sudo iptables -D INPUT -j DROP && break; done while true; do sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT && break; done ' >/tmp/drop-inbound.log 2>&1 & Jan 30 06:10:15.067: INFO: ssh prow@34.83.145.21:22: stdout: "" Jan 30 06:10:15.067: INFO: ssh prow@34.83.145.21:22: stderr: "" Jan 30 06:10:15.067: INFO: ssh prow@34.83.145.21:22: exit code: 0 Jan 30 06:10:15.067: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-jt1b condition Ready to be false Jan 30 06:10:15.072: INFO: ssh prow@34.168.49.142:22: command: nohup sh -c ' set -x sleep 10 while true; do sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT && break; done while true; do sudo iptables -I INPUT 2 -j DROP && break; done date sleep 120 while true; do sudo iptables -D INPUT -j DROP && break; done while true; do sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT && break; done ' >/tmp/drop-inbound.log 2>&1 & Jan 30 06:10:15.072: INFO: ssh prow@34.168.49.142:22: stdout: "" Jan 30 06:10:15.072: INFO: ssh prow@34.168.49.142:22: stderr: "" Jan 30 06:10:15.072: INFO: ssh prow@34.168.49.142:22: exit code: 0 Jan 30 06:10:15.072: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-89rb condition Ready to be false Jan 30 06:10:15.072: INFO: ssh prow@34.82.243.144:22: command: nohup sh -c ' set -x sleep 10 while true; do sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT && break; done while true; do sudo iptables -I INPUT 2 -j DROP && break; done date sleep 120 while true; do sudo iptables -D INPUT -j DROP && break; done while true; do sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT && break; done ' >/tmp/drop-inbound.log 2>&1 & Jan 30 06:10:15.072: INFO: ssh prow@34.82.243.144:22: stdout: "" Jan 30 06:10:15.072: INFO: ssh prow@34.82.243.144:22: stderr: "" Jan 30 06:10:15.072: INFO: ssh prow@34.82.243.144:22: exit code: 0 Jan 30 06:10:15.072: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-j5pg condition Ready to be false Jan 30 06:10:15.110: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:15.114: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:15.114: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:17.162: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:17.164: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:17.164: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:19.209: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:19.209: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:19.209: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:21.254: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:21.254: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:21.254: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:23.300: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:23.300: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:23.300: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:25.345: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:25.345: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:25.345: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:10:27.385: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:27.385: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:27.385: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:29.425: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:29.425: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:29.426: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:31.465: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:31.465: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:31.465: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:33.505: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:33.505: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:33.505: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:35.546: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:35.546: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:35.546: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:37.586: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:37.586: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:37.586: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:39.626: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:39.626: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:39.626: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:41.666: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:41.666: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:41.666: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:43.707: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:43.707: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:43.707: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:45.748: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:45.748: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:45.748: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:47.788: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:47.788: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:47.788: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:49.828: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:49.828: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:49.828: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:51.869: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:51.869: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:51.869: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:53.909: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:53.909: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:53.909: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:55.950: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:55.950: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:55.950: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:57.990: INFO: Couldn't get node bootstrap-e2e-minion-group-89rb Jan 30 06:10:57.990: INFO: Couldn't get node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:57.990: INFO: Couldn't get node bootstrap-e2e-minion-group-jt1b Jan 30 06:11:02.803: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:02.803: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:02.803: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:04.850: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:04.850: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:04.850: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:06.897: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:06.897: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:06.898: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:08.943: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:08.946: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:08.946: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:10.985: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:10.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:10.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:13.028: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:13.034: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:13.034: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:15.072: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:15.078: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:15.078: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:17.116: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:17.125: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:17.125: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:19.158: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:19.167: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:19.169: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:21.202: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:21.211: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:21.212: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:23.346: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:23.346: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:23.346: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:25.392: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:25.393: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:25.393: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:27.447: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:27.447: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:27.447: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:29.493: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:29.493: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:29.493: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:31.541: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:31.541: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:31.541: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:33.588: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:33.588: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:33.588: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:35.635: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:35.635: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:35.635: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:37.681: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:37.681: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:37.681: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:39.729: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:39.729: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:39.729: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:41.777: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:41.777: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:41.777: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:43.822: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:43.823: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:43.826: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:45.865: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:45.865: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:45.868: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:47.907: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:47.910: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:47.911: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:49.951: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:49.955: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:49.955: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:51.995: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:51.999: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:51.999: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:54.038: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:54.044: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:54.044: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:56.080: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:56.089: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:56.089: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:58.124: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:58.134: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:11:58.134: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:00.168: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:00.178: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:00.178: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:02.212: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:02.224: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:02.224: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:04.260: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:04.275: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:04.275: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:06.303: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:06.318: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:06.318: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:08.345: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:08.363: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:08.363: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:10.389: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:10.407: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:10.407: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:12.439: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:12.453: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:12.453: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:14.482: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:14.498: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:14.498: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:12:16.482: INFO: Node bootstrap-e2e-minion-group-j5pg didn't reach desired Ready condition status (false) within 2m0s Jan 30 06:12:16.499: INFO: Node bootstrap-e2e-minion-group-jt1b didn't reach desired Ready condition status (false) within 2m0s Jan 30 06:12:16.499: INFO: Node bootstrap-e2e-minion-group-89rb didn't reach desired Ready condition status (false) within 2m0s Jan 30 06:12:16.499: INFO: Node bootstrap-e2e-minion-group-89rb failed reboot test. Jan 30 06:12:16.499: INFO: Node bootstrap-e2e-minion-group-j5pg failed reboot test. Jan 30 06:12:16.499: INFO: Node bootstrap-e2e-minion-group-jt1b failed reboot test. Jan 30 06:12:16.499: INFO: Executing termination hook on nodes Jan 30 06:12:16.499: INFO: Getting external IP address for bootstrap-e2e-minion-group-89rb Jan 30 06:12:16.499: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-89rb(34.168.49.142:22) Jan 30 06:12:32.370: INFO: ssh prow@34.168.49.142:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 30 06:12:32.370: INFO: ssh prow@34.168.49.142:22: stdout: "+ sleep 10\n+ true\n+ sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT\n+ break\n+ true\n+ sudo iptables -I INPUT 2 -j DROP\n+ break\n+ date\nMon Jan 30 06:10:25 UTC 2023\n+ sleep 120\n+ true\n+ sudo iptables -D INPUT -j DROP\n+ break\n+ true\n+ sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT\n+ break\n" Jan 30 06:12:32.370: INFO: ssh prow@34.168.49.142:22: stderr: "" Jan 30 06:12:32.370: INFO: ssh prow@34.168.49.142:22: exit code: 0 Jan 30 06:12:32.370: INFO: Getting external IP address for bootstrap-e2e-minion-group-j5pg Jan 30 06:12:32.370: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-j5pg(34.82.243.144:22) Jan 30 06:12:32.899: INFO: ssh prow@34.82.243.144:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 30 06:12:32.899: INFO: ssh prow@34.82.243.144:22: stdout: "+ sleep 10\n+ true\n+ sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT\n+ break\n+ true\n+ sudo iptables -I INPUT 2 -j DROP\n+ break\n+ date\nMon Jan 30 06:10:25 UTC 2023\n+ sleep 120\n+ true\n+ sudo iptables -D INPUT -j DROP\n+ break\n+ true\n+ sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT\n+ break\n" Jan 30 06:12:32.899: INFO: ssh prow@34.82.243.144:22: stderr: "" Jan 30 06:12:32.899: INFO: ssh prow@34.82.243.144:22: exit code: 0 Jan 30 06:12:32.899: INFO: Getting external IP address for bootstrap-e2e-minion-group-jt1b Jan 30 06:12:32.899: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-jt1b(34.83.145.21:22) Jan 30 06:12:33.421: INFO: ssh prow@34.83.145.21:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 30 06:12:33.421: INFO: ssh prow@34.83.145.21:22: stdout: "+ sleep 10\n+ true\n+ sudo iptables -I INPUT 1 -s 127.0.0.1 -j ACCEPT\n+ break\n+ true\n+ sudo iptables -I INPUT 2 -j DROP\n+ break\n+ date\nMon Jan 30 06:10:25 UTC 2023\n+ sleep 120\n+ true\n+ sudo iptables -D INPUT -j DROP\n+ break\n+ true\n+ sudo iptables -D INPUT -s 127.0.0.1 -j ACCEPT\n+ break\n" Jan 30 06:12:33.421: INFO: ssh prow@34.83.145.21:22: stderr: "" Jan 30 06:12:33.421: INFO: ssh prow@34.83.145.21:22: exit code: 0 [FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 06:12:33.422 < Exit [It] each node by dropping all inbound packets for a while and ensure they function afterwards - test/e2e/cloud/gcp/reboot.go:136 @ 01/30/23 06:12:33.422 (2m19.103s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:12:33.422 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 06:12:33.422 Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-27hpv to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} FailedMount: MountVolume.SetUp failed for volume "config-volume" : failed to sync configmap cache: timed out waiting for the condition Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 2.636021002s (2.636034032s including waiting) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container coredns Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container coredns Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container coredns Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: Get "http://10.64.3.7:8181/ready": dial tcp 10.64.3.7:8181: connect: connection refused Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: Get "http://10.64.3.12:8181/ready": dial tcp 10.64.3.12:8181: connect: connection refused Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-27hpv_kube-system(d5696a97-0c32-4875-8ac5-fdb1ce1816da) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: Get "http://10.64.3.14:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.14:8080/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-27hpv: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-vtndh to bootstrap-e2e-minion-group-jt1b Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 1.034366695s (1.034389733s including waiting) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container coredns Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container coredns Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Stopping container coredns Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.3:8181/ready": dial tcp 10.64.2.3:8181: connect: connection refused Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.5:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-vtndh_kube-system(9c9e7a94-38c6-4663-8f82-43b74a199e59) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.6:8181/ready": dial tcp 10.64.2.6:8181: i/o timeout (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.6:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f-vtndh: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f: {replicaset-controller } FailedCreate: Error creating: insufficient quota to match these scopes: [{PriorityClass In [system-node-critical system-cluster-critical]}] Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-27hpv Jan 30 06:12:33.470: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-vtndh Jan 30 06:12:33.470: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 1 Jan 30 06:12:33.470: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 2 from 1 Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container etcd-container Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container etcd-container Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container etcd-container Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe errored: rpc error: code = Unknown desc = failed to exec in container: container is in CONTAINER_EXITED state Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/etcd:3.5.7-0" already present on machine Jan 30 06:12:33.470: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container etcd-container in pod etcd-server-bootstrap-e2e-master_kube-system(2ef2f0d9ccfe01aa3c1d26059de8a300) Jan 30 06:12:33.470: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_2e2da became leader Jan 30 06:12:33.470: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_7c8d0 became leader Jan 30 06:12:33.470: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_1ffa4 became leader Jan 30 06:12:33.470: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_b9c2e became leader Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-lsjtz to bootstrap-e2e-minion-group-jt1b Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 664.348201ms (664.364985ms including waiting) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Stopping container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Liveness probe failed: Get "http://10.64.2.4:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 06:12:33.470: INFO: event for konnectivity-agent-lsjtz: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-sv2mg to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 2.45385434s (2.453864342s including waiting) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.5:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.19:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-sv2mg: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-vpdtl to bootstrap-e2e-minion-group-89rb Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 657.450417ms (657.460286ms including waiting) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container konnectivity-agent Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Liveness probe failed: Get "http://10.64.1.5:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Failed: Error: failed to get sandbox container task: no running task found: task 38160c3af9302d8f890a71a78eed322e52a69e59da84d5a3ca773407ab029cd1 not found: not found Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-vpdtl_kube-system(73c6f815-a15e-4e7a-a972-20e282f676c0) Jan 30 06:12:33.470: INFO: event for konnectivity-agent-vpdtl: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-sv2mg Jan 30 06:12:33.470: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-vpdtl Jan 30 06:12:33.470: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-lsjtz Jan 30 06:12:33.470: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-addon-manager Jan 30 06:12:33.470: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-addon-manager Jan 30 06:12:33.470: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-addon-manager Jan 30 06:12:33.470: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/addon-manager/kube-addon-manager:v9.1.6" already present on machine Jan 30 06:12:33.470: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 06:12:33.470: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-apiserver Jan 30 06:12:33.470: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Readiness probe failed: Get "https://127.0.0.1:443/readyz": dial tcp 127.0.0.1:443: connect: connection refused Jan 30 06:12:33.470: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/kube-controller-manager-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:12:33.470: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-controller-manager Jan 30 06:12:33.470: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-controller-manager Jan 30 06:12:33.470: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-controller-manager Jan 30 06:12:33.470: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container kube-controller-manager in pod kube-controller-manager-bootstrap-e2e-master_kube-system(4fc5a5aeac3c203e3876adb08d878c93) Jan 30 06:12:33.470: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_c4dee0f1-ebbd-431b-a4f5-cdaba3338ff1 became leader Jan 30 06:12:33.470: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_6a930d5c-d857-45d7-8821-ab6144cfb617 became leader Jan 30 06:12:33.470: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_52b92c73-5b92-4994-9104-bec143d48796 became leader Jan 30 06:12:33.470: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_24f84219-2bae-4a66-bead-e8bbaf2fb7a6 became leader Jan 30 06:12:33.470: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_24c1fd47-ae61-4e44-8476-8212cb452f58 became leader Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-dns-autoscaler-5f6455f985-bg4vb to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" in 2.01573763s (2.015748792s including waiting) Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container autoscaler Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container autoscaler Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container autoscaler Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" already present on machine Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container autoscaler in pod kube-dns-autoscaler-5f6455f985-bg4vb_kube-system(d17909b1-64e2-475c-a08b-b40ba36f6afa) Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985: {replicaset-controller } FailedCreate: Error creating: pods "kube-dns-autoscaler-5f6455f985-" is forbidden: error looking up service account kube-system/kube-dns-autoscaler: serviceaccount "kube-dns-autoscaler" not found Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler-5f6455f985: {replicaset-controller } SuccessfulCreate: Created pod: kube-dns-autoscaler-5f6455f985-bg4vb Jan 30 06:12:33.470: INFO: event for kube-dns-autoscaler: {deployment-controller } ScalingReplicaSet: Scaled up replica set kube-dns-autoscaler-5f6455f985 to 1 Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-89rb_kube-system(a86edc08c98ce4fefed543ad485600a4) Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-j5pg_kube-system(adff6fb483f7c9e3d86fb4cb79733a2e) Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Stopping container kube-proxy Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-jt1b_kube-system(87a78f5a508a69cfa60729c5d4dc7da6) Jan 30 06:12:33.470: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/kube-scheduler-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-scheduler Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-scheduler Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container kube-scheduler in pod kube-scheduler-bootstrap-e2e-master_kube-system(5b3c0a3dad3d723f9e5778ab0a62849c) Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-scheduler Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe failed: Get "https://127.0.0.1:10259/healthz": dial tcp 127.0.0.1:10259: connect: connection refused Jan 30 06:12:33.470: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.470: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_18ee2297-5499-4a10-b782-8bf60ef964f2 became leader Jan 30 06:12:33.470: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_959dc035-06e0-4f47-9fbb-6328d3119de5 became leader Jan 30 06:12:33.470: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_36535314-0b8e-4eff-a7de-1c139a5f4105 became leader Jan 30 06:12:33.470: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_8d92bf3b-8542-4829-90e1-576b213e261b became leader Jan 30 06:12:33.470: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_95bd1561-0f4e-420f-8860-23de9b4e3cb0 became leader Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {default-scheduler } Scheduled: Successfully assigned kube-system/l7-default-backend-8549d69d99-slz4q to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" in 2.282907597s (2.282919912s including waiting) Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container default-http-backend Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container default-http-backend Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.4:8080/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Container default-http-backend failed liveness probe, will be restarted Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99-slz4q: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for l7-default-backend-8549d69d99: {replicaset-controller } SuccessfulCreate: Created pod: l7-default-backend-8549d69d99-slz4q Jan 30 06:12:33.470: INFO: event for l7-default-backend: {deployment-controller } ScalingReplicaSet: Scaled up replica set l7-default-backend-8549d69d99 to 1 Jan 30 06:12:33.470: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container l7-lb-controller Jan 30 06:12:33.470: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container l7-lb-controller Jan 30 06:12:33.470: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "gcr.io/k8s-ingress-image-push/ingress-gce-glbc-amd64:v1.20.1" already present on machine Jan 30 06:12:33.470: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container l7-lb-controller in pod l7-lb-controller-bootstrap-e2e-master_kube-system(f922c87738da4b787ed79e8be7ae0573) Jan 30 06:12:33.470: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe failed: Get "http://10.138.0.2:8086/healthz": dial tcp 10.138.0.2:8086: connect: connection refused Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-4glfd to bootstrap-e2e-minion-group-89rb Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 743.096978ms (743.138916ms including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.911633038s (1.911644632s including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4glfd: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-4rnk7 to bootstrap-e2e-master Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 751.7056ms (751.711494ms including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Failed: Error: services have not yet been read at least once, cannot construct envvars Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.335358551s (2.33536641s including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Created: Created container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Started: Started container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Created: Created container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Started: Started container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-srxc6 to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 804.763467ms (804.774083ms including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.089844613s (2.089864707s including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-srxc6: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-zckpq to bootstrap-e2e-minion-group-jt1b Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 842.219895ms (842.229354ms including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container metadata-proxy Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.054812451s (2.054822588s including waiting) Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container prometheus-to-sd-exporter Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1-zckpq: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-4rnk7 Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-4glfd Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-zckpq Jan 30 06:12:33.470: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-srxc6 Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-6764bf875c-vbxz7 to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} FailedMount: MountVolume.SetUp failed for volume "metrics-server-config-volume" : failed to sync configmap cache: timed out waiting for the condition Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 3.531930568s (3.532067103s including waiting) Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container metrics-server Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container metrics-server Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 1.812865403s (1.812874646s including waiting) Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container metrics-server-nanny Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container metrics-server-nanny Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container metrics-server Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container metrics-server-nanny Jan 30 06:12:33.470: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-6764bf875c-vbxz7 Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulDelete: Deleted pod: metrics-server-v0.5.2-6764bf875c-vbxz7 Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-867b8754b9-s79bn to bootstrap-e2e-minion-group-89rb Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 1.367491088s (1.367525697s including waiting) Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container metrics-server Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container metrics-server Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 1.035914064s (1.035929902s including waiting) Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container metrics-server-nanny Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container metrics-server-nanny Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Readiness probe failed: Get "https://10.64.1.3:10250/readyz": dial tcp 10.64.1.3:10250: connect: connection refused Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Liveness probe failed: Get "https://10.64.1.3:10250/livez": dial tcp 10.64.1.3:10250: connect: connection refused Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Liveness probe failed: Get "https://10.64.1.3:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Readiness probe failed: Get "https://10.64.1.3:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container metrics-server Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container metrics-server-nanny Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Readiness probe failed: Get "https://10.64.1.4:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2-867b8754b9: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-867b8754b9-s79bn Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-v0.5.2-6764bf875c to 1 Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-v0.5.2-867b8754b9 to 1 Jan 30 06:12:33.471: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled down replica set metrics-server-v0.5.2-6764bf875c to 0 from 1 Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {default-scheduler } Scheduled: Successfully assigned kube-system/volume-snapshot-controller-0 to bootstrap-e2e-minion-group-j5pg Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" in 1.683320982s (1.68333161s including waiting) Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container volume-snapshot-controller Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container volume-snapshot-controller Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container volume-snapshot-controller Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(694587fc-d43c-43bc-bbab-563d942a4f03) Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller-0: {node-controller } NodeNotReady: Node is not ready Jan 30 06:12:33.471: INFO: event for volume-snapshot-controller: {statefulset-controller } SuccessfulCreate: create Pod volume-snapshot-controller-0 in StatefulSet volume-snapshot-controller successful < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:12:33.471 (49ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:12:33.471 Jan 30 06:12:33.471: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:12:33.532 (61ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 06:12:33.532 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 06:12:33.532 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:12:33.532 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:12:33.532 STEP: Collecting events from namespace "reboot-2856". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 06:12:33.532 STEP: Found 0 events. - test/e2e/framework/debug/dump.go:46 @ 01/30/23 06:12:33.573 Jan 30 06:12:33.615: INFO: POD NODE PHASE GRACE CONDITIONS Jan 30 06:12:33.615: INFO: Jan 30 06:12:33.663: INFO: Logging node info for node bootstrap-e2e-master Jan 30 06:12:33.707: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-master da42dd0c-bb3c-402f-847c-793de73fb287 1204 0 2023-01-30 06:04:10 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-1 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-master kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-1 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:10 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{},"f:unschedulable":{}}} } {kube-controller-manager Update v1 2023-01-30 06:04:27 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.0.0/24\"":{}},"f:taints":{}}} } {kube-controller-manager Update v1 2023-01-30 06:04:27 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kubelet Update v1 2023-01-30 06:09:37 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:10.64.0.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-master,Unschedulable:true,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:<nil>,},Taint{Key:node.kubernetes.io/unschedulable,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[10.64.0.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{1 0} {<nil>} 1 DecimalSI},ephemeral-storage: {{16656896000 0} {<nil>} 16266500Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3858370560 0} {<nil>} 3767940Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{1 0} {<nil>} 1 DecimalSI},ephemeral-storage: {{14991206376 0} {<nil>} 14991206376 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3596226560 0} {<nil>} 3511940Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:10 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:10 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:10 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:14 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.2,},NodeAddress{Type:ExternalIP,Address:34.145.121.12,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-master.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-master.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ceaf667f6b5e1324cd116eb2db802512,SystemUUID:ceaf667f-6b5e-1324-cd11-6eb2db802512,BootID:f3af49de-86af-4adc-82a1-ca040b706b59,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-apiserver-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:135961043,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:125279033,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:51eae8381dcb1078289fa7b4f3df2630cdc18d09fb56f8e56b41c40e191d6c83 registry.k8s.io/etcd:3.5.7-0],SizeBytes:101639218,},ContainerImage{Names:[registry.k8s.io/kube-scheduler-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:57551672,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[gcr.io/k8s-ingress-image-push/ingress-gce-glbc-amd64@sha256:5db27383add6d9f4ebdf0286409ac31f7f5d273690204b341a4e37998917693b gcr.io/k8s-ingress-image-push/ingress-gce-glbc-amd64:v1.20.1],SizeBytes:36598135,},ContainerImage{Names:[registry.k8s.io/addon-manager/kube-addon-manager@sha256:49cc4e6e4a3745b427ce14b0141476ab339bb65c6bc05033019e046c8727dcb0 registry.k8s.io/addon-manager/kube-addon-manager:v9.1.6],SizeBytes:30464183,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-server@sha256:b1389e7014425a1752aac55f5043ef4c52edaef0e223bf4d48ed1324e298087c registry.k8s.io/kas-network-proxy/proxy-server:v0.1.1],SizeBytes:21875112,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:12:33.707: INFO: Logging kubelet events for node bootstrap-e2e-master Jan 30 06:12:33.754: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-master Jan 30 06:12:33.833: INFO: konnectivity-server-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container konnectivity-server-container ready: true, restart count 0 Jan 30 06:12:33.833: INFO: kube-controller-manager-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container kube-controller-manager ready: true, restart count 5 Jan 30 06:12:33.833: INFO: etcd-server-events-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container etcd-container ready: true, restart count 0 Jan 30 06:12:33.833: INFO: kube-addon-manager-bootstrap-e2e-master started at 2023-01-30 06:03:43 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container kube-addon-manager ready: true, restart count 1 Jan 30 06:12:33.833: INFO: kube-apiserver-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container kube-apiserver ready: true, restart count 1 Jan 30 06:12:33.833: INFO: etcd-server-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container etcd-container ready: true, restart count 2 Jan 30 06:12:33.833: INFO: kube-scheduler-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container kube-scheduler ready: true, restart count 4 Jan 30 06:12:33.833: INFO: l7-lb-controller-bootstrap-e2e-master started at 2023-01-30 06:03:43 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:33.833: INFO: Container l7-lb-controller ready: true, restart count 5 Jan 30 06:12:33.833: INFO: metadata-proxy-v0.1-4rnk7 started at 2023-01-30 06:04:10 +0000 UTC (0+2 container statuses recorded) Jan 30 06:12:33.833: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:12:33.833: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:12:34.010: INFO: Latency metrics for node bootstrap-e2e-master Jan 30 06:12:34.010: INFO: Logging node info for node bootstrap-e2e-minion-group-89rb Jan 30 06:12:34.052: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-89rb 7a6374a4-18c6-4a29-8950-b11b5056de6e 1336 0 2023-01-30 06:04:12 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-2 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-minion-group-89rb kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-2 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.1.0/24\"":{}}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kubelet Update v1 2023-01-30 06:10:01 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status} {node-problem-detector Update v1 2023-01-30 06:10:03 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.1.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-minion-group-89rb,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.1.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815430144 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553286144 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.5,},NodeAddress{Type:ExternalIP,Address:34.168.49.142,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-89rb.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-89rb.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:a886a977671560a8ccd3c81c9111e6c4,SystemUUID:a886a977-6715-60a8-ccd3-c81c9111e6c4,BootID:2435cf70-73c9-4f65-bb5d-1b1f7ed9a49e,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:66988744,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[registry.k8s.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 registry.k8s.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[registry.k8s.io/autoscaling/addon-resizer@sha256:43f129b81d28f0fdd54de6d8e7eacd5728030782e03db16087fc241ad747d3d6 registry.k8s.io/autoscaling/addon-resizer:1.8.14],SizeBytes:10153852,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-agent@sha256:939c42e815e6b6af3181f074652c0d18fe429fcee9b49c1392aee7e92887cfef registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1],SizeBytes:8364694,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:12:34.052: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-89rb Jan 30 06:12:34.101: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-89rb Jan 30 06:12:34.212: INFO: kube-proxy-bootstrap-e2e-minion-group-89rb started at 2023-01-30 06:04:12 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.212: INFO: Container kube-proxy ready: false, restart count 3 Jan 30 06:12:34.212: INFO: metadata-proxy-v0.1-4glfd started at 2023-01-30 06:04:13 +0000 UTC (0+2 container statuses recorded) Jan 30 06:12:34.212: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:12:34.212: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:12:34.212: INFO: konnectivity-agent-vpdtl started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.212: INFO: Container konnectivity-agent ready: false, restart count 2 Jan 30 06:12:34.212: INFO: metrics-server-v0.5.2-867b8754b9-s79bn started at 2023-01-30 06:04:46 +0000 UTC (0+2 container statuses recorded) Jan 30 06:12:34.212: INFO: Container metrics-server ready: false, restart count 6 Jan 30 06:12:34.212: INFO: Container metrics-server-nanny ready: true, restart count 2 Jan 30 06:12:34.369: INFO: Latency metrics for node bootstrap-e2e-minion-group-89rb Jan 30 06:12:34.369: INFO: Logging node info for node bootstrap-e2e-minion-group-j5pg Jan 30 06:12:34.412: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-j5pg 77296218-aa10-476d-a138-052026f8f306 1359 0 2023-01-30 06:04:14 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-2 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-minion-group-j5pg kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-2 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.3.0/24\"":{}}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {node-problem-detector Update v1 2023-01-30 06:10:05 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-30 06:10:10 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:10.64.3.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-minion-group-j5pg,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.3.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815438336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553294336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.3,},NodeAddress{Type:ExternalIP,Address:34.82.243.144,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-j5pg.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-j5pg.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:00c00596a04cd69c19526ec9065fe3a0,SystemUUID:00c00596-a04c-d69c-1952-6ec9065fe3a0,BootID:8b0896f1-a065-4ffa-97fa-b74f7309fbf4,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:66988744,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[registry.k8s.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 registry.k8s.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[registry.k8s.io/sig-storage/snapshot-controller@sha256:823c75d0c45d1427f6d850070956d9ca657140a7bbf828381541d1d808475280 registry.k8s.io/sig-storage/snapshot-controller:v6.1.0],SizeBytes:22620891,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/cpa/cluster-proportional-autoscaler@sha256:fd636b33485c7826fb20ef0688a83ee0910317dbb6c0c6f3ad14661c1db25def registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4],SizeBytes:15209393,},ContainerImage{Names:[registry.k8s.io/autoscaling/addon-resizer@sha256:43f129b81d28f0fdd54de6d8e7eacd5728030782e03db16087fc241ad747d3d6 registry.k8s.io/autoscaling/addon-resizer:1.8.14],SizeBytes:10153852,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-agent@sha256:939c42e815e6b6af3181f074652c0d18fe429fcee9b49c1392aee7e92887cfef registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1],SizeBytes:8364694,},ContainerImage{Names:[registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64@sha256:7eb7b3cee4d33c10c49893ad3c386232b86d4067de5251294d4c620d6e072b93 registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11],SizeBytes:6463068,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:12:34.412: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-j5pg Jan 30 06:12:34.457: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-j5pg Jan 30 06:12:34.519: INFO: metadata-proxy-v0.1-srxc6 started at 2023-01-30 06:04:15 +0000 UTC (0+2 container statuses recorded) Jan 30 06:12:34.519: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:12:34.519: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:12:34.519: INFO: kube-dns-autoscaler-5f6455f985-bg4vb started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.519: INFO: Container autoscaler ready: false, restart count 4 Jan 30 06:12:34.519: INFO: coredns-6846b5b5f-27hpv started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.519: INFO: Container coredns ready: false, restart count 4 Jan 30 06:12:34.519: INFO: l7-default-backend-8549d69d99-slz4q started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.519: INFO: Container default-http-backend ready: true, restart count 2 Jan 30 06:12:34.519: INFO: volume-snapshot-controller-0 started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.519: INFO: Container volume-snapshot-controller ready: false, restart count 5 Jan 30 06:12:34.519: INFO: konnectivity-agent-sv2mg started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.519: INFO: Container konnectivity-agent ready: true, restart count 4 Jan 30 06:12:34.519: INFO: kube-proxy-bootstrap-e2e-minion-group-j5pg started at 2023-01-30 06:04:14 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.519: INFO: Container kube-proxy ready: true, restart count 3 Jan 30 06:12:34.689: INFO: Latency metrics for node bootstrap-e2e-minion-group-j5pg Jan 30 06:12:34.689: INFO: Logging node info for node bootstrap-e2e-minion-group-jt1b Jan 30 06:12:34.732: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-jt1b 9c9847ba-4388-4123-89c6-52ccc637e6c3 1337 0 2023-01-30 06:04:14 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-2 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-minion-group-jt1b kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-2 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.2.0/24\"":{}}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kubelet Update v1 2023-01-30 06:10:01 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status} {node-problem-detector Update v1 2023-01-30 06:10:03 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.2.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-minion-group-jt1b,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.2.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815438336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553294336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.4,},NodeAddress{Type:ExternalIP,Address:34.83.145.21,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-jt1b.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-jt1b.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:a84e7124d1b77ea5a363b5b4e806099f,SystemUUID:a84e7124-d1b7-7ea5-a363-b5b4e806099f,BootID:c2771298-b9a1-4721-be1f-55ff63f4a2d8,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:66988744,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-agent@sha256:939c42e815e6b6af3181f074652c0d18fe429fcee9b49c1392aee7e92887cfef registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1],SizeBytes:8364694,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:12:34.732: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-jt1b Jan 30 06:12:34.776: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-jt1b Jan 30 06:12:34.835: INFO: kube-proxy-bootstrap-e2e-minion-group-jt1b started at 2023-01-30 06:04:14 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.835: INFO: Container kube-proxy ready: true, restart count 3 Jan 30 06:12:34.835: INFO: metadata-proxy-v0.1-zckpq started at 2023-01-30 06:04:14 +0000 UTC (0+2 container statuses recorded) Jan 30 06:12:34.835: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:12:34.835: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:12:34.835: INFO: konnectivity-agent-lsjtz started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.835: INFO: Container konnectivity-agent ready: false, restart count 4 Jan 30 06:12:34.835: INFO: coredns-6846b5b5f-vtndh started at 2023-01-30 06:04:32 +0000 UTC (0+1 container statuses recorded) Jan 30 06:12:34.835: INFO: Container coredns ready: false, restart count 4 Jan 30 06:12:34.991: INFO: Latency metrics for node bootstrap-e2e-minion-group-jt1b END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:12:34.991 (1.459s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:12:34.991 (1.459s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:12:34.991 STEP: Destroying namespace "reboot-2856" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 06:12:34.991 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:12:35.035 (43ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:12:35.035 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:12:35.035 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sdropping\sall\soutbound\spackets\sfor\sa\swhile\sand\sensure\sthey\sfunction\safterwards$'
[FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 06:10:08.257from ginkgo_report.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:07:49.803 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:07:49.803 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:07:49.803 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 06:07:49.803 Jan 30 06:07:49.803: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 06:07:49.805 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/30/23 06:07:49.931 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/30/23 06:07:50.012 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:07:50.092 (289ms) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 06:07:50.092 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 06:07:50.092 (0s) > Enter [It] each node by dropping all outbound packets for a while and ensure they function afterwards - test/e2e/cloud/gcp/reboot.go:144 @ 01/30/23 06:07:50.092 Jan 30 06:07:50.186: INFO: Getting bootstrap-e2e-minion-group-j5pg Jan 30 06:07:50.186: INFO: Getting bootstrap-e2e-minion-group-89rb Jan 30 06:07:50.186: INFO: Getting bootstrap-e2e-minion-group-jt1b Jan 30 06:07:50.261: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-89rb condition Ready to be true Jan 30 06:07:50.262: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-j5pg condition Ready to be true Jan 30 06:07:50.262: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-jt1b condition Ready to be true Jan 30 06:07:50.305: INFO: Node bootstrap-e2e-minion-group-j5pg has 4 assigned pods with no liveness probes: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:07:50.305: INFO: Node bootstrap-e2e-minion-group-89rb has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-4glfd" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-89rb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-bg4vb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-srxc6" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.306: INFO: Node bootstrap-e2e-minion-group-jt1b has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:07:50.306: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:07:50.306: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-zckpq" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.306: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-jt1b" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.347: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 42.631446ms Jan 30 06:07:50.347: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.352: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb": Phase="Running", Reason="", readiness=true. Elapsed: 46.902453ms Jan 30 06:07:50.352: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.353: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg": Phase="Running", Reason="", readiness=true. Elapsed: 48.235213ms Jan 30 06:07:50.353: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.353: INFO: Pod "metadata-proxy-v0.1-srxc6": Phase="Running", Reason="", readiness=true. Elapsed: 48.294842ms Jan 30 06:07:50.353: INFO: Pod "metadata-proxy-v0.1-srxc6" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.353: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: true. Pods: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:07:50.353: INFO: Getting external IP address for bootstrap-e2e-minion-group-j5pg Jan 30 06:07:50.353: INFO: SSH "\n\t\tnohup sh -c '\n\t\t\tset -x\n\t\t\tsleep 10\n\t\t\twhile true; do sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT && break; done\n\t\t\twhile true; do sudo iptables -I OUTPUT 2 -j DROP && break; done\n\t\t\tdate\n\t\t\tsleep 120\n\t\t\twhile true; do sudo iptables -D OUTPUT -j DROP && break; done\n\t\t\twhile true; do sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT && break; done\n\t\t' >/tmp/drop-outbound.log 2>&1 &\n\t\t" on bootstrap-e2e-minion-group-j5pg(34.82.243.144:22) Jan 30 06:07:50.357: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb": Phase="Running", Reason="", readiness=true. Elapsed: 52.271274ms Jan 30 06:07:50.357: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.357: INFO: Pod "metadata-proxy-v0.1-4glfd": Phase="Running", Reason="", readiness=true. Elapsed: 52.46078ms Jan 30 06:07:50.357: INFO: Pod "metadata-proxy-v0.1-4glfd" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.357: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:07:50.357: INFO: Getting external IP address for bootstrap-e2e-minion-group-89rb Jan 30 06:07:50.357: INFO: SSH "\n\t\tnohup sh -c '\n\t\t\tset -x\n\t\t\tsleep 10\n\t\t\twhile true; do sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT && break; done\n\t\t\twhile true; do sudo iptables -I OUTPUT 2 -j DROP && break; done\n\t\t\tdate\n\t\t\tsleep 120\n\t\t\twhile true; do sudo iptables -D OUTPUT -j DROP && break; done\n\t\t\twhile true; do sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT && break; done\n\t\t' >/tmp/drop-outbound.log 2>&1 &\n\t\t" on bootstrap-e2e-minion-group-89rb(34.168.49.142:22) Jan 30 06:07:50.359: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=true. Elapsed: 53.257423ms Jan 30 06:07:50.359: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.359: INFO: Pod "metadata-proxy-v0.1-zckpq": Phase="Running", Reason="", readiness=true. Elapsed: 53.488892ms Jan 30 06:07:50.359: INFO: Pod "metadata-proxy-v0.1-zckpq" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.359: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:07:50.359: INFO: Getting external IP address for bootstrap-e2e-minion-group-jt1b Jan 30 06:07:50.359: INFO: SSH "\n\t\tnohup sh -c '\n\t\t\tset -x\n\t\t\tsleep 10\n\t\t\twhile true; do sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT && break; done\n\t\t\twhile true; do sudo iptables -I OUTPUT 2 -j DROP && break; done\n\t\t\tdate\n\t\t\tsleep 120\n\t\t\twhile true; do sudo iptables -D OUTPUT -j DROP && break; done\n\t\t\twhile true; do sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT && break; done\n\t\t' >/tmp/drop-outbound.log 2>&1 &\n\t\t" on bootstrap-e2e-minion-group-jt1b(34.83.145.21:22) Jan 30 06:07:50.878: INFO: ssh prow@34.82.243.144:22: command: nohup sh -c ' set -x sleep 10 while true; do sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT && break; done while true; do sudo iptables -I OUTPUT 2 -j DROP && break; done date sleep 120 while true; do sudo iptables -D OUTPUT -j DROP && break; done while true; do sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT && break; done ' >/tmp/drop-outbound.log 2>&1 & Jan 30 06:07:50.878: INFO: ssh prow@34.82.243.144:22: stdout: "" Jan 30 06:07:50.878: INFO: ssh prow@34.82.243.144:22: stderr: "" Jan 30 06:07:50.878: INFO: ssh prow@34.82.243.144:22: exit code: 0 Jan 30 06:07:50.878: INFO: ssh prow@34.83.145.21:22: command: nohup sh -c ' set -x sleep 10 while true; do sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT && break; done while true; do sudo iptables -I OUTPUT 2 -j DROP && break; done date sleep 120 while true; do sudo iptables -D OUTPUT -j DROP && break; done while true; do sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT && break; done ' >/tmp/drop-outbound.log 2>&1 & Jan 30 06:07:50.878: INFO: ssh prow@34.83.145.21:22: stdout: "" Jan 30 06:07:50.878: INFO: ssh prow@34.83.145.21:22: stderr: "" Jan 30 06:07:50.878: INFO: ssh prow@34.83.145.21:22: exit code: 0 Jan 30 06:07:50.878: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-j5pg condition Ready to be false Jan 30 06:07:50.878: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-jt1b condition Ready to be false Jan 30 06:07:50.886: INFO: ssh prow@34.168.49.142:22: command: nohup sh -c ' set -x sleep 10 while true; do sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT && break; done while true; do sudo iptables -I OUTPUT 2 -j DROP && break; done date sleep 120 while true; do sudo iptables -D OUTPUT -j DROP && break; done while true; do sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT && break; done ' >/tmp/drop-outbound.log 2>&1 & Jan 30 06:07:50.886: INFO: ssh prow@34.168.49.142:22: stdout: "" Jan 30 06:07:50.886: INFO: ssh prow@34.168.49.142:22: stderr: "" Jan 30 06:07:50.886: INFO: ssh prow@34.168.49.142:22: exit code: 0 Jan 30 06:07:50.886: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-89rb condition Ready to be false Jan 30 06:07:50.923: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:07:50.923: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:07:50.928: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:07:52.966: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:07:52.966: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:07:52.970: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:11.060: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:11.060: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:11.060: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:13.104: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:13.104: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:13.104: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:15.148: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:15.149: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:15.149: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:17.207: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:17.207: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:17.207: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:19.252: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:19.252: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:19.252: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:21.296: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:21.299: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:21.299: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:23.339: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:23.343: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:23.343: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:25.382: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:25.388: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:25.388: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:27.425: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:27.438: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:27.438: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:29.469: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:29.482: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:29.482: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:31.514: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:31.526: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:31.526: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:33.557: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:33.569: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:33.569: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:35.601: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:35.612: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:35.612: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:37.644: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:37.657: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:37.657: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:39.686: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:39.701: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:39.701: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:41.731: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:41.746: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:41.746: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:43.773: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:43.790: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:43.790: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:45.819: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:45.836: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:45.836: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:47.862: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:47.880: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:47.880: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:49.905: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:49.923: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:49.923: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:51.948: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:51.966: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:51.967: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:53.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:54.010: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:54.010: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:56.032: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:56.055: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:56.055: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:58.075: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:58.098: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:58.098: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:00.118: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:00.143: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:00.143: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:02.161: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:02.206: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:02.206: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:04.205: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:04.250: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:04.250: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:06.249: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:06.294: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:06.294: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:08.292: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:08.337: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:08.337: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:10.336: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:10.385: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:10.385: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:12.380: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:12.429: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:12.429: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:14.423: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:14.473: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:14.473: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:16.465: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:16.516: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:16.516: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:18.527: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:18.561: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:18.561: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:20.569: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:20.605: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:20.605: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:22.614: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:22.651: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:22.651: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:24.657: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:24.698: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:24.698: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:26.699: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:26.743: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:26.743: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:28.744: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:28.788: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:28.788: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:30.786: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:30.833: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:30.833: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:32.830: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:32.876: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:32.876: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:34.872: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:34.920: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:34.920: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:36.915: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:36.965: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:36.965: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:38.959: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:39.010: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:39.011: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:41.002: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:41.053: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:41.054: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:43.045: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:43.094: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:43.097: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:45.088: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:45.137: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:45.139: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:47.132: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:47.208: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:47.208: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:49.175: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:49.253: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:49.253: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:51.176: INFO: Node bootstrap-e2e-minion-group-jt1b didn't reach desired Ready condition status (false) within 2m0s Jan 30 06:09:51.254: INFO: Node bootstrap-e2e-minion-group-j5pg didn't reach desired Ready condition status (false) within 2m0s Jan 30 06:09:51.254: INFO: Node bootstrap-e2e-minion-group-89rb didn't reach desired Ready condition status (false) within 2m0s Jan 30 06:09:51.254: INFO: Node bootstrap-e2e-minion-group-89rb failed reboot test. Jan 30 06:09:51.254: INFO: Node bootstrap-e2e-minion-group-j5pg failed reboot test. Jan 30 06:09:51.254: INFO: Node bootstrap-e2e-minion-group-jt1b failed reboot test. Jan 30 06:09:51.254: INFO: Executing termination hook on nodes Jan 30 06:09:51.254: INFO: Getting external IP address for bootstrap-e2e-minion-group-89rb Jan 30 06:09:51.254: INFO: SSH "cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log" on bootstrap-e2e-minion-group-89rb(34.168.49.142:22) Jan 30 06:10:07.218: INFO: ssh prow@34.168.49.142:22: command: cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log Jan 30 06:10:07.218: INFO: ssh prow@34.168.49.142:22: stdout: "+ sleep 10\n+ true\n+ sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT\n+ break\n+ true\n+ sudo iptables -I OUTPUT 2 -j DROP\n+ break\n+ date\nMon Jan 30 06:08:00 UTC 2023\n+ sleep 120\n+ true\n+ sudo iptables -D OUTPUT -j DROP\n+ break\n+ true\n+ sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT\n+ break\n" Jan 30 06:10:07.218: INFO: ssh prow@34.168.49.142:22: stderr: "" Jan 30 06:10:07.218: INFO: ssh prow@34.168.49.142:22: exit code: 0 Jan 30 06:10:07.218: INFO: Getting external IP address for bootstrap-e2e-minion-group-j5pg Jan 30 06:10:07.218: INFO: SSH "cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log" on bootstrap-e2e-minion-group-j5pg(34.82.243.144:22) Jan 30 06:10:07.742: INFO: ssh prow@34.82.243.144:22: command: cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log Jan 30 06:10:07.742: INFO: ssh prow@34.82.243.144:22: stdout: "+ sleep 10\n+ true\n+ sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT\n+ break\n+ true\n+ sudo iptables -I OUTPUT 2 -j DROP\n+ break\n+ date\nMon Jan 30 06:08:00 UTC 2023\n+ sleep 120\n+ true\n+ sudo iptables -D OUTPUT -j DROP\n+ break\n+ true\n+ sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT\n+ break\n" Jan 30 06:10:07.742: INFO: ssh prow@34.82.243.144:22: stderr: "" Jan 30 06:10:07.742: INFO: ssh prow@34.82.243.144:22: exit code: 0 Jan 30 06:10:07.742: INFO: Getting external IP address for bootstrap-e2e-minion-group-jt1b Jan 30 06:10:07.742: INFO: SSH "cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log" on bootstrap-e2e-minion-group-jt1b(34.83.145.21:22) Jan 30 06:10:08.257: INFO: ssh prow@34.83.145.21:22: command: cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log Jan 30 06:10:08.257: INFO: ssh prow@34.83.145.21:22: stdout: "+ sleep 10\n+ true\n+ sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT\n+ break\n+ true\n+ sudo iptables -I OUTPUT 2 -j DROP\n+ break\n+ date\nMon Jan 30 06:08:00 UTC 2023\n+ sleep 120\n+ true\n+ sudo iptables -D OUTPUT -j DROP\n+ break\n+ true\n+ sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT\n+ break\n" Jan 30 06:10:08.257: INFO: ssh prow@34.83.145.21:22: stderr: "" Jan 30 06:10:08.257: INFO: ssh prow@34.83.145.21:22: exit code: 0 [FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 06:10:08.257 < Exit [It] each node by dropping all outbound packets for a while and ensure they function afterwards - test/e2e/cloud/gcp/reboot.go:144 @ 01/30/23 06:10:08.257 (2m18.165s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:10:08.257 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 06:10:08.257 Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-27hpv to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} FailedMount: MountVolume.SetUp failed for volume "config-volume" : failed to sync configmap cache: timed out waiting for the condition Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 2.636021002s (2.636034032s including waiting) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container coredns Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container coredns Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container coredns Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: Get "http://10.64.3.7:8181/ready": dial tcp 10.64.3.7:8181: connect: connection refused Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: Get "http://10.64.3.12:8181/ready": dial tcp 10.64.3.12:8181: connect: connection refused Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-27hpv_kube-system(d5696a97-0c32-4875-8ac5-fdb1ce1816da) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: Get "http://10.64.3.14:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.14:8080/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-vtndh to bootstrap-e2e-minion-group-jt1b Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 1.034366695s (1.034389733s including waiting) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container coredns Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container coredns Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Stopping container coredns Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.3:8181/ready": dial tcp 10.64.2.3:8181: connect: connection refused Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.5:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-vtndh_kube-system(9c9e7a94-38c6-4663-8f82-43b74a199e59) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.6:8181/ready": dial tcp 10.64.2.6:8181: i/o timeout (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.6:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f: {replicaset-controller } FailedCreate: Error creating: insufficient quota to match these scopes: [{PriorityClass In [system-node-critical system-cluster-critical]}] Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-27hpv Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-vtndh Jan 30 06:10:08.308: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 1 Jan 30 06:10:08.308: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 2 from 1 Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container etcd-container Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container etcd-container Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container etcd-container Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe errored: rpc error: code = Unknown desc = failed to exec in container: container is in CONTAINER_EXITED state Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/etcd:3.5.7-0" already present on machine Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container etcd-container in pod etcd-server-bootstrap-e2e-master_kube-system(2ef2f0d9ccfe01aa3c1d26059de8a300) Jan 30 06:10:08.308: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_2e2da became leader Jan 30 06:10:08.308: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_7c8d0 became leader Jan 30 06:10:08.308: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_1ffa4 became leader Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-lsjtz to bootstrap-e2e-minion-group-jt1b Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 664.348201ms (664.364985ms including waiting) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Stopping container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Liveness probe failed: Get "http://10.64.2.4:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-sv2mg to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 2.45385434s (2.453864342s including waiting) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.5:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.19:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-vpdtl to bootstrap-e2e-minion-group-89rb Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 657.450417ms (657.460286ms including waiting) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Liveness probe failed: Get "http://10.64.1.5:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Failed: Error: failed to get sandbox container task: no running task found: task 38160c3af9302d8f890a71a78eed322e52a69e59da84d5a3ca773407ab029cd1 not found: not found Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-vpdtl_kube-system(73c6f815-a15e-4e7a-a972-20e282f676c0) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-sv2mg Jan 30 06:10:08.308: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-vpdtl Jan 30 06:10:08.308: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-lsjtz Jan 30 06:10:08.308: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-addon-manager Jan 30 06:10:08.308: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-addon-manager Jan 30 06:10:08.308: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-addon-manager Jan 30 06:10:08.308: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/addon-manager/kube-addon-manager:v9.1.6" already present on machine Jan 30 06:10:08.308: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 06:10:08.308: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/kube-controller-manager-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:10:08.308: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-controller-manager Jan 30 06:10:08.308: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-controller-manager Jan 30 06:10:08.308: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-controller-manager Jan 30 06:10:08.308: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container kube-controller-manager in pod kube-controller-manager-bootstrap-e2e-master_kube-system(4fc5a5aeac3c203e3876adb08d878c93) Jan 30 06:10:08.308: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_c4dee0f1-ebbd-431b-a4f5-cdaba3338ff1 became leader Jan 30 06:10:08.308: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_6a930d5c-d857-45d7-8821-ab6144cfb617 became leader Jan 30 06:10:08.308: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_52b92c73-5b92-4994-9104-bec143d48796 became leader Jan 30 06:10:08.308: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_24f84219-2bae-4a66-bead-e8bbaf2fb7a6 became leader Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-dns-autoscaler-5f6455f985-bg4vb to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" in 2.01573763s (2.015748792s including waiting) Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container autoscaler Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container autoscaler Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container autoscaler Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" already present on machine Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container autoscaler in pod kube-dns-autoscaler-5f6455f985-bg4vb_kube-system(d17909b1-64e2-475c-a08b-b40ba36f6afa) Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985: {replicaset-controller } FailedCreate: Error creating: pods "kube-dns-autoscaler-5f6455f985-" is forbidden: error looking up service account kube-system/kube-dns-autoscaler: serviceaccount "kube-dns-autoscaler" not found Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985: {replicaset-controller } SuccessfulCreate: Created pod: kube-dns-autoscaler-5f6455f985-bg4vb Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler: {deployment-controller } ScalingReplicaSet: Scaled up replica set kube-dns-autoscaler-5f6455f985 to 1 Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-89rb_kube-system(a86edc08c98ce4fefed543ad485600a4) Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-j5pg_kube-system(adff6fb483f7c9e3d86fb4cb79733a2e) Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Stopping container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-jt1b_kube-system(87a78f5a508a69cfa60729c5d4dc7da6) Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/kube-scheduler-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-scheduler Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-scheduler Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container kube-scheduler in pod kube-scheduler-bootstrap-e2e-master_kube-system(5b3c0a3dad3d723f9e5778ab0a62849c) Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-scheduler Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe failed: Get "https://127.0.0.1:10259/healthz": dial tcp 127.0.0.1:10259: connect: connection refused Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_18ee2297-5499-4a10-b782-8bf60ef964f2 became leader Jan 30 06:10:08.308: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_959dc035-06e0-4f47-9fbb-6328d3119de5 became leader Jan 30 06:10:08.308: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_36535314-0b8e-4eff-a7de-1c139a5f4105 became leader Jan 30 06:10:08.308: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_8d92bf3b-8542-4829-90e1-576b213e261b became leader Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {default-scheduler } Scheduled: Successfully assigned kube-system/l7-default-backend-8549d69d99-slz4q to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" in 2.282907597s (2.282919912s including waiting) Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container default-http-backend Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container default-http-backend Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.4:8080/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Container default-http-backend failed liveness probe, will be restarted Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99: {replicaset-controller } SuccessfulCreate: Created pod: l7-default-backend-8549d69d99-slz4q Jan 30 06:10:08.308: INFO: event for l7-default-backend: {deployment-controller } ScalingReplicaSet: Scaled up replica set l7-default-backend-8549d69d99 to 1 Jan 30 06:10:08.308: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container l7-lb-controller Jan 30 06:10:08.308: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container l7-lb-controller Jan 30 06:10:08.308: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "gcr.io/k8s-ingress-image-push/ingress-gce-glbc-amd64:v1.20.1" already present on machine Jan 30 06:10:08.308: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container l7-lb-controller in pod l7-lb-controller-bootstrap-e2e-master_kube-system(f922c87738da4b787ed79e8be7ae0573) Jan 30 06:10:08.308: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe failed: Get "http://10.138.0.2:8086/healthz": dial tcp 10.138.0.2:8086: connect: connection refused Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-4glfd to bootstrap-e2e-minion-group-89rb Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 743.096978ms (743.138916ms including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.911633038s (1.911644632s including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-4rnk7 to bootstrap-e2e-master Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 751.7056ms (751.711494ms including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Failed: Error: services have not yet been read at least once, cannot construct envvars Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.335358551s (2.33536641s including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Created: Created container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Started: Started container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Created: Created container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Started: Started container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-srxc6 to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 804.763467ms (804.774083ms including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.089844613s (2.089864707s including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-zckpq to bootstrap-e2e-minion-group-jt1b Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 842.219895ms (842.229354ms including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.054812451s (2.054822588s including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-4rnk7 Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-4glfd Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-zckpq Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-srxc6 Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-6764bf875c-vbxz7 to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} FailedMount: MountVolume.SetUp failed for volume "metrics-server-config-volume" : failed to sync configmap cache: timed out waiting for the condition Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 3.531930568s (3.532067103s including waiting) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container metrics-server Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container metrics-server Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 1.812865403s (1.812874646s including waiting) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container metrics-server-nanny Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container metrics-server-nanny Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container metrics-server Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container metrics-server-nanny Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-6764bf875c-vbxz7 Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulDelete: Deleted pod: metrics-server-v0.5.2-6764bf875c-vbxz7 Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-867b8754b9-s79bn to bootstrap-e2e-minion-group-89rb Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 1.367491088s (1.367525697s including waiting) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container metrics-server Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container metrics-server Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 1.035914064s (1.035929902s including waiting) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container metrics-server-nanny Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container metrics-server-nanny Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Readiness probe failed: Get "https://10.64.1.3:10250/readyz": dial tcp 10.64.1.3:10250: connect: connection refused Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Liveness probe failed: Get "https://10.64.1.3:10250/livez": dial tcp 10.64.1.3:10250: connect: connection refused Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Liveness probe failed: Get "https://10.64.1.3:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Readiness probe failed: Get "https://10.64.1.3:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container metrics-server Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container metrics-server-nanny Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Readiness probe failed: Get "https://10.64.1.4:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-867b8754b9-s79bn Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-v0.5.2-6764bf875c to 1 Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-v0.5.2-867b8754b9 to 1 Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled down replica set metrics-server-v0.5.2-6764bf875c to 0 from 1 Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {default-scheduler } Scheduled: Successfully assigned kube-system/volume-snapshot-controller-0 to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" in 1.683320982s (1.68333161s including waiting) Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container volume-snapshot-controller Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container volume-snapshot-controller Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container volume-snapshot-controller Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(694587fc-d43c-43bc-bbab-563d942a4f03) Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller: {statefulset-controller } SuccessfulCreate: create Pod volume-snapshot-controller-0 in StatefulSet volume-snapshot-controller successful < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:10:08.308 (51ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:10:08.308 Jan 30 06:10:08.308: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 30 06:10:08.352: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:10:10.396: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:10:12.395 (4.087s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 06:10:12.395 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 06:10:12.395 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:10:12.395 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:10:12.395 STEP: Collecting events from namespace "reboot-3328". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 06:10:12.395 STEP: Found 0 events. - test/e2e/framework/debug/dump.go:46 @ 01/30/23 06:10:12.439 Jan 30 06:10:12.481: INFO: POD NODE PHASE GRACE CONDITIONS Jan 30 06:10:12.481: INFO: Jan 30 06:10:12.526: INFO: Logging node info for node bootstrap-e2e-master Jan 30 06:10:12.568: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-master da42dd0c-bb3c-402f-847c-793de73fb287 1204 0 2023-01-30 06:04:10 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-1 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-master kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-1 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:10 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{},"f:unschedulable":{}}} } {kube-controller-manager Update v1 2023-01-30 06:04:27 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.0.0/24\"":{}},"f:taints":{}}} } {kube-controller-manager Update v1 2023-01-30 06:04:27 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kubelet Update v1 2023-01-30 06:09:37 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:10.64.0.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-master,Unschedulable:true,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:<nil>,},Taint{Key:node.kubernetes.io/unschedulable,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[10.64.0.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{1 0} {<nil>} 1 DecimalSI},ephemeral-storage: {{16656896000 0} {<nil>} 16266500Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3858370560 0} {<nil>} 3767940Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{1 0} {<nil>} 1 DecimalSI},ephemeral-storage: {{14991206376 0} {<nil>} 14991206376 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3596226560 0} {<nil>} 3511940Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:10 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:10 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:10 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:14 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.2,},NodeAddress{Type:ExternalIP,Address:34.145.121.12,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-master.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-master.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ceaf667f6b5e1324cd116eb2db802512,SystemUUID:ceaf667f-6b5e-1324-cd11-6eb2db802512,BootID:f3af49de-86af-4adc-82a1-ca040b706b59,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-apiserver-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:135961043,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:125279033,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:51eae8381dcb1078289fa7b4f3df2630cdc18d09fb56f8e56b41c40e191d6c83 registry.k8s.io/etcd:3.5.7-0],SizeBytes:101639218,},ContainerImage{Names:[registry.k8s.io/kube-scheduler-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:57551672,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[gcr.io/k8s-ingress-image-push/ingress-gce-glbc-amd64@sha256:5db27383add6d9f4ebdf0286409ac31f7f5d273690204b341a4e37998917693b gcr.io/k8s-ingress-image-push/ingress-gce-glbc-amd64:v1.20.1],SizeBytes:36598135,},ContainerImage{Names:[registry.k8s.io/addon-manager/kube-addon-manager@sha256:49cc4e6e4a3745b427ce14b0141476ab339bb65c6bc05033019e046c8727dcb0 registry.k8s.io/addon-manager/kube-addon-manager:v9.1.6],SizeBytes:30464183,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-server@sha256:b1389e7014425a1752aac55f5043ef4c52edaef0e223bf4d48ed1324e298087c registry.k8s.io/kas-network-proxy/proxy-server:v0.1.1],SizeBytes:21875112,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:10:12.569: INFO: Logging kubelet events for node bootstrap-e2e-master Jan 30 06:10:12.613: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-master Jan 30 06:10:12.669: INFO: kube-addon-manager-bootstrap-e2e-master started at 2023-01-30 06:03:43 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container kube-addon-manager ready: true, restart count 1 Jan 30 06:10:12.669: INFO: konnectivity-server-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container konnectivity-server-container ready: true, restart count 0 Jan 30 06:10:12.669: INFO: kube-controller-manager-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container kube-controller-manager ready: true, restart count 4 Jan 30 06:10:12.669: INFO: etcd-server-events-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container etcd-container ready: true, restart count 0 Jan 30 06:10:12.669: INFO: l7-lb-controller-bootstrap-e2e-master started at 2023-01-30 06:03:43 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container l7-lb-controller ready: true, restart count 4 Jan 30 06:10:12.669: INFO: metadata-proxy-v0.1-4rnk7 started at 2023-01-30 06:04:10 +0000 UTC (0+2 container statuses recorded) Jan 30 06:10:12.669: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:10:12.669: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:10:12.669: INFO: kube-apiserver-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container kube-apiserver ready: true, restart count 0 Jan 30 06:10:12.669: INFO: etcd-server-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container etcd-container ready: true, restart count 2 Jan 30 06:10:12.669: INFO: kube-scheduler-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container kube-scheduler ready: true, restart count 3 Jan 30 06:10:12.866: INFO: Latency metrics for node bootstrap-e2e-master Jan 30 06:10:12.866: INFO: Logging node info for node bootstrap-e2e-minion-group-89rb Jan 30 06:10:12.908: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-89rb 7a6374a4-18c6-4a29-8950-b11b5056de6e 1336 0 2023-01-30 06:04:12 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-2 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-minion-group-89rb kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-2 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.1.0/24\"":{}}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kubelet Update v1 2023-01-30 06:10:01 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status} {node-problem-detector Update v1 2023-01-30 06:10:03 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.1.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-minion-group-89rb,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.1.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815430144 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553286144 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.5,},NodeAddress{Type:ExternalIP,Address:34.168.49.142,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-89rb.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-89rb.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:a886a977671560a8ccd3c81c9111e6c4,SystemUUID:a886a977-6715-60a8-ccd3-c81c9111e6c4,BootID:2435cf70-73c9-4f65-bb5d-1b1f7ed9a49e,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:66988744,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[registry.k8s.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 registry.k8s.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[registry.k8s.io/autoscaling/addon-resizer@sha256:43f129b81d28f0fdd54de6d8e7eacd5728030782e03db16087fc241ad747d3d6 registry.k8s.io/autoscaling/addon-resizer:1.8.14],SizeBytes:10153852,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-agent@sha256:939c42e815e6b6af3181f074652c0d18fe429fcee9b49c1392aee7e92887cfef registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1],SizeBytes:8364694,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:10:12.909: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-89rb Jan 30 06:10:12.952: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-89rb Jan 30 06:10:13.013: INFO: kube-proxy-bootstrap-e2e-minion-group-89rb started at 2023-01-30 06:04:12 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.013: INFO: Container kube-proxy ready: true, restart count 3 Jan 30 06:10:13.013: INFO: metadata-proxy-v0.1-4glfd started at 2023-01-30 06:04:13 +0000 UTC (0+2 container statuses recorded) Jan 30 06:10:13.013: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:10:13.013: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:10:13.013: INFO: konnectivity-agent-vpdtl started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.013: INFO: Container konnectivity-agent ready: true, restart count 2 Jan 30 06:10:13.013: INFO: metrics-server-v0.5.2-867b8754b9-s79bn started at 2023-01-30 06:04:46 +0000 UTC (0+2 container statuses recorded) Jan 30 06:10:13.013: INFO: Container metrics-server ready: false, restart count 4 Jan 30 06:10:13.013: INFO: Container metrics-server-nanny ready: true, restart count 1 Jan 30 06:10:13.185: INFO: Latency metrics for node bootstrap-e2e-minion-group-89rb Jan 30 06:10:13.185: INFO: Logging node info for node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:13.230: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-j5pg 77296218-aa10-476d-a138-052026f8f306 1359 0 2023-01-30 06:04:14 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-2 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-minion-group-j5pg kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-2 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.3.0/24\"":{}}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {node-problem-detector Update v1 2023-01-30 06:10:05 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-30 06:10:10 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:10.64.3.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-minion-group-j5pg,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.3.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815438336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553294336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.3,},NodeAddress{Type:ExternalIP,Address:34.82.243.144,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-j5pg.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-j5pg.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:00c00596a04cd69c19526ec9065fe3a0,SystemUUID:00c00596-a04c-d69c-1952-6ec9065fe3a0,BootID:8b0896f1-a065-4ffa-97fa-b74f7309fbf4,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:66988744,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[registry.k8s.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 registry.k8s.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[registry.k8s.io/sig-storage/snapshot-controller@sha256:823c75d0c45d1427f6d850070956d9ca657140a7bbf828381541d1d808475280 registry.k8s.io/sig-storage/snapshot-controller:v6.1.0],SizeBytes:22620891,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/cpa/cluster-proportional-autoscaler@sha256:fd636b33485c7826fb20ef0688a83ee0910317dbb6c0c6f3ad14661c1db25def registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4],SizeBytes:15209393,},ContainerImage{Names:[registry.k8s.io/autoscaling/addon-resizer@sha256:43f129b81d28f0fdd54de6d8e7eacd5728030782e03db16087fc241ad747d3d6 registry.k8s.io/autoscaling/addon-resizer:1.8.14],SizeBytes:10153852,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-agent@sha256:939c42e815e6b6af3181f074652c0d18fe429fcee9b49c1392aee7e92887cfef registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1],SizeBytes:8364694,},ContainerImage{Names:[registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64@sha256:7eb7b3cee4d33c10c49893ad3c386232b86d4067de5251294d4c620d6e072b93 registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11],SizeBytes:6463068,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:10:13.230: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:13.274: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:13.339: INFO: l7-default-backend-8549d69d99-slz4q started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.339: INFO: Container default-http-backend ready: true, restart count 1 Jan 30 06:10:13.339: INFO: volume-snapshot-controller-0 started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.339: INFO: Container volume-snapshot-controller ready: true, restart count 5 Jan 30 06:10:13.339: INFO: konnectivity-agent-sv2mg started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.339: INFO: Container konnectivity-agent ready: true, restart count 3 Jan 30 06:10:13.339: INFO: kube-proxy-bootstrap-e2e-minion-group-j5pg started at 2023-01-30 06:04:14 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.339: INFO: Container kube-proxy ready: true, restart count 2 Jan 30 06:10:13.339: INFO: metadata-proxy-v0.1-srxc6 started at 2023-01-30 06:04:15 +0000 UTC (0+2 container statuses recorded) Jan 30 06:10:13.339: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:10:13.339: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:10:13.339: INFO: kube-dns-autoscaler-5f6455f985-bg4vb started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.339: INFO: Container autoscaler ready: true, restart count 4 Jan 30 06:10:13.339: INFO: coredns-6846b5b5f-27hpv started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.339: INFO: Container coredns ready: true, restart count 3 Jan 30 06:10:13.541: INFO: Latency metrics for node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:13.541: INFO: Logging node info for node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:13.584: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-jt1b 9c9847ba-4388-4123-89c6-52ccc637e6c3 1337 0 2023-01-30 06:04:14 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-2 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-minion-group-jt1b kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-2 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.2.0/24\"":{}}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kubelet Update v1 2023-01-30 06:10:01 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status} {node-problem-detector Update v1 2023-01-30 06:10:03 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.2.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-minion-group-jt1b,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.2.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815438336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553294336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.4,},NodeAddress{Type:ExternalIP,Address:34.83.145.21,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-jt1b.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-jt1b.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:a84e7124d1b77ea5a363b5b4e806099f,SystemUUID:a84e7124-d1b7-7ea5-a363-b5b4e806099f,BootID:c2771298-b9a1-4721-be1f-55ff63f4a2d8,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:66988744,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-agent@sha256:939c42e815e6b6af3181f074652c0d18fe429fcee9b49c1392aee7e92887cfef registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1],SizeBytes:8364694,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:10:13.584: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:13.631: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:13.706: INFO: kube-proxy-bootstrap-e2e-minion-group-jt1b started at 2023-01-30 06:04:14 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.706: INFO: Container kube-proxy ready: true, restart count 3 Jan 30 06:10:13.706: INFO: metadata-proxy-v0.1-zckpq started at 2023-01-30 06:04:14 +0000 UTC (0+2 container statuses recorded) Jan 30 06:10:13.706: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:10:13.706: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:10:13.706: INFO: konnectivity-agent-lsjtz started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.706: INFO: Container konnectivity-agent ready: true, restart count 3 Jan 30 06:10:13.706: INFO: coredns-6846b5b5f-vtndh started at 2023-01-30 06:04:32 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.706: INFO: Container coredns ready: false, restart count 2 Jan 30 06:10:13.887: INFO: Latency metrics for node bootstrap-e2e-minion-group-jt1b END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:10:13.887 (1.492s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:10:13.887 (1.492s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:10:13.887 STEP: Destroying namespace "reboot-3328" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 06:10:13.888 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:10:13.931 (43ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:10:13.931 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:10:13.931 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sdropping\sall\soutbound\spackets\sfor\sa\swhile\sand\sensure\sthey\sfunction\safterwards$'
[FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 06:10:08.257from junit_01.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:07:49.803 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:07:49.803 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:07:49.803 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 06:07:49.803 Jan 30 06:07:49.803: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 06:07:49.805 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/30/23 06:07:49.931 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/30/23 06:07:50.012 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:07:50.092 (289ms) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 06:07:50.092 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 06:07:50.092 (0s) > Enter [It] each node by dropping all outbound packets for a while and ensure they function afterwards - test/e2e/cloud/gcp/reboot.go:144 @ 01/30/23 06:07:50.092 Jan 30 06:07:50.186: INFO: Getting bootstrap-e2e-minion-group-j5pg Jan 30 06:07:50.186: INFO: Getting bootstrap-e2e-minion-group-89rb Jan 30 06:07:50.186: INFO: Getting bootstrap-e2e-minion-group-jt1b Jan 30 06:07:50.261: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-89rb condition Ready to be true Jan 30 06:07:50.262: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-j5pg condition Ready to be true Jan 30 06:07:50.262: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-jt1b condition Ready to be true Jan 30 06:07:50.305: INFO: Node bootstrap-e2e-minion-group-j5pg has 4 assigned pods with no liveness probes: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:07:50.305: INFO: Node bootstrap-e2e-minion-group-89rb has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-4glfd" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-89rb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-bg4vb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.305: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-srxc6" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.306: INFO: Node bootstrap-e2e-minion-group-jt1b has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:07:50.306: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:07:50.306: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-zckpq" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.306: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-jt1b" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:07:50.347: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 42.631446ms Jan 30 06:07:50.347: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.352: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb": Phase="Running", Reason="", readiness=true. Elapsed: 46.902453ms Jan 30 06:07:50.352: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.353: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg": Phase="Running", Reason="", readiness=true. Elapsed: 48.235213ms Jan 30 06:07:50.353: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.353: INFO: Pod "metadata-proxy-v0.1-srxc6": Phase="Running", Reason="", readiness=true. Elapsed: 48.294842ms Jan 30 06:07:50.353: INFO: Pod "metadata-proxy-v0.1-srxc6" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.353: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: true. Pods: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:07:50.353: INFO: Getting external IP address for bootstrap-e2e-minion-group-j5pg Jan 30 06:07:50.353: INFO: SSH "\n\t\tnohup sh -c '\n\t\t\tset -x\n\t\t\tsleep 10\n\t\t\twhile true; do sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT && break; done\n\t\t\twhile true; do sudo iptables -I OUTPUT 2 -j DROP && break; done\n\t\t\tdate\n\t\t\tsleep 120\n\t\t\twhile true; do sudo iptables -D OUTPUT -j DROP && break; done\n\t\t\twhile true; do sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT && break; done\n\t\t' >/tmp/drop-outbound.log 2>&1 &\n\t\t" on bootstrap-e2e-minion-group-j5pg(34.82.243.144:22) Jan 30 06:07:50.357: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb": Phase="Running", Reason="", readiness=true. Elapsed: 52.271274ms Jan 30 06:07:50.357: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.357: INFO: Pod "metadata-proxy-v0.1-4glfd": Phase="Running", Reason="", readiness=true. Elapsed: 52.46078ms Jan 30 06:07:50.357: INFO: Pod "metadata-proxy-v0.1-4glfd" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.357: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:07:50.357: INFO: Getting external IP address for bootstrap-e2e-minion-group-89rb Jan 30 06:07:50.357: INFO: SSH "\n\t\tnohup sh -c '\n\t\t\tset -x\n\t\t\tsleep 10\n\t\t\twhile true; do sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT && break; done\n\t\t\twhile true; do sudo iptables -I OUTPUT 2 -j DROP && break; done\n\t\t\tdate\n\t\t\tsleep 120\n\t\t\twhile true; do sudo iptables -D OUTPUT -j DROP && break; done\n\t\t\twhile true; do sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT && break; done\n\t\t' >/tmp/drop-outbound.log 2>&1 &\n\t\t" on bootstrap-e2e-minion-group-89rb(34.168.49.142:22) Jan 30 06:07:50.359: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=true. Elapsed: 53.257423ms Jan 30 06:07:50.359: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.359: INFO: Pod "metadata-proxy-v0.1-zckpq": Phase="Running", Reason="", readiness=true. Elapsed: 53.488892ms Jan 30 06:07:50.359: INFO: Pod "metadata-proxy-v0.1-zckpq" satisfied condition "running and ready, or succeeded" Jan 30 06:07:50.359: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:07:50.359: INFO: Getting external IP address for bootstrap-e2e-minion-group-jt1b Jan 30 06:07:50.359: INFO: SSH "\n\t\tnohup sh -c '\n\t\t\tset -x\n\t\t\tsleep 10\n\t\t\twhile true; do sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT && break; done\n\t\t\twhile true; do sudo iptables -I OUTPUT 2 -j DROP && break; done\n\t\t\tdate\n\t\t\tsleep 120\n\t\t\twhile true; do sudo iptables -D OUTPUT -j DROP && break; done\n\t\t\twhile true; do sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT && break; done\n\t\t' >/tmp/drop-outbound.log 2>&1 &\n\t\t" on bootstrap-e2e-minion-group-jt1b(34.83.145.21:22) Jan 30 06:07:50.878: INFO: ssh prow@34.82.243.144:22: command: nohup sh -c ' set -x sleep 10 while true; do sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT && break; done while true; do sudo iptables -I OUTPUT 2 -j DROP && break; done date sleep 120 while true; do sudo iptables -D OUTPUT -j DROP && break; done while true; do sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT && break; done ' >/tmp/drop-outbound.log 2>&1 & Jan 30 06:07:50.878: INFO: ssh prow@34.82.243.144:22: stdout: "" Jan 30 06:07:50.878: INFO: ssh prow@34.82.243.144:22: stderr: "" Jan 30 06:07:50.878: INFO: ssh prow@34.82.243.144:22: exit code: 0 Jan 30 06:07:50.878: INFO: ssh prow@34.83.145.21:22: command: nohup sh -c ' set -x sleep 10 while true; do sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT && break; done while true; do sudo iptables -I OUTPUT 2 -j DROP && break; done date sleep 120 while true; do sudo iptables -D OUTPUT -j DROP && break; done while true; do sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT && break; done ' >/tmp/drop-outbound.log 2>&1 & Jan 30 06:07:50.878: INFO: ssh prow@34.83.145.21:22: stdout: "" Jan 30 06:07:50.878: INFO: ssh prow@34.83.145.21:22: stderr: "" Jan 30 06:07:50.878: INFO: ssh prow@34.83.145.21:22: exit code: 0 Jan 30 06:07:50.878: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-j5pg condition Ready to be false Jan 30 06:07:50.878: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-jt1b condition Ready to be false Jan 30 06:07:50.886: INFO: ssh prow@34.168.49.142:22: command: nohup sh -c ' set -x sleep 10 while true; do sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT && break; done while true; do sudo iptables -I OUTPUT 2 -j DROP && break; done date sleep 120 while true; do sudo iptables -D OUTPUT -j DROP && break; done while true; do sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT && break; done ' >/tmp/drop-outbound.log 2>&1 & Jan 30 06:07:50.886: INFO: ssh prow@34.168.49.142:22: stdout: "" Jan 30 06:07:50.886: INFO: ssh prow@34.168.49.142:22: stderr: "" Jan 30 06:07:50.886: INFO: ssh prow@34.168.49.142:22: exit code: 0 Jan 30 06:07:50.886: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-89rb condition Ready to be false Jan 30 06:07:50.923: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:07:50.923: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:07:50.928: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:07:52.966: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:07:52.966: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:07:52.970: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:11.060: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:11.060: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:11.060: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:13.104: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:13.104: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:13.104: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:15.148: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:15.149: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:15.149: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:17.207: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:17.207: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:17.207: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:19.252: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:19.252: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:19.252: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:21.296: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:21.299: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:21.299: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:23.339: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:23.343: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:23.343: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:25.382: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:25.388: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:25.388: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:27.425: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:27.438: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:27.438: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:29.469: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:29.482: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:29.482: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:31.514: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:31.526: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:31.526: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:33.557: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:33.569: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:33.569: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:35.601: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:35.612: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:35.612: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:37.644: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:37.657: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:37.657: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:39.686: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:39.701: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:39.701: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:41.731: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:41.746: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:41.746: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:43.773: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:43.790: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:43.790: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:45.819: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:45.836: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:45.836: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:47.862: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:47.880: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:47.880: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:49.905: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:49.923: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:49.923: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:51.948: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:51.966: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:51.967: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:53.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:54.010: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:54.010: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:56.032: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:56.055: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:56.055: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:58.075: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:58.098: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:08:58.098: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:00.118: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:00.143: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:00.143: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:02.161: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:02.206: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:02.206: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:04.205: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:04.250: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:04.250: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:06.249: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:06.294: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:06.294: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:08.292: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:08.337: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:08.337: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:10.336: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:10.385: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:10.385: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:12.380: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:12.429: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:12.429: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:14.423: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:14.473: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:14.473: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:16.465: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:16.516: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:16.516: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:18.527: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:18.561: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:18.561: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:20.569: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:20.605: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:20.605: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:22.614: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:22.651: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:22.651: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:24.657: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:24.698: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:24.698: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:26.699: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:26.743: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:26.743: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:28.744: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:28.788: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:28.788: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:30.786: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:30.833: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:30.833: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:32.830: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:32.876: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:32.876: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:34.872: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:34.920: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:34.920: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:36.915: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:36.965: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:36.965: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:38.959: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:39.010: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:39.011: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:41.002: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:41.053: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:41.054: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:43.045: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:43.094: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:43.097: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:45.088: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:45.137: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:45.139: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:47.132: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:47.208: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:47.208: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:49.175: INFO: Condition Ready of node bootstrap-e2e-minion-group-jt1b is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:49.253: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:49.253: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:09:51.176: INFO: Node bootstrap-e2e-minion-group-jt1b didn't reach desired Ready condition status (false) within 2m0s Jan 30 06:09:51.254: INFO: Node bootstrap-e2e-minion-group-j5pg didn't reach desired Ready condition status (false) within 2m0s Jan 30 06:09:51.254: INFO: Node bootstrap-e2e-minion-group-89rb didn't reach desired Ready condition status (false) within 2m0s Jan 30 06:09:51.254: INFO: Node bootstrap-e2e-minion-group-89rb failed reboot test. Jan 30 06:09:51.254: INFO: Node bootstrap-e2e-minion-group-j5pg failed reboot test. Jan 30 06:09:51.254: INFO: Node bootstrap-e2e-minion-group-jt1b failed reboot test. Jan 30 06:09:51.254: INFO: Executing termination hook on nodes Jan 30 06:09:51.254: INFO: Getting external IP address for bootstrap-e2e-minion-group-89rb Jan 30 06:09:51.254: INFO: SSH "cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log" on bootstrap-e2e-minion-group-89rb(34.168.49.142:22) Jan 30 06:10:07.218: INFO: ssh prow@34.168.49.142:22: command: cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log Jan 30 06:10:07.218: INFO: ssh prow@34.168.49.142:22: stdout: "+ sleep 10\n+ true\n+ sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT\n+ break\n+ true\n+ sudo iptables -I OUTPUT 2 -j DROP\n+ break\n+ date\nMon Jan 30 06:08:00 UTC 2023\n+ sleep 120\n+ true\n+ sudo iptables -D OUTPUT -j DROP\n+ break\n+ true\n+ sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT\n+ break\n" Jan 30 06:10:07.218: INFO: ssh prow@34.168.49.142:22: stderr: "" Jan 30 06:10:07.218: INFO: ssh prow@34.168.49.142:22: exit code: 0 Jan 30 06:10:07.218: INFO: Getting external IP address for bootstrap-e2e-minion-group-j5pg Jan 30 06:10:07.218: INFO: SSH "cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log" on bootstrap-e2e-minion-group-j5pg(34.82.243.144:22) Jan 30 06:10:07.742: INFO: ssh prow@34.82.243.144:22: command: cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log Jan 30 06:10:07.742: INFO: ssh prow@34.82.243.144:22: stdout: "+ sleep 10\n+ true\n+ sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT\n+ break\n+ true\n+ sudo iptables -I OUTPUT 2 -j DROP\n+ break\n+ date\nMon Jan 30 06:08:00 UTC 2023\n+ sleep 120\n+ true\n+ sudo iptables -D OUTPUT -j DROP\n+ break\n+ true\n+ sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT\n+ break\n" Jan 30 06:10:07.742: INFO: ssh prow@34.82.243.144:22: stderr: "" Jan 30 06:10:07.742: INFO: ssh prow@34.82.243.144:22: exit code: 0 Jan 30 06:10:07.742: INFO: Getting external IP address for bootstrap-e2e-minion-group-jt1b Jan 30 06:10:07.742: INFO: SSH "cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log" on bootstrap-e2e-minion-group-jt1b(34.83.145.21:22) Jan 30 06:10:08.257: INFO: ssh prow@34.83.145.21:22: command: cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log Jan 30 06:10:08.257: INFO: ssh prow@34.83.145.21:22: stdout: "+ sleep 10\n+ true\n+ sudo iptables -I OUTPUT 1 -s 127.0.0.1 -j ACCEPT\n+ break\n+ true\n+ sudo iptables -I OUTPUT 2 -j DROP\n+ break\n+ date\nMon Jan 30 06:08:00 UTC 2023\n+ sleep 120\n+ true\n+ sudo iptables -D OUTPUT -j DROP\n+ break\n+ true\n+ sudo iptables -D OUTPUT -s 127.0.0.1 -j ACCEPT\n+ break\n" Jan 30 06:10:08.257: INFO: ssh prow@34.83.145.21:22: stderr: "" Jan 30 06:10:08.257: INFO: ssh prow@34.83.145.21:22: exit code: 0 [FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 06:10:08.257 < Exit [It] each node by dropping all outbound packets for a while and ensure they function afterwards - test/e2e/cloud/gcp/reboot.go:144 @ 01/30/23 06:10:08.257 (2m18.165s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:10:08.257 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 06:10:08.257 Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-27hpv to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} FailedMount: MountVolume.SetUp failed for volume "config-volume" : failed to sync configmap cache: timed out waiting for the condition Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 2.636021002s (2.636034032s including waiting) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container coredns Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container coredns Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container coredns Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: Get "http://10.64.3.7:8181/ready": dial tcp 10.64.3.7:8181: connect: connection refused Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: Get "http://10.64.3.12:8181/ready": dial tcp 10.64.3.12:8181: connect: connection refused Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-27hpv_kube-system(d5696a97-0c32-4875-8ac5-fdb1ce1816da) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: Get "http://10.64.3.14:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.14:8080/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-27hpv: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-vtndh to bootstrap-e2e-minion-group-jt1b Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 1.034366695s (1.034389733s including waiting) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container coredns Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container coredns Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Stopping container coredns Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.3:8181/ready": dial tcp 10.64.2.3:8181: connect: connection refused Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.5:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-vtndh_kube-system(9c9e7a94-38c6-4663-8f82-43b74a199e59) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.6:8181/ready": dial tcp 10.64.2.6:8181: i/o timeout (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Readiness probe failed: Get "http://10.64.2.6:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f-vtndh: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f: {replicaset-controller } FailedCreate: Error creating: insufficient quota to match these scopes: [{PriorityClass In [system-node-critical system-cluster-critical]}] Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-27hpv Jan 30 06:10:08.308: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-vtndh Jan 30 06:10:08.308: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 1 Jan 30 06:10:08.308: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 2 from 1 Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container etcd-container Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container etcd-container Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container etcd-container Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe errored: rpc error: code = Unknown desc = failed to exec in container: container is in CONTAINER_EXITED state Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/etcd:3.5.7-0" already present on machine Jan 30 06:10:08.308: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container etcd-container in pod etcd-server-bootstrap-e2e-master_kube-system(2ef2f0d9ccfe01aa3c1d26059de8a300) Jan 30 06:10:08.308: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_2e2da became leader Jan 30 06:10:08.308: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_7c8d0 became leader Jan 30 06:10:08.308: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_1ffa4 became leader Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-lsjtz to bootstrap-e2e-minion-group-jt1b Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 664.348201ms (664.364985ms including waiting) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Stopping container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Unhealthy: Liveness probe failed: Get "http://10.64.2.4:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 06:10:08.308: INFO: event for konnectivity-agent-lsjtz: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-sv2mg to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 2.45385434s (2.453864342s including waiting) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.5:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.19:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-sv2mg: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-vpdtl to bootstrap-e2e-minion-group-89rb Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 657.450417ms (657.460286ms including waiting) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container konnectivity-agent Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Liveness probe failed: Get "http://10.64.1.5:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} Failed: Error: failed to get sandbox container task: no running task found: task 38160c3af9302d8f890a71a78eed322e52a69e59da84d5a3ca773407ab029cd1 not found: not found Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {kubelet bootstrap-e2e-minion-group-89rb} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-vpdtl_kube-system(73c6f815-a15e-4e7a-a972-20e282f676c0) Jan 30 06:10:08.308: INFO: event for konnectivity-agent-vpdtl: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-sv2mg Jan 30 06:10:08.308: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-vpdtl Jan 30 06:10:08.308: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-lsjtz Jan 30 06:10:08.308: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-addon-manager Jan 30 06:10:08.308: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-addon-manager Jan 30 06:10:08.308: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-addon-manager Jan 30 06:10:08.308: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/addon-manager/kube-addon-manager:v9.1.6" already present on machine Jan 30 06:10:08.308: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 06:10:08.308: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/kube-controller-manager-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:10:08.308: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-controller-manager Jan 30 06:10:08.308: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-controller-manager Jan 30 06:10:08.308: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-controller-manager Jan 30 06:10:08.308: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container kube-controller-manager in pod kube-controller-manager-bootstrap-e2e-master_kube-system(4fc5a5aeac3c203e3876adb08d878c93) Jan 30 06:10:08.308: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_c4dee0f1-ebbd-431b-a4f5-cdaba3338ff1 became leader Jan 30 06:10:08.308: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_6a930d5c-d857-45d7-8821-ab6144cfb617 became leader Jan 30 06:10:08.308: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_52b92c73-5b92-4994-9104-bec143d48796 became leader Jan 30 06:10:08.308: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_24f84219-2bae-4a66-bead-e8bbaf2fb7a6 became leader Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-dns-autoscaler-5f6455f985-bg4vb to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" in 2.01573763s (2.015748792s including waiting) Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container autoscaler Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container autoscaler Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container autoscaler Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" already present on machine Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container autoscaler in pod kube-dns-autoscaler-5f6455f985-bg4vb_kube-system(d17909b1-64e2-475c-a08b-b40ba36f6afa) Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985-bg4vb: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985: {replicaset-controller } FailedCreate: Error creating: pods "kube-dns-autoscaler-5f6455f985-" is forbidden: error looking up service account kube-system/kube-dns-autoscaler: serviceaccount "kube-dns-autoscaler" not found Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler-5f6455f985: {replicaset-controller } SuccessfulCreate: Created pod: kube-dns-autoscaler-5f6455f985-bg4vb Jan 30 06:10:08.308: INFO: event for kube-dns-autoscaler: {deployment-controller } ScalingReplicaSet: Scaled up replica set kube-dns-autoscaler-5f6455f985 to 1 Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {kubelet bootstrap-e2e-minion-group-89rb} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-89rb_kube-system(a86edc08c98ce4fefed543ad485600a4) Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-89rb: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-j5pg_kube-system(adff6fb483f7c9e3d86fb4cb79733a2e) Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-j5pg: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} Killing: Stopping container kube-proxy Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {kubelet bootstrap-e2e-minion-group-jt1b} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-jt1b_kube-system(87a78f5a508a69cfa60729c5d4dc7da6) Jan 30 06:10:08.308: INFO: event for kube-proxy-bootstrap-e2e-minion-group-jt1b: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/kube-scheduler-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-scheduler Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-scheduler Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container kube-scheduler in pod kube-scheduler-bootstrap-e2e-master_kube-system(5b3c0a3dad3d723f9e5778ab0a62849c) Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-scheduler Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe failed: Get "https://127.0.0.1:10259/healthz": dial tcp 127.0.0.1:10259: connect: connection refused Jan 30 06:10:08.308: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_18ee2297-5499-4a10-b782-8bf60ef964f2 became leader Jan 30 06:10:08.308: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_959dc035-06e0-4f47-9fbb-6328d3119de5 became leader Jan 30 06:10:08.308: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_36535314-0b8e-4eff-a7de-1c139a5f4105 became leader Jan 30 06:10:08.308: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_8d92bf3b-8542-4829-90e1-576b213e261b became leader Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {default-scheduler } Scheduled: Successfully assigned kube-system/l7-default-backend-8549d69d99-slz4q to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" in 2.282907597s (2.282919912s including waiting) Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container default-http-backend Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container default-http-backend Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Liveness probe failed: Get "http://10.64.3.4:8080/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Container default-http-backend failed liveness probe, will be restarted Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99-slz4q: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for l7-default-backend-8549d69d99: {replicaset-controller } SuccessfulCreate: Created pod: l7-default-backend-8549d69d99-slz4q Jan 30 06:10:08.308: INFO: event for l7-default-backend: {deployment-controller } ScalingReplicaSet: Scaled up replica set l7-default-backend-8549d69d99 to 1 Jan 30 06:10:08.308: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container l7-lb-controller Jan 30 06:10:08.308: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container l7-lb-controller Jan 30 06:10:08.308: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "gcr.io/k8s-ingress-image-push/ingress-gce-glbc-amd64:v1.20.1" already present on machine Jan 30 06:10:08.308: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container l7-lb-controller in pod l7-lb-controller-bootstrap-e2e-master_kube-system(f922c87738da4b787ed79e8be7ae0573) Jan 30 06:10:08.308: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe failed: Get "http://10.138.0.2:8086/healthz": dial tcp 10.138.0.2:8086: connect: connection refused Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-4glfd to bootstrap-e2e-minion-group-89rb Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 743.096978ms (743.138916ms including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.911633038s (1.911644632s including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4glfd: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-4rnk7 to bootstrap-e2e-master Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 751.7056ms (751.711494ms including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Failed: Error: services have not yet been read at least once, cannot construct envvars Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.335358551s (2.33536641s including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Created: Created container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Started: Started container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Created: Created container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-4rnk7: {kubelet bootstrap-e2e-master} Started: Started container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-srxc6 to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 804.763467ms (804.774083ms including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.089844613s (2.089864707s including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-srxc6: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-zckpq to bootstrap-e2e-minion-group-jt1b Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 842.219895ms (842.229354ms including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container metadata-proxy Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.054812451s (2.054822588s including waiting) Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Created: Created container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {kubelet bootstrap-e2e-minion-group-jt1b} Started: Started container prometheus-to-sd-exporter Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1-zckpq: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-4rnk7 Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-4glfd Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-zckpq Jan 30 06:10:08.308: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-srxc6 Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-6764bf875c-vbxz7 to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} FailedMount: MountVolume.SetUp failed for volume "metrics-server-config-volume" : failed to sync configmap cache: timed out waiting for the condition Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 3.531930568s (3.532067103s including waiting) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container metrics-server Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container metrics-server Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 1.812865403s (1.812874646s including waiting) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container metrics-server-nanny Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container metrics-server-nanny Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container metrics-server Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c-vbxz7: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container metrics-server-nanny Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-6764bf875c-vbxz7 Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulDelete: Deleted pod: metrics-server-v0.5.2-6764bf875c-vbxz7 Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-867b8754b9-s79bn to bootstrap-e2e-minion-group-89rb Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 1.367491088s (1.367525697s including waiting) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container metrics-server Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container metrics-server Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 1.035914064s (1.035929902s including waiting) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Created: Created container metrics-server-nanny Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Started: Started container metrics-server-nanny Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Readiness probe failed: Get "https://10.64.1.3:10250/readyz": dial tcp 10.64.1.3:10250: connect: connection refused Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Liveness probe failed: Get "https://10.64.1.3:10250/livez": dial tcp 10.64.1.3:10250: connect: connection refused Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Liveness probe failed: Get "https://10.64.1.3:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Readiness probe failed: Get "https://10.64.1.3:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container metrics-server Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Killing: Stopping container metrics-server-nanny Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {kubelet bootstrap-e2e-minion-group-89rb} Unhealthy: Readiness probe failed: Get "https://10.64.1.4:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9-s79bn: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2-867b8754b9: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-867b8754b9-s79bn Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-v0.5.2-6764bf875c to 1 Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-v0.5.2-867b8754b9 to 1 Jan 30 06:10:08.308: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled down replica set metrics-server-v0.5.2-6764bf875c to 0 from 1 Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: 0/2 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }, 1 node(s) were unschedulable. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.. Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {default-scheduler } Scheduled: Successfully assigned kube-system/volume-snapshot-controller-0 to bootstrap-e2e-minion-group-j5pg Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Pulling: Pulling image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Successfully pulled image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" in 1.683320982s (1.68333161s including waiting) Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Created: Created container volume-snapshot-controller Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Started: Started container volume-snapshot-controller Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Killing: Stopping container volume-snapshot-controller Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-j5pg} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(694587fc-d43c-43bc-bbab-563d942a4f03) Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller-0: {node-controller } NodeNotReady: Node is not ready Jan 30 06:10:08.308: INFO: event for volume-snapshot-controller: {statefulset-controller } SuccessfulCreate: create Pod volume-snapshot-controller-0 in StatefulSet volume-snapshot-controller successful < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:10:08.308 (51ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:10:08.308 Jan 30 06:10:08.308: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 30 06:10:08.352: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:10:10.396: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:10:12.395 (4.087s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 06:10:12.395 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 06:10:12.395 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:10:12.395 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:10:12.395 STEP: Collecting events from namespace "reboot-3328". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 06:10:12.395 STEP: Found 0 events. - test/e2e/framework/debug/dump.go:46 @ 01/30/23 06:10:12.439 Jan 30 06:10:12.481: INFO: POD NODE PHASE GRACE CONDITIONS Jan 30 06:10:12.481: INFO: Jan 30 06:10:12.526: INFO: Logging node info for node bootstrap-e2e-master Jan 30 06:10:12.568: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-master da42dd0c-bb3c-402f-847c-793de73fb287 1204 0 2023-01-30 06:04:10 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-1 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-master kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-1 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:10 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{},"f:unschedulable":{}}} } {kube-controller-manager Update v1 2023-01-30 06:04:27 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.0.0/24\"":{}},"f:taints":{}}} } {kube-controller-manager Update v1 2023-01-30 06:04:27 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kubelet Update v1 2023-01-30 06:09:37 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:10.64.0.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-master,Unschedulable:true,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:<nil>,},Taint{Key:node.kubernetes.io/unschedulable,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[10.64.0.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{1 0} {<nil>} 1 DecimalSI},ephemeral-storage: {{16656896000 0} {<nil>} 16266500Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3858370560 0} {<nil>} 3767940Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{1 0} {<nil>} 1 DecimalSI},ephemeral-storage: {{14991206376 0} {<nil>} 14991206376 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3596226560 0} {<nil>} 3511940Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:10 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:10 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:10 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:09:37 +0000 UTC,LastTransitionTime:2023-01-30 06:04:14 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.2,},NodeAddress{Type:ExternalIP,Address:34.145.121.12,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-master.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-master.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ceaf667f6b5e1324cd116eb2db802512,SystemUUID:ceaf667f-6b5e-1324-cd11-6eb2db802512,BootID:f3af49de-86af-4adc-82a1-ca040b706b59,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-apiserver-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:135961043,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:125279033,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:51eae8381dcb1078289fa7b4f3df2630cdc18d09fb56f8e56b41c40e191d6c83 registry.k8s.io/etcd:3.5.7-0],SizeBytes:101639218,},ContainerImage{Names:[registry.k8s.io/kube-scheduler-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:57551672,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[gcr.io/k8s-ingress-image-push/ingress-gce-glbc-amd64@sha256:5db27383add6d9f4ebdf0286409ac31f7f5d273690204b341a4e37998917693b gcr.io/k8s-ingress-image-push/ingress-gce-glbc-amd64:v1.20.1],SizeBytes:36598135,},ContainerImage{Names:[registry.k8s.io/addon-manager/kube-addon-manager@sha256:49cc4e6e4a3745b427ce14b0141476ab339bb65c6bc05033019e046c8727dcb0 registry.k8s.io/addon-manager/kube-addon-manager:v9.1.6],SizeBytes:30464183,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-server@sha256:b1389e7014425a1752aac55f5043ef4c52edaef0e223bf4d48ed1324e298087c registry.k8s.io/kas-network-proxy/proxy-server:v0.1.1],SizeBytes:21875112,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:10:12.569: INFO: Logging kubelet events for node bootstrap-e2e-master Jan 30 06:10:12.613: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-master Jan 30 06:10:12.669: INFO: kube-addon-manager-bootstrap-e2e-master started at 2023-01-30 06:03:43 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container kube-addon-manager ready: true, restart count 1 Jan 30 06:10:12.669: INFO: konnectivity-server-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container konnectivity-server-container ready: true, restart count 0 Jan 30 06:10:12.669: INFO: kube-controller-manager-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container kube-controller-manager ready: true, restart count 4 Jan 30 06:10:12.669: INFO: etcd-server-events-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container etcd-container ready: true, restart count 0 Jan 30 06:10:12.669: INFO: l7-lb-controller-bootstrap-e2e-master started at 2023-01-30 06:03:43 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container l7-lb-controller ready: true, restart count 4 Jan 30 06:10:12.669: INFO: metadata-proxy-v0.1-4rnk7 started at 2023-01-30 06:04:10 +0000 UTC (0+2 container statuses recorded) Jan 30 06:10:12.669: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:10:12.669: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:10:12.669: INFO: kube-apiserver-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container kube-apiserver ready: true, restart count 0 Jan 30 06:10:12.669: INFO: etcd-server-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container etcd-container ready: true, restart count 2 Jan 30 06:10:12.669: INFO: kube-scheduler-bootstrap-e2e-master started at 2023-01-30 06:03:26 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:12.669: INFO: Container kube-scheduler ready: true, restart count 3 Jan 30 06:10:12.866: INFO: Latency metrics for node bootstrap-e2e-master Jan 30 06:10:12.866: INFO: Logging node info for node bootstrap-e2e-minion-group-89rb Jan 30 06:10:12.908: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-89rb 7a6374a4-18c6-4a29-8950-b11b5056de6e 1336 0 2023-01-30 06:04:12 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-2 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-minion-group-89rb kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-2 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.1.0/24\"":{}}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kubelet Update v1 2023-01-30 06:10:01 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status} {node-problem-detector Update v1 2023-01-30 06:10:03 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.1.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-minion-group-89rb,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.1.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815430144 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553286144 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:16 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.5,},NodeAddress{Type:ExternalIP,Address:34.168.49.142,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-89rb.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-89rb.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:a886a977671560a8ccd3c81c9111e6c4,SystemUUID:a886a977-6715-60a8-ccd3-c81c9111e6c4,BootID:2435cf70-73c9-4f65-bb5d-1b1f7ed9a49e,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:66988744,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[registry.k8s.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 registry.k8s.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[registry.k8s.io/autoscaling/addon-resizer@sha256:43f129b81d28f0fdd54de6d8e7eacd5728030782e03db16087fc241ad747d3d6 registry.k8s.io/autoscaling/addon-resizer:1.8.14],SizeBytes:10153852,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-agent@sha256:939c42e815e6b6af3181f074652c0d18fe429fcee9b49c1392aee7e92887cfef registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1],SizeBytes:8364694,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:10:12.909: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-89rb Jan 30 06:10:12.952: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-89rb Jan 30 06:10:13.013: INFO: kube-proxy-bootstrap-e2e-minion-group-89rb started at 2023-01-30 06:04:12 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.013: INFO: Container kube-proxy ready: true, restart count 3 Jan 30 06:10:13.013: INFO: metadata-proxy-v0.1-4glfd started at 2023-01-30 06:04:13 +0000 UTC (0+2 container statuses recorded) Jan 30 06:10:13.013: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:10:13.013: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:10:13.013: INFO: konnectivity-agent-vpdtl started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.013: INFO: Container konnectivity-agent ready: true, restart count 2 Jan 30 06:10:13.013: INFO: metrics-server-v0.5.2-867b8754b9-s79bn started at 2023-01-30 06:04:46 +0000 UTC (0+2 container statuses recorded) Jan 30 06:10:13.013: INFO: Container metrics-server ready: false, restart count 4 Jan 30 06:10:13.013: INFO: Container metrics-server-nanny ready: true, restart count 1 Jan 30 06:10:13.185: INFO: Latency metrics for node bootstrap-e2e-minion-group-89rb Jan 30 06:10:13.185: INFO: Logging node info for node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:13.230: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-j5pg 77296218-aa10-476d-a138-052026f8f306 1359 0 2023-01-30 06:04:14 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-2 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-minion-group-j5pg kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-2 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.3.0/24\"":{}}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {node-problem-detector Update v1 2023-01-30 06:10:05 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-30 06:10:10 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:10.64.3.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-minion-group-j5pg,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.3.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815438336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553294336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 06:09:49 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:10:10 +0000 UTC,LastTransitionTime:2023-01-30 06:10:10 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.3,},NodeAddress{Type:ExternalIP,Address:34.82.243.144,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-j5pg.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-j5pg.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:00c00596a04cd69c19526ec9065fe3a0,SystemUUID:00c00596-a04c-d69c-1952-6ec9065fe3a0,BootID:8b0896f1-a065-4ffa-97fa-b74f7309fbf4,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:66988744,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[registry.k8s.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 registry.k8s.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[registry.k8s.io/sig-storage/snapshot-controller@sha256:823c75d0c45d1427f6d850070956d9ca657140a7bbf828381541d1d808475280 registry.k8s.io/sig-storage/snapshot-controller:v6.1.0],SizeBytes:22620891,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/cpa/cluster-proportional-autoscaler@sha256:fd636b33485c7826fb20ef0688a83ee0910317dbb6c0c6f3ad14661c1db25def registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4],SizeBytes:15209393,},ContainerImage{Names:[registry.k8s.io/autoscaling/addon-resizer@sha256:43f129b81d28f0fdd54de6d8e7eacd5728030782e03db16087fc241ad747d3d6 registry.k8s.io/autoscaling/addon-resizer:1.8.14],SizeBytes:10153852,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-agent@sha256:939c42e815e6b6af3181f074652c0d18fe429fcee9b49c1392aee7e92887cfef registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1],SizeBytes:8364694,},ContainerImage{Names:[registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64@sha256:7eb7b3cee4d33c10c49893ad3c386232b86d4067de5251294d4c620d6e072b93 registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11],SizeBytes:6463068,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:10:13.230: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:13.274: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:13.339: INFO: l7-default-backend-8549d69d99-slz4q started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.339: INFO: Container default-http-backend ready: true, restart count 1 Jan 30 06:10:13.339: INFO: volume-snapshot-controller-0 started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.339: INFO: Container volume-snapshot-controller ready: true, restart count 5 Jan 30 06:10:13.339: INFO: konnectivity-agent-sv2mg started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.339: INFO: Container konnectivity-agent ready: true, restart count 3 Jan 30 06:10:13.339: INFO: kube-proxy-bootstrap-e2e-minion-group-j5pg started at 2023-01-30 06:04:14 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.339: INFO: Container kube-proxy ready: true, restart count 2 Jan 30 06:10:13.339: INFO: metadata-proxy-v0.1-srxc6 started at 2023-01-30 06:04:15 +0000 UTC (0+2 container statuses recorded) Jan 30 06:10:13.339: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:10:13.339: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:10:13.339: INFO: kube-dns-autoscaler-5f6455f985-bg4vb started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.339: INFO: Container autoscaler ready: true, restart count 4 Jan 30 06:10:13.339: INFO: coredns-6846b5b5f-27hpv started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.339: INFO: Container coredns ready: true, restart count 3 Jan 30 06:10:13.541: INFO: Latency metrics for node bootstrap-e2e-minion-group-j5pg Jan 30 06:10:13.541: INFO: Logging node info for node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:13.584: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-jt1b 9c9847ba-4388-4123-89c6-52ccc637e6c3 1337 0 2023-01-30 06:04:14 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:n1-standard-2 beta.kubernetes.io/os:linux cloud.google.com/metadata-proxy-ready:true failure-domain.beta.kubernetes.io/region:us-west1 failure-domain.beta.kubernetes.io/zone:us-west1-b kubernetes.io/arch:amd64 kubernetes.io/hostname:bootstrap-e2e-minion-group-jt1b kubernetes.io/os:linux node.kubernetes.io/instance-type:n1-standard-2 topology.kubernetes.io/region:us-west1 topology.kubernetes.io/zone:us-west1-b] map[node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-30 06:04:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:cloud.google.com/metadata-proxy-ready":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"10.64.2.0/24\"":{}}}} } {kube-controller-manager Update v1 2023-01-30 06:09:54 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kubelet Update v1 2023-01-30 06:10:01 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status} {node-problem-detector Update v1 2023-01-30 06:10:03 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.2.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-serial-1-2/us-west1-b/bootstrap-e2e-minion-group-jt1b,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.2.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815438336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553294336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 06:09:48 +0000 UTC,LastTransitionTime:2023-01-30 06:04:17 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 06:04:27 +0000 UTC,LastTransitionTime:2023-01-30 06:04:27 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 06:10:01 +0000 UTC,LastTransitionTime:2023-01-30 06:10:01 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.4,},NodeAddress{Type:ExternalIP,Address:34.83.145.21,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-jt1b.c.k8s-jkns-e2e-gce-serial-1-2.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-jt1b.c.k8s-jkns-e2e-gce-serial-1-2.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:a84e7124d1b77ea5a363b5b4e806099f,SystemUUID:a84e7124-d1b7-7ea5-a363-b5b4e806099f,BootID:c2771298-b9a1-4721-be1f-55ff63f4a2d8,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-11-g9857b5d1b,KubeletVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,KubeProxyVersion:v1.27.0-alpha.1.88+7b243cef1a81f4,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4],SizeBytes:66988744,},ContainerImage{Names:[gke.gcr.io/prometheus-to-sd@sha256:e739643c3939ba0b161425f45a1989eedfc4a3b166db9a7100863296b4c70510 gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1],SizeBytes:48742566,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/kas-network-proxy/proxy-agent@sha256:939c42e815e6b6af3181f074652c0d18fe429fcee9b49c1392aee7e92887cfef registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1],SizeBytes:8364694,},ContainerImage{Names:[registry.k8s.io/metadata-proxy@sha256:e914645f22e946bce5165737e1b244e0a296ad1f0f81a9531adc57af2780978a registry.k8s.io/metadata-proxy:v0.1.12],SizeBytes:5301657,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 30 06:10:13.584: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:13.631: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-jt1b Jan 30 06:10:13.706: INFO: kube-proxy-bootstrap-e2e-minion-group-jt1b started at 2023-01-30 06:04:14 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.706: INFO: Container kube-proxy ready: true, restart count 3 Jan 30 06:10:13.706: INFO: metadata-proxy-v0.1-zckpq started at 2023-01-30 06:04:14 +0000 UTC (0+2 container statuses recorded) Jan 30 06:10:13.706: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 06:10:13.706: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 06:10:13.706: INFO: konnectivity-agent-lsjtz started at 2023-01-30 06:04:27 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.706: INFO: Container konnectivity-agent ready: true, restart count 3 Jan 30 06:10:13.706: INFO: coredns-6846b5b5f-vtndh started at 2023-01-30 06:04:32 +0000 UTC (0+1 container statuses recorded) Jan 30 06:10:13.706: INFO: Container coredns ready: false, restart count 2 Jan 30 06:10:13.887: INFO: Latency metrics for node bootstrap-e2e-minion-group-jt1b END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:10:13.887 (1.492s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:10:13.887 (1.492s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:10:13.887 STEP: Destroying namespace "reboot-3328" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 06:10:13.888 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:10:13.931 (43ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:10:13.931 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:10:13.931 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sordering\sclean\sreboot\sand\sensure\sthey\sfunction\supon\srestart$'
[FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 06:22:03.482 There were additional failures detected after the initial failure. These are visible in the timelinefrom ginkgo_report.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:21:33.36 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:21:33.361 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:21:33.361 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 06:21:33.361 Jan 30 06:21:33.361: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 06:21:33.362 Jan 30 06:21:33.401: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:35.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:37.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:39.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:41.442: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:43.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:45.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:47.442: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:49.442: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:51.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:53.442: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:55.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:57.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:59.442: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:22:01.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:22:03.442: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:22:03.481: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:22:03.481: INFO: Unexpected error: <*errors.errorString | 0xc000115d00>: { s: "timed out waiting for the condition", } [FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 06:22:03.482 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:22:03.482 (30.121s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:22:03.482 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 06:22:03.482 Jan 30 06:22:03.521: INFO: Unexpected error: <*url.Error | 0xc005124000>: { Op: "Get", URL: "https://34.145.121.12/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc004720000>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc00385a6c0>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 145, 121, 12], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc00289a000>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.145.121.12/api/v1/namespaces/kube-system/events": dial tcp 34.145.121.12:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 06:22:03.521 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:22:03.521 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:22:03.521 Jan 30 06:22:03.521: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:22:03.561 (39ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:22:03.561 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:22:03.561 END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:22:03.561 (0s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:22:03.561 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:22:03.561 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:22:03.561 (0s) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:22:03.561 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:22:03.561 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sordering\sclean\sreboot\sand\sensure\sthey\sfunction\supon\srestart$'
[FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 06:22:03.482 There were additional failures detected after the initial failure. These are visible in the timelinefrom junit_01.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:21:33.36 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:21:33.361 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:21:33.361 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 06:21:33.361 Jan 30 06:21:33.361: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 06:21:33.362 Jan 30 06:21:33.401: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:35.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:37.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:39.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:41.442: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:43.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:45.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:47.442: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:49.442: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:51.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:53.442: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:55.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:57.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:59.442: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:22:01.441: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:22:03.442: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:22:03.481: INFO: Unexpected error while creating namespace: Post "https://34.145.121.12/api/v1/namespaces": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:22:03.481: INFO: Unexpected error: <*errors.errorString | 0xc000115d00>: { s: "timed out waiting for the condition", } [FAILED] timed out waiting for the condition In [BeforeEach] at: test/e2e/framework/framework.go:251 @ 01/30/23 06:22:03.482 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:22:03.482 (30.121s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:22:03.482 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 06:22:03.482 Jan 30 06:22:03.521: INFO: Unexpected error: <*url.Error | 0xc005124000>: { Op: "Get", URL: "https://34.145.121.12/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc004720000>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc00385a6c0>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 145, 121, 12], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc00289a000>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.145.121.12/api/v1/namespaces/kube-system/events": dial tcp 34.145.121.12:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 06:22:03.521 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:22:03.521 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:22:03.521 Jan 30 06:22:03.521: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:22:03.561 (39ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:22:03.561 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:22:03.561 END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:22:03.561 (0s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:22:03.561 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:22:03.561 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:22:03.561 (0s) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:22:03.561 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:22:03.561 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sordering\sunclean\sreboot\sand\sensure\sthey\sfunction\supon\srestart$'
[FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 06:21:33.152 There were additional failures detected after the initial failure. These are visible in the timelinefrom ginkgo_report.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:20:01.984 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:20:01.984 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:20:01.984 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 06:20:01.984 Jan 30 06:20:01.984: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 06:20:01.986 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/30/23 06:20:02.112 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/30/23 06:20:02.206 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:20:02.287 (302ms) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 06:20:02.287 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 06:20:02.287 (0s) > Enter [It] each node by ordering unclean reboot and ensure they function upon restart - test/e2e/cloud/gcp/reboot.go:103 @ 01/30/23 06:20:02.287 Jan 30 06:20:02.383: INFO: Getting bootstrap-e2e-minion-group-89rb Jan 30 06:20:02.383: INFO: Getting bootstrap-e2e-minion-group-j5pg Jan 30 06:20:02.383: INFO: Getting bootstrap-e2e-minion-group-jt1b Jan 30 06:20:02.460: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-jt1b condition Ready to be true Jan 30 06:20:02.460: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-89rb condition Ready to be true Jan 30 06:20:02.460: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-j5pg condition Ready to be true Jan 30 06:20:02.506: INFO: Node bootstrap-e2e-minion-group-j5pg has 4 assigned pods with no liveness probes: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:20:02.506: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:20:02.506: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.506: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-bg4vb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.506: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.506: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-srxc6" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.507: INFO: Node bootstrap-e2e-minion-group-jt1b has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:20:02.507: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:20:02.507: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-zckpq" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.507: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-jt1b" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.507: INFO: Node bootstrap-e2e-minion-group-89rb has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:20:02.507: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:20:02.507: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-4glfd" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.507: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-89rb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.554: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb": Phase="Running", Reason="", readiness=true. Elapsed: 48.1127ms Jan 30 06:20:02.554: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.554: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 48.430092ms Jan 30 06:20:02.554: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.557: INFO: Pod "metadata-proxy-v0.1-4glfd": Phase="Running", Reason="", readiness=true. Elapsed: 49.636363ms Jan 30 06:20:02.557: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb": Phase="Running", Reason="", readiness=true. Elapsed: 49.551669ms Jan 30 06:20:02.557: INFO: Pod "metadata-proxy-v0.1-4glfd" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.557: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.557: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:20:02.557: INFO: Getting external IP address for bootstrap-e2e-minion-group-89rb Jan 30 06:20:02.557: INFO: SSH "nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo b | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-89rb(34.168.49.142:22) Jan 30 06:20:02.557: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg": Phase="Running", Reason="", readiness=true. Elapsed: 50.35476ms Jan 30 06:20:02.557: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.557: INFO: Pod "metadata-proxy-v0.1-srxc6": Phase="Running", Reason="", readiness=true. Elapsed: 50.357594ms Jan 30 06:20:02.557: INFO: Pod "metadata-proxy-v0.1-srxc6" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.557: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: true. Pods: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:20:02.557: INFO: Getting external IP address for bootstrap-e2e-minion-group-j5pg Jan 30 06:20:02.557: INFO: SSH "nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo b | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-j5pg(34.82.243.144:22) Jan 30 06:20:02.557: INFO: Pod "metadata-proxy-v0.1-zckpq": Phase="Running", Reason="", readiness=true. Elapsed: 50.248508ms Jan 30 06:20:02.557: INFO: Pod "metadata-proxy-v0.1-zckpq" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.557: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 50.290677ms Jan 30 06:20:02.557: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:03.080: INFO: ssh prow@34.82.243.144:22: command: nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo b | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 & Jan 30 06:20:03.080: INFO: ssh prow@34.82.243.144:22: stdout: "" Jan 30 06:20:03.080: INFO: ssh prow@34.82.243.144:22: stderr: "" Jan 30 06:20:03.080: INFO: ssh prow@34.82.243.144:22: exit code: 0 Jan 30 06:20:03.080: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-j5pg condition Ready to be false Jan 30 06:20:03.080: INFO: ssh prow@34.168.49.142:22: command: nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo b | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 & Jan 30 06:20:03.080: INFO: ssh prow@34.168.49.142:22: stdout: "" Jan 30 06:20:03.080: INFO: ssh prow@34.168.49.142:22: stderr: "" Jan 30 06:20:03.080: INFO: ssh prow@34.168.49.142:22: exit code: 0 Jan 30 06:20:03.080: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-89rb condition Ready to be false Jan 30 06:20:03.124: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:03.124: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:04.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 2.093782285s Jan 30 06:20:04.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:05.169: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:05.169: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:06.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 4.093222656s Jan 30 06:20:06.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:07.213: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:07.213: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:08.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 6.094094699s Jan 30 06:20:08.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:09.258: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:09.258: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:10.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 8.093285101s Jan 30 06:20:10.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:11.302: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:11.302: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:12.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 10.092773548s Jan 30 06:20:12.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:13.347: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:13.347: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:14.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 12.094305118s Jan 30 06:20:14.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:15.391: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:15.391: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:16.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 14.093282521s Jan 30 06:20:16.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:17.441: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:17.441: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:18.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 16.093961969s Jan 30 06:20:18.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:19.486: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:19.486: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:20.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 18.093080536s Jan 30 06:20:20.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:21.530: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:21.530: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:22.599: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 20.092244388s Jan 30 06:20:22.599: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:23.575: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:23.575: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:24.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 22.093510389s Jan 30 06:20:24.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:25.618: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:25.618: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:26.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 24.092731528s Jan 30 06:20:26.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:27.663: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:27.664: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:28.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 26.094110455s Jan 30 06:20:28.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:29.708: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:29.708: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:30.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 28.093444948s Jan 30 06:20:30.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:31.751: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:31.752: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:32.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 30.092980009s Jan 30 06:20:32.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:33.797: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:33.797: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:34.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 32.094230098s Jan 30 06:20:34.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:35.842: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:35.842: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:36.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 34.092841586s Jan 30 06:20:36.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:37.887: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:37.887: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:38.615: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 36.108275852s Jan 30 06:20:38.615: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:39.931: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:39.931: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:40.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 38.093338898s Jan 30 06:20:40.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:41.975: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:41.975: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:42.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 40.093098855s Jan 30 06:20:42.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:46.064: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:46.065: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-89rb condition Ready to be true Jan 30 06:20:46.126: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 43.619123146s Jan 30 06:20:46.126: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:46.190: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:20:46.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 44.093761978s Jan 30 06:20:46.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:48.107: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:48.232: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:20:48.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 46.09290681s Jan 30 06:20:48.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:50.150: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:50.277: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:20:50.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 48.094077267s Jan 30 06:20:50.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:52.205: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:52.320: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:20:52.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 50.093721081s Jan 30 06:20:52.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:54.247: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:54.363: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:20:54.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 52.092748807s Jan 30 06:20:54.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:56.300: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-j5pg condition Ready to be true Jan 30 06:20:56.378: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:20:56.405: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:20:56.599: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 54.092062901s Jan 30 06:20:56.599: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:58.420: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:20:58.449: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:20:58.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 56.093449714s Jan 30 06:20:58.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:00.464: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:21:00.491: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:00.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 58.092788392s Jan 30 06:21:00.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:02.507: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:02.535: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:02.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m0.09440931s Jan 30 06:21:02.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:04.550: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:04.578: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:04.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m2.093729898s Jan 30 06:21:04.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:06.592: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:06.599: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.092444394s Jan 30 06:21:06.599: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:06.621: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:08.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.094378398s Jan 30 06:21:08.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:08.635: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:08.686: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:10.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m8.09302246s Jan 30 06:21:10.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:10.679: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:10.729: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:12.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.092875224s Jan 30 06:21:12.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:12.721: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:12.772: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:14.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.092980311s Jan 30 06:21:14.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:14.767: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:14.817: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:16.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m14.09272813s Jan 30 06:21:16.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:16.812: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:16.860: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:18.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.093770003s Jan 30 06:21:18.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:18.856: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:18.903: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:20.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.093766883s Jan 30 06:21:20.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:20.898: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:20.946: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:22.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.093614634s Jan 30 06:21:22.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:22.941: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:22.989: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:24.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.094042548s Jan 30 06:21:24.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:24.986: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:25.032: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:26.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m24.092889737s Jan 30 06:21:26.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:27.028: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:21:27.028: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:21:27.028: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-srxc6" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:21:27.028: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:21:27.029: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-bg4vb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:21:27.071: INFO: Pod "metadata-proxy-v0.1-srxc6": Phase="Running", Reason="", readiness=false. Elapsed: 42.980113ms Jan 30 06:21:27.071: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-srxc6' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:15 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:15 +0000 UTC }] Jan 30 06:21:27.071: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 43.142705ms Jan 30 06:21:27.071: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:00 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC }] Jan 30 06:21:27.072: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg": Phase="Running", Reason="", readiness=false. Elapsed: 43.932826ms Jan 30 06:21:27.072: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-j5pg' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:11:54 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:27.072: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb": Phase="Running", Reason="", readiness=false. Elapsed: 43.657715ms Jan 30 06:21:27.072: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-bg4vb' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:21:26 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC }] Jan 30 06:21:27.075: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:21:27.075: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-4glfd" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:21:27.075: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-89rb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:21:27.117: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb": Phase="Running", Reason="", readiness=true. Elapsed: 42.477435ms Jan 30 06:21:27.117: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb" satisfied condition "running and ready, or succeeded" Jan 30 06:21:27.117: INFO: Pod "metadata-proxy-v0.1-4glfd": Phase="Running", Reason="", readiness=false. Elapsed: 42.53531ms Jan 30 06:21:27.118: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-4glfd' on 'bootstrap-e2e-minion-group-89rb' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:13 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:46 +0000 UTC ContainersNotReady containers with unready status: [metadata-proxy prometheus-to-sd-exporter]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:21:24 +0000 UTC ContainersNotReady containers with unready status: [metadata-proxy prometheus-to-sd-exporter]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:12 +0000 UTC }] Jan 30 06:21:28.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m26.09354723s Jan 30 06:21:28.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:29.114: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2.085534152s Jan 30 06:21:29.114: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:00 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC }] Jan 30 06:21:29.116: INFO: Pod "metadata-proxy-v0.1-srxc6": Phase="Running", Reason="", readiness=false. Elapsed: 2.087438366s Jan 30 06:21:29.116: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-srxc6' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:15 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:15 +0000 UTC }] Jan 30 06:21:29.116: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb": Phase="Running", Reason="", readiness=false. Elapsed: 2.087189633s Jan 30 06:21:29.116: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-bg4vb' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:21:26 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC }] Jan 30 06:21:29.117: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg": Phase="Running", Reason="", readiness=false. Elapsed: 2.08865727s Jan 30 06:21:29.117: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-j5pg' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:11:54 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:29.160: INFO: Pod "metadata-proxy-v0.1-4glfd": Phase="Running", Reason="", readiness=true. Elapsed: 2.084701302s Jan 30 06:21:29.160: INFO: Pod "metadata-proxy-v0.1-4glfd" satisfied condition "running and ready, or succeeded" Jan 30 06:21:29.160: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:21:29.160: INFO: Reboot successful on node bootstrap-e2e-minion-group-89rb Jan 30 06:21:30.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m28.093549667s Jan 30 06:21:30.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:31.116: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4.087767582s Jan 30 06:21:31.116: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:21:26 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC }] Jan 30 06:21:31.119: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg": Phase="Running", Reason="", readiness=true. Elapsed: 4.090425966s Jan 30 06:21:31.119: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" satisfied condition "running and ready, or succeeded" Jan 30 06:21:31.119: INFO: Pod "metadata-proxy-v0.1-srxc6": Phase="Running", Reason="", readiness=true. Elapsed: 4.090445606s Jan 30 06:21:31.119: INFO: Pod "metadata-proxy-v0.1-srxc6" satisfied condition "running and ready, or succeeded" Jan 30 06:21:31.119: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb": Phase="Running", Reason="", readiness=false. Elapsed: 4.090193925s Jan 30 06:21:31.119: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-bg4vb' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:21:26 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC }] Jan 30 06:21:32.597: INFO: Encountered non-retryable error while getting pod kube-system/kube-proxy-bootstrap-e2e-minion-group-jt1b: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/kube-proxy-bootstrap-e2e-minion-group-jt1b": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:32.597: INFO: Pod kube-proxy-bootstrap-e2e-minion-group-jt1b failed to be running and ready, or succeeded. Jan 30 06:21:32.597: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: false. Pods: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:21:32.597: INFO: Status for not ready pod kube-system/kube-proxy-bootstrap-e2e-minion-group-jt1b: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:04:14 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:19:33 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-proxy]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:19:33 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-proxy]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:04:14 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP:10.138.0.4 PodIPs:[{IP:10.138.0.4}] StartTime:2023-01-30 06:04:14 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:kube-proxy State:{Waiting:&ContainerStateWaiting{Reason:CrashLoopBackOff,Message:back-off 2m40s restarting failed container=kube-proxy pod=kube-proxy-bootstrap-e2e-minion-group-jt1b_kube-system(87a78f5a508a69cfa60729c5d4dc7da6),} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-30 06:18:15 +0000 UTC,FinishedAt:2023-01-30 06:19:32 +0000 UTC,ContainerID:containerd://2706e16bf15ab1c5d363a47ede8c5e7c702cbd5397878deabd334d57735a2432,}} Ready:false RestartCount:5 Image:registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4 ImageID:sha256:c4cd2f6a04c334ec2dfc72eb03fcaacc3231faaa0dfd84b73b8f65c5b0afa401 ContainerID:containerd://2706e16bf15ab1c5d363a47ede8c5e7c702cbd5397878deabd334d57735a2432 Started:0xc0035e18df}] QOSClass:Burstable EphemeralContainerStatuses:[]} Jan 30 06:21:32.637: INFO: Retrieving log for container kube-system/kube-proxy-bootstrap-e2e-minion-group-jt1b/kube-proxy, err: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/kube-proxy-bootstrap-e2e-minion-group-jt1b/log?container=kube-proxy&previous=false": dial tcp 34.145.121.12:443: connect: connection refused: Jan 30 06:21:32.637: INFO: Retrieving log for the last terminated container kube-system/kube-proxy-bootstrap-e2e-minion-group-jt1b/kube-proxy, err: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/kube-proxy-bootstrap-e2e-minion-group-jt1b/log?container=kube-proxy&previous=false": dial tcp 34.145.121.12:443: connect: connection refused: Jan 30 06:21:33.112: INFO: Encountered non-retryable error while getting pod kube-system/volume-snapshot-controller-0: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/volume-snapshot-controller-0": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:33.112: INFO: Encountered non-retryable error while getting pod kube-system/kube-dns-autoscaler-5f6455f985-bg4vb: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/kube-dns-autoscaler-5f6455f985-bg4vb": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:33.112: INFO: Pod volume-snapshot-controller-0 failed to be running and ready, or succeeded. Jan 30 06:21:33.112: INFO: Pod kube-dns-autoscaler-5f6455f985-bg4vb failed to be running and ready, or succeeded. Jan 30 06:21:33.112: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: false. Pods: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:21:33.112: INFO: Status for not ready pod kube-system/kube-dns-autoscaler-5f6455f985-bg4vb: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:04:27 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:20:56 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [autoscaler]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:21:26 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [autoscaler]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:04:27 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.3 PodIP: PodIPs:[] StartTime:2023-01-30 06:04:27 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:autoscaler State:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:255,Signal:0,Reason:Unknown,Message:,StartedAt:2023-01-30 06:17:57 +0000 UTC,FinishedAt:2023-01-30 06:20:33 +0000 UTC,ContainerID:containerd://8f100b8734a08caf875dab9185fa342bfaff9c5689c62ccd09d606c6ebb5059f,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:6 Image:registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4 ImageID:registry.k8s.io/cpa/cluster-proportional-autoscaler@sha256:fd636b33485c7826fb20ef0688a83ee0910317dbb6c0c6f3ad14661c1db25def ContainerID:containerd://8f100b8734a08caf875dab9185fa342bfaff9c5689c62ccd09d606c6ebb5059f Started:0xc0046c9b77}] QOSClass:Burstable EphemeralContainerStatuses:[]} Jan 30 06:21:33.151: INFO: Retrieving log for container kube-system/kube-dns-autoscaler-5f6455f985-bg4vb/autoscaler, err: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/kube-dns-autoscaler-5f6455f985-bg4vb/log?container=autoscaler&previous=false": dial tcp 34.145.121.12:443: connect: connection refused: Jan 30 06:21:33.151: INFO: Retrieving log for the last terminated container kube-system/kube-dns-autoscaler-5f6455f985-bg4vb/autoscaler, err: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/kube-dns-autoscaler-5f6455f985-bg4vb/log?container=autoscaler&previous=false": dial tcp 34.145.121.12:443: connect: connection refused: Jan 30 06:21:33.151: INFO: Node bootstrap-e2e-minion-group-j5pg failed reboot test. Jan 30 06:21:33.151: INFO: Node bootstrap-e2e-minion-group-jt1b failed reboot test. [FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 06:21:33.152 < Exit [It] each node by ordering unclean reboot and ensure they function upon restart - test/e2e/cloud/gcp/reboot.go:103 @ 01/30/23 06:21:33.152 (1m30.865s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:21:33.152 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 06:21:33.152 Jan 30 06:21:33.191: INFO: Unexpected error: <*url.Error | 0xc003945d70>: { Op: "Get", URL: "https://34.145.121.12/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc0039191d0>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc0043daf60>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 145, 121, 12], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc00533ca60>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.145.121.12/api/v1/namespaces/kube-system/events": dial tcp 34.145.121.12:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 06:21:33.192 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:21:33.192 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:21:33.192 Jan 30 06:21:33.192: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:21:33.231 (39ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 06:21:33.231 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 06:21:33.231 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:21:33.231 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:21:33.231 STEP: Collecting events from namespace "reboot-127". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 06:21:33.231 Jan 30 06:21:33.271: INFO: Unexpected error: failed to list events in namespace "reboot-127": <*url.Error | 0xc005012ea0>: { Op: "Get", URL: "https://34.145.121.12/api/v1/namespaces/reboot-127/events", Err: <*net.OpError | 0xc004868870>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc0043db500>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 145, 121, 12], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc000597760>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:21:33.271 (40ms) [FAILED] failed to list events in namespace "reboot-127": Get "https://34.145.121.12/api/v1/namespaces/reboot-127/events": dial tcp 34.145.121.12:443: connect: connection refused In [DeferCleanup (Each)] at: test/e2e/framework/debug/dump.go:44 @ 01/30/23 06:21:33.271 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:21:33.271 (40ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:21:33.271 STEP: Destroying namespace "reboot-127" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 06:21:33.271 [FAILED] Couldn't delete ns: "reboot-127": Delete "https://34.145.121.12/api/v1/namespaces/reboot-127": dial tcp 34.145.121.12:443: connect: connection refused (&url.Error{Op:"Delete", URL:"https://34.145.121.12/api/v1/namespaces/reboot-127", Err:(*net.OpError)(0xc001c28280)}) In [DeferCleanup (Each)] at: test/e2e/framework/framework.go:383 @ 01/30/23 06:21:33.311 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:21:33.311 (40ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:21:33.311 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:21:33.311 (0s)
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[It\]\s\[sig\-cloud\-provider\-gcp\]\sReboot\s\[Disruptive\]\s\[Feature\:Reboot\]\seach\snode\sby\sordering\sunclean\sreboot\sand\sensure\sthey\sfunction\supon\srestart$'
[FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 06:21:33.152 There were additional failures detected after the initial failure. These are visible in the timelinefrom junit_01.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:20:01.984 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 06:20:01.984 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:20:01.984 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 06:20:01.984 Jan 30 06:20:01.984: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 06:20:01.986 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/30/23 06:20:02.112 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/30/23 06:20:02.206 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 06:20:02.287 (302ms) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 06:20:02.287 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 06:20:02.287 (0s) > Enter [It] each node by ordering unclean reboot and ensure they function upon restart - test/e2e/cloud/gcp/reboot.go:103 @ 01/30/23 06:20:02.287 Jan 30 06:20:02.383: INFO: Getting bootstrap-e2e-minion-group-89rb Jan 30 06:20:02.383: INFO: Getting bootstrap-e2e-minion-group-j5pg Jan 30 06:20:02.383: INFO: Getting bootstrap-e2e-minion-group-jt1b Jan 30 06:20:02.460: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-jt1b condition Ready to be true Jan 30 06:20:02.460: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-89rb condition Ready to be true Jan 30 06:20:02.460: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-j5pg condition Ready to be true Jan 30 06:20:02.506: INFO: Node bootstrap-e2e-minion-group-j5pg has 4 assigned pods with no liveness probes: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:20:02.506: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:20:02.506: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.506: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-bg4vb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.506: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.506: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-srxc6" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.507: INFO: Node bootstrap-e2e-minion-group-jt1b has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:20:02.507: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:20:02.507: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-zckpq" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.507: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-jt1b" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.507: INFO: Node bootstrap-e2e-minion-group-89rb has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:20:02.507: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:20:02.507: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-4glfd" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.507: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-89rb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:20:02.554: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb": Phase="Running", Reason="", readiness=true. Elapsed: 48.1127ms Jan 30 06:20:02.554: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.554: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 48.430092ms Jan 30 06:20:02.554: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.557: INFO: Pod "metadata-proxy-v0.1-4glfd": Phase="Running", Reason="", readiness=true. Elapsed: 49.636363ms Jan 30 06:20:02.557: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb": Phase="Running", Reason="", readiness=true. Elapsed: 49.551669ms Jan 30 06:20:02.557: INFO: Pod "metadata-proxy-v0.1-4glfd" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.557: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.557: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:20:02.557: INFO: Getting external IP address for bootstrap-e2e-minion-group-89rb Jan 30 06:20:02.557: INFO: SSH "nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo b | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-89rb(34.168.49.142:22) Jan 30 06:20:02.557: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg": Phase="Running", Reason="", readiness=true. Elapsed: 50.35476ms Jan 30 06:20:02.557: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.557: INFO: Pod "metadata-proxy-v0.1-srxc6": Phase="Running", Reason="", readiness=true. Elapsed: 50.357594ms Jan 30 06:20:02.557: INFO: Pod "metadata-proxy-v0.1-srxc6" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.557: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: true. Pods: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:20:02.557: INFO: Getting external IP address for bootstrap-e2e-minion-group-j5pg Jan 30 06:20:02.557: INFO: SSH "nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo b | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 &" on bootstrap-e2e-minion-group-j5pg(34.82.243.144:22) Jan 30 06:20:02.557: INFO: Pod "metadata-proxy-v0.1-zckpq": Phase="Running", Reason="", readiness=true. Elapsed: 50.248508ms Jan 30 06:20:02.557: INFO: Pod "metadata-proxy-v0.1-zckpq" satisfied condition "running and ready, or succeeded" Jan 30 06:20:02.557: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 50.290677ms Jan 30 06:20:02.557: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:03.080: INFO: ssh prow@34.82.243.144:22: command: nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo b | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 & Jan 30 06:20:03.080: INFO: ssh prow@34.82.243.144:22: stdout: "" Jan 30 06:20:03.080: INFO: ssh prow@34.82.243.144:22: stderr: "" Jan 30 06:20:03.080: INFO: ssh prow@34.82.243.144:22: exit code: 0 Jan 30 06:20:03.080: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-j5pg condition Ready to be false Jan 30 06:20:03.080: INFO: ssh prow@34.168.49.142:22: command: nohup sh -c 'echo 1 | sudo tee /proc/sys/kernel/sysrq && sleep 10 && echo b | sudo tee /proc/sysrq-trigger' >/dev/null 2>&1 & Jan 30 06:20:03.080: INFO: ssh prow@34.168.49.142:22: stdout: "" Jan 30 06:20:03.080: INFO: ssh prow@34.168.49.142:22: stderr: "" Jan 30 06:20:03.080: INFO: ssh prow@34.168.49.142:22: exit code: 0 Jan 30 06:20:03.080: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-89rb condition Ready to be false Jan 30 06:20:03.124: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:03.124: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:04.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 2.093782285s Jan 30 06:20:04.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:05.169: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:05.169: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:06.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 4.093222656s Jan 30 06:20:06.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:07.213: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:07.213: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:08.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 6.094094699s Jan 30 06:20:08.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:09.258: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:09.258: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:10.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 8.093285101s Jan 30 06:20:10.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:11.302: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:11.302: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:12.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 10.092773548s Jan 30 06:20:12.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:13.347: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:13.347: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:14.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 12.094305118s Jan 30 06:20:14.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:15.391: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:15.391: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:16.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 14.093282521s Jan 30 06:20:16.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:17.441: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:17.441: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:18.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 16.093961969s Jan 30 06:20:18.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:19.486: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:19.486: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:20.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 18.093080536s Jan 30 06:20:20.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:21.530: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:21.530: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:22.599: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 20.092244388s Jan 30 06:20:22.599: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:23.575: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:23.575: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:24.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 22.093510389s Jan 30 06:20:24.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:25.618: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:25.618: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:26.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 24.092731528s Jan 30 06:20:26.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:27.663: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:27.664: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:28.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 26.094110455s Jan 30 06:20:28.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:29.708: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:29.708: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:30.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 28.093444948s Jan 30 06:20:30.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:31.751: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:31.752: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:32.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 30.092980009s Jan 30 06:20:32.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:33.797: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:33.797: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:34.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 32.094230098s Jan 30 06:20:34.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:35.842: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:35.842: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:36.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 34.092841586s Jan 30 06:20:36.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:37.887: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:37.887: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:38.615: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 36.108275852s Jan 30 06:20:38.615: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:39.931: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:39.931: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:40.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 38.093338898s Jan 30 06:20:40.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:41.975: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:41.975: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:42.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 40.093098855s Jan 30 06:20:42.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:46.064: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:46.065: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-89rb condition Ready to be true Jan 30 06:20:46.126: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 43.619123146s Jan 30 06:20:46.126: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:46.190: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:20:46.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 44.093761978s Jan 30 06:20:46.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:48.107: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:48.232: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:20:48.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 46.09290681s Jan 30 06:20:48.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:50.150: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:50.277: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:20:50.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 48.094077267s Jan 30 06:20:50.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:52.205: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:52.320: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:20:52.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 50.093721081s Jan 30 06:20:52.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:54.247: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 06:20:54.363: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:20:54.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 52.092748807s Jan 30 06:20:54.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:56.300: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-j5pg condition Ready to be true Jan 30 06:20:56.378: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:20:56.405: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:20:56.599: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 54.092062901s Jan 30 06:20:56.599: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:20:58.420: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:20:58.449: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:20:58.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 56.093449714s Jan 30 06:20:58.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:00.464: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 06:21:00.491: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:00.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 58.092788392s Jan 30 06:21:00.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:02.507: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:02.535: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:02.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m0.09440931s Jan 30 06:21:02.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:04.550: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:04.578: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:04.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m2.093729898s Jan 30 06:21:04.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:06.592: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:06.599: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.092444394s Jan 30 06:21:06.599: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:06.621: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:08.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.094378398s Jan 30 06:21:08.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:08.635: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:08.686: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:10.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m8.09302246s Jan 30 06:21:10.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:10.679: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:10.729: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:12.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.092875224s Jan 30 06:21:12.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:12.721: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:12.772: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:14.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.092980311s Jan 30 06:21:14.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:14.767: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:14.817: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:16.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m14.09272813s Jan 30 06:21:16.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:16.812: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:16.860: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:18.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.093770003s Jan 30 06:21:18.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:18.856: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:18.903: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:20.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.093766883s Jan 30 06:21:20.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:20.898: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:20.946: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:22.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.093614634s Jan 30 06:21:22.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:22.941: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:22.989: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:46 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:24.601: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.094042548s Jan 30 06:21:24.601: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:24.986: INFO: Condition Ready of node bootstrap-e2e-minion-group-j5pg is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 06:20:56 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 06:21:01 +0000 UTC}]. Failure Jan 30 06:21:25.032: INFO: Condition Ready of node bootstrap-e2e-minion-group-89rb is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoExecute 2023-01-30 06:20:51 +0000 UTC}]. Failure Jan 30 06:21:26.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m24.092889737s Jan 30 06:21:26.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:27.028: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:21:27.028: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:21:27.028: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-srxc6" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:21:27.028: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:21:27.029: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-bg4vb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:21:27.071: INFO: Pod "metadata-proxy-v0.1-srxc6": Phase="Running", Reason="", readiness=false. Elapsed: 42.980113ms Jan 30 06:21:27.071: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-srxc6' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:15 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:15 +0000 UTC }] Jan 30 06:21:27.071: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 43.142705ms Jan 30 06:21:27.071: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:00 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC }] Jan 30 06:21:27.072: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg": Phase="Running", Reason="", readiness=false. Elapsed: 43.932826ms Jan 30 06:21:27.072: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-j5pg' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:11:54 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:27.072: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb": Phase="Running", Reason="", readiness=false. Elapsed: 43.657715ms Jan 30 06:21:27.072: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-bg4vb' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:21:26 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC }] Jan 30 06:21:27.075: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:21:27.075: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-4glfd" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:21:27.075: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-89rb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 06:21:27.117: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb": Phase="Running", Reason="", readiness=true. Elapsed: 42.477435ms Jan 30 06:21:27.117: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-89rb" satisfied condition "running and ready, or succeeded" Jan 30 06:21:27.117: INFO: Pod "metadata-proxy-v0.1-4glfd": Phase="Running", Reason="", readiness=false. Elapsed: 42.53531ms Jan 30 06:21:27.118: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-4glfd' on 'bootstrap-e2e-minion-group-89rb' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:13 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:46 +0000 UTC ContainersNotReady containers with unready status: [metadata-proxy prometheus-to-sd-exporter]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:21:24 +0000 UTC ContainersNotReady containers with unready status: [metadata-proxy prometheus-to-sd-exporter]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:12 +0000 UTC }] Jan 30 06:21:28.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m26.09354723s Jan 30 06:21:28.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:29.114: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2.085534152s Jan 30 06:21:29.114: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:00 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC }] Jan 30 06:21:29.116: INFO: Pod "metadata-proxy-v0.1-srxc6": Phase="Running", Reason="", readiness=false. Elapsed: 2.087438366s Jan 30 06:21:29.116: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'metadata-proxy-v0.1-srxc6' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:15 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:15 +0000 UTC }] Jan 30 06:21:29.116: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb": Phase="Running", Reason="", readiness=false. Elapsed: 2.087189633s Jan 30 06:21:29.116: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-bg4vb' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:21:26 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC }] Jan 30 06:21:29.117: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg": Phase="Running", Reason="", readiness=false. Elapsed: 2.08865727s Jan 30 06:21:29.117: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-j5pg' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:11:54 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:29.160: INFO: Pod "metadata-proxy-v0.1-4glfd": Phase="Running", Reason="", readiness=true. Elapsed: 2.084701302s Jan 30 06:21:29.160: INFO: Pod "metadata-proxy-v0.1-4glfd" satisfied condition "running and ready, or succeeded" Jan 30 06:21:29.160: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-89rb metadata-proxy-v0.1-4glfd] Jan 30 06:21:29.160: INFO: Reboot successful on node bootstrap-e2e-minion-group-89rb Jan 30 06:21:30.600: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-jt1b": Phase="Running", Reason="", readiness=false. Elapsed: 1m28.093549667s Jan 30 06:21:30.600: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-jt1b' on 'bootstrap-e2e-minion-group-jt1b' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:19:33 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:14 +0000 UTC }] Jan 30 06:21:31.116: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4.087767582s Jan 30 06:21:31.116: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:21:26 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC }] Jan 30 06:21:31.119: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg": Phase="Running", Reason="", readiness=true. Elapsed: 4.090425966s Jan 30 06:21:31.119: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-j5pg" satisfied condition "running and ready, or succeeded" Jan 30 06:21:31.119: INFO: Pod "metadata-proxy-v0.1-srxc6": Phase="Running", Reason="", readiness=true. Elapsed: 4.090445606s Jan 30 06:21:31.119: INFO: Pod "metadata-proxy-v0.1-srxc6" satisfied condition "running and ready, or succeeded" Jan 30 06:21:31.119: INFO: Pod "kube-dns-autoscaler-5f6455f985-bg4vb": Phase="Running", Reason="", readiness=false. Elapsed: 4.090193925s Jan 30 06:21:31.119: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-bg4vb' on 'bootstrap-e2e-minion-group-j5pg' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:20:56 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:21:26 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 06:04:27 +0000 UTC }] Jan 30 06:21:32.597: INFO: Encountered non-retryable error while getting pod kube-system/kube-proxy-bootstrap-e2e-minion-group-jt1b: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/kube-proxy-bootstrap-e2e-minion-group-jt1b": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:32.597: INFO: Pod kube-proxy-bootstrap-e2e-minion-group-jt1b failed to be running and ready, or succeeded. Jan 30 06:21:32.597: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: false. Pods: [kube-proxy-bootstrap-e2e-minion-group-jt1b metadata-proxy-v0.1-zckpq] Jan 30 06:21:32.597: INFO: Status for not ready pod kube-system/kube-proxy-bootstrap-e2e-minion-group-jt1b: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:04:14 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:19:33 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-proxy]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:19:33 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-proxy]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:04:14 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP:10.138.0.4 PodIPs:[{IP:10.138.0.4}] StartTime:2023-01-30 06:04:14 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:kube-proxy State:{Waiting:&ContainerStateWaiting{Reason:CrashLoopBackOff,Message:back-off 2m40s restarting failed container=kube-proxy pod=kube-proxy-bootstrap-e2e-minion-group-jt1b_kube-system(87a78f5a508a69cfa60729c5d4dc7da6),} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-30 06:18:15 +0000 UTC,FinishedAt:2023-01-30 06:19:32 +0000 UTC,ContainerID:containerd://2706e16bf15ab1c5d363a47ede8c5e7c702cbd5397878deabd334d57735a2432,}} Ready:false RestartCount:5 Image:registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4 ImageID:sha256:c4cd2f6a04c334ec2dfc72eb03fcaacc3231faaa0dfd84b73b8f65c5b0afa401 ContainerID:containerd://2706e16bf15ab1c5d363a47ede8c5e7c702cbd5397878deabd334d57735a2432 Started:0xc0035e18df}] QOSClass:Burstable EphemeralContainerStatuses:[]} Jan 30 06:21:32.637: INFO: Retrieving log for container kube-system/kube-proxy-bootstrap-e2e-minion-group-jt1b/kube-proxy, err: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/kube-proxy-bootstrap-e2e-minion-group-jt1b/log?container=kube-proxy&previous=false": dial tcp 34.145.121.12:443: connect: connection refused: Jan 30 06:21:32.637: INFO: Retrieving log for the last terminated container kube-system/kube-proxy-bootstrap-e2e-minion-group-jt1b/kube-proxy, err: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/kube-proxy-bootstrap-e2e-minion-group-jt1b/log?container=kube-proxy&previous=false": dial tcp 34.145.121.12:443: connect: connection refused: Jan 30 06:21:33.112: INFO: Encountered non-retryable error while getting pod kube-system/volume-snapshot-controller-0: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/volume-snapshot-controller-0": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:33.112: INFO: Encountered non-retryable error while getting pod kube-system/kube-dns-autoscaler-5f6455f985-bg4vb: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/kube-dns-autoscaler-5f6455f985-bg4vb": dial tcp 34.145.121.12:443: connect: connection refused Jan 30 06:21:33.112: INFO: Pod volume-snapshot-controller-0 failed to be running and ready, or succeeded. Jan 30 06:21:33.112: INFO: Pod kube-dns-autoscaler-5f6455f985-bg4vb failed to be running and ready, or succeeded. Jan 30 06:21:33.112: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: false. Pods: [kube-dns-autoscaler-5f6455f985-bg4vb kube-proxy-bootstrap-e2e-minion-group-j5pg metadata-proxy-v0.1-srxc6 volume-snapshot-controller-0] Jan 30 06:21:33.112: INFO: Status for not ready pod kube-system/kube-dns-autoscaler-5f6455f985-bg4vb: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:04:27 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:20:56 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [autoscaler]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:21:26 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [autoscaler]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 06:04:27 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.3 PodIP: PodIPs:[] StartTime:2023-01-30 06:04:27 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:autoscaler State:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:255,Signal:0,Reason:Unknown,Message:,StartedAt:2023-01-30 06:17:57 +0000 UTC,FinishedAt:2023-01-30 06:20:33 +0000 UTC,ContainerID:containerd://8f100b8734a08caf875dab9185fa342bfaff9c5689c62ccd09d606c6ebb5059f,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:6 Image:registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4 ImageID:registry.k8s.io/cpa/cluster-proportional-autoscaler@sha256:fd636b33485c7826fb20ef0688a83ee0910317dbb6c0c6f3ad14661c1db25def ContainerID:containerd://8f100b8734a08caf875dab9185fa342bfaff9c5689c62ccd09d606c6ebb5059f Started:0xc0046c9b77}] QOSClass:Burstable EphemeralContainerStatuses:[]} Jan 30 06:21:33.151: INFO: Retrieving log for container kube-system/kube-dns-autoscaler-5f6455f985-bg4vb/autoscaler, err: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/kube-dns-autoscaler-5f6455f985-bg4vb/log?container=autoscaler&previous=false": dial tcp 34.145.121.12:443: connect: connection refused: Jan 30 06:21:33.151: INFO: Retrieving log for the last terminated container kube-system/kube-dns-autoscaler-5f6455f985-bg4vb/autoscaler, err: Get "https://34.145.121.12/api/v1/namespaces/kube-system/pods/kube-dns-autoscaler-5f6455f985-bg4vb/log?container=autoscaler&previous=false": dial tcp 34.145.121.12:443: connect: connection refused: Jan 30 06:21:33.151: INFO: Node bootstrap-e2e-minion-group-j5pg failed reboot test. Jan 30 06:21:33.151: INFO: Node bootstrap-e2e-minion-group-jt1b failed reboot test. [FAILED] Test failed; at least one node failed to reboot in the time given. In [It] at: test/e2e/cloud/gcp/reboot.go:190 @ 01/30/23 06:21:33.152 < Exit [It] each node by ordering unclean reboot and ensure they function upon restart - test/e2e/cloud/gcp/reboot.go:103 @ 01/30/23 06:21:33.152 (1m30.865s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:21:33.152 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 06:21:33.152 Jan 30 06:21:33.191: INFO: Unexpected error: <*url.Error | 0xc003945d70>: { Op: "Get", URL: "https://34.145.121.12/api/v1/namespaces/kube-system/events", Err: <*net.OpError | 0xc0039191d0>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc0043daf60>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 145, 121, 12], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc00533ca60>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } [FAILED] Get "https://34.145.121.12/api/v1/namespaces/kube-system/events": dial tcp 34.145.121.12:443: connect: connection refused In [AfterEach] at: test/e2e/cloud/gcp/reboot.go:75 @ 01/30/23 06:21:33.192 < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 06:21:33.192 (40ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:21:33.192 Jan 30 06:21:33.192: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready < Exit [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 06:21:33.231 (39ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 06:21:33.231 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 06:21:33.231 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:21:33.231 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:21:33.231 STEP: Collecting events from namespace "reboot-127". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 06:21:33.231 Jan 30 06:21:33.271: INFO: Unexpected error: failed to list events in namespace "reboot-127": <*url.Error | 0xc005012ea0>: { Op: "Get", URL: "https://34.145.121.12/api/v1/namespaces/reboot-127/events", Err: <*net.OpError | 0xc004868870>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc0043db500>{ IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 34, 145, 121, 12], Port: 443, Zone: "", }, Err: <*os.SyscallError | 0xc000597760>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, } END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 06:21:33.271 (40ms) [FAILED] failed to list events in namespace "reboot-127": Get "https://34.145.121.12/api/v1/namespaces/reboot-127/events": dial tcp 34.145.121.12:443: connect: connection refused In [DeferCleanup (Each)] at: test/e2e/framework/debug/dump.go:44 @ 01/30/23 06:21:33.271 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 06:21:33.271 (40ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:21:33.271 STEP: Destroying namespace "reboot-127" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 06:21:33.271 [FAILED] Couldn't delete ns: "reboot-127": Delete "https://34.145.121.12/api/v1/namespaces/reboot-127": dial tcp 34.145.121.12:443: connect: connection refused (&url.Error{Op:"Delete", URL:"https://34.145.121.12/api/v1/namespaces/reboot-127", Err:(*net.OpError)(0xc001c28280)}) In [DeferCleanup (Each)] at: test/e2e/framework/framework.go:383 @ 01/30/23 06:21:33.311 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 06:21:33.311 (40ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:21:33.311 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 06:21:33.311 (0s)
Filter through log files
error during ./hack/ginkgo-e2e.sh --ginkgo.focus=\[Feature:Reboot\] --minStartupPods=8 --report-dir=/workspace/_artifacts --disable-log-dump=true: exit status 1
from junit_runner.xml
Filter through log files
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by switching off the network interface and ensure they function upon switch on
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by switching off the network interface and ensure they function upon switch on
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by triggering kernel panic and ensure they function upon restart
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by triggering kernel panic and ensure they function upon restart
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e JUnit report
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [ReportBeforeSuite]
Kubernetes e2e suite [ReportBeforeSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedBeforeSuite]
Kubernetes e2e suite [SynchronizedBeforeSuite]
kubetest Check APIReachability
kubetest Deferred TearDown
kubetest DumpClusterLogs
kubetest Extract
kubetest GetDeployer
kubetest IsUp
kubetest Prepare
kubetest TearDown
kubetest TearDown Previous
kubetest Timeout
kubetest Up
kubetest diffResources
kubetest kubectl version
kubetest list nodes
kubetest listResources After
kubetest listResources Before
kubetest listResources Down
kubetest listResources Up
kubetest test setup
Kubernetes e2e suite [It] [sig-api-machinery] API priority and fairness should ensure that requests can be classified by adding FlowSchema and PriorityLevelConfiguration
Kubernetes e2e suite [It] [sig-api-machinery] API priority and fairness should ensure that requests can be classified by adding FlowSchema and PriorityLevelConfiguration
Kubernetes e2e suite [It] [sig-api-machinery] API priority and fairness should ensure that requests can't be drowned out (fairness)
Kubernetes e2e suite [It] [sig-api-machinery] API priority and fairness should ensure that requests can't be drowned out (fairness)
Kubernetes e2e suite [It] [sig-api-machinery] API priority and fairness should ensure that requests can't be drowned out (priority)
Kubernetes e2e suite [It] [sig-api-machinery] API priority and fairness should ensure that requests can't be drowned out (priority)
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing mutating webhooks should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing mutating webhooks should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing validating webhooks should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing validating webhooks should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny attaching pod [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny attaching pod [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny pod and configmap creation [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny pod and configmap creation [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should deny crd creation [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should deny crd creation [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should include webhook resources in discovery documents [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should include webhook resources in discovery documents [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with different stored version [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with different stored version [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with pruning [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with pruning [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Aggregator Should be able to support the 1.17 Sample API Server using the current Aggregator [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Aggregator Should be able to support the 1.17 Sample API Server using the current Aggregator [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert a non homogeneous list of CRs [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert a non homogeneous list of CRs [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition Watch [Privileged:ClusterAdmin] CustomResourceDefinition Watch watch on custom resource definition objects [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition Watch [Privileged:ClusterAdmin] CustomResourceDefinition Watch watch on custom resource definition objects [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition creating/deleting custom resource definition objects works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition creating/deleting custom resource definition objects works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition getting/updating/patching custom resource definition status sub-resource works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition getting/updating/patching custom resource definition status sub-resource works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition listing custom resource definition objects works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition listing custom resource definition objects works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] custom resource defaulting for requests and from storage works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] custom resource defaulting for requests and from storage works [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] should include custom resource definition resources in discovery documents [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] should include custom resource definition resources in discovery documents [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] [Flaky] kubectl explain works for CR with the same resource name as built-in object.
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] [Flaky] kubectl explain works for CR with the same resource name as built-in object.
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] removes definition from spec when one version gets changed to not be served [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] removes definition from spec when one version gets changed to not be served [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] updates the published spec when one version gets renamed [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] updates the published spec when one version gets renamed [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD preserving unknown fields at the schema root [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD preserving unknown fields at the schema root [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD preserving unknown fields in an embedded object [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD preserving unknown fields in an embedded object [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD with validation schema [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD with validation schema [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD without validation schema [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD without validation schema [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of different groups [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of different groups [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of same group and version but different kinds [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of same group and version but different kinds [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of same group but different versions [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of same group but different versions [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST NOT fail validation for create of a custom resource that satisfies the x-kubernetes-validations rules
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST NOT fail validation for create of a custom resource that satisfies the x-kubernetes-validations rules
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource definition that contains a x-kubernetes-validations rule that refers to a property that do not exist
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource definition that contains a x-kubernetes-validations rule that refers to a property that do not exist
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource definition that contains an x-kubernetes-validations rule that contains a syntax error
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource definition that contains an x-kubernetes-validations rule that contains a syntax error
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource definition that contains an x-kubernetes-validations rule that exceeds the estimated cost limit
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource definition that contains an x-kubernetes-validations rule that exceeds the estimated cost limit
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource that exceeds the runtime cost limit for x-kubernetes-validations rule execution
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail create of a custom resource that exceeds the runtime cost limit for x-kubernetes-validations rule execution
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail update of a custom resource that does not satisfy a x-kubernetes-validations transition rule
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail update of a custom resource that does not satisfy a x-kubernetes-validations transition rule
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail validation for create of a custom resource that does not satisfy the x-kubernetes-validations rules
Kubernetes e2e suite [It] [sig-api-machinery] CustomResourceValidationRules [Privileged:ClusterAdmin] MUST fail validation for create of a custom resource that does not satisfy the x-kubernetes-validations rules
Kubernetes e2e suite [It] [sig-api-machinery] Discovery Custom resource should have storage version hash
Kubernetes e2e suite [It] [sig-api-machinery] Discovery Custom resource should have storage version hash
Kubernetes e2e suite [It] [sig-api-machinery] Discovery should accurately determine present and missing resources
Kubernetes e2e suite [It] [sig-api-machinery] Discovery should accurately determine present and missing resources
Kubernetes e2e suite [It] [sig-api-machinery] Discovery should validate PreferredVersion for each APIGroup [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Discovery should validate PreferredVersion for each APIGroup [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Etcd failure [Disruptive] should recover from SIGKILL
Kubernetes e2e suite [It] [sig-api-machinery] Etcd failure [Disruptive] should recover from SIGKILL
Kubernetes e2e suite [It] [sig-api-machinery] Etcd failure [Disruptive] should recover from network partition with master
Kubernetes e2e suite [It] [sig-api-machinery] Etcd failure [Disruptive] should recover from network partition with master
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should create/apply a CR with unknown fields for CRD with no validation schema
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should create/apply a CR with unknown fields for CRD with no validation schema
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should create/apply a valid CR for CRD with validation schema
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should create/apply a valid CR for CRD with validation schema
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should create/apply an invalid CR with extra properties for CRD with validation schema
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should create/apply an invalid CR with extra properties for CRD with validation schema
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect duplicates in a CR when preserving unknown fields
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect duplicates in a CR when preserving unknown fields
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect unknown and duplicate fields of a typed object
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect unknown and duplicate fields of a typed object
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect unknown metadata fields in both the root and embedded object of a CR
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect unknown metadata fields in both the root and embedded object of a CR
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect unknown metadata fields of a typed object
Kubernetes e2e suite [It] [sig-api-machinery] FieldValidation should detect unknown metadata fields of a typed object
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should delete RS created by deployment when not orphaning [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should delete RS created by deployment when not orphaning [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should delete jobs and pods created by cronjob
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should delete jobs and pods created by cronjob
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should delete pods created by rc when not orphaning [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should delete pods created by rc when not orphaning [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should keep the rc around until all its pods are deleted if the deleteOptions says so [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should keep the rc around until all its pods are deleted if the deleteOptions says so [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should not be blocked by dependency circle [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should not be blocked by dependency circle [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should not delete dependents that have both valid owner and owner that's waiting for dependents to be deleted [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should not delete dependents that have both valid owner and owner that's waiting for dependents to be deleted [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should orphan RS created by deployment when deleteOptions.PropagationPolicy is Orphan [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should orphan RS created by deployment when deleteOptions.PropagationPolicy is Orphan [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should orphan pods created by rc if delete options say so [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should orphan pods created by rc if delete options say so [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should orphan pods created by rc if deleteOptions.OrphanDependents is nil
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should orphan pods created by rc if deleteOptions.OrphanDependents is nil
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should support cascading deletion of custom resources
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should support cascading deletion of custom resources
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should support orphan deletion of custom resources
Kubernetes e2e suite [It] [sig-api-machinery] Garbage collector should support orphan deletion of custom resources
Kubernetes e2e suite [It] [sig-api-machinery] Generated clientset should create pods, set the deletionTimestamp and deletionGracePeriodSeconds of the pod
Kubernetes e2e suite [It] [sig-api-machinery] Generated clientset should create pods, set the deletionTimestamp and deletionGracePeriodSeconds of the pod
Kubernetes e2e suite [It] [sig-api-machinery] Generated clientset should create v1 cronJobs, delete cronJobs, watch cronJobs
Kubernetes e2e suite [It] [sig-api-machinery] Generated clientset should create v1 cronJobs, delete cronJobs, watch cronJobs
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should always delete fast (ALL of 100 namespaces in 150 seconds) [Feature:ComprehensiveNamespaceDraining]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should always delete fast (ALL of 100 namespaces in 150 seconds) [Feature:ComprehensiveNamespaceDraining]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should apply a finalizer to a Namespace [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should apply a finalizer to a Namespace [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should apply an update to a Namespace [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should apply an update to a Namespace [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should apply changes to a namespace status [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should apply changes to a namespace status [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should delete fast enough (90 percent of 100 namespaces in 150 seconds)
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should delete fast enough (90 percent of 100 namespaces in 150 seconds)
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should ensure that all pods are removed when a namespace is deleted [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should ensure that all pods are removed when a namespace is deleted [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should patch a Namespace [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Namespaces [Serial] should patch a Namespace [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's multiple priority class scope (quota set to pod count: 2) against 2 pods with same priority classes.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's multiple priority class scope (quota set to pod count: 2) against 2 pods with same priority classes.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (cpu, memory quota set) against a pod with same priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (cpu, memory quota set) against a pod with same priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against 2 pods with different priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against 2 pods with different priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against 2 pods with same priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against 2 pods with same priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against a pod with different priority class (ScopeSelectorOpExists).
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against a pod with different priority class (ScopeSelectorOpExists).
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against a pod with different priority class (ScopeSelectorOpNotIn).
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against a pod with different priority class (ScopeSelectorOpNotIn).
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against a pod with same priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:PodPriority] should verify ResourceQuota's priority class scope (quota set to pod count: 1) against a pod with same priority class.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:ScopeSelectors] should verify ResourceQuota with best effort scope using scope-selectors.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:ScopeSelectors] should verify ResourceQuota with best effort scope using scope-selectors.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:ScopeSelectors] should verify ResourceQuota with terminating scopes through scope selectors.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota [Feature:ScopeSelectors] should verify ResourceQuota with terminating scopes through scope selectors.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should apply changes to a resourcequota status [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should apply changes to a resourcequota status [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should be able to update and delete ResourceQuota. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should be able to update and delete ResourceQuota. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a configMap. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a configMap. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a custom resource.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a custom resource.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a persistent volume claim
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a persistent volume claim
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a persistent volume claim with a storage class
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a persistent volume claim with a storage class
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a pod. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a pod. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a replica set. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a replica set. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a replication controller. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a replication controller. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a secret. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a secret. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a service. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a service. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and ensure its status is promptly calculated. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should create a ResourceQuota and ensure its status is promptly calculated. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should manage the lifecycle of a ResourceQuota [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should manage the lifecycle of a ResourceQuota [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should verify ResourceQuota with best effort scope. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should verify ResourceQuota with best effort scope. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should verify ResourceQuota with cross namespace pod affinity scope using scope-selectors.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should verify ResourceQuota with cross namespace pod affinity scope using scope-selectors.
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should verify ResourceQuota with terminating scopes. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] ResourceQuota should verify ResourceQuota with terminating scopes. [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Server request timeout default timeout should be used if the specified timeout in the request URL is 0s
Kubernetes e2e suite [It] [sig-api-machinery] Server request timeout default timeout should be used if the specified timeout in the request URL is 0s
Kubernetes e2e suite [It] [sig-api-machinery] Server request timeout should return HTTP status code 400 if the user specifies an invalid timeout in the request URL
Kubernetes e2e suite [It] [sig-api-machinery] Server request timeout should return HTTP status code 400 if the user specifies an invalid timeout in the request URL
Kubernetes e2e suite [It] [sig-api-machinery] Server request timeout the request should be served with a default timeout if the specified timeout in the request URL exceeds maximum allowed
Kubernetes e2e suite [It] [sig-api-machinery] Server request timeout the request should be served with a default timeout if the specified timeout in the request URL exceeds maximum allowed
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should create an applied object if it does not already exist
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should create an applied object if it does not already exist
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should give up ownership of a field if forced applied by a controller
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should give up ownership of a field if forced applied by a controller
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should ignore conflict errors if force apply is used
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should ignore conflict errors if force apply is used
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should not remove a field if an owner unsets the field but other managers still have ownership of the field
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should not remove a field if an owner unsets the field but other managers still have ownership of the field
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should remove a field if it is owned but removed in the apply request
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should remove a field if it is owned but removed in the apply request
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should work for CRDs
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should work for CRDs
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should work for subresources
Kubernetes e2e suite [It] [sig-api-machinery] ServerSideApply should work for subresources
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for API chunking should return chunks of results for list calls
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for API chunking should return chunks of results for list calls
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for API chunking should support continue listing from the last key if the original version has been compacted away, though the list is inconsistent [Slow]
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for API chunking should support continue listing from the last key if the original version has been compacted away, though the list is inconsistent [Slow]
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return a 406 for a backend which does not implement metadata [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return a 406 for a backend which does not implement metadata [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return chunks of table results for list calls
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return chunks of table results for list calls
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return generic metadata details across all namespaces for nodes
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return generic metadata details across all namespaces for nodes
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return pod details
Kubernetes e2e suite [It] [sig-api-machinery] Servers with support for Table transformation should return pod details
Kubernetes e2e suite [It] [sig-api-machinery] StorageVersion resources [Feature:StorageVersionAPI] storage version with non-existing id should be GC'ed
Kubernetes e2e suite [It] [sig-api-machinery] StorageVersion resources [Feature:StorageVersionAPI] storage version with non-existing id should be GC'ed
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should be able to restart watching from the last resource version observed by the previous watch [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should be able to restart watching from the last resource version observed by the previous watch [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should be able to start watching from a specific resource version [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should be able to start watching from a specific resource version [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should observe add, update, and delete watch notifications on configmaps [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should observe add, update, and delete watch notifications on configmaps [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should observe an object deletion if it stops meeting the requirements of the selector [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should observe an object deletion if it stops meeting the requirements of the selector [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should receive events on concurrent watches in same order [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] Watchers should receive events on concurrent watches in same order [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/json"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/json"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/json,application/vnd.kubernetes.protobuf"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/json,application/vnd.kubernetes.protobuf"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/vnd.kubernetes.protobuf"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/vnd.kubernetes.protobuf"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/vnd.kubernetes.protobuf,application/json"
Kubernetes e2e suite [It] [sig-api-machinery] client-go should negotiate watch and report errors with accept "application/vnd.kubernetes.protobuf,application/json"
Kubernetes e2e suite [It] [sig-api-machinery] health handlers should contain necessary checks
Kubernetes e2e suite [It] [sig-api-machinery] health handlers should contain necessary checks
Kubernetes e2e suite [It] [sig-api-machinery] kube-apiserver identity [Feature:APIServerIdentity] kube-apiserver identity should persist after restart [Disruptive]
Kubernetes e2e suite [It] [sig-api-machinery] kube-apiserver identity [Feature:APIServerIdentity] kube-apiserver identity should persist after restart [Disruptive]
Kubernetes e2e suite [It] [sig-api-machinery] server version should find the server version [Conformance]
Kubernetes e2e suite [It] [sig-api-machinery] server version should find the server version [Conformance]
Kubernetes e2e suite [It] [sig-apps] ControllerRevision [Serial] should manage the lifecycle of a ControllerRevision [Conformance]
Kubernetes e2e suite [It] [sig-apps] ControllerRevision [Serial] should manage the lifecycle of a ControllerRevision [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should be able to schedule after more than 100 missed schedule
Kubernetes e2e suite [It] [sig-apps] CronJob should be able to schedule after more than 100 missed schedule
Kubernetes e2e suite [It] [sig-apps] CronJob should delete failed finished jobs with limit of one job
Kubernetes e2e suite [It] [sig-apps] CronJob should delete failed finished jobs with limit of one job
Kubernetes e2e suite [It] [sig-apps] CronJob should delete successful finished jobs with limit of one successful job
Kubernetes e2e suite [It] [sig-apps] CronJob should delete successful finished jobs with limit of one successful job
Kubernetes e2e suite [It] [sig-apps] CronJob should not emit unexpected warnings
Kubernetes e2e suite [It] [sig-apps] CronJob should not emit unexpected warnings
Kubernetes e2e suite [It] [sig-apps] CronJob should not schedule jobs when suspended [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should not schedule jobs when suspended [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should not schedule new jobs when ForbidConcurrent [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should not schedule new jobs when ForbidConcurrent [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should remove from active list jobs that have been deleted
Kubernetes e2e suite [It] [sig-apps] CronJob should remove from active list jobs that have been deleted
Kubernetes e2e suite [It] [sig-apps] CronJob should replace jobs when ReplaceConcurrent [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should replace jobs when ReplaceConcurrent [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should schedule multiple jobs concurrently [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should schedule multiple jobs concurrently [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should support CronJob API operations [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should support CronJob API operations [Conformance]
Kubernetes e2e suite [It] [sig-apps] CronJob should support timezone
Kubernetes e2e suite [It] [sig-apps] CronJob should support timezone
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should list and delete a collection of DaemonSets [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should list and delete a collection of DaemonSets [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should not update pod when spec was updated and update strategy is OnDelete
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should not update pod when spec was updated and update strategy is OnDelete
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should retry creating failed daemon pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should retry creating failed daemon pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should run and stop complex daemon with node affinity
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should run and stop complex daemon with node affinity
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should surge pods onto nodes when spec was updated and update strategy is RollingUpdate
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should surge pods onto nodes when spec was updated and update strategy is RollingUpdate
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should verify changes to a daemon set status [Conformance]
Kubernetes e2e suite [It] [sig-apps] Daemon set [Serial] should verify changes to a daemon set status [Conformance]
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Controller Manager should not create/delete replicas across restart
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Controller Manager should not create/delete replicas across restart
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Kube-proxy should recover after being killed accidentally
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Kube-proxy should recover after being killed accidentally
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Kubelet should not restart containers across restart
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Kubelet should not restart containers across restart
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Scheduler should continue assigning pods to nodes across restart
Kubernetes e2e suite [It] [sig-apps] DaemonRestart [Disruptive] Scheduler should continue assigning pods to nodes across restart
Kubernetes e2e suite [It] [sig-apps] Deployment Deployment should have a working scale subresource [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment Deployment should have a working scale subresource [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment RecreateDeployment should delete old pods and create new ones [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment RecreateDeployment should delete old pods and create new ones [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment RollingUpdateDeployment should delete old pods and create new ones [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment RollingUpdateDeployment should delete old pods and create new ones [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment deployment reaping should cascade to its replica sets and pods
Kubernetes e2e suite [It] [sig-apps] Deployment deployment reaping should cascade to its replica sets and pods
Kubernetes e2e suite [It] [sig-apps] Deployment deployment should delete old replica sets [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment deployment should delete old replica sets [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment deployment should support proportional scaling [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment deployment should support proportional scaling [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment deployment should support rollover [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment deployment should support rollover [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment iterative rollouts should eventually progress
Kubernetes e2e suite [It] [sig-apps] Deployment iterative rollouts should eventually progress
Kubernetes e2e suite [It] [sig-apps] Deployment should not disrupt a cloud load-balancer's connectivity during rollout
Kubernetes e2e suite [It] [sig-apps] Deployment should not disrupt a cloud load-balancer's connectivity during rollout
Kubernetes e2e suite [It] [sig-apps] Deployment should run the lifecycle of a Deployment [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment should run the lifecycle of a Deployment [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment should validate Deployment Status endpoints [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment should validate Deployment Status endpoints [Conformance]
Kubernetes e2e suite [It] [sig-apps] Deployment test Deployment ReplicaSet orphaning and adoption regarding controllerRef
Kubernetes e2e suite [It] [sig-apps] Deployment test Deployment ReplicaSet orphaning and adoption regarding controllerRef
Kubernetes e2e suite [It] [sig-apps] DisruptionController Listing PodDisruptionBudgets for all namespaces should list and delete a collection of PodDisruptionBudgets [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController Listing PodDisruptionBudgets for all namespaces should list and delete a collection of PodDisruptionBudgets [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: enough pods, absolute => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: enough pods, absolute => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: enough pods, replicaSet, percentage => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: enough pods, replicaSet, percentage => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: maxUnavailable allow single eviction, percentage => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: maxUnavailable allow single eviction, percentage => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: maxUnavailable deny evictions, integer => should not allow an eviction [Serial]
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: maxUnavailable deny evictions, integer => should not allow an eviction [Serial]
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: no PDB => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: no PDB => should allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: too few pods, absolute => should not allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: too few pods, absolute => should not allow an eviction
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: too few pods, replicaSet, percentage => should not allow an eviction [Serial]
Kubernetes e2e suite [It] [sig-apps] DisruptionController evictions: too few pods, replicaSet, percentage => should not allow an eviction [Serial]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should block an eviction until the PDB is updated to allow it [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should block an eviction until the PDB is updated to allow it [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should create a PodDisruptionBudget [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should create a PodDisruptionBudget [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should observe PodDisruptionBudget status updated [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should observe PodDisruptionBudget status updated [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should observe that the PodDisruptionBudget status is not updated for unmanaged pods
Kubernetes e2e suite [It] [sig-apps] DisruptionController should observe that the PodDisruptionBudget status is not updated for unmanaged pods
Kubernetes e2e suite [It] [sig-apps] DisruptionController should update/patch PodDisruptionBudget status [Conformance]
Kubernetes e2e suite [It] [sig-apps] DisruptionController should update/patch PodDisruptionBudget status [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job Using a pod failure policy to not count some failures towards the backoffLimit Ignore DisruptionTarget condition
Kubernetes e2e suite [It] [sig-apps] Job Using a pod failure policy to not count some failures towards the backoffLimit Ignore DisruptionTarget condition
Kubernetes e2e suite [It] [sig-apps] Job Using a pod failure policy to not count some failures towards the backoffLimit Ignore exit code 137
Kubernetes e2e suite [It] [sig-apps] Job Using a pod failure policy to not count some failures towards the backoffLimit Ignore exit code 137
Kubernetes e2e suite [It] [sig-apps] Job should adopt matching orphans and release non-matching pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should adopt matching orphans and release non-matching pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should allow to use the pod failure policy on exit code to fail the job early
Kubernetes e2e suite [It] [sig-apps] Job should allow to use the pod failure policy on exit code to fail the job early
Kubernetes e2e suite [It] [sig-apps] Job should allow to use the pod failure policy to not count the failure towards the backoffLimit
Kubernetes e2e suite [It] [sig-apps] Job should allow to use the pod failure policy to not count the failure towards the backoffLimit
Kubernetes e2e suite [It] [sig-apps] Job should apply changes to a job status [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should apply changes to a job status [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should create pods for an Indexed job with completion indexes and specified hostname [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should create pods for an Indexed job with completion indexes and specified hostname [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should delete a job [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should delete a job [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should delete pods when suspended
Kubernetes e2e suite [It] [sig-apps] Job should delete pods when suspended
Kubernetes e2e suite [It] [sig-apps] Job should fail to exceed backoffLimit
Kubernetes e2e suite [It] [sig-apps] Job should fail to exceed backoffLimit
Kubernetes e2e suite [It] [sig-apps] Job should fail when exceeds active deadline
Kubernetes e2e suite [It] [sig-apps] Job should fail when exceeds active deadline
Kubernetes e2e suite [It] [sig-apps] Job should manage the lifecycle of a job [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should manage the lifecycle of a job [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should not create pods when created in suspend state
Kubernetes e2e suite [It] [sig-apps] Job should not create pods when created in suspend state
Kubernetes e2e suite [It] [sig-apps] Job should remove pods when job is deleted
Kubernetes e2e suite [It] [sig-apps] Job should remove pods when job is deleted
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion when tasks sometimes fail and are locally restarted [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion when tasks sometimes fail and are locally restarted [Conformance]
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion when tasks sometimes fail and are not locally restarted
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion when tasks sometimes fail and are not locally restarted
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion when tasks succeed
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion when tasks succeed
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion with CPU requests [Serial]
Kubernetes e2e suite [It] [sig-apps] Job should run a job to completion with CPU requests [Serial]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet Replace and Patch tests [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet Replace and Patch tests [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet Replicaset should have a working scale subresource [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet Replicaset should have a working scale subresource [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should adopt matching pods on creation and release no longer matching pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should adopt matching pods on creation and release no longer matching pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should list and delete a collection of ReplicaSets [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should list and delete a collection of ReplicaSets [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should serve a basic image on each replica with a private image
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should serve a basic image on each replica with a private image
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should serve a basic image on each replica with a public image [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should serve a basic image on each replica with a public image [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should surface a failure condition on a common issue like exceeded quota
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should surface a failure condition on a common issue like exceeded quota
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should validate Replicaset Status endpoints [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicaSet should validate Replicaset Status endpoints [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should adopt matching pods on creation [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should adopt matching pods on creation [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should get and update a ReplicationController scale [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should get and update a ReplicationController scale [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should release no longer matching pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should release no longer matching pods [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should serve a basic image on each replica with a private image
Kubernetes e2e suite [It] [sig-apps] ReplicationController should serve a basic image on each replica with a private image
Kubernetes e2e suite [It] [sig-apps] ReplicationController should serve a basic image on each replica with a public image [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should serve a basic image on each replica with a public image [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should surface a failure condition on a common issue like exceeded quota [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should surface a failure condition on a common issue like exceeded quota [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should test the lifecycle of a ReplicationController [Conformance]
Kubernetes e2e suite [It] [sig-apps] ReplicationController should test the lifecycle of a ReplicationController [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet AvailableReplicas should get updated accordingly when MinReadySeconds is enabled
Kubernetes e2e suite [It] [sig-apps] StatefulSet AvailableReplicas should get updated accordingly when MinReadySeconds is enabled
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Burst scaling should run to completion even with unhealthy pods [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Burst scaling should run to completion even with unhealthy pods [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Scaling should happen in predictable order and halt if any stateful pod is unhealthy [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Scaling should happen in predictable order and halt if any stateful pod is unhealthy [Slow] [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Should recreate evicted statefulset [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Should recreate evicted statefulset [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should adopt matching orphans and release non-matching pods
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should adopt matching orphans and release non-matching pods
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should have a working scale subresource [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should have a working scale subresource [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should implement legacy replacement when the update strategy is OnDelete
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should implement legacy replacement when the update strategy is OnDelete
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should list, patch and delete a collection of StatefulSets [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should list, patch and delete a collection of StatefulSets [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should not deadlock when a pod's predecessor fails
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should not deadlock when a pod's predecessor fails
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform canary updates and phased rolling updates of template modifications [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform canary updates and phased rolling updates of template modifications [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications with PVCs
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should provide basic identity
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should provide basic identity
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should validate Statefulset Status endpoints [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should validate Statefulset Status endpoints [Conformance]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working CockroachDB cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working CockroachDB cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working mysql cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working mysql cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working redis cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working redis cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working zookeeper cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet Deploy clustered applications [Feature:StatefulSet] [Slow] should creating a working zookeeper cluster
Kubernetes e2e suite [It] [sig-apps] StatefulSet MinReadySeconds should be honored when enabled
Kubernetes e2e suite [It] [sig-apps] StatefulSet MinReadySeconds should be honored when enabled
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs after adopting pod (WhenDeleted)
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs after adopting pod (WhenDeleted)
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs after adopting pod (WhenScaled) [Feature:StatefulSetAutoDeletePVC]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs after adopting pod (WhenScaled) [Feature:StatefulSetAutoDeletePVC]
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs with a OnScaledown policy
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs with a OnScaledown policy
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs with a WhenDeleted policy
Kubernetes e2e suite [It] [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy [Feature:StatefulSetAutoDeletePVC] should delete PVCs with a WhenDeleted policy
Kubernetes e2e suite [It] [sig-apps] TTLAfterFinished job should be deleted once it finishes after TTL seconds
Kubernetes e2e suite [It] [sig-apps] TTLAfterFinished job should be deleted once it finishes after TTL seconds
Kubernetes e2e suite [It] [sig-apps] stateful Upgrade [Feature:StatefulUpgrade] stateful upgrade should maintain a functioning cluster
Kubernetes e2e suite [It] [sig-apps] stateful Upgrade [Feature:StatefulUpgrade] stateful upgrade should maintain a functioning cluster
Kubernetes e2e suite [It] [sig-architecture] Conformance Tests should have at least two untainted nodes [Conformance]
Kubernetes e2e suite [It] [sig-architecture] Conformance Tests should have at least two untainted nodes [Conformance]
Kubernetes e2e suite [It] [sig-auth] Certificates API [Privileged:ClusterAdmin] should support CSR API operations [Conformance]
Kubernetes e2e suite [It] [sig-auth] Certificates API [Privileged:ClusterAdmin] should support CSR API operations [Conformance]
Kubernetes e2e suite [It] [sig-auth] Certificates API [Privileged:ClusterAdmin] should support building a client with a CSR
Kubernetes e2e suite [It] [sig-auth] Certificates API [Privileged:ClusterAdmin] should support building a client with a CSR
Kubernetes e2e suite [It] [sig-auth] SelfSubjectReview [Feature:APISelfSubjectReview] should support SelfSubjectReview API operations
Kubernetes e2e suite [It] [sig-auth] SelfSubjectReview [Feature:APISelfSubjectReview] should support SelfSubjectReview API operations
Kubernetes e2e suite [It] [sig-auth] ServiceAccount admission controller migration [Feature:BoundServiceAccountTokenVolume] master upgrade should maintain a functioning cluster
Kubernetes e2e suite [It] [sig-auth] ServiceAccount admission controller migration [Feature:BoundServiceAccountTokenVolume] master upgrade should maintain a functioning cluster
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts no secret-based service account token should be auto-generated
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts no secret-based service account token should be auto-generated
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should allow opting out of API token automount [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should allow opting out of API token automount [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should guarantee kube-root-ca.crt exist in any namespace [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should guarantee kube-root-ca.crt exist in any namespace [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should mount an API token into pods [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should mount an API token into pods [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should mount projected service account token [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should mount projected service account token [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should run through the lifecycle of a ServiceAccount [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should run through the lifecycle of a ServiceAccount [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should set ownership and permission when RunAsUser or FsGroup is present [LinuxOnly] [NodeFeature:FSGroup]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should set ownership and permission when RunAsUser or FsGroup is present [LinuxOnly] [NodeFeature:FSGroup]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should support InClusterConfig with token rotation [Slow]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should support InClusterConfig with token rotation [Slow]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should update a ServiceAccount [Conformance]
Kubernetes e2e suite [It] [sig-auth] ServiceAccounts should update a ServiceAccount [Conformance]
Kubernetes e2e suite [It] [sig-auth] SubjectReview should support SubjectReview API operations [Conformance]
Kubernetes e2e suite [It] [sig-auth] SubjectReview should support SubjectReview API operations [Conformance]
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthenticator] The kubelet can delegate ServiceAccount tokens to the API server
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthenticator] The kubelet can delegate ServiceAccount tokens to the API server
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthenticator] The kubelet's main port 10250 should reject requests with no credentials
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthenticator] The kubelet's main port 10250 should reject requests with no credentials
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] A node shouldn't be able to create another node
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] A node shouldn't be able to create another node
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] A node shouldn't be able to delete another node
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] A node shouldn't be able to delete another node
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting a non-existent configmap should exit with the Forbidden error, not a NotFound error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting a non-existent configmap should exit with the Forbidden error, not a NotFound error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting a non-existent secret should exit with the Forbidden error, not a NotFound error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting a non-existent secret should exit with the Forbidden error, not a NotFound error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting a secret for a workload the node has access to should succeed
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting a secret for a workload the node has access to should succeed
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting an existing configmap should exit with the Forbidden error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting an existing configmap should exit with the Forbidden error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting an existing secret should exit with the Forbidden error
Kubernetes e2e suite [It] [sig-auth] [Feature:NodeAuthorizer] Getting an existing secret should exit with the Forbidden error
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] CA ignores unschedulable pods while scheduling schedulable pods [Feature:ClusterAutoscalerScalability6]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] CA ignores unschedulable pods while scheduling schedulable pods [Feature:ClusterAutoscalerScalability6]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale down empty nodes [Feature:ClusterAutoscalerScalability3]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale down empty nodes [Feature:ClusterAutoscalerScalability3]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale down underutilized nodes [Feature:ClusterAutoscalerScalability4]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale down underutilized nodes [Feature:ClusterAutoscalerScalability4]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale up at all [Feature:ClusterAutoscalerScalability1]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale up at all [Feature:ClusterAutoscalerScalability1]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale up twice [Feature:ClusterAutoscalerScalability2]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] should scale up twice [Feature:ClusterAutoscalerScalability2]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] shouldn't scale down with underutilized nodes due to host port conflicts [Feature:ClusterAutoscalerScalability5]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaler scalability [Slow] shouldn't scale down with underutilized nodes due to host port conflicts [Feature:ClusterAutoscalerScalability5]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should be able to scale a node group down to 0[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should be able to scale a node group down to 0[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should be able to scale a node group up from 0[Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should be able to scale a node group up from 0[Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should not scale GPU pool up if pod does not require GPUs [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should not scale GPU pool up if pod does not require GPUs [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should scale down GPU pool from 1 [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should scale down GPU pool from 1 [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should scale up GPU pool from 0 [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should scale up GPU pool from 0 [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should scale up GPU pool from 1 [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Should scale up GPU pool from 1 [GpuType:] [Feature:ClusterSizeAutoscalingGpu]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Shouldn't perform scale up operation and should list unhealthy status if most of the cluster is broken[Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] Shouldn't perform scale up operation and should list unhealthy status if most of the cluster is broken[Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should add node to the particular mig [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should add node to the particular mig [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down by draining multiple pods one by one as dictated by pdb[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down by draining multiple pods one by one as dictated by pdb[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down by draining system pods with pdb[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down by draining system pods with pdb[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down when rescheduling a pod is required and pdb allows for it[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down when rescheduling a pod is required and pdb allows for it[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should correctly scale down after a node is not needed [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should correctly scale down after a node is not needed [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should correctly scale down after a node is not needed and one node is broken [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should correctly scale down after a node is not needed and one node is broken [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should correctly scale down after a node is not needed when there is non autoscaled pool[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should correctly scale down after a node is not needed when there is non autoscaled pool[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should disable node pool autoscaling [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should disable node pool autoscaling [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small and one node is broken [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small and one node is broken [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small and there is another node pool that is not autoscaled [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pending pods are small and there is another node pool that is not autoscaled [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pod requesting EmptyDir volume is pending [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pod requesting EmptyDir volume is pending [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pod requesting volume is pending [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pod requesting volume is pending [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pods are pending due to host port conflict [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pods are pending due to host port conflict [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pods are pending due to pod anti-affinity [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should increase cluster size if pods are pending due to pod anti-affinity [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should scale down when expendable pod is running [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should scale down when expendable pod is running [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should scale up correct target pool [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should scale up correct target pool [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should scale up when non expendable pod is created [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] should scale up when non expendable pod is created [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't be able to scale down when rescheduling a pod is required, but pdb doesn't allow drain[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't be able to scale down when rescheduling a pod is required, but pdb doesn't allow drain[Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't increase cluster size if pending pod is too large [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't increase cluster size if pending pod is too large [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't scale down when non expendable pod is running [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't scale down when non expendable pod is running [Feature:ClusterSizeAutoscalingScaleDown]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't scale up when expendable pod is created [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't scale up when expendable pod is created [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't scale up when expendable pod is preempted [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't scale up when expendable pod is preempted [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't trigger additional scale-ups during processing scale-up [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] Cluster size autoscaling [Slow] shouldn't trigger additional scale-ups during processing scale-up [Feature:ClusterSizeAutoscalingScaleUp]
Kubernetes e2e suite [It] [sig-autoscaling] DNS horizontal autoscaling [Serial] [Slow] kube-dns-autoscaler should scale kube-dns pods when cluster size changed
Kubernetes e2e suite [It] [sig-autoscaling] DNS horizontal autoscaling [Serial] [Slow] kube-dns-autoscaler should scale kube-dns pods when cluster size changed
Kubernetes e2e suite [It] [sig-autoscaling] DNS horizontal autoscaling kube-dns-autoscaler should scale kube-dns pods in both nonfaulty and faulty scenarios
Kubernetes e2e suite [It] [sig-autoscaling] DNS horizontal autoscaling kube-dns-autoscaler should scale kube-dns pods in both nonfaulty and faulty scenarios
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:ClusterSizeAutoscalingScaleUp] [Slow] Autoscaling Autoscaling a service from 1 pod and 3 nodes to 8 pods and >=4 nodes takes less than 15 minutes
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:ClusterSizeAutoscalingScaleUp] [Slow] Autoscaling Autoscaling a service from 1 pod and 3 nodes to 8 pods and >=4 nodes takes less than 15 minutes
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) CustomResourceDefinition Should scale with a CRD targetRef
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) CustomResourceDefinition Should scale with a CRD targetRef
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) ReplicationController light Should scale from 1 pod to 2 pods
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) ReplicationController light Should scale from 1 pod to 2 pods
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) ReplicationController light [Slow] Should scale from 2 pods to 1 pod
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) ReplicationController light [Slow] Should scale from 2 pods to 1 pod
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Pod Resource) Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment (Pod Resource) Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet with idle sidecar (ContainerResource use case) Should not scale up on a busy sidecar with an idle application
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet with idle sidecar (ContainerResource use case) Should not scale up on a busy sidecar with an idle application
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet with idle sidecar (ContainerResource use case) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods on a busy application with an idle sidecar container
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet with idle sidecar (ContainerResource use case) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods on a busy application with an idle sidecar container
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods and verify decision stability
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods and verify decision stability
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicationController Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod and verify decision stability
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicationController Should scale from 5 pods to 3 pods and then from 3 pods to 1 pod and verify decision stability
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Container Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Utilization for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] Horizontal pod autoscaling (scale resource: Memory) [Serial] [Slow] Deployment (Pod Resource) Should scale from 1 pod to 3 pods and then from 3 pods to 5 pods using Average Value for aggregation
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with autoscaling disabled shouldn't scale down
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with autoscaling disabled shouldn't scale down
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with autoscaling disabled shouldn't scale up
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with autoscaling disabled shouldn't scale up
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with both scale up and down controls configured should keep recommendation within the range over two stabilization windows
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with both scale up and down controls configured should keep recommendation within the range over two stabilization windows
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with both scale up and down controls configured should keep recommendation within the range with stabilization window and pod limit rate
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with both scale up and down controls configured should keep recommendation within the range with stabilization window and pod limit rate
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with long upscale stabilization window should scale up only after the stabilization period
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with long upscale stabilization window should scale up only after the stabilization period
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by number of Pods rate should scale down no more than given number of Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by number of Pods rate should scale down no more than given number of Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by number of Pods rate should scale up no more than given number of Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by number of Pods rate should scale up no more than given number of Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by percentage should scale down no more than given percentage of current Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by percentage should scale down no more than given percentage of current Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by percentage should scale up no more than given percentage of current Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with scale limited by percentage should scale up no more than given percentage of current Pods per minute
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with short downscale stabilization window should scale down soon after the stabilization period
Kubernetes e2e suite [It] [sig-autoscaling] [Feature:HPA] [Serial] [Slow] Horizontal pod autoscaling (non-default behavior) with short downscale stabilization window should scale down soon after the stabilization period
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Object from Stackdriver should scale down
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Object from Stackdriver should scale down
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Object from Stackdriver should scale down to 0
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Object from Stackdriver should scale down to 0
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Pod from Stackdriver should scale down
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Pod from Stackdriver should scale down
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Pod from Stackdriver should scale down with Prometheus
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Pod from Stackdriver should scale down with Prometheus
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Pod from Stackdriver should scale up with two metrics
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with Custom Metric of type Pod from Stackdriver should scale up with two metrics
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with External Metric from Stackdriver should scale down with target average value
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with External Metric from Stackdriver should scale down with target average value
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with External Metric from Stackdriver should scale down with target value
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with External Metric from Stackdriver should scale down with target value
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with External Metric from Stackdriver should scale up with two metrics
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with External Metric from Stackdriver should scale up with two metrics
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should not scale down when one metric is missing (Container Resource and External Metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should not scale down when one metric is missing (Container Resource and External Metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should not scale down when one metric is missing (Pod and Object Metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should not scale down when one metric is missing (Pod and Object Metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should scale up when one metric is missing (Pod and External metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should scale up when one metric is missing (Pod and External metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should scale up when one metric is missing (Resource and Object metrics)
Kubernetes e2e suite [It] [sig-autoscaling] [HPA] [Feature:CustomMetricsAutoscaling] Horizontal pod autoscaling (scale resource: Custom Metrics from Stackdriver) with multiple metrics of different types should scale up when one metric is missing (Resource and Object metrics)
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 should support forwarding over websockets
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 should support forwarding over websockets
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects NO client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects NO client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects a client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects a client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects a client request should support a client that connects, sends NO DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on 0.0.0.0 that expects a client request should support a client that connects, sends NO DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost should support forwarding over websockets
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost should support forwarding over websockets
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects NO client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects NO client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects a client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects a client request should support a client that connects, sends DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects a client request should support a client that connects, sends NO DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl Port forwarding With a server listening on localhost that expects a client request should support a client that connects, sends NO DATA, and disconnects
Kubernetes e2e suite [It] [sig-cli] Kubectl client Guestbook application should create and stop a working application [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Guestbook application should create and stop a working application [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl api-versions should check if v1 is in available api versions [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl api-versions should check if v1 is in available api versions [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl apply apply set/view last-applied
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl apply apply set/view last-applied
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl apply should apply a new configuration to an existing RC
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl apply should apply a new configuration to an existing RC
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl apply should reuse port when apply to an existing SVC
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl apply should reuse port when apply to an existing SVC
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl cluster-info dump should check if cluster-info dump succeeds
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl cluster-info dump should check if cluster-info dump succeeds
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl cluster-info should check if Kubernetes control plane services is included in cluster-info [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl cluster-info should check if Kubernetes control plane services is included in cluster-info [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl copy should copy a file from a running Pod
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl copy should copy a file from a running Pod
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl create quota should create a quota with scopes
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl create quota should create a quota with scopes
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl create quota should create a quota without scopes
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl create quota should create a quota without scopes
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl create quota should reject quota with invalid scopes
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl create quota should reject quota with invalid scopes
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl describe should check if kubectl describe prints relevant information for cronjob
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl describe should check if kubectl describe prints relevant information for cronjob
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl describe should check if kubectl describe prints relevant information for rc and pods [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl describe should check if kubectl describe prints relevant information for rc and pods [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl diff should check if kubectl diff finds a difference for Deployments [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl diff should check if kubectl diff finds a difference for Deployments [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl events should show event when pod is created
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl events should show event when pod is created
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl expose should create services for rc [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl expose should create services for rc [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl get componentstatuses should get componentstatuses
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl get componentstatuses should get componentstatuses
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl label should update the label on a resource [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl label should update the label on a resource [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl patch should add annotations for pods in rc [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl patch should add annotations for pods in rc [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl replace should update a single-container pod's image [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl replace should update a single-container pod's image [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl run pod should create a pod from an image when restart is Never [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl run pod should create a pod from an image when restart is Never [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl server-side dry-run should check if kubectl can dry-run update Pods [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl server-side dry-run should check if kubectl can dry-run update Pods [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl taint [Serial] should remove all the taints with the same key off a node
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl taint [Serial] should remove all the taints with the same key off a node
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl taint [Serial] should update the taint on a node
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl taint [Serial] should update the taint on a node
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should create/apply a CR with unknown fields for CRD with no validation schema
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should create/apply a CR with unknown fields for CRD with no validation schema
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should create/apply a valid CR for CRD with validation schema
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should create/apply a valid CR for CRD with validation schema
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should create/apply an invalid/valid CR with arbitrary-extra properties for CRD with partially-specified validation schema
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should create/apply an invalid/valid CR with arbitrary-extra properties for CRD with partially-specified validation schema
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should detect unknown metadata fields in both the root and embedded object of a CR
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should detect unknown metadata fields in both the root and embedded object of a CR
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should detect unknown metadata fields of a typed object
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl validation should detect unknown metadata fields of a typed object
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl version should check is all data is printed [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Kubectl version should check is all data is printed [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Proxy server should support --unix-socket=/path [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Proxy server should support --unix-socket=/path [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Proxy server should support proxy with --port 0 [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Proxy server should support proxy with --port 0 [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run [Slow] running a failing command with --leave-stdin-open
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run [Slow] running a failing command with --leave-stdin-open
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run [Slow] running a failing command without --restart=Never
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run [Slow] running a failing command without --restart=Never
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run [Slow] running a failing command without --restart=Never, but with --rm
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run [Slow] running a failing command without --restart=Never, but with --rm
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run running a failing command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run running a failing command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run running a successful command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod Kubectl run running a successful command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should contain last line of the log
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should contain last line of the log
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes execing into a container with a failing command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes execing into a container with a failing command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes execing into a container with a successful command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes execing into a container with a successful command
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes should handle in-cluster config
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes should handle in-cluster config
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes should support port-forward
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should return command exit codes should support port-forward
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec through an HTTP proxy
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec through an HTTP proxy
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec through kubectl proxy
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec through kubectl proxy
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec using resource/name
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support exec using resource/name
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support inline execution and attach
Kubernetes e2e suite [It] [sig-cli] Kubectl client Simple pod should support inline execution and attach
Kubernetes e2e suite [It] [sig-cli] Kubectl client Update Demo should create and stop a replication controller [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Update Demo should create and stop a replication controller [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Update Demo should scale a replication controller [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client Update Demo should scale a replication controller [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl client kubectl wait should ignore not found error with --for=delete
Kubernetes e2e suite [It] [sig-cli] Kubectl client kubectl wait should ignore not found error with --for=delete
Kubernetes e2e suite [It] [sig-cli] Kubectl logs default container logs the second container is the default-container by annotation should log default container if not specified
Kubernetes e2e suite [It] [sig-cli] Kubectl logs default container logs the second container is the default-container by annotation should log default container if not specified
Kubernetes e2e suite [It] [sig-cli] Kubectl logs logs should be able to retrieve and filter logs [Conformance]
Kubernetes e2e suite [It] [sig-cli] Kubectl logs logs should be able to retrieve and filter logs [Conformance]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Addon update should propagate add-on file changes [Slow]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Addon update should propagate add-on file changes [Slow]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Downgrade [Feature:Downgrade] cluster downgrade should maintain a functioning cluster [Feature:ClusterDowngrade]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Downgrade [Feature:Downgrade] cluster downgrade should maintain a functioning cluster [Feature:ClusterDowngrade]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] GKE node pools [Feature:GKENodePool] should create a cluster with multiple node pools [Feature:GKENodePool]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] GKE node pools [Feature:GKENodePool] should create a cluster with multiple node pools [Feature:GKENodePool]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] HA-master [Feature:HAMaster] survive addition/removal replicas different zones [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] HA-master [Feature:HAMaster] survive addition/removal replicas different zones [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] HA-master [Feature:HAMaster] survive addition/removal replicas multizone workers [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] HA-master [Feature:HAMaster] survive addition/removal replicas multizone workers [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] HA-master [Feature:HAMaster] survive addition/removal replicas same zone [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] HA-master [Feature:HAMaster] survive addition/removal replicas same zone [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Nodes [Disruptive] Resize [Slow] should be able to add nodes
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Nodes [Disruptive] Resize [Slow] should be able to add nodes
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Nodes [Disruptive] Resize [Slow] should be able to delete nodes
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Nodes [Disruptive] Resize [Slow] should be able to delete nodes
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not be able to proxy to cadvisor port 4194 using proxy subresource
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not be able to proxy to cadvisor port 4194 using proxy subresource
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not be able to proxy to the readonly kubelet port 10255 using proxy subresource
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not be able to proxy to the readonly kubelet port 10255 using proxy subresource
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not have port 10255 open on its all public IP addresses
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not have port 10255 open on its all public IP addresses
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not have port 4194 open on its all public IP addresses
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not have port 4194 open on its all public IP addresses
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Recreate [Feature:Recreate] recreate nodes and ensure they function upon restart
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Recreate [Feature:Recreate] recreate nodes and ensure they function upon restart
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Restart [Disruptive] should restart all nodes and ensure all nodes and pods recover
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Restart [Disruptive] should restart all nodes and ensure all nodes and pods recover
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Upgrade [Feature:Upgrade] cluster upgrade should maintain a functioning cluster [Feature:ClusterUpgrade]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Upgrade [Feature:Upgrade] cluster upgrade should maintain a functioning cluster [Feature:ClusterUpgrade]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Upgrade [Feature:Upgrade] master upgrade should maintain a functioning cluster [Feature:MasterUpgrade]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] Upgrade [Feature:Upgrade] master upgrade should maintain a functioning cluster [Feature:MasterUpgrade]
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] [Disruptive]NodeLease NodeLease deletion node lease should be deleted when corresponding node is deleted
Kubernetes e2e suite [It] [sig-cloud-provider-gcp] [Disruptive]NodeLease NodeLease deletion node lease should be deleted when corresponding node is deleted
Kubernetes e2e suite [It] [sig-cloud-provider] [Feature:CloudProvider][Disruptive] Nodes should be deleted on API server if it doesn't exist in the cloud provider
Kubernetes e2e suite [It] [sig-cloud-provider] [Feature:CloudProvider][Disruptive] Nodes should be deleted on API server if it doesn't exist in the cloud provider
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should delete the signed bootstrap tokens from clusterInfo ConfigMap when bootstrap token is deleted
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should delete the signed bootstrap tokens from clusterInfo ConfigMap when bootstrap token is deleted
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should delete the token secret when the secret expired
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should delete the token secret when the secret expired
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should not delete the token secret when the secret is not expired
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should not delete the token secret when the secret is not expired
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should resign the bootstrap tokens when the clusterInfo ConfigMap updated [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should resign the bootstrap tokens when the clusterInfo ConfigMap updated [Serial][Disruptive]
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should sign the new added bootstrap tokens
Kubernetes e2e suite [It] [sig-cluster-lifecycle] [Feature:BootstrapTokens] should sign the new added bootstrap tokens
Kubernetes e2e suite [It] [sig-instrumentation] Events API should delete a collection of events [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events API should delete a collection of events [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events API should ensure that an event can be fetched, patched, deleted, and listed [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events API should ensure that an event can be fetched, patched, deleted, and listed [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events should delete a collection of events [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events should delete a collection of events [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events should manage the lifecycle of an event [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Events should manage the lifecycle of an event [Conformance]
Kubernetes e2e suite [It] [sig-instrumentation] Logging soak [Performance] [Slow] [Disruptive] should survive logging 1KB every 1s seconds, for a duration of 2m0s
Kubernetes e2e suite [It] [sig-instrumentation] Logging soak [Performance] [Slow] [Disruptive] should survive logging 1KB every 1s seconds, for a duration of 2m0s
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from API server.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from API server.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from a ControllerManager.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from a ControllerManager.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from a Kubelet.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from a Kubelet.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from a Scheduler.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics from a Scheduler.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics slis from API server.
Kubernetes e2e suite [It] [sig-instrumentation] MetricsGrabber should grab all metrics slis from API server.
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should have accelerator metrics [Feature:StackdriverAcceleratorMonitoring]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should have accelerator metrics [Feature:StackdriverAcceleratorMonitoring]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should have cluster metrics [Feature:StackdriverMonitoring]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should have cluster metrics [Feature:StackdriverMonitoring]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Custom Metrics - Stackdriver Adapter for external metrics [Feature:StackdriverExternalMetrics]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Custom Metrics - Stackdriver Adapter for external metrics [Feature:StackdriverExternalMetrics]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Custom Metrics - Stackdriver Adapter for new resource model [Feature:StackdriverCustomMetrics]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Custom Metrics - Stackdriver Adapter for new resource model [Feature:StackdriverCustomMetrics]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Custom Metrics - Stackdriver Adapter for old resource model [Feature:StackdriverCustomMetrics]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Custom Metrics - Stackdriver Adapter for old resource model [Feature:StackdriverCustomMetrics]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Stackdriver Metadata Agent [Feature:StackdriverMetadataAgent]
Kubernetes e2e suite [It] [sig-instrumentation] Stackdriver Monitoring should run Stackdriver Metadata Agent [Feature:StackdriverMetadataAgent]
Kubernetes e2e suite [It] [sig-network] CVE-2021-29923 IPv4 Service Type ClusterIP with leading zeros should work interpreted as decimal
Kubernetes e2e suite [It] [sig-network] CVE-2021-29923 IPv4 Service Type ClusterIP with leading zeros should work interpreted as decimal
Kubernetes e2e suite [It] [sig-network] ClusterDns [Feature:Example] should create pod that uses dns
Kubernetes e2e suite [It] [sig-network] ClusterDns [Feature:Example] should create pod that uses dns
Kubernetes e2e suite [It] [sig-network] Conntrack should be able to preserve UDP traffic when initial unready endpoints get ready
Kubernetes e2e suite [It] [sig-network] Conntrack should be able to preserve UDP traffic when initial unready endpoints get ready
Kubernetes e2e suite [It] [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service
Kubernetes e2e suite [It] [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service
Kubernetes e2e suite [It] [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a NodePort service
Kubernetes e2e suite [It] [sig-network] Conntrack should be able to preserve UDP traffic when server pod cycles for a NodePort service
Kubernetes e2e suite [It] [sig-network] Conntrack should drop INVALID conntrack entries [Privileged]
Kubernetes e2e suite [It] [sig-network] Conntrack should drop INVALID conntrack entries [Privileged]
Kubernetes e2e suite [It] [sig-network] DNS HostNetwork should resolve DNS of partial qualified names for services on hostNetwork pods with dnsPolicy: ClusterFirstWithHostNet [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] DNS HostNetwork should resolve DNS of partial qualified names for services on hostNetwork pods with dnsPolicy: ClusterFirstWithHostNet [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] DNS configMap nameserver Change stubDomain should be able to change stubDomain configuration [Slow][Serial]
Kubernetes e2e suite [It] [sig-network] DNS configMap nameserver Change stubDomain should be able to change stubDomain configuration [Slow][Serial]
Kubernetes e2e suite [It] [sig-network] DNS configMap nameserver Forward PTR lookup should forward PTR records lookup to upstream nameserver [Slow][Serial]
Kubernetes e2e suite [It] [sig-network] DNS configMap nameserver Forward PTR lookup should forward PTR records lookup to upstream nameserver [Slow][Serial]
Kubernetes e2e suite [It] [sig-network] DNS configMap nameserver Forward external name lookup should forward externalname lookup to upstream nameserver [Slow][Serial]
Kubernetes e2e suite [It] [sig-network] DNS configMap nameserver Forward external name lookup should forward externalname lookup to upstream nameserver [Slow][Serial]
Kubernetes e2e suite [It] [sig-network] DNS should provide /etc/hosts entries for the cluster [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide /etc/hosts entries for the cluster [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for ExternalName services [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for ExternalName services [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for pods for Hostname [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for pods for Hostname [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for pods for Subdomain [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for pods for Subdomain [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for services [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for services [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for the cluster [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for the cluster [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for the cluster [Provider:GCE]
Kubernetes e2e suite [It] [sig-network] DNS should provide DNS for the cluster [Provider:GCE]
Kubernetes e2e suite [It] [sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should resolve DNS of partial qualified names for the cluster [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] DNS should resolve DNS of partial qualified names for the cluster [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] DNS should support configurable pod DNS nameservers [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should support configurable pod DNS nameservers [Conformance]
Kubernetes e2e suite [It] [sig-network] DNS should support configurable pod resolv.conf
Kubernetes e2e suite [It] [sig-network] DNS should support configurable pod resolv.conf
Kubernetes e2e suite [It] [sig-network] DNS should work with the pod containing more than 6 DNS search paths and longer than 256 search list characters
Kubernetes e2e suite [It] [sig-network] DNS should work with the pod containing more than 6 DNS search paths and longer than 256 search list characters
Kubernetes e2e suite [It] [sig-network] EndpointSlice should create Endpoints and EndpointSlices for Pods matching a Service [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should create Endpoints and EndpointSlices for Pods matching a Service [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should create and delete Endpoints and EndpointSlices for a Service with a selector specified [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should create and delete Endpoints and EndpointSlices for a Service with a selector specified [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should have Endpoints and EndpointSlices pointing to API Server [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should have Endpoints and EndpointSlices pointing to API Server [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should support creating EndpointSlice API operations [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSlice should support creating EndpointSlice API operations [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSliceMirroring should mirror a custom Endpoint with multiple subsets and same IP address
Kubernetes e2e suite [It] [sig-network] EndpointSliceMirroring should mirror a custom Endpoint with multiple subsets and same IP address
Kubernetes e2e suite [It] [sig-network] EndpointSliceMirroring should mirror a custom Endpoints resource through create update and delete [Conformance]
Kubernetes e2e suite [It] [sig-network] EndpointSliceMirroring should mirror a custom Endpoints resource through create update and delete [Conformance]
Kubernetes e2e suite [It] [sig-network] Firewall rule [Slow] [Serial] should create valid firewall rules for LoadBalancer type service
Kubernetes e2e suite [It] [sig-network] Firewall rule [Slow] [Serial] should create valid firewall rules for LoadBalancer type service
Kubernetes e2e suite [It] [sig-network] Firewall rule control plane should not expose well-known ports
Kubernetes e2e suite [It] [sig-network] Firewall rule control plane should not expose well-known ports
Kubernetes e2e suite [It] [sig-network] Firewall rule should have correct firewall rules for e2e cluster
Kubernetes e2e suite [It] [sig-network] Firewall rule should have correct firewall rules for e2e cluster
Kubernetes e2e suite [It] [sig-network] HostPort validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] HostPort validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Ingress API should support creating Ingress API operations [Conformance]
Kubernetes e2e suite [It] [sig-network] Ingress API should support creating Ingress API operations [Conformance]
Kubernetes e2e suite [It] [sig-network] IngressClass API should support creating IngressClass API operations [Conformance]
Kubernetes e2e suite [It] [sig-network] IngressClass API should support creating IngressClass API operations [Conformance]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should allow IngressClass to have Namespace-scoped parameters [Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should allow IngressClass to have Namespace-scoped parameters [Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should choose the one with the later CreationTimestamp, if equal the one with the lower name when two ingressClasses are marked as default[Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should choose the one with the later CreationTimestamp, if equal the one with the lower name when two ingressClasses are marked as default[Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should not set default value if no default IngressClass [Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should not set default value if no default IngressClass [Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should set default value on new IngressClass [Serial]
Kubernetes e2e suite [It] [sig-network] IngressClass [Feature:Ingress] should set default value on new IngressClass [Serial]
Kubernetes e2e suite [It] [sig-network] KubeProxy should set TCP CLOSE_WAIT timeout [Privileged]
Kubernetes e2e suite [It] [sig-network] KubeProxy should set TCP CLOSE_WAIT timeout [Privileged]
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should handle updates to ExternalTrafficPolicy field
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should handle updates to ExternalTrafficPolicy field
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should only target nodes with endpoints
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should only target nodes with endpoints
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should work for type=LoadBalancer
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should work for type=LoadBalancer
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should work for type=NodePort
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should work for type=NodePort
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should work from pods
Kubernetes e2e suite [It] [sig-network] LoadBalancers ESIPP [Slow] should work from pods
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to change the type and ports of a TCP service [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to change the type and ports of a TCP service [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to change the type and ports of a UDP service [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to change the type and ports of a UDP service [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to create LoadBalancer Service without NodePort and change it [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to create LoadBalancer Service without NodePort and change it [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to create an internal type load balancer [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to create an internal type load balancer [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on different nodes
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on different nodes
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on the same nodes
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on the same nodes
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to switch session affinity for LoadBalancer service with ESIPP off [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to switch session affinity for LoadBalancer service with ESIPP off [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to switch session affinity for LoadBalancer service with ESIPP on [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should be able to switch session affinity for LoadBalancer service with ESIPP on [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should handle load balancer cleanup finalizer for service [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should handle load balancer cleanup finalizer for service [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should have session affinity work for LoadBalancer service with ESIPP off [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should have session affinity work for LoadBalancer service with ESIPP off [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should have session affinity work for LoadBalancer service with ESIPP on [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should have session affinity work for LoadBalancer service with ESIPP on [Slow] [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should not have connectivity disruption during rolling update with externalTrafficPolicy=Cluster [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should not have connectivity disruption during rolling update with externalTrafficPolicy=Cluster [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should not have connectivity disruption during rolling update with externalTrafficPolicy=Local [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should not have connectivity disruption during rolling update with externalTrafficPolicy=Local [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should only allow access from service loadbalancer source ranges [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should only allow access from service loadbalancer source ranges [Slow]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should reconcile LB health check interval [Slow][Serial][Disruptive]
Kubernetes e2e suite [It] [sig-network] LoadBalancers should reconcile LB health check interval [Slow][Serial][Disruptive]
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] should conform to Ingress spec
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] should conform to Ingress spec
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] rolling update backend pods should not cause service disruption
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] rolling update backend pods should not cause service disruption
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should be able to create a ClusterIP service
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should be able to create a ClusterIP service
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should be able to switch between IG and NEG modes
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should be able to switch between IG and NEG modes
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should conform to Ingress spec
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should conform to Ingress spec
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should create NEGs for all ports with the Ingress annotation, and NEGs for the standalone annotation otherwise
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should create NEGs for all ports with the Ingress annotation, and NEGs for the standalone annotation otherwise
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should sync endpoints for both Ingress-referenced NEG and standalone NEG
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should sync endpoints for both Ingress-referenced NEG and standalone NEG
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should sync endpoints to NEG
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should sync endpoints to NEG
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 Scalability GCE [Slow] [Serial] [Feature:IngressScale] Creating and updating ingresses should happen promptly with small/medium/large amount of ingresses
Kubernetes e2e suite [It] [sig-network] Loadbalancing: L7 Scalability GCE [Slow] [Serial] [Feature:IngressScale] Creating and updating ingresses should happen promptly with small/medium/large amount of ingresses
Kubernetes e2e suite [It] [sig-network] Netpol API should support creating NetworkPolicy API operations
Kubernetes e2e suite [It] [sig-network] Netpol API should support creating NetworkPolicy API operations
Kubernetes e2e suite [It] [sig-network] Netpol API should support creating NetworkPolicy API with endport field
Kubernetes e2e suite [It] [sig-network] Netpol API should support creating NetworkPolicy API with endport field
Kubernetes e2e suite [It] [sig-network] Netpol API should support creating NetworkPolicy with Status subresource [Feature:NetworkPolicyStatus]
Kubernetes e2e suite [It] [sig-network] Netpol API should support creating NetworkPolicy with Status subresource [Feature:NetworkPolicyStatus]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow egress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow egress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access from namespace on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access from namespace on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access from updated namespace [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access from updated namespace [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access from updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access from updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should allow ingress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny egress from all pods in a namespace [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny egress from all pods in a namespace [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny egress from pods based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny egress from pods based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny ingress access to updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny ingress access to updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny ingress from pods on other namespaces [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should deny ingress from pods on other namespaces [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce egress policy allowing traffic to a server in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce egress policy allowing traffic to a server in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce except clause while egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce except clause while egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce ingress policy allowing any port traffic to a server on a specific protocol [Feature:NetworkPolicy] [Feature:UDP]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce ingress policy allowing any port traffic to a server on a specific protocol [Feature:NetworkPolicy] [Feature:UDP]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce multiple egress policies with egress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce multiple egress policies with egress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce multiple ingress policies with ingress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce multiple ingress policies with ingress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce multiple, stacked policies with overlapping podSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce multiple, stacked policies with overlapping podSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policies to check ingress and egress policies can be controlled independently based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policies to check ingress and egress policies can be controlled independently based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on Multiple PodSelectors and NamespaceSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on Multiple PodSelectors and NamespaceSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on NamespaceSelector with MatchExpressions using default ns label [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on NamespaceSelector with MatchExpressions using default ns label [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on NamespaceSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on NamespaceSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on PodSelector or NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on PodSelector or NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on PodSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on PodSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on any PodSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy based on any PodSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow ingress traffic for a target [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow ingress traffic for a target [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow ingress traffic from pods in all namespaces [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow ingress traffic from pods in all namespaces [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic based on NamespaceSelector with MatchLabels using default ns label [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic based on NamespaceSelector with MatchLabels using default ns label [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic from pods within server namespace based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic from pods within server namespace based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic only from a different namespace, based on NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic only from a different namespace, based on NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce updated policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should enforce updated policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should ensure an IP overlapping both IPBlock.CIDR and IPBlock.Except is allowed [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should ensure an IP overlapping both IPBlock.CIDR and IPBlock.Except is allowed [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should not allow access by TCP when a policy specifies only UDP [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should not allow access by TCP when a policy specifies only UDP [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should not mistakenly treat 'protocol: SCTP' as 'protocol: TCP', even if the plugin doesn't support SCTP [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should not mistakenly treat 'protocol: SCTP' as 'protocol: TCP', even if the plugin doesn't support SCTP [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should properly isolate pods that are selected by a policy allowing SCTP, even if the plugin doesn't support SCTP [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should properly isolate pods that are selected by a policy allowing SCTP, even if the plugin doesn't support SCTP [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should stop enforcing policies after they are deleted [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should stop enforcing policies after they are deleted [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support a 'default-deny-all' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support a 'default-deny-all' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support allow-all policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support allow-all policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support denying of egress traffic on the client side (even if the server explicitly allows this traffic) [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should support denying of egress traffic on the client side (even if the server explicitly allows this traffic) [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should work with Ingress, Egress specified together [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol NetworkPolicy between server and client should work with Ingress, Egress specified together [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [LinuxOnly] NetworkPolicy between server and client using UDP should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [LinuxOnly] NetworkPolicy between server and client using UDP should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [LinuxOnly] NetworkPolicy between server and client using UDP should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [LinuxOnly] NetworkPolicy between server and client using UDP should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [LinuxOnly] NetworkPolicy between server and client using UDP should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Netpol [LinuxOnly] NetworkPolicy between server and client using UDP should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicy API should support creating NetworkPolicy API operations
Kubernetes e2e suite [It] [sig-network] NetworkPolicy API should support creating NetworkPolicy API operations
Kubernetes e2e suite [It] [sig-network] NetworkPolicy [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicy [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicy [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicy [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicy [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should support a 'default-deny' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicy [Feature:SCTPConnectivity][LinuxOnly] NetworkPolicy between server and client using SCTP should support a 'default-deny' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow egress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow egress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access from namespace on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access from namespace on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access from updated namespace [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access from updated namespace [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access from updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access from updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should allow ingress access on one named port [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should deny ingress access to updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should deny ingress access to updated pod [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce egress policy allowing traffic to a server in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce egress policy allowing traffic to a server in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce except clause while egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce except clause while egress access to server in CIDR block [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce multiple egress policies with egress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce multiple egress policies with egress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce multiple ingress policies with ingress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce multiple ingress policies with ingress allow-all policy taking precedence [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce multiple, stacked policies with overlapping podSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce multiple, stacked policies with overlapping podSelectors [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policies to check ingress and egress policies can be controlled independently based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policies to check ingress and egress policies can be controlled independently based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on NamespaceSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on NamespaceSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on PodSelector or NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on PodSelector or NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on PodSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on PodSelector with MatchExpressions[Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy based on Ports [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy to allow traffic from pods within server namespace based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy to allow traffic from pods within server namespace based on PodSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy to allow traffic only from a different namespace, based on NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy to allow traffic only from a different namespace, based on NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce updated policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should enforce updated policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should ensure an IP overlapping both IPBlock.CIDR and IPBlock.Except is allowed [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should ensure an IP overlapping both IPBlock.CIDR and IPBlock.Except is allowed [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should not allow access by TCP when a policy specifies only SCTP [Feature:NetworkPolicy] [Serial]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should not allow access by TCP when a policy specifies only SCTP [Feature:NetworkPolicy] [Serial]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should stop enforcing policies after they are deleted [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should stop enforcing policies after they are deleted [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should support a 'default-deny-all' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should support a 'default-deny-all' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should support a 'default-deny-ingress' policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should support allow-all policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should support allow-all policy [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should work with Ingress,Egress specified together [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] NetworkPolicyLegacy [LinuxOnly] NetworkPolicy between server and client should work with Ingress,Egress specified together [Feature:NetworkPolicy]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: sctp [LinuxOnly][Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: sctp [LinuxOnly][Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: udp [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: udp [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for node-pod communication: http [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for node-pod communication: http [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for node-pod communication: sctp [LinuxOnly][Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for node-pod communication: sctp [LinuxOnly][Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for node-pod communication: udp [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Pods should function for node-pod communication: udp [LinuxOnly] [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should be able to handle large requests: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should be able to handle large requests: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should be able to handle large requests: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should be able to handle large requests: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for client IP based session affinity: http [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for client IP based session affinity: http [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for client IP based session affinity: udp [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for client IP based session affinity: udp [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for endpoint-Service: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for endpoint-Service: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for endpoint-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for endpoint-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for endpoint-Service: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for endpoint-Service: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for multiple endpoint-Services with same selector
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for multiple endpoint-Services with same selector
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for node-Service: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for node-Service: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for node-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for node-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for node-Service: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for node-Service: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for pod-Service: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for pod-Service: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for pod-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for pod-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for pod-Service: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for pod-Service: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for service endpoints using hostNetwork
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should function for service endpoints using hostNetwork
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should support basic nodePort: udp functionality
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should support basic nodePort: udp functionality
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update endpoints: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update endpoints: http
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update endpoints: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update endpoints: udp
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update nodePort: http [Slow]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update nodePort: http [Slow]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update nodePort: udp [Slow]
Kubernetes e2e suite [It] [sig-network] Networking Granular Checks: Services should update nodePort: udp [Slow]
Kubernetes e2e suite [It] [sig-network] Networking IPerf2 [Feature:Networking-Performance] should run iperf2
Kubernetes e2e suite [It] [sig-network] Networking IPerf2 [Feature:Networking-Performance] should run iperf2
Kubernetes e2e suite [It] [sig-network] Networking should allow creating a Pod with an SCTP HostPort [LinuxOnly] [Serial]
Kubernetes e2e suite [It] [sig-network] Networking should allow creating a Pod with an SCTP HostPort [LinuxOnly] [Serial]
Kubernetes e2e suite [It] [sig-network] Networking should check kube-proxy urls
Kubernetes e2e suite [It] [sig-network] Networking should check kube-proxy urls
Kubernetes e2e suite [It] [sig-network] Networking should provide Internet connection for containers [Feature:Networking-IPv4]
Kubernetes e2e suite [It] [sig-network] Networking should provide Internet connection for containers [Feature:Networking-IPv4]
Kubernetes e2e suite [It] [sig-network] Networking should provide Internet connection for containers [Feature:Networking-IPv6][Experimental][LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Networking should provide Internet connection for containers [Feature:Networking-IPv6][Experimental][LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Networking should provide unchanging, static URL paths for kubernetes api services
Kubernetes e2e suite [It] [sig-network] Networking should provide unchanging, static URL paths for kubernetes api services
Kubernetes e2e suite [It] [sig-network] Networking should provider Internet connection for containers using DNS [Feature:Networking-DNS]
Kubernetes e2e suite [It] [sig-network] Networking should provider Internet connection for containers using DNS [Feature:Networking-DNS]
Kubernetes e2e suite [It] [sig-network] Networking should recreate its iptables rules if they are deleted [Disruptive]
Kubernetes e2e suite [It] [sig-network] Networking should recreate its iptables rules if they are deleted [Disruptive]
Kubernetes e2e suite [It] [sig-network] NoSNAT [Feature:NoSNAT] [Slow] Should be able to send traffic between Pods without SNAT
Kubernetes e2e suite [It] [sig-network] NoSNAT [Feature:NoSNAT] [Slow] Should be able to send traffic between Pods without SNAT
Kubernetes e2e suite [It] [sig-network] Proxy version v1 A set of valid responses are returned for both pod and service Proxy [Conformance]
Kubernetes e2e suite [It] [sig-network] Proxy version v1 A set of valid responses are returned for both pod and service Proxy [Conformance]
Kubernetes e2e suite [It] [sig-network] Proxy version v1 A set of valid responses are returned for both pod and service ProxyWithPath [Conformance]
Kubernetes e2e suite [It] [sig-network] Proxy version v1 A set of valid responses are returned for both pod and service ProxyWithPath [Conformance]
Kubernetes e2e suite [It] [sig-network] Proxy version v1 should proxy logs on node using proxy subresource
Kubernetes e2e suite [It] [sig-network] Proxy version v1 should proxy logs on node using proxy subresource
Kubernetes e2e suite [It] [sig-network] Proxy version v1 should proxy logs on node with explicit kubelet port using proxy subresource
Kubernetes e2e suite [It] [sig-network] Proxy version v1 should proxy logs on node with explicit kubelet port using proxy subresource
Kubernetes e2e suite [It] [sig-network] Proxy version v1 should proxy through a service and a pod [Conformance]
Kubernetes e2e suite [It] [sig-network] Proxy version v1 should proxy through a service and a pod [Conformance]
Kubernetes e2e suite [It] [sig-network] Service endpoints latency should not be very high [Conformance]
Kubernetes e2e suite [It] [sig-network] Service endpoints latency should not be very high [Conformance]
Kubernetes e2e suite [It] [sig-network] Services GCE [Slow] should be able to create and tear down a standard-tier load balancer [Slow]
Kubernetes e2e suite [It] [sig-network] Services GCE [Slow] should be able to create and tear down a standard-tier load balancer [Slow]
Kubernetes e2e suite [It] [sig-network] Services should allow creating a basic SCTP service with pod and endpoints [LinuxOnly] [Serial]
Kubernetes e2e suite [It] [sig-network] Services should allow creating a basic SCTP service with pod and endpoints [LinuxOnly] [Serial]
Kubernetes e2e suite [It] [sig-network] Services should allow pods to hairpin back to themselves through services
Kubernetes e2e suite [It] [sig-network] Services should allow pods to hairpin back to themselves through services
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from ClusterIP to ExternalName [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from ClusterIP to ExternalName [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from ExternalName to ClusterIP [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from ExternalName to ClusterIP [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from NodePort to ExternalName [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to change the type from NodePort to ExternalName [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to connect to terminating and unready endpoints if PublishNotReadyAddresses is true
Kubernetes e2e suite [It] [sig-network] Services should be able to connect to terminating and unready endpoints if PublishNotReadyAddresses is true
Kubernetes e2e suite [It] [sig-network] Services should be able to create a functioning NodePort service [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to create a functioning NodePort service [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to switch session affinity for service with type clusterIP [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to switch session affinity for service with type clusterIP [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should be able to up and down services
Kubernetes e2e suite [It] [sig-network] Services should be able to up and down services
Kubernetes e2e suite [It] [sig-network] Services should be able to update service type to NodePort listening on same port number but different protocols
Kubernetes e2e suite [It] [sig-network] Services should be able to update service type to NodePort listening on same port number but different protocols
Kubernetes e2e suite [It] [sig-network] Services should be possible to connect to a service via ExternalIP when the external IP is not assigned to a node
Kubernetes e2e suite [It] [sig-network] Services should be possible to connect to a service via ExternalIP when the external IP is not assigned to a node
Kubernetes e2e suite [It] [sig-network] Services should be rejected for evicted pods (no endpoints exist)
Kubernetes e2e suite [It] [sig-network] Services should be rejected for evicted pods (no endpoints exist)
Kubernetes e2e suite [It] [sig-network] Services should be rejected when no endpoints exist
Kubernetes e2e suite [It] [sig-network] Services should be rejected when no endpoints exist
Kubernetes e2e suite [It] [sig-network] Services should be updated after adding or deleting ports
Kubernetes e2e suite [It] [sig-network] Services should be updated after adding or deleting ports
Kubernetes e2e suite [It] [sig-network] Services should check NodePort out-of-range
Kubernetes e2e suite [It] [sig-network] Services should check NodePort out-of-range
Kubernetes e2e suite [It] [sig-network] Services should complete a service status lifecycle [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should complete a service status lifecycle [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should create endpoints for unready pods
Kubernetes e2e suite [It] [sig-network] Services should create endpoints for unready pods
Kubernetes e2e suite [It] [sig-network] Services should delete a collection of services [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should delete a collection of services [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should fail health check node port if there are only terminating endpoints [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fail health check node port if there are only terminating endpoints [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to local terminating endpoints when there are no ready endpoints with externalTrafficPolicy=Local [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to local terminating endpoints when there are no ready endpoints with externalTrafficPolicy=Local [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to local terminating endpoints when there are no ready endpoints with internalTrafficPolicy=Local [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to local terminating endpoints when there are no ready endpoints with internalTrafficPolicy=Local [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to terminating endpoints when there are no ready endpoints with externallTrafficPolicy=Cluster [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to terminating endpoints when there are no ready endpoints with externallTrafficPolicy=Cluster [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to terminating endpoints when there are no ready endpoints with internalTrafficPolicy=Cluster [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should fallback to terminating endpoints when there are no ready endpoints with internalTrafficPolicy=Cluster [Feature:ProxyTerminatingEndpoints]
Kubernetes e2e suite [It] [sig-network] Services should find a service from listing all namespaces [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should find a service from listing all namespaces [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity timeout work for NodePort service [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity timeout work for NodePort service [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity timeout work for service with type clusterIP [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity timeout work for service with type clusterIP [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity work for NodePort service [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity work for NodePort service [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should implement service.kubernetes.io/headless
Kubernetes e2e suite [It] [sig-network] Services should implement service.kubernetes.io/headless
Kubernetes e2e suite [It] [sig-network] Services should implement service.kubernetes.io/service-proxy-name
Kubernetes e2e suite [It] [sig-network] Services should implement service.kubernetes.io/service-proxy-name
Kubernetes e2e suite [It] [sig-network] Services should not be able to connect to terminating and unready endpoints if PublishNotReadyAddresses is false
Kubernetes e2e suite [It] [sig-network] Services should not be able to connect to terminating and unready endpoints if PublishNotReadyAddresses is false
Kubernetes e2e suite [It] [sig-network] Services should preserve source pod IP for traffic thru service cluster IP [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Services should preserve source pod IP for traffic thru service cluster IP [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] Services should prevent NodePort collisions
Kubernetes e2e suite [It] [sig-network] Services should prevent NodePort collisions
Kubernetes e2e suite [It] [sig-network] Services should provide secure master service [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should provide secure master service [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should release NodePorts on delete
Kubernetes e2e suite [It] [sig-network] Services should release NodePorts on delete
Kubernetes e2e suite [It] [sig-network] Services should respect internalTrafficPolicy=Local Pod (hostNetwork: true) to Pod [Feature:ServiceInternalTrafficPolicy]
Kubernetes e2e suite [It] [sig-network] Services should respect internalTrafficPolicy=Local Pod (hostNetwork: true) to Pod [Feature:ServiceInternalTrafficPolicy]
Kubernetes e2e suite [It] [sig-network] Services should respect internalTrafficPolicy=Local Pod and Node, to Pod (hostNetwork: true) [Feature:ServiceInternalTrafficPolicy]
Kubernetes e2e suite [It] [sig-network] Services should respect internalTrafficPolicy=Local Pod and Node, to Pod (hostNetwork: true) [Feature:ServiceInternalTrafficPolicy]
Kubernetes e2e suite [It] [sig-network] Services should respect internalTrafficPolicy=Local Pod to Pod [Feature:ServiceInternalTrafficPolicy]
Kubernetes e2e suite [It] [sig-network] Services should respect internalTrafficPolicy=Local Pod to Pod [Feature:ServiceInternalTrafficPolicy]
Kubernetes e2e suite [It] [sig-network] Services should serve a basic endpoint from pods [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should serve a basic endpoint from pods [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should serve endpoints on same port and different protocol for internal traffic on Type LoadBalancer
Kubernetes e2e suite [It] [sig-network] Services should serve endpoints on same port and different protocol for internal traffic on Type LoadBalancer
Kubernetes e2e suite [It] [sig-network] Services should serve multiport endpoints from pods [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should serve multiport endpoints from pods [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should test the lifecycle of an Endpoint [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should test the lifecycle of an Endpoint [Conformance]
Kubernetes e2e suite [It] [sig-network] Services should work after restarting apiserver [Disruptive]
Kubernetes e2e suite [It] [sig-network] Services should work after restarting apiserver [Disruptive]
Kubernetes e2e suite [It] [sig-network] Services should work after restarting kube-proxy [Disruptive]
Kubernetes e2e suite [It] [sig-network] Services should work after restarting kube-proxy [Disruptive]
Kubernetes e2e suite [It] [sig-network] Services should work after the service has been recreated
Kubernetes e2e suite [It] [sig-network] Services should work after the service has been recreated
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should be able to handle large requests: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should be able to handle large requests: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should be able to handle large requests: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should be able to handle large requests: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for client IP based session affinity: http [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for client IP based session affinity: http [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for client IP based session affinity: udp [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for client IP based session affinity: udp [LinuxOnly]
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for endpoint-Service: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for endpoint-Service: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for endpoint-Service: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for endpoint-Service: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for node-Service: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for node-Service: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for node-Service: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for node-Service: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for pod-Service: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for pod-Service: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for pod-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for pod-Service: sctp [Feature:SCTPConnectivity]
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for pod-Service: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for pod-Service: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for service endpoints using hostNetwork
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for service endpoints using hostNetwork
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should update endpoints: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should update endpoints: http
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should update endpoints: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should update endpoints: udp
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should be able to reach pod on ipv4 and ipv6 ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should be able to reach pod on ipv4 and ipv6 ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create a single stack service with cluster ip from primary service range
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create a single stack service with cluster ip from primary service range
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create pod, add ipv6 and ipv4 ip to pod ips
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create pod, add ipv6 and ipv4 ip to pod ips
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv4 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv4 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv4,v6 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv4,v6 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv6 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv6 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv6,v4 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should create service with ipv6,v4 cluster ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should have ipv4 and ipv6 internal node ip
Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] should have ipv4 and ipv6 internal node ip
Kubernetes e2e suite [It] [sig-network] [Feature:PerformanceDNS][Serial] Should answer DNS query for maximum number of services per cluster
Kubernetes e2e suite [It] [sig-network] [Feature:PerformanceDNS][Serial] Should answer DNS query for maximum number of services per cluster
Kubernetes e2e suite [It] [sig-network] [Feature:Topology Hints] should distribute endpoints evenly
Kubernetes e2e suite [It] [sig-network] [Feature:Topology Hints] should distribute endpoints evenly
Kubernetes e2e suite [It] [sig-network] kube-proxy migration [Feature:KubeProxyDaemonSetMigration] Downgrade kube-proxy from a DaemonSet to static pods should maintain a functioning cluster [Feature:KubeProxyDaemonSetDowngrade]
Kubernetes e2e suite [It] [sig-network] kube-proxy migration [Feature:KubeProxyDaemonSetMigration] Downgrade kube-proxy from a DaemonSet to static pods should maintain a functioning cluster [Feature:KubeProxyDaemonSetDowngrade]
Kubernetes e2e suite [It] [sig-network] kube-proxy migration [Feature:KubeProxyDaemonSetMigration] Upgrade kube-proxy from static pods to a DaemonSet should maintain a functioning cluster [Feature:KubeProxyDaemonSetUpgrade]
Kubernetes e2e suite [It] [sig-network] kube-proxy migration [Feature:KubeProxyDaemonSetMigration] Upgrade kube-proxy from static pods to a DaemonSet should maintain a functioning cluster [Feature:KubeProxyDaemonSetUpgrade]
Kubernetes e2e suite [It] [sig-node] AppArmor load AppArmor profiles can disable an AppArmor profile, using unconfined
Kubernetes e2e suite [It] [sig-node] AppArmor load AppArmor profiles can disable an AppArmor profile, using unconfined
Kubernetes e2e suite [It] [sig-node] AppArmor load AppArmor profiles should enforce an AppArmor profile
Kubernetes e2e suite [It] [sig-node] AppArmor load AppArmor profiles should enforce an AppArmor profile
Kubernetes e2e suite [It] [sig-node] ConfigMap should be consumable via environment variable [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should be consumable via environment variable [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should be consumable via the environment [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should be consumable via the environment [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should fail to create ConfigMap with empty key [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should fail to create ConfigMap with empty key [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should run through a ConfigMap lifecycle [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should run through a ConfigMap lifecycle [Conformance]
Kubernetes e2e suite [It] [sig-node] ConfigMap should update ConfigMap successfully
Kubernetes e2e suite [It] [sig-node] ConfigMap should update ConfigMap successfully
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart exec hook properly [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart exec hook properly [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart http hook properly [NodeConformance] [Conformance]
Kubernetes e2e suite [It] [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart http hook properly [NodeConformance] [Conformance]
Kubernetes e2e suite