ci-cri-containerd-e2e-cos-gce-reboot #1619968248437018624
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 08:30:51.214from ginkgo_report.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 08:25:48.904 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 08:25:48.904 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 08:25:48.904 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 08:25:48.904 Jan 30 08:25:48.904: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 08:25:48.906 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/30/23 08:25:49.036 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/30/23 08:25:49.117 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 08:25:49.199 (295ms) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 08:25:49.199 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 08:25:49.199 (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 08:25:49.199 Jan 30 08:25:49.293: INFO: Getting bootstrap-e2e-minion-group-70zb Jan 30 08:25:49.293: INFO: Getting bootstrap-e2e-minion-group-4sww Jan 30 08:25:49.293: INFO: Getting bootstrap-e2e-minion-group-lzpl Jan 30 08:25:49.353: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-lzpl condition Ready to be true Jan 30 08:25:49.355: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-4sww condition Ready to be true Jan 30 08:25:49.355: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-70zb condition Ready to be true Jan 30 08:25:49.397: INFO: Node bootstrap-e2e-minion-group-lzpl has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:25:49.397: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:25:49.397: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-hs8dc" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.397: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-lzpl" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.399: INFO: Node bootstrap-e2e-minion-group-70zb has 2 assigned pods with no liveness probes: [metadata-proxy-v0.1-ntpwl kube-proxy-bootstrap-e2e-minion-group-70zb] Jan 30 08:25:49.399: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [metadata-proxy-v0.1-ntpwl kube-proxy-bootstrap-e2e-minion-group-70zb] Jan 30 08:25:49.399: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-70zb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.400: INFO: Node bootstrap-e2e-minion-group-4sww has 4 assigned pods with no liveness probes: [kube-dns-autoscaler-5f6455f985-9xvq8 kube-proxy-bootstrap-e2e-minion-group-4sww metadata-proxy-v0.1-2x5bf volume-snapshot-controller-0] Jan 30 08:25:49.400: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-9xvq8 kube-proxy-bootstrap-e2e-minion-group-4sww metadata-proxy-v0.1-2x5bf volume-snapshot-controller-0] Jan 30 08:25:49.400: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.400: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-ntpwl" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.400: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-9xvq8" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.400: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-4sww" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.400: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-2x5bf" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.444: INFO: Pod "metadata-proxy-v0.1-hs8dc": Phase="Running", Reason="", readiness=true. Elapsed: 47.716525ms Jan 30 08:25:49.444: INFO: Pod "metadata-proxy-v0.1-hs8dc" satisfied condition "running and ready, or succeeded" Jan 30 08:25:49.444: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-lzpl": Phase="Running", Reason="", readiness=true. Elapsed: 47.648274ms Jan 30 08:25:49.444: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-lzpl" satisfied condition "running and ready, or succeeded" Jan 30 08:25:49.444: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:25:49.444: INFO: Getting external IP address for bootstrap-e2e-minion-group-lzpl Jan 30 08:25:49.444: 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-lzpl(104.198.98.143:22) Jan 30 08:25:49.448: INFO: Pod "metadata-proxy-v0.1-2x5bf": Phase="Running", Reason="", readiness=true. Elapsed: 48.016934ms Jan 30 08:25:49.448: INFO: Pod "metadata-proxy-v0.1-2x5bf" satisfied condition "running and ready, or succeeded" Jan 30 08:25:49.448: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 48.773328ms Jan 30 08:25:49.448: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:49.449: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 48.820859ms Jan 30 08:25:49.449: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:49.450: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=true. Elapsed: 50.328663ms Jan 30 08:25:49.450: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww" satisfied condition "running and ready, or succeeded" Jan 30 08:25:49.450: INFO: Pod "metadata-proxy-v0.1-ntpwl": Phase="Running", Reason="", readiness=true. Elapsed: 50.497938ms Jan 30 08:25:49.450: INFO: Pod "metadata-proxy-v0.1-ntpwl" satisfied condition "running and ready, or succeeded" Jan 30 08:25:49.450: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-70zb": Phase="Running", Reason="", readiness=true. Elapsed: 50.942499ms Jan 30 08:25:49.450: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-70zb" satisfied condition "running and ready, or succeeded" Jan 30 08:25:49.450: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [metadata-proxy-v0.1-ntpwl kube-proxy-bootstrap-e2e-minion-group-70zb] Jan 30 08:25:49.450: INFO: Getting external IP address for bootstrap-e2e-minion-group-70zb Jan 30 08:25:49.450: 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-70zb(34.105.73.232:22) Jan 30 08:25:49.957: INFO: ssh prow@104.198.98.143: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 08:25:49.957: INFO: ssh prow@104.198.98.143:22: stdout: "" Jan 30 08:25:49.957: INFO: ssh prow@104.198.98.143:22: stderr: "" Jan 30 08:25:49.957: INFO: ssh prow@104.198.98.143:22: exit code: 0 Jan 30 08:25:49.957: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-lzpl condition Ready to be false Jan 30 08:25:49.969: INFO: ssh prow@34.105.73.232: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 08:25:49.969: INFO: ssh prow@34.105.73.232:22: stdout: "" Jan 30 08:25:49.969: INFO: ssh prow@34.105.73.232:22: stderr: "" Jan 30 08:25:49.969: INFO: ssh prow@34.105.73.232:22: exit code: 0 Jan 30 08:25:49.969: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-70zb condition Ready to be false Jan 30 08:25:50.000: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:50.012: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:51.496: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2.096115045s Jan 30 08:25:51.496: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:51.496: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 2.096029798s Jan 30 08:25:51.496: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:52.045: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:52.056: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:53.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4.092956488s Jan 30 08:25:53.493: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 4.092814668s Jan 30 08:25:53.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:53.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:54.089: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:54.099: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:55.495: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 6.095640535s Jan 30 08:25:55.495: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:55.497: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 6.096967007s Jan 30 08:25:55.497: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:56.133: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:56.143: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:57.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 8.091561883s Jan 30 08:25:57.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:57.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 8.091492464s Jan 30 08:25:57.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:58.175: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:58.187: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:59.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 10.091330401s Jan 30 08:25:59.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:59.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 10.091313856s Jan 30 08:25:59.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:00.218: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:00.229: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:01.493: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 12.09311556s Jan 30 08:26:01.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 12.093263185s Jan 30 08:26:01.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:01.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:02.262: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:02.272: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:03.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 14.091428262s Jan 30 08:26:03.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 14.091296426s Jan 30 08:26:03.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:03.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:04.306: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:04.317: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:05.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 16.091971622s Jan 30 08:26:05.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:05.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 16.092076094s Jan 30 08:26:05.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:06.364: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:06.364: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:07.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 18.091879414s Jan 30 08:26:07.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 18.091728796s Jan 30 08:26:07.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:07.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:08.409: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:08.409: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:09.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 20.092062958s Jan 30 08:26:09.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:09.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 20.094028768s Jan 30 08:26:09.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:10.454: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:10.454: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:11.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 22.093961758s Jan 30 08:26:11.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:11.494: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 22.093990915s Jan 30 08:26:11.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:12.498: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:12.498: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:13.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 24.09215671s Jan 30 08:26:13.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:13.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 24.092078773s Jan 30 08:26:13.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:14.545: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:14.545: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:15.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 26.09132851s Jan 30 08:26:15.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:15.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 26.091367319s Jan 30 08:26:15.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:16.590: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:16.590: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:17.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 28.092505944s Jan 30 08:26:17.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:17.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 28.094461623s Jan 30 08:26:17.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:18.636: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:18.638: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:19.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 30.091914507s Jan 30 08:26:19.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 30.091775445s Jan 30 08:26:19.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:19.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:20.681: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:20.683: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:21.493: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 32.093178042s Jan 30 08:26:21.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:21.495: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 32.095245038s Jan 30 08:26:21.495: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:22.723: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:22.726: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:23.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 34.092521411s Jan 30 08:26:23.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:23.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 34.092409497s Jan 30 08:26:23.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:24.766: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:24.769: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:25.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 36.091156263s Jan 30 08:26:25.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:25.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 36.093143092s Jan 30 08:26:25.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:26.811: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:26.813: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:27.496: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 38.096028289s Jan 30 08:26:27.496: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:27.498: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 38.098167256s Jan 30 08:26:27.498: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:28.855: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:28.857: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:29.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 40.091893767s Jan 30 08:26:29.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 40.091776817s Jan 30 08:26:29.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:29.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:30.899: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:30.901: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:31.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 42.092268733s Jan 30 08:26:31.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:31.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 42.094492692s Jan 30 08:26:31.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:32.944: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:32.945: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:33.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 44.092200312s Jan 30 08:26:33.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:33.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 44.092208596s Jan 30 08:26:33.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:34.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:34.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:35.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 46.09265903s Jan 30 08:26:35.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:35.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 46.09260939s Jan 30 08:26:35.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:37.038: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:37.038: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-lzpl condition Ready to be true Jan 30 08:26:37.089: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:37.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 48.091382561s Jan 30 08:26:37.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 48.091529174s Jan 30 08:26:37.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:37.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:39.082: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:39.134: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:39.493: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 50.093528763s Jan 30 08:26:39.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:39.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 50.094826793s Jan 30 08:26:39.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:41.126: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-70zb condition Ready to be true Jan 30 08:26:41.170: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:41.177: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:41.511: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 52.111452858s Jan 30 08:26:41.511: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:41.513: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 52.113486516s Jan 30 08:26:41.513: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:43.213: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:43.221: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:43.505: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 54.105299335s Jan 30 08:26:43.505: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:43.505: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=true. Elapsed: 54.105317568s Jan 30 08:26:43.505: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8" satisfied condition "running and ready, or succeeded" Jan 30 08:26:45.258: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:45.267: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:45.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 56.091693487s Jan 30 08:26:45.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:47.303: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:47.314: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:47.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 58.092189526s Jan 30 08:26:47.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:49.346: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:49.358: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:49.503: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m0.103721033s Jan 30 08:26:49.503: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:51.389: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:26:51.402: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:51.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m2.091375667s Jan 30 08:26:51.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:53.433: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:26:53.445: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:53.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.092105483s Jan 30 08:26:53.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:55.477: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:26:55.488: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:55.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.090675243s Jan 30 08:26:55.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:57.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m8.093965657s Jan 30 08:26:57.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:57.521: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:26:57.531: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:59.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.091096135s Jan 30 08:26:59.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:59.565: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:26:59.575: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:01.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.094569497s Jan 30 08:27:01.505: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:01.607: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:01.619: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:03.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m14.091504907s Jan 30 08:27:03.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:03.652: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:03.663: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:05.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.091418798s Jan 30 08:27:05.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:05.700: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:05.706: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:07.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.091085557s Jan 30 08:27:07.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:07.744: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:07.749: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:09.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.090771535s Jan 30 08:27:09.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:09.787: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:09.791: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:11.495: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.095773593s Jan 30 08:27:11.495: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:11.852: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:11.852: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:13.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m24.090719521s Jan 30 08:27:13.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:13.898: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:13.898: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:15.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m26.091545306s Jan 30 08:27:15.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:15.944: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:15.944: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:17.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m28.09105169s Jan 30 08:27:17.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:17.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:17.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:19.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m30.091092376s Jan 30 08:27:19.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:20.035: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:20.035: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:21.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m32.092792717s Jan 30 08:27:21.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:22.081: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:22.081: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:23.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m34.091635868s Jan 30 08:27:23.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:24.125: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:24.125: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:25.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m36.091621195s Jan 30 08:27:25.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:26.170: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:26.170: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:27.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m38.09097842s Jan 30 08:27:27.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:28.216: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:28.216: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:29.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m40.092503303s Jan 30 08:27:29.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:30.259: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:30.260: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:31.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m42.091884144s Jan 30 08:27:31.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:32.303: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:32.307: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:33.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m44.091961056s Jan 30 08:27:33.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:34.346: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:34.350: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:35.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m46.091164157s Jan 30 08:27:35.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:36.390: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:36.395: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:37.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m48.091156613s Jan 30 08:27:37.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:38.435: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:38.438: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:39.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m50.091259399s Jan 30 08:27:39.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:40.478: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:40.482: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:41.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m52.091024472s Jan 30 08:27:41.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:42.524: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:42.526: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:43.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m54.093986212s Jan 30 08:27:43.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:44.568: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:44.570: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:45.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m56.091725186s Jan 30 08:27:45.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:46.612: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:46.615: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:47.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m58.091970861s Jan 30 08:27:47.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:48.664: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:48.664: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:49.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m0.091219812s Jan 30 08:27:49.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:50.709: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:50.709: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:51.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m2.092690423s Jan 30 08:27:51.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:52.753: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:52.753: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:53.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m4.091874262s Jan 30 08:27:53.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:54.800: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:54.800: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:55.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m6.091580013s Jan 30 08:27:55.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:56.844: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:56.844: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:57.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m8.091441645s Jan 30 08:27:57.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:58.889: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:58.889: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:59.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m10.090763704s Jan 30 08:27:59.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:00.934: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:28:00.934: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:28:01.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m12.092022626s Jan 30 08:28:01.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:02.979: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:28:02.979: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:28:03.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m14.091336294s Jan 30 08:28:03.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:05.026: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:28:05.026: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:28:05.499: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m16.099280115s Jan 30 08:28:05.499: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:07.073: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [metadata-proxy-v0.1-ntpwl kube-proxy-bootstrap-e2e-minion-group-70zb] Jan 30 08:28:07.073: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-70zb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:28:07.073: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:28:07.073: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-hs8dc" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:28:07.073: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-lzpl" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:28:07.073: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-ntpwl" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:28:07.121: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-lzpl": Phase="Running", Reason="", readiness=true. Elapsed: 47.126104ms Jan 30 08:28:07.121: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-lzpl" satisfied condition "running and ready, or succeeded" Jan 30 08:28:07.121: INFO: Pod "metadata-proxy-v0.1-ntpwl": Phase="Running", Reason="", readiness=true. Elapsed: 47.188328ms Jan 30 08:28:07.121: INFO: Pod "metadata-proxy-v0.1-ntpwl" satisfied condition "running and ready, or succeeded" Jan 30 08:28:07.121: INFO: Pod "metadata-proxy-v0.1-hs8dc": Phase="Running", Reason="", readiness=true. Elapsed: 47.324456ms Jan 30 08:28:07.121: INFO: Pod "metadata-proxy-v0.1-hs8dc" satisfied condition "running and ready, or succeeded" Jan 30 08:28:07.121: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:28:07.121: INFO: Reboot successful on node bootstrap-e2e-minion-group-lzpl Jan 30 08:28:07.121: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-70zb": Phase="Running", Reason="", readiness=true. Elapsed: 47.465633ms Jan 30 08:28:07.121: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-70zb" satisfied condition "running and ready, or succeeded" Jan 30 08:28:07.121: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [metadata-proxy-v0.1-ntpwl kube-proxy-bootstrap-e2e-minion-group-70zb] Jan 30 08:28:07.121: INFO: Reboot successful on node bootstrap-e2e-minion-group-70zb Jan 30 08:28:07.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m18.091344888s Jan 30 08:28:07.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:09.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m20.091970501s Jan 30 08:28:09.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:11.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m22.09402355s Jan 30 08:28:11.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:13.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m24.091451014s Jan 30 08:28:13.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:15.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m26.091996736s Jan 30 08:28:15.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:17.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m28.091393449s Jan 30 08:28:17.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:19.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m30.091024783s Jan 30 08:28:19.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:21.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m32.091208573s Jan 30 08:28:21.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:23.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m34.091855294s Jan 30 08:28:23.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:25.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m36.093167421s Jan 30 08:28:25.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:27.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m38.091264006s Jan 30 08:28:27.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:29.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m40.091092619s Jan 30 08:28:29.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:31.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m42.092595683s Jan 30 08:28:31.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:33.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m44.091330092s Jan 30 08:28:33.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:35.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m46.091734119s Jan 30 08:28:35.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:37.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m48.091153138s Jan 30 08:28:37.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:39.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m50.092982854s Jan 30 08:28:39.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:41.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m52.091893859s Jan 30 08:28:41.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:43.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m54.091511377s Jan 30 08:28:43.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:45.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m56.0926068s Jan 30 08:28:45.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:47.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m58.090676884s Jan 30 08:28:47.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:49.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m0.090757014s Jan 30 08:28:49.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:51.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m2.092188065s Jan 30 08:28:51.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:53.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m4.091454642s Jan 30 08:28:53.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:55.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m6.090809517s Jan 30 08:28:55.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:57.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m8.091423556s Jan 30 08:28:57.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:59.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m10.091386128s Jan 30 08:28:59.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:01.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m12.091929664s Jan 30 08:29:01.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:03.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m14.091041927s Jan 30 08:29:03.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:05.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m16.091588956s Jan 30 08:29:05.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:07.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m18.090800828s Jan 30 08:29:07.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:09.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m20.090522563s Jan 30 08:29:09.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:11.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m22.092975267s Jan 30 08:29:11.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:13.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m24.091247945s Jan 30 08:29:13.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:15.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m26.091666319s Jan 30 08:29:15.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:17.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m28.09258671s Jan 30 08:29:17.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:19.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m30.09122392s Jan 30 08:29:19.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:21.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m32.092533577s Jan 30 08:29:21.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:23.501: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m34.101453549s Jan 30 08:29:23.501: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:25.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m36.090939334s Jan 30 08:29:25.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:27.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m38.093089037s Jan 30 08:29:27.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:29.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m40.091174167s Jan 30 08:29:29.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:31.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m42.091408118s Jan 30 08:29:31.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:33.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m44.09163303s Jan 30 08:29:33.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:35.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m46.090527133s Jan 30 08:29:35.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:37.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m48.092666903s Jan 30 08:29:37.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:39.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m50.092954847s Jan 30 08:29:39.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:41.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m52.094469387s Jan 30 08:29:41.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:43.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m54.091633117s Jan 30 08:29:43.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:45.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m56.09101419s Jan 30 08:29:45.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:47.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m58.091373025s Jan 30 08:29:47.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:49.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m0.091477925s Jan 30 08:29:49.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:51.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m2.091985067s Jan 30 08:29:51.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:53.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m4.091506363s Jan 30 08:29:53.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:55.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m6.091365925s Jan 30 08:29:55.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:57.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m8.092634652s Jan 30 08:29:57.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:59.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m10.090741537s Jan 30 08:29:59.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:01.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m12.092356065s Jan 30 08:30:01.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:03.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m14.091801856s Jan 30 08:30:03.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:05.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m16.09101208s Jan 30 08:30:05.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:07.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m18.091396817s Jan 30 08:30:07.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:09.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m20.091344522s Jan 30 08:30:09.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:11.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m22.092124862s Jan 30 08:30:11.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:13.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m24.091416847s Jan 30 08:30:13.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:15.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m26.091134567s Jan 30 08:30:15.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:17.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m28.091657708s Jan 30 08:30:17.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:19.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m30.092110741s Jan 30 08:30:19.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:21.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m32.092083113s Jan 30 08:30:21.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:23.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m34.091252521s Jan 30 08:30:23.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:25.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m36.090750083s Jan 30 08:30:25.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:27.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m38.091313583s Jan 30 08:30:27.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:29.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m40.090655446s Jan 30 08:30:29.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:31.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m42.091982991s Jan 30 08:30:31.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:33.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m44.091297666s Jan 30 08:30:33.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:35.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m46.090776681s Jan 30 08:30:35.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:37.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m48.091243975s Jan 30 08:30:37.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:39.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m50.091573326s Jan 30 08:30:39.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:41.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m52.093513668s Jan 30 08:30:41.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:43.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m54.091283409s Jan 30 08:30:43.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:45.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m56.091477377s Jan 30 08:30:45.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:47.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m58.091164806s Jan 30 08:30:47.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Automatically polling progress: [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by dropping all inbound packets for a while and ensure they function afterwards (Spec Runtime: 5m0.295s) test/e2e/cloud/gcp/reboot.go:136 In [It] (Node Runtime: 5m0s) test/e2e/cloud/gcp/reboot.go:136 Spec Goroutine goroutine 7742 [semacquire, 5 minutes] sync.runtime_Semacquire(0xc0044dc390?) /usr/local/go/src/runtime/sema.go:62 sync.(*WaitGroup).Wait(0x7f5a5026a0f8?) /usr/local/go/src/sync/waitgroup.go:139 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot({0x7f5a5026a0f8?, 0xc003a45940}, {0x8147128?, 0xc004ee9380}, {0xc000edb6c0, 0x182}, 0xc003c30060) test/e2e/cloud/gcp/reboot.go:181 > k8s.io/kubernetes/test/e2e/cloud/gcp.glob..func8.7({0x7f5a5026a0f8, 0xc003a45940}) test/e2e/cloud/gcp/reboot.go:141 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func2({0x8111f08?, 0xc003a45940}) vendor/github.com/onsi/ginkgo/v2/internal/node.go:452 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() vendor/github.com/onsi/ginkgo/v2/internal/suite.go:854 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode vendor/github.com/onsi/ginkgo/v2/internal/suite.go:841 Goroutines of Interest goroutine 7744 [chan receive, 5 minutes] k8s.io/kubernetes/test/e2e/framework/pod.checkPodsCondition({0x7f5a5026a0f8?, 0xc003a45940}, {0x8147128?, 0xc004ee9380}, {0x76d190b, 0xb}, {0xc0047d8000, 0x4, 0x4}, 0x45d964b800, ...) test/e2e/framework/pod/resource.go:531 k8s.io/kubernetes/test/e2e/framework/pod.CheckPodsRunningReadyOrSucceeded(...) test/e2e/framework/pod/resource.go:508 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f5a5026a0f8, 0xc003a45940}, {0x8147128, 0xc004ee9380}, {0x7ffde098c5ee, 0x3}, {0xc0037d5300, 0x1f}, {0xc000edb6c0, 0x182}) test/e2e/cloud/gcp/reboot.go:284 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x0) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 Jan 30 08:30:49.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 5m0.092124034s Jan 30 08:30:49.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:49.534: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 5m0.134251122s Jan 30 08:30:49.534: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:49.534: INFO: Pod volume-snapshot-controller-0 failed to be running and ready, or succeeded. Jan 30 08:30:49.534: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: false. Pods: [kube-dns-autoscaler-5f6455f985-9xvq8 kube-proxy-bootstrap-e2e-minion-group-4sww metadata-proxy-v0.1-2x5bf volume-snapshot-controller-0] Jan 30 08:30:49.534: INFO: Status for not ready pod kube-system/kube-dns-autoscaler-5f6455f985-9xvq8: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:04:24 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:25:19 +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 08:25:19 +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 08:04:24 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP:10.64.1.33 PodIPs:[{IP:10.64.1.33}] StartTime:2023-01-30 08:04:24 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:autoscaler State:{Waiting:&ContainerStateWaiting{Reason:CrashLoopBackOff,Message:back-off 1m20s restarting failed container=autoscaler pod=kube-dns-autoscaler-5f6455f985-9xvq8_kube-system(feddd70a-8a25-432a-bdec-943c9ac3981f),} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-30 08:25:17 +0000 UTC,FinishedAt:2023-01-30 08:25:18 +0000 UTC,ContainerID:containerd://876e862172aaac4ff4066671c4a05ae3acd2267e3adbc5c9b9033a8253cab448,}} 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://876e862172aaac4ff4066671c4a05ae3acd2267e3adbc5c9b9033a8253cab448 Started:0xc00428626f}] QOSClass:Burstable EphemeralContainerStatuses:[]} Jan 30 08:30:49.596: INFO: Retrieving log for container kube-system/kube-dns-autoscaler-5f6455f985-9xvq8/autoscaler: I0130 08:26:42.866870 1 autoscaler.go:49] Scaling Namespace: kube-system, Target: deployment/coredns I0130 08:26:43.122970 1 plugin.go:50] Set control mode to linear I0130 08:26:43.122995 1 linear_controller.go:60] ConfigMap version change (old: new: 581) - rebuilding params I0130 08:26:43.123004 1 linear_controller.go:61] Params from apiserver: {"coresPerReplica":256,"includeUnschedulableNodes":true,"nodesPerReplica":16,"preventSinglePointFailure":true} I0130 08:26:43.123186 1 linear_controller.go:80] Defaulting min replicas count to 1 for linear controller Jan 30 08:30:49.596: INFO: Retrieving log for the last terminated container kube-system/kube-dns-autoscaler-5f6455f985-9xvq8/autoscaler: I0130 08:26:42.866870 1 autoscaler.go:49] Scaling Namespace: kube-system, Target: deployment/coredns I0130 08:26:43.122970 1 plugin.go:50] Set control mode to linear I0130 08:26:43.122995 1 linear_controller.go:60] ConfigMap version change (old: new: 581) - rebuilding params I0130 08:26:43.123004 1 linear_controller.go:61] Params from apiserver: {"coresPerReplica":256,"includeUnschedulableNodes":true,"nodesPerReplica":16,"preventSinglePointFailure":true} I0130 08:26:43.123186 1 linear_controller.go:80] Defaulting min replicas count to 1 for linear controller Jan 30 08:30:49.596: INFO: Status for not ready pod kube-system/volume-snapshot-controller-0: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:04:24 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:13:16 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-snapshot-controller]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:13:16 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-snapshot-controller]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:04:24 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP: PodIPs:[] StartTime:2023-01-30 08:04:24 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:volume-snapshot-controller State:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:255,Signal:0,Reason:Unknown,Message:,StartedAt:2023-01-30 08:09:36 +0000 UTC,FinishedAt:2023-01-30 08:10:08 +0000 UTC,ContainerID:containerd://fc5fe498ab9f9ef05d29250867b55487c202cb13ae08f863960b97a4a70ab311,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:5 Image:registry.k8s.io/sig-storage/snapshot-controller:v6.1.0 ImageID:registry.k8s.io/sig-storage/snapshot-controller@sha256:823c75d0c45d1427f6d850070956d9ca657140a7bbf828381541d1d808475280 ContainerID:containerd://fc5fe498ab9f9ef05d29250867b55487c202cb13ae08f863960b97a4a70ab311 Started:0xc004286c97}] QOSClass:BestEffort EphemeralContainerStatuses:[]} Jan 30 08:30:49.660: INFO: Retrieving log for container kube-system/volume-snapshot-controller-0/volume-snapshot-controller: Jan 30 08:30:49.660: INFO: Retrieving log for the last terminated container kube-system/volume-snapshot-controller-0/volume-snapshot-controller: Jan 30 08:30:49.660: INFO: Node bootstrap-e2e-minion-group-4sww failed reboot test. Jan 30 08:30:49.661: INFO: Executing termination hook on nodes Jan 30 08:30:49.661: INFO: Getting external IP address for bootstrap-e2e-minion-group-4sww Jan 30 08:30:49.661: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-4sww(34.127.116.58:22) Jan 30 08:30:50.174: INFO: ssh prow@34.127.116.58:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 30 08:30:50.174: INFO: ssh prow@34.127.116.58:22: stdout: "" Jan 30 08:30:50.174: INFO: ssh prow@34.127.116.58:22: stderr: "cat: /tmp/drop-inbound.log: No such file or directory\n" Jan 30 08:30:50.174: INFO: ssh prow@34.127.116.58:22: exit code: 1 Jan 30 08:30:50.174: INFO: Error while issuing ssh command: failed running "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log": <nil> (exit code 1, stderr cat: /tmp/drop-inbound.log: No such file or directory ) Jan 30 08:30:50.174: INFO: Getting external IP address for bootstrap-e2e-minion-group-70zb Jan 30 08:30:50.174: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-70zb(34.105.73.232:22) Jan 30 08:30:50.698: INFO: ssh prow@34.105.73.232:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 30 08:30:50.698: INFO: ssh prow@34.105.73.232: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 08:25:59 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 08:30:50.698: INFO: ssh prow@34.105.73.232:22: stderr: "" Jan 30 08:30:50.698: INFO: ssh prow@34.105.73.232:22: exit code: 0 Jan 30 08:30:50.698: INFO: Getting external IP address for bootstrap-e2e-minion-group-lzpl Jan 30 08:30:50.698: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-lzpl(104.198.98.143:22) Jan 30 08:30:51.214: INFO: ssh prow@104.198.98.143:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 30 08:30:51.214: INFO: ssh prow@104.198.98.143: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 08:25:59 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 08:30:51.214: INFO: ssh prow@104.198.98.143:22: stderr: "" Jan 30 08:30:51.214: INFO: ssh prow@104.198.98.143: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 08:30:51.214 < 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 08:30:51.215 (5m2.016s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 08:30:51.215 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 08:30:51.215 Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-f4jgz to bootstrap-e2e-minion-group-70zb Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 928.320713ms (928.329043ms including waiting) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-6846b5b5f-f4jgz Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Unhealthy: Readiness probe failed: Get "http://10.64.2.7:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Unhealthy: Liveness probe failed: Get "http://10.64.2.7:8080/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Killing: Container coredns failed liveness probe, will be restarted Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-6846b5b5f-f4jgz Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-fr6bb to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 2.34366857s (2.343676986s including waiting) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.6:8181/ready": dial tcp 10.64.1.6:8181: connect: connection refused Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-fr6bb_kube-system(daf9ffd3-e380-4f4d-ad87-79e4ab4a4657) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.13:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.17:8181/ready": dial tcp 10.64.1.17:8181: connect: connection refused Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-fr6bb_kube-system(daf9ffd3-e380-4f4d-ad87-79e4ab4a4657) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.22:8181/ready": dial tcp 10.64.1.22:8181: connect: connection refused Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} FailedMount: MountVolume.SetUp failed for volume "config-volume" : object "kube-system"/"coredns" not registered Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-6846b5b5f-fr6bb Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.27:8181/ready": dial tcp 10.64.1.27:8181: connect: connection refused Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-fr6bb_kube-system(daf9ffd3-e380-4f4d-ad87-79e4ab4a4657) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.28:8181/ready": dial tcp 10.64.1.28:8181: connect: connection refused Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.29:8181/ready": dial tcp 10.64.1.29:8181: connect: connection refused Jan 30 08:30:51.272: 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 08:30:51.272: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-fr6bb Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-f4jgz Jan 30 08:30:51.272: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 1 Jan 30 08:30:51.272: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 2 from 1 Jan 30 08:30:51.272: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container etcd-container Jan 30 08:30:51.272: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container etcd-container Jan 30 08:30:51.272: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container etcd-container Jan 30 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container etcd-container Jan 30 08:30:51.272: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container etcd-container Jan 30 08:30:51.272: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe failed: Jan 30 08:30:51.272: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/etcd:3.5.7-0" already present on machine Jan 30 08:30:51.272: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_eac7a became leader Jan 30 08:30:51.272: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_b6cb3 became leader Jan 30 08:30:51.272: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_a9a9e became leader Jan 30 08:30:51.272: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_ab557 became leader Jan 30 08:30:51.272: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_46919 became leader Jan 30 08:30:51.272: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_d62f8 became leader Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-jzpmd to bootstrap-e2e-minion-group-70zb Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 596.974861ms (596.984979ms including waiting) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Killing: Stopping container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-pwpgn to bootstrap-e2e-minion-group-lzpl Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 616.72361ms (616.743908ms including waiting) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-pwpgn_kube-system(73d72a79-ab94-4213-a4e3-cc1b78ebf5e1) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-pwpgn_kube-system(73d72a79-ab94-4213-a4e3-cc1b78ebf5e1) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "http://10.64.3.11:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "http://10.64.3.14:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-zfhmc to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 1.276962957s (1.276975297s including waiting) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-zfhmc_kube-system(8e0c73bc-79ed-465e-9e1b-3d9d3b215fbd) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Liveness probe failed: Get "http://10.64.1.20:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-zfhmc Jan 30 08:30:51.272: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-jzpmd Jan 30 08:30:51.272: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-pwpgn Jan 30 08:30:51.272: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container konnectivity-server-container Jan 30 08:30:51.272: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container konnectivity-server-container Jan 30 08:30:51.272: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container konnectivity-server-container Jan 30 08:30:51.272: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-server:v0.1.1" already present on machine Jan 30 08:30:51.272: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-addon-manager Jan 30 08:30:51.272: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-addon-manager Jan 30 08:30:51.272: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-addon-manager Jan 30 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container kube-addon-manager in pod kube-addon-manager-bootstrap-e2e-master_kube-system(ecad253bdb3dfebf3d39882505699622) Jan 30 08:30:51.272: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 08:30:51.272: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-apiserver Jan 30 08:30:51.272: 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 08:30:51.272: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe failed: Get "https://127.0.0.1:443/livez?exclude=etcd&exclude=kms-provider-0&exclude=kms-provider-1": dial tcp 127.0.0.1:443: connect: connection refused Jan 30 08:30:51.272: 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 08:30:51.272: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-controller-manager Jan 30 08:30:51.272: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-controller-manager Jan 30 08:30:51.272: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-controller-manager Jan 30 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_eb52f13c-d35a-4660-ac4b-5487ea4674b4 became leader Jan 30 08:30:51.272: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_d7cd6907-4822-4c1e-ab3e-96a2a537c9c8 became leader Jan 30 08:30:51.272: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_f911ee3b-2fcd-4329-9631-7240c46847a2 became leader Jan 30 08:30:51.272: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_e9a6a3b8-afc2-40c9-88b5-1bffbed3472d became leader Jan 30 08:30:51.272: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_67d4675f-aab3-4535-8235-dca5abe9126b became leader Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-dns-autoscaler-5f6455f985-9xvq8 to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" in 1.290542065s (1.290556435s including waiting) Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container autoscaler in pod kube-dns-autoscaler-5f6455f985-9xvq8_kube-system(feddd70a-8a25-432a-bdec-943c9ac3981f) Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/kube-dns-autoscaler-5f6455f985-9xvq8 Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container autoscaler in pod kube-dns-autoscaler-5f6455f985-9xvq8_kube-system(feddd70a-8a25-432a-bdec-943c9ac3981f) Jan 30 08:30:51.272: 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 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985: {replicaset-controller } SuccessfulCreate: Created pod: kube-dns-autoscaler-5f6455f985-9xvq8 Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler: {deployment-controller } ScalingReplicaSet: Scaled up replica set kube-dns-autoscaler-5f6455f985 to 1 Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-4sww_kube-system(2a66a2cc36d62b3aeb028309b150fd28) Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-4sww_kube-system(2a66a2cc36d62b3aeb028309b150fd28) Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-70zb_kube-system(a4babc2e16d27b32a55d77ad17615418) Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-lzpl_kube-system(bb8aee5a88c070b1c20014b5786bd63b) Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-lzpl_kube-system(bb8aee5a88c070b1c20014b5786bd63b) Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: 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 08:30:51.272: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-scheduler Jan 30 08:30:51.272: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-scheduler Jan 30 08:30:51.272: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-scheduler Jan 30 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_2d942942-28fe-4c7b-bf8d-c8add0a5e06b became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_5f846ea0-d739-4bd9-b437-b9a92cd83f2e became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_a0fb5dc7-f249-47a8-8d3e-33ccabb95f6f became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_7415f67b-bfba-4fdd-9056-39d4c5856eb5 became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_d5208f23-af49-4f12-93ef-16ebe1f537c7 became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_2bdd6aa6-17b4-471f-8fda-40a08b27f8b4 became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_5271494a-3330-45b8-8161-3e097c9f15c7 became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_46a97a32-4de5-4aa0-ba77-5e6ce565bea7 became leader Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {default-scheduler } Scheduled: Successfully assigned kube-system/l7-default-backend-8549d69d99-sfzcc to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" in 689.339496ms (689.364815ms including waiting) Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container default-http-backend Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container default-http-backend Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container default-http-backend Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container default-http-backend Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container default-http-backend Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/l7-default-backend-8549d69d99-sfzcc Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container default-http-backend Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99: {replicaset-controller } SuccessfulCreate: Created pod: l7-default-backend-8549d69d99-sfzcc Jan 30 08:30:51.272: INFO: event for l7-default-backend: {deployment-controller } ScalingReplicaSet: Scaled up replica set l7-default-backend-8549d69d99 to 1 Jan 30 08:30:51.272: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container l7-lb-controller Jan 30 08:30:51.272: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container l7-lb-controller Jan 30 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container l7-lb-controller Jan 30 08:30:51.272: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-2n86l to bootstrap-e2e-master Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 752.740258ms (752.748002ms including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.074248729s (2.074257418s including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-2x5bf to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 749.462052ms (749.507403ms including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.527604672s (1.527613918s including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-hs8dc to bootstrap-e2e-minion-group-lzpl Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 764.181591ms (764.191233ms including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.918416325s (1.918454047s including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-ntpwl to bootstrap-e2e-minion-group-70zb Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 710.312601ms (710.332713ms including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.813089082s (1.813114209s including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-2n86l Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-2x5bf Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-ntpwl Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-hs8dc Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-6764bf875c-mz4ml to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 2.739401416s (2.739412077s including waiting) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 3.5812862s (3.581293742s including waiting) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-6764bf875c-mz4ml Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulDelete: Deleted pod: metrics-server-v0.5.2-6764bf875c-mz4ml Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-867b8754b9-l4cmw to bootstrap-e2e-minion-group-lzpl Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 1.344954453s (1.344972808s including waiting) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 1.027183997s (1.027202082s including waiting) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.3:10250/readyz": dial tcp 10.64.3.3:10250: connect: connection refused Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.3:10250/livez": dial tcp 10.64.3.3:10250: connect: connection refused Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.3:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.3:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.4:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.6:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.6:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.7:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.7:10250/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.7:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/metrics-server-v0.5.2-867b8754b9-l4cmw Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.10:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.10:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.10:10250/livez": dial tcp 10.64.3.10:10250: connect: connection refused Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container metrics-server in pod metrics-server-v0.5.2-867b8754b9-l4cmw_kube-system(edb88606-dea5-4d78-a129-394d7e5e1621) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container metrics-server-nanny in pod metrics-server-v0.5.2-867b8754b9-l4cmw_kube-system(edb88606-dea5-4d78-a129-394d7e5e1621) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.13:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/metrics-server-v0.5.2-867b8754b9-l4cmw Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.17:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-867b8754b9-l4cmw Jan 30 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {default-scheduler } Scheduled: Successfully assigned kube-system/volume-snapshot-controller-0 to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" in 2.209540469s (2.209562216s including waiting) Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container volume-snapshot-controller Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container volume-snapshot-controller Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container volume-snapshot-controller Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(c6c6c7f7-c5e1-4952-92a4-213bd7b74a7d) Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container volume-snapshot-controller Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container volume-snapshot-controller Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container volume-snapshot-controller Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(c6c6c7f7-c5e1-4952-92a4-213bd7b74a7d) Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/volume-snapshot-controller-0 Jan 30 08:30:51.272: 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 08:30:51.272 (58ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 08:30:51.272 Jan 30 08:30:51.272: 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 08:30:51.318 (46ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 08:30:51.318 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 08:30:51.318 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 08:30:51.318 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 08:30:51.319 STEP: Collecting events from namespace "reboot-8896". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 08:30:51.319 STEP: Found 0 events. - test/e2e/framework/debug/dump.go:46 @ 01/30/23 08:30:51.368 Jan 30 08:30:51.411: INFO: POD NODE PHASE GRACE CONDITIONS Jan 30 08:30:51.411: INFO: Jan 30 08:30:51.455: INFO: Logging node info for node bootstrap-e2e-master Jan 30 08:30:51.499: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-master 25e3a9be-de28-4f0d-af40-b41298dcace3 3088 0 2023-01-30 08:04:04 +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 08:04:04 +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 08:04:12 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kube-controller-manager Update v1 2023-01-30 08:04:25 +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":{}}} } {kubelet Update v1 2023-01-30 08:26:58 +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-gci-gce-slow-1-3/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 08:04:12 +0000 UTC,LastTransitionTime:2023-01-30 08:04:12 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 08:26:58 +0000 UTC,LastTransitionTime:2023-01-30 08:04:04 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 08:26:58 +0000 UTC,LastTransitionTime:2023-01-30 08:04:04 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 08:26:58 +0000 UTC,LastTransitionTime:2023-01-30 08:04:04 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 08:26:58 +0000 UTC,LastTransitionTime:2023-01-30 08:04:25 +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:35.185.242.153,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-master.c.k8s-jkns-gci-gce-slow-1-3.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-master.c.k8s-jkns-gci-gce-slow-1-3.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:477868102422177d7f7415c3e373afa6,SystemUUID:47786810-2422-177d-7f74-15c3e373afa6,BootID:a3908d7b-f0bc-40bf-b765-9bf9e0b2edd5,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-17-g3695f29c3,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 08:30:51.500: INFO: Logging kubelet events for node bootstrap-e2e-master Jan 30 08:30:51.549: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-master Jan 30 08:30:51.624: INFO: kube-addon-manager-bootstrap-e2e-master started at 2023-01-30 08:03:36 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container kube-addon-manager ready: true, restart count 4 Jan 30 08:30:51.624: INFO: l7-lb-controller-bootstrap-e2e-master started at 2023-01-30 08:03:36 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container l7-lb-controller ready: false, restart count 7 Jan 30 08:30:51.624: INFO: kube-scheduler-bootstrap-e2e-master started at 2023-01-30 08:03:15 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container kube-scheduler ready: false, restart count 7 Jan 30 08:30:51.624: INFO: etcd-server-bootstrap-e2e-master started at 2023-01-30 08:03:15 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container etcd-container ready: true, restart count 3 Jan 30 08:30:51.624: INFO: konnectivity-server-bootstrap-e2e-master started at 2023-01-30 08:03:15 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container konnectivity-server-container ready: true, restart count 1 Jan 30 08:30:51.624: INFO: kube-apiserver-bootstrap-e2e-master started at 2023-01-30 08:03:15 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container kube-apiserver ready: true, restart count 2 Jan 30 08:30:51.624: INFO: kube-controller-manager-bootstrap-e2e-master started at 2023-01-30 08:03:15 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container kube-controller-manager ready: true, restart count 6 Jan 30 08:30:51.624: INFO: metadata-proxy-v0.1-2n86l started at 2023-01-30 08:04:47 +0000 UTC (0+2 container statuses recorded) Jan 30 08:30:51.624: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 08:30:51.624: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 08:30:51.624: INFO: etcd-server-events-bootstrap-e2e-master started at 2023-01-30 08:03:15 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container etcd-container ready: true, restart count 1 Jan 30 08:30:51.807: INFO: Latency metrics for node bootstrap-e2e-master Jan 30 08:30:51.807: INFO: Logging node info for node bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.850: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-4sww e5ebaefa-6c48-484d-bcca-ee34144f5220 3311 0 2023-01-30 08:04:10 +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-4sww 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 08: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":{}}} } {kube-controller-manager Update v1 2023-01-30 08:04:24 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kube-controller-manager Update v1 2023-01-30 08:13:26 +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\"":{}}}} } {node-problem-detector Update v1 2023-01-30 08:26:46 +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 08:28:46 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:memory":{}},"f:capacity":{"f:memory":{}},"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":{},"f:nodeInfo":{"f:bootID":{}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.1.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-gci-gce-slow-1-3/us-west1-b/bootstrap-e2e-minion-group-4sww,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: {{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:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 08:04:24 +0000 UTC,LastTransitionTime:2023-01-30 08:04:24 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:46 +0000 UTC,LastTransitionTime:2023-01-30 08:04:10 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:46 +0000 UTC,LastTransitionTime:2023-01-30 08:04:10 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:46 +0000 UTC,LastTransitionTime:2023-01-30 08:04:10 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 08:28:46 +0000 UTC,LastTransitionTime:2023-01-30 08:13:26 +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.127.116.58,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-4sww.c.k8s-jkns-gci-gce-slow-1-3.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-4sww.c.k8s-jkns-gci-gce-slow-1-3.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:1587ef0cadce15f90180f38710627777,SystemUUID:1587ef0c-adce-15f9-0180-f38710627777,BootID:fa460ea4-d0a2-4dbe-ab97-6c9aa2001dd9,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-17-g3695f29c3,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 08:30:51.851: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.943: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.999: INFO: kube-proxy-bootstrap-e2e-minion-group-4sww started at 2023-01-30 08:04:10 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.999: INFO: Container kube-proxy ready: false, restart count 9 Jan 30 08:30:51.999: INFO: l7-default-backend-8549d69d99-sfzcc started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.999: INFO: Container default-http-backend ready: true, restart count 2 Jan 30 08:30:51.999: INFO: volume-snapshot-controller-0 started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.999: INFO: Container volume-snapshot-controller ready: false, restart count 5 Jan 30 08:30:51.999: INFO: kube-dns-autoscaler-5f6455f985-9xvq8 started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.999: INFO: Container autoscaler ready: true, restart count 7 Jan 30 08:30:51.999: INFO: coredns-6846b5b5f-fr6bb started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.999: INFO: Container coredns ready: true, restart count 10 Jan 30 08:30:51.999: INFO: metadata-proxy-v0.1-2x5bf started at 2023-01-30 08:04:11 +0000 UTC (0+2 container statuses recorded) Jan 30 08:30:51.999: INFO: Container metadata-proxy ready: true, restart count 2 Jan 30 08:30:51.999: INFO: Container prometheus-to-sd-exporter ready: true, restart count 2 Jan 30 08:30:51.999: INFO: konnectivity-agent-zfhmc started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.999: INFO: Container konnectivity-agent ready: false, restart count 2 Jan 30 08:30:52.173: INFO: Latency metrics for node bootstrap-e2e-minion-group-4sww Jan 30 08:30:52.173: INFO: Logging node info for node bootstrap-e2e-minion-group-70zb Jan 30 08:30:52.217: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-70zb 3c700f64-69ef-4f4a-9d26-cfc819dde532 3229 0 2023-01-30 08:04:10 +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-70zb 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 08: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":{}}} } {kube-controller-manager Update v1 2023-01-30 08:26:40 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kube-controller-manager Update v1 2023-01-30 08:28:01 +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\"":{}}}} } {kubelet Update v1 2023-01-30 08:28:01 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:memory":{}},"f:capacity":{"f:memory":{}},"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":{},"f:nodeInfo":{"f:bootID":{}}}} status} {node-problem-detector Update v1 2023-01-30 08:28:01 +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-gci-gce-slow-1-3/us-west1-b/bootstrap-e2e-minion-group-70zb,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: {{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:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 08:04:24 +0000 UTC,LastTransitionTime:2023-01-30 08:04:24 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:28:01 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:28:01 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:28:01 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:28:01 +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.105.73.232,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-70zb.c.k8s-jkns-gci-gce-slow-1-3.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-70zb.c.k8s-jkns-gci-gce-slow-1-3.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:7f22ddd81920bdd3c04a64243a5643ef,SystemUUID:7f22ddd8-1920-bdd3-c04a-64243a5643ef,BootID:679fc1c1-66e6-4845-a9ee-b48426fcbc78,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-17-g3695f29c3,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 08:30:52.217: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-70zb Jan 30 08:30:52.276: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-70zb Jan 30 08:30:52.364: INFO: kube-proxy-bootstrap-e2e-minion-group-70zb started at 2023-01-30 08:04:10 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:52.364: INFO: Container kube-proxy ready: true, restart count 5 Jan 30 08:30:52.364: INFO: metadata-proxy-v0.1-ntpwl started at 2023-01-30 08:04:11 +0000 UTC (0+2 container statuses recorded) Jan 30 08:30:52.364: INFO: Container metadata-proxy ready: true, restart count 3 Jan 30 08:30:52.364: INFO: Container prometheus-to-sd-exporter ready: true, restart count 3 Jan 30 08:30:52.364: INFO: konnectivity-agent-jzpmd started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:52.364: INFO: Container konnectivity-agent ready: false, restart count 1 Jan 30 08:30:52.364: INFO: coredns-6846b5b5f-f4jgz started at 2023-01-30 08:04:28 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:52.364: INFO: Container coredns ready: true, restart count 5 Jan 30 08:30:52.527: INFO: Latency metrics for node bootstrap-e2e-minion-group-70zb Jan 30 08:30:52.527: INFO: Logging node info for node bootstrap-e2e-minion-group-lzpl Jan 30 08:30:52.570: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-lzpl a4c3b699-8691-4511-bcbb-47a3a1d6ae50 3230 0 2023-01-30 08:04:11 +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-lzpl 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 08:04:11 +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 08:26:35 +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 08:28:00 +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} {kube-controller-manager Update v1 2023-01-30 08:28:02 +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\"":{}}}} } {kubelet Update v1 2023-01-30 08:28:02 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:memory":{}},"f:capacity":{"f:memory":{}},"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":{},"f:nodeInfo":{"f:bootID":{}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.3.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-gci-gce-slow-1-3/us-west1-b/bootstrap-e2e-minion-group-lzpl,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:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 08:04:24 +0000 UTC,LastTransitionTime:2023-01-30 08:04:24 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:02 +0000 UTC,LastTransitionTime:2023-01-30 08:28:02 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:02 +0000 UTC,LastTransitionTime:2023-01-30 08:28:02 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:02 +0000 UTC,LastTransitionTime:2023-01-30 08:28:02 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 08:28:02 +0000 UTC,LastTransitionTime:2023-01-30 08:28:02 +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:104.198.98.143,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-lzpl.c.k8s-jkns-gci-gce-slow-1-3.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-lzpl.c.k8s-jkns-gci-gce-slow-1-3.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:8ed08c8f76fc2b446575644ca4d5d671,SystemUUID:8ed08c8f-76fc-2b44-6575-644ca4d5d671,BootID:1325252c-b17f-492b-a094-22a121e386a3,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-17-g3695f29c3,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 08:30:52.571: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-lzpl Jan 30 08:30:52.626: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-lzpl Jan 30 08:30:52.690: INFO: kube-proxy-bootstrap-e2e-minion-group-lzpl started at 2023-01-30 08:04:11 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:52.690: INFO: Container kube-proxy ready: true, restart count 7 Jan 30 08:30:52.690: INFO: metadata-proxy-v0.1-hs8dc started at 2023-01-30 08:04:12 +0000 UTC (0+2 container statuses recorded) Jan 30 08:30:52.690: INFO: Container metadata-proxy ready: true, restart count 3 Jan 30 08:30:52.690: INFO: Container prometheus-to-sd-exporter ready: true, restart count 3 Jan 30 08:30:52.690: INFO: konnectivity-agent-pwpgn started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:52.690: INFO: Container konnectivity-agent ready: true, restart count 9 Jan 30 08:30:52.690: INFO: metrics-server-v0.5.2-867b8754b9-l4cmw started at 2023-01-30 08:04:46 +0000 UTC (0+2 container statuses recorded) Jan 30 08:30:52.690: INFO: Container metrics-server ready: false, restart count 8 Jan 30 08:30:52.690: INFO: Container metrics-server-nanny ready: false, restart count 9 Jan 30 08:30:52.873: INFO: Latency metrics for node bootstrap-e2e-minion-group-lzpl END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 08:30:52.873 (1.554s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 08:30:52.873 (1.555s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 08:30:52.873 STEP: Destroying namespace "reboot-8896" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 08:30:52.873 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 08:30:52.919 (46ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 08:30:52.92 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 08:30:52.92 (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 08:30:51.214from junit_01.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 08:25:48.904 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 08:25:48.904 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 08:25:48.904 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 08:25:48.904 Jan 30 08:25:48.904: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 08:25:48.906 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/30/23 08:25:49.036 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/30/23 08:25:49.117 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 08:25:49.199 (295ms) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 08:25:49.199 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 08:25:49.199 (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 08:25:49.199 Jan 30 08:25:49.293: INFO: Getting bootstrap-e2e-minion-group-70zb Jan 30 08:25:49.293: INFO: Getting bootstrap-e2e-minion-group-4sww Jan 30 08:25:49.293: INFO: Getting bootstrap-e2e-minion-group-lzpl Jan 30 08:25:49.353: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-lzpl condition Ready to be true Jan 30 08:25:49.355: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-4sww condition Ready to be true Jan 30 08:25:49.355: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-70zb condition Ready to be true Jan 30 08:25:49.397: INFO: Node bootstrap-e2e-minion-group-lzpl has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:25:49.397: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:25:49.397: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-hs8dc" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.397: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-lzpl" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.399: INFO: Node bootstrap-e2e-minion-group-70zb has 2 assigned pods with no liveness probes: [metadata-proxy-v0.1-ntpwl kube-proxy-bootstrap-e2e-minion-group-70zb] Jan 30 08:25:49.399: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [metadata-proxy-v0.1-ntpwl kube-proxy-bootstrap-e2e-minion-group-70zb] Jan 30 08:25:49.399: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-70zb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.400: INFO: Node bootstrap-e2e-minion-group-4sww has 4 assigned pods with no liveness probes: [kube-dns-autoscaler-5f6455f985-9xvq8 kube-proxy-bootstrap-e2e-minion-group-4sww metadata-proxy-v0.1-2x5bf volume-snapshot-controller-0] Jan 30 08:25:49.400: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-9xvq8 kube-proxy-bootstrap-e2e-minion-group-4sww metadata-proxy-v0.1-2x5bf volume-snapshot-controller-0] Jan 30 08:25:49.400: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.400: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-ntpwl" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.400: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-9xvq8" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.400: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-4sww" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.400: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-2x5bf" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:25:49.444: INFO: Pod "metadata-proxy-v0.1-hs8dc": Phase="Running", Reason="", readiness=true. Elapsed: 47.716525ms Jan 30 08:25:49.444: INFO: Pod "metadata-proxy-v0.1-hs8dc" satisfied condition "running and ready, or succeeded" Jan 30 08:25:49.444: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-lzpl": Phase="Running", Reason="", readiness=true. Elapsed: 47.648274ms Jan 30 08:25:49.444: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-lzpl" satisfied condition "running and ready, or succeeded" Jan 30 08:25:49.444: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:25:49.444: INFO: Getting external IP address for bootstrap-e2e-minion-group-lzpl Jan 30 08:25:49.444: 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-lzpl(104.198.98.143:22) Jan 30 08:25:49.448: INFO: Pod "metadata-proxy-v0.1-2x5bf": Phase="Running", Reason="", readiness=true. Elapsed: 48.016934ms Jan 30 08:25:49.448: INFO: Pod "metadata-proxy-v0.1-2x5bf" satisfied condition "running and ready, or succeeded" Jan 30 08:25:49.448: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 48.773328ms Jan 30 08:25:49.448: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:49.449: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 48.820859ms Jan 30 08:25:49.449: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:49.450: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=true. Elapsed: 50.328663ms Jan 30 08:25:49.450: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww" satisfied condition "running and ready, or succeeded" Jan 30 08:25:49.450: INFO: Pod "metadata-proxy-v0.1-ntpwl": Phase="Running", Reason="", readiness=true. Elapsed: 50.497938ms Jan 30 08:25:49.450: INFO: Pod "metadata-proxy-v0.1-ntpwl" satisfied condition "running and ready, or succeeded" Jan 30 08:25:49.450: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-70zb": Phase="Running", Reason="", readiness=true. Elapsed: 50.942499ms Jan 30 08:25:49.450: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-70zb" satisfied condition "running and ready, or succeeded" Jan 30 08:25:49.450: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [metadata-proxy-v0.1-ntpwl kube-proxy-bootstrap-e2e-minion-group-70zb] Jan 30 08:25:49.450: INFO: Getting external IP address for bootstrap-e2e-minion-group-70zb Jan 30 08:25:49.450: 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-70zb(34.105.73.232:22) Jan 30 08:25:49.957: INFO: ssh prow@104.198.98.143: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 08:25:49.957: INFO: ssh prow@104.198.98.143:22: stdout: "" Jan 30 08:25:49.957: INFO: ssh prow@104.198.98.143:22: stderr: "" Jan 30 08:25:49.957: INFO: ssh prow@104.198.98.143:22: exit code: 0 Jan 30 08:25:49.957: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-lzpl condition Ready to be false Jan 30 08:25:49.969: INFO: ssh prow@34.105.73.232: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 08:25:49.969: INFO: ssh prow@34.105.73.232:22: stdout: "" Jan 30 08:25:49.969: INFO: ssh prow@34.105.73.232:22: stderr: "" Jan 30 08:25:49.969: INFO: ssh prow@34.105.73.232:22: exit code: 0 Jan 30 08:25:49.969: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-70zb condition Ready to be false Jan 30 08:25:50.000: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:50.012: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:51.496: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2.096115045s Jan 30 08:25:51.496: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:51.496: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 2.096029798s Jan 30 08:25:51.496: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:52.045: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:52.056: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:53.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4.092956488s Jan 30 08:25:53.493: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 4.092814668s Jan 30 08:25:53.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:53.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:54.089: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:54.099: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:55.495: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 6.095640535s Jan 30 08:25:55.495: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:55.497: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 6.096967007s Jan 30 08:25:55.497: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:56.133: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:56.143: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:57.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 8.091561883s Jan 30 08:25:57.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:57.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 8.091492464s Jan 30 08:25:57.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:58.175: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:58.187: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:25:59.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 10.091330401s Jan 30 08:25:59.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:59.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 10.091313856s Jan 30 08:25:59.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:00.218: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:00.229: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:01.493: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 12.09311556s Jan 30 08:26:01.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 12.093263185s Jan 30 08:26:01.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:01.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:02.262: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:02.272: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:03.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 14.091428262s Jan 30 08:26:03.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 14.091296426s Jan 30 08:26:03.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:03.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:04.306: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:04.317: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:05.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 16.091971622s Jan 30 08:26:05.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:05.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 16.092076094s Jan 30 08:26:05.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:06.364: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:06.364: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:07.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 18.091879414s Jan 30 08:26:07.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 18.091728796s Jan 30 08:26:07.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:07.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:08.409: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:08.409: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:09.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 20.092062958s Jan 30 08:26:09.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:09.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 20.094028768s Jan 30 08:26:09.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:10.454: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:10.454: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:11.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 22.093961758s Jan 30 08:26:11.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:11.494: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 22.093990915s Jan 30 08:26:11.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:12.498: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:12.498: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:13.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 24.09215671s Jan 30 08:26:13.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:13.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 24.092078773s Jan 30 08:26:13.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:14.545: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:14.545: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:15.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 26.09132851s Jan 30 08:26:15.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:15.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 26.091367319s Jan 30 08:26:15.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:16.590: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:16.590: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:17.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 28.092505944s Jan 30 08:26:17.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:17.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 28.094461623s Jan 30 08:26:17.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:18.636: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:18.638: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:19.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 30.091914507s Jan 30 08:26:19.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 30.091775445s Jan 30 08:26:19.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:19.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:20.681: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:20.683: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:21.493: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 32.093178042s Jan 30 08:26:21.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:21.495: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 32.095245038s Jan 30 08:26:21.495: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:22.723: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:22.726: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:23.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 34.092521411s Jan 30 08:26:23.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:23.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 34.092409497s Jan 30 08:26:23.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:24.766: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:24.769: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:25.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 36.091156263s Jan 30 08:26:25.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:25.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 36.093143092s Jan 30 08:26:25.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:26.811: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:26.813: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:27.496: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 38.096028289s Jan 30 08:26:27.496: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:27.498: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 38.098167256s Jan 30 08:26:27.498: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:28.855: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:28.857: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:29.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 40.091893767s Jan 30 08:26:29.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 40.091776817s Jan 30 08:26:29.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:29.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:30.899: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:30.901: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:31.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 42.092268733s Jan 30 08:26:31.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:31.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 42.094492692s Jan 30 08:26:31.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:32.944: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:32.945: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:33.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 44.092200312s Jan 30 08:26:33.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:33.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 44.092208596s Jan 30 08:26:33.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:34.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:34.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:35.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 46.09265903s Jan 30 08:26:35.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:35.492: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 46.09260939s Jan 30 08:26:35.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:37.038: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:37.038: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-lzpl condition Ready to be true Jan 30 08:26:37.089: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:37.491: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 48.091382561s Jan 30 08:26:37.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 48.091529174s Jan 30 08:26:37.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:37.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:39.082: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:26:39.134: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:39.493: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 50.093528763s Jan 30 08:26:39.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:39.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 50.094826793s Jan 30 08:26:39.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:41.126: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-70zb condition Ready to be true Jan 30 08:26:41.170: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:41.177: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:41.511: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=false. Elapsed: 52.111452858s Jan 30 08:26:41.511: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-9xvq8' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:25:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:41.513: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 52.113486516s Jan 30 08:26:41.513: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:43.213: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:43.221: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:43.505: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 54.105299335s Jan 30 08:26:43.505: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:43.505: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=true. Elapsed: 54.105317568s Jan 30 08:26:43.505: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8" satisfied condition "running and ready, or succeeded" Jan 30 08:26:45.258: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:45.267: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:45.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 56.091693487s Jan 30 08:26:45.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:47.303: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:47.314: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:47.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 58.092189526s Jan 30 08:26:47.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:49.346: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:26:49.358: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:49.503: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m0.103721033s Jan 30 08:26:49.503: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:51.389: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:26:51.402: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:51.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m2.091375667s Jan 30 08:26:51.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:53.433: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:26:53.445: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:53.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.092105483s Jan 30 08:26:53.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:55.477: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:26:55.488: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:55.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.090675243s Jan 30 08:26:55.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:57.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m8.093965657s Jan 30 08:26:57.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:57.521: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:26:57.531: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:26:59.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.091096135s Jan 30 08:26:59.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:26:59.565: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:26:59.575: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:01.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.094569497s Jan 30 08:27:01.505: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:01.607: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:01.619: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:03.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m14.091504907s Jan 30 08:27:03.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:03.652: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:03.663: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:05.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.091418798s Jan 30 08:27:05.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:05.700: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:05.706: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:07.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.091085557s Jan 30 08:27:07.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:07.744: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:07.749: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:09.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.090771535s Jan 30 08:27:09.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:09.787: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:09.791: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:11.495: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.095773593s Jan 30 08:27:11.495: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:11.852: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:11.852: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:13.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m24.090719521s Jan 30 08:27:13.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:13.898: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:13.898: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:15.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m26.091545306s Jan 30 08:27:15.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:15.944: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:15.944: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:17.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m28.09105169s Jan 30 08:27:17.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:17.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:17.990: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:19.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m30.091092376s Jan 30 08:27:19.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:20.035: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:20.035: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:21.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m32.092792717s Jan 30 08:27:21.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:22.081: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:22.081: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:23.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m34.091635868s Jan 30 08:27:23.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:24.125: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:24.125: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:25.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m36.091621195s Jan 30 08:27:25.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:26.170: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:26.170: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:27.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m38.09097842s Jan 30 08:27:27.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:28.216: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:28.216: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:29.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m40.092503303s Jan 30 08:27:29.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:30.259: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:30.260: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:31.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m42.091884144s Jan 30 08:27:31.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:32.303: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:32.307: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:33.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m44.091961056s Jan 30 08:27:33.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:34.346: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:34.350: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:35.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m46.091164157s Jan 30 08:27:35.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:36.390: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:36.395: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:37.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m48.091156613s Jan 30 08:27:37.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:38.435: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:38.438: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:39.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m50.091259399s Jan 30 08:27:39.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:40.478: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:40.482: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:41.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m52.091024472s Jan 30 08:27:41.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:42.524: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:42.526: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:43.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m54.093986212s Jan 30 08:27:43.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:44.568: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:44.570: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:45.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m56.091725186s Jan 30 08:27:45.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:46.612: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:46.615: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:47.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m58.091970861s Jan 30 08:27:47.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:48.664: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:48.664: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:49.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m0.091219812s Jan 30 08:27:49.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:50.709: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:50.709: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:51.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m2.092690423s Jan 30 08:27:51.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:52.753: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:52.753: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:53.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m4.091874262s Jan 30 08:27:53.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:54.800: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:54.800: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:55.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m6.091580013s Jan 30 08:27:55.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:56.844: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:56.844: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:57.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m8.091441645s Jan 30 08:27:57.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:27:58.889: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:27:58.889: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:27:59.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m10.090763704s Jan 30 08:27:59.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:00.934: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:40 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:28:00.934: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:26:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:28:01.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m12.092022626s Jan 30 08:28:01.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:02.979: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:28:02.979: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:28:03.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m14.091336294s Jan 30 08:28:03.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:05.026: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:40 +0000 UTC}]. Failure Jan 30 08:28:05.026: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoExecute 2023-01-30 08:26:50 +0000 UTC}]. Failure Jan 30 08:28:05.499: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m16.099280115s Jan 30 08:28:05.499: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:07.073: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [metadata-proxy-v0.1-ntpwl kube-proxy-bootstrap-e2e-minion-group-70zb] Jan 30 08:28:07.073: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-70zb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:28:07.073: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:28:07.073: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-hs8dc" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:28:07.073: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-lzpl" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:28:07.073: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-ntpwl" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:28:07.121: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-lzpl": Phase="Running", Reason="", readiness=true. Elapsed: 47.126104ms Jan 30 08:28:07.121: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-lzpl" satisfied condition "running and ready, or succeeded" Jan 30 08:28:07.121: INFO: Pod "metadata-proxy-v0.1-ntpwl": Phase="Running", Reason="", readiness=true. Elapsed: 47.188328ms Jan 30 08:28:07.121: INFO: Pod "metadata-proxy-v0.1-ntpwl" satisfied condition "running and ready, or succeeded" Jan 30 08:28:07.121: INFO: Pod "metadata-proxy-v0.1-hs8dc": Phase="Running", Reason="", readiness=true. Elapsed: 47.324456ms Jan 30 08:28:07.121: INFO: Pod "metadata-proxy-v0.1-hs8dc" satisfied condition "running and ready, or succeeded" Jan 30 08:28:07.121: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:28:07.121: INFO: Reboot successful on node bootstrap-e2e-minion-group-lzpl Jan 30 08:28:07.121: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-70zb": Phase="Running", Reason="", readiness=true. Elapsed: 47.465633ms Jan 30 08:28:07.121: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-70zb" satisfied condition "running and ready, or succeeded" Jan 30 08:28:07.121: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [metadata-proxy-v0.1-ntpwl kube-proxy-bootstrap-e2e-minion-group-70zb] Jan 30 08:28:07.121: INFO: Reboot successful on node bootstrap-e2e-minion-group-70zb Jan 30 08:28:07.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m18.091344888s Jan 30 08:28:07.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:09.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m20.091970501s Jan 30 08:28:09.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:11.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m22.09402355s Jan 30 08:28:11.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:13.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m24.091451014s Jan 30 08:28:13.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:15.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m26.091996736s Jan 30 08:28:15.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:17.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m28.091393449s Jan 30 08:28:17.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:19.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m30.091024783s Jan 30 08:28:19.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:21.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m32.091208573s Jan 30 08:28:21.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:23.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m34.091855294s Jan 30 08:28:23.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:25.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m36.093167421s Jan 30 08:28:25.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:27.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m38.091264006s Jan 30 08:28:27.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:29.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m40.091092619s Jan 30 08:28:29.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:31.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m42.092595683s Jan 30 08:28:31.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:33.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m44.091330092s Jan 30 08:28:33.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:35.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m46.091734119s Jan 30 08:28:35.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:37.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m48.091153138s Jan 30 08:28:37.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:39.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m50.092982854s Jan 30 08:28:39.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:41.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m52.091893859s Jan 30 08:28:41.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:43.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m54.091511377s Jan 30 08:28:43.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:45.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m56.0926068s Jan 30 08:28:45.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:47.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m58.090676884s Jan 30 08:28:47.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:49.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m0.090757014s Jan 30 08:28:49.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:51.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m2.092188065s Jan 30 08:28:51.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:53.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m4.091454642s Jan 30 08:28:53.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:55.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m6.090809517s Jan 30 08:28:55.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:57.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m8.091423556s Jan 30 08:28:57.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:28:59.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m10.091386128s Jan 30 08:28:59.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:01.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m12.091929664s Jan 30 08:29:01.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:03.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m14.091041927s Jan 30 08:29:03.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:05.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m16.091588956s Jan 30 08:29:05.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:07.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m18.090800828s Jan 30 08:29:07.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:09.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m20.090522563s Jan 30 08:29:09.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:11.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m22.092975267s Jan 30 08:29:11.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:13.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m24.091247945s Jan 30 08:29:13.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:15.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m26.091666319s Jan 30 08:29:15.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:17.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m28.09258671s Jan 30 08:29:17.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:19.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m30.09122392s Jan 30 08:29:19.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:21.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m32.092533577s Jan 30 08:29:21.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:23.501: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m34.101453549s Jan 30 08:29:23.501: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:25.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m36.090939334s Jan 30 08:29:25.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:27.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m38.093089037s Jan 30 08:29:27.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:29.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m40.091174167s Jan 30 08:29:29.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:31.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m42.091408118s Jan 30 08:29:31.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:33.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m44.09163303s Jan 30 08:29:33.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:35.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m46.090527133s Jan 30 08:29:35.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:37.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m48.092666903s Jan 30 08:29:37.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:39.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m50.092954847s Jan 30 08:29:39.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:41.494: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m52.094469387s Jan 30 08:29:41.494: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:43.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m54.091633117s Jan 30 08:29:43.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:45.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m56.09101419s Jan 30 08:29:45.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:47.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m58.091373025s Jan 30 08:29:47.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:49.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m0.091477925s Jan 30 08:29:49.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:51.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m2.091985067s Jan 30 08:29:51.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:53.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m4.091506363s Jan 30 08:29:53.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:55.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m6.091365925s Jan 30 08:29:55.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:57.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m8.092634652s Jan 30 08:29:57.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:29:59.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m10.090741537s Jan 30 08:29:59.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:01.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m12.092356065s Jan 30 08:30:01.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:03.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m14.091801856s Jan 30 08:30:03.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:05.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m16.09101208s Jan 30 08:30:05.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:07.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m18.091396817s Jan 30 08:30:07.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:09.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m20.091344522s Jan 30 08:30:09.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:11.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m22.092124862s Jan 30 08:30:11.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:13.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m24.091416847s Jan 30 08:30:13.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:15.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m26.091134567s Jan 30 08:30:15.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:17.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m28.091657708s Jan 30 08:30:17.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:19.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m30.092110741s Jan 30 08:30:19.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:21.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m32.092083113s Jan 30 08:30:21.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:23.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m34.091252521s Jan 30 08:30:23.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:25.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m36.090750083s Jan 30 08:30:25.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:27.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m38.091313583s Jan 30 08:30:27.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:29.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m40.090655446s Jan 30 08:30:29.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:31.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m42.091982991s Jan 30 08:30:31.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:33.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m44.091297666s Jan 30 08:30:33.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:35.490: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m46.090776681s Jan 30 08:30:35.490: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:37.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m48.091243975s Jan 30 08:30:37.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:39.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m50.091573326s Jan 30 08:30:39.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:41.493: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m52.093513668s Jan 30 08:30:41.493: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:43.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m54.091283409s Jan 30 08:30:43.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:45.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m56.091477377s Jan 30 08:30:45.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:47.491: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m58.091164806s Jan 30 08:30:47.491: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Automatically polling progress: [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by dropping all inbound packets for a while and ensure they function afterwards (Spec Runtime: 5m0.295s) test/e2e/cloud/gcp/reboot.go:136 In [It] (Node Runtime: 5m0s) test/e2e/cloud/gcp/reboot.go:136 Spec Goroutine goroutine 7742 [semacquire, 5 minutes] sync.runtime_Semacquire(0xc0044dc390?) /usr/local/go/src/runtime/sema.go:62 sync.(*WaitGroup).Wait(0x7f5a5026a0f8?) /usr/local/go/src/sync/waitgroup.go:139 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot({0x7f5a5026a0f8?, 0xc003a45940}, {0x8147128?, 0xc004ee9380}, {0xc000edb6c0, 0x182}, 0xc003c30060) test/e2e/cloud/gcp/reboot.go:181 > k8s.io/kubernetes/test/e2e/cloud/gcp.glob..func8.7({0x7f5a5026a0f8, 0xc003a45940}) test/e2e/cloud/gcp/reboot.go:141 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func2({0x8111f08?, 0xc003a45940}) vendor/github.com/onsi/ginkgo/v2/internal/node.go:452 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() vendor/github.com/onsi/ginkgo/v2/internal/suite.go:854 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode vendor/github.com/onsi/ginkgo/v2/internal/suite.go:841 Goroutines of Interest goroutine 7744 [chan receive, 5 minutes] k8s.io/kubernetes/test/e2e/framework/pod.checkPodsCondition({0x7f5a5026a0f8?, 0xc003a45940}, {0x8147128?, 0xc004ee9380}, {0x76d190b, 0xb}, {0xc0047d8000, 0x4, 0x4}, 0x45d964b800, ...) test/e2e/framework/pod/resource.go:531 k8s.io/kubernetes/test/e2e/framework/pod.CheckPodsRunningReadyOrSucceeded(...) test/e2e/framework/pod/resource.go:508 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f5a5026a0f8, 0xc003a45940}, {0x8147128, 0xc004ee9380}, {0x7ffde098c5ee, 0x3}, {0xc0037d5300, 0x1f}, {0xc000edb6c0, 0x182}) test/e2e/cloud/gcp/reboot.go:284 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x0) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 Jan 30 08:30:49.492: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 5m0.092124034s Jan 30 08:30:49.492: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:49.534: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 5m0.134251122s Jan 30 08:30:49.534: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:30:49.534: INFO: Pod volume-snapshot-controller-0 failed to be running and ready, or succeeded. Jan 30 08:30:49.534: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: false. Pods: [kube-dns-autoscaler-5f6455f985-9xvq8 kube-proxy-bootstrap-e2e-minion-group-4sww metadata-proxy-v0.1-2x5bf volume-snapshot-controller-0] Jan 30 08:30:49.534: INFO: Status for not ready pod kube-system/kube-dns-autoscaler-5f6455f985-9xvq8: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:04:24 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:25:19 +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 08:25:19 +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 08:04:24 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP:10.64.1.33 PodIPs:[{IP:10.64.1.33}] StartTime:2023-01-30 08:04:24 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:autoscaler State:{Waiting:&ContainerStateWaiting{Reason:CrashLoopBackOff,Message:back-off 1m20s restarting failed container=autoscaler pod=kube-dns-autoscaler-5f6455f985-9xvq8_kube-system(feddd70a-8a25-432a-bdec-943c9ac3981f),} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-30 08:25:17 +0000 UTC,FinishedAt:2023-01-30 08:25:18 +0000 UTC,ContainerID:containerd://876e862172aaac4ff4066671c4a05ae3acd2267e3adbc5c9b9033a8253cab448,}} 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://876e862172aaac4ff4066671c4a05ae3acd2267e3adbc5c9b9033a8253cab448 Started:0xc00428626f}] QOSClass:Burstable EphemeralContainerStatuses:[]} Jan 30 08:30:49.596: INFO: Retrieving log for container kube-system/kube-dns-autoscaler-5f6455f985-9xvq8/autoscaler: I0130 08:26:42.866870 1 autoscaler.go:49] Scaling Namespace: kube-system, Target: deployment/coredns I0130 08:26:43.122970 1 plugin.go:50] Set control mode to linear I0130 08:26:43.122995 1 linear_controller.go:60] ConfigMap version change (old: new: 581) - rebuilding params I0130 08:26:43.123004 1 linear_controller.go:61] Params from apiserver: {"coresPerReplica":256,"includeUnschedulableNodes":true,"nodesPerReplica":16,"preventSinglePointFailure":true} I0130 08:26:43.123186 1 linear_controller.go:80] Defaulting min replicas count to 1 for linear controller Jan 30 08:30:49.596: INFO: Retrieving log for the last terminated container kube-system/kube-dns-autoscaler-5f6455f985-9xvq8/autoscaler: I0130 08:26:42.866870 1 autoscaler.go:49] Scaling Namespace: kube-system, Target: deployment/coredns I0130 08:26:43.122970 1 plugin.go:50] Set control mode to linear I0130 08:26:43.122995 1 linear_controller.go:60] ConfigMap version change (old: new: 581) - rebuilding params I0130 08:26:43.123004 1 linear_controller.go:61] Params from apiserver: {"coresPerReplica":256,"includeUnschedulableNodes":true,"nodesPerReplica":16,"preventSinglePointFailure":true} I0130 08:26:43.123186 1 linear_controller.go:80] Defaulting min replicas count to 1 for linear controller Jan 30 08:30:49.596: INFO: Status for not ready pod kube-system/volume-snapshot-controller-0: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:04:24 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:13:16 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-snapshot-controller]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:13:16 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-snapshot-controller]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:04:24 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP: PodIPs:[] StartTime:2023-01-30 08:04:24 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:volume-snapshot-controller State:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:255,Signal:0,Reason:Unknown,Message:,StartedAt:2023-01-30 08:09:36 +0000 UTC,FinishedAt:2023-01-30 08:10:08 +0000 UTC,ContainerID:containerd://fc5fe498ab9f9ef05d29250867b55487c202cb13ae08f863960b97a4a70ab311,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:5 Image:registry.k8s.io/sig-storage/snapshot-controller:v6.1.0 ImageID:registry.k8s.io/sig-storage/snapshot-controller@sha256:823c75d0c45d1427f6d850070956d9ca657140a7bbf828381541d1d808475280 ContainerID:containerd://fc5fe498ab9f9ef05d29250867b55487c202cb13ae08f863960b97a4a70ab311 Started:0xc004286c97}] QOSClass:BestEffort EphemeralContainerStatuses:[]} Jan 30 08:30:49.660: INFO: Retrieving log for container kube-system/volume-snapshot-controller-0/volume-snapshot-controller: Jan 30 08:30:49.660: INFO: Retrieving log for the last terminated container kube-system/volume-snapshot-controller-0/volume-snapshot-controller: Jan 30 08:30:49.660: INFO: Node bootstrap-e2e-minion-group-4sww failed reboot test. Jan 30 08:30:49.661: INFO: Executing termination hook on nodes Jan 30 08:30:49.661: INFO: Getting external IP address for bootstrap-e2e-minion-group-4sww Jan 30 08:30:49.661: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-4sww(34.127.116.58:22) Jan 30 08:30:50.174: INFO: ssh prow@34.127.116.58:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 30 08:30:50.174: INFO: ssh prow@34.127.116.58:22: stdout: "" Jan 30 08:30:50.174: INFO: ssh prow@34.127.116.58:22: stderr: "cat: /tmp/drop-inbound.log: No such file or directory\n" Jan 30 08:30:50.174: INFO: ssh prow@34.127.116.58:22: exit code: 1 Jan 30 08:30:50.174: INFO: Error while issuing ssh command: failed running "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log": <nil> (exit code 1, stderr cat: /tmp/drop-inbound.log: No such file or directory ) Jan 30 08:30:50.174: INFO: Getting external IP address for bootstrap-e2e-minion-group-70zb Jan 30 08:30:50.174: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-70zb(34.105.73.232:22) Jan 30 08:30:50.698: INFO: ssh prow@34.105.73.232:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 30 08:30:50.698: INFO: ssh prow@34.105.73.232: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 08:25:59 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 08:30:50.698: INFO: ssh prow@34.105.73.232:22: stderr: "" Jan 30 08:30:50.698: INFO: ssh prow@34.105.73.232:22: exit code: 0 Jan 30 08:30:50.698: INFO: Getting external IP address for bootstrap-e2e-minion-group-lzpl Jan 30 08:30:50.698: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-lzpl(104.198.98.143:22) Jan 30 08:30:51.214: INFO: ssh prow@104.198.98.143:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 30 08:30:51.214: INFO: ssh prow@104.198.98.143: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 08:25:59 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 08:30:51.214: INFO: ssh prow@104.198.98.143:22: stderr: "" Jan 30 08:30:51.214: INFO: ssh prow@104.198.98.143: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 08:30:51.214 < 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 08:30:51.215 (5m2.016s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 08:30:51.215 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 08:30:51.215 Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-f4jgz to bootstrap-e2e-minion-group-70zb Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 928.320713ms (928.329043ms including waiting) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-6846b5b5f-f4jgz Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Unhealthy: Readiness probe failed: Get "http://10.64.2.7:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Unhealthy: Liveness probe failed: Get "http://10.64.2.7:8080/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Killing: Container coredns failed liveness probe, will be restarted Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-f4jgz: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-6846b5b5f-f4jgz Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-fr6bb to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 2.34366857s (2.343676986s including waiting) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.6:8181/ready": dial tcp 10.64.1.6:8181: connect: connection refused Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-fr6bb_kube-system(daf9ffd3-e380-4f4d-ad87-79e4ab4a4657) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.13:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.17:8181/ready": dial tcp 10.64.1.17:8181: connect: connection refused Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-fr6bb_kube-system(daf9ffd3-e380-4f4d-ad87-79e4ab4a4657) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.22:8181/ready": dial tcp 10.64.1.22:8181: connect: connection refused Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} FailedMount: MountVolume.SetUp failed for volume "config-volume" : object "kube-system"/"coredns" not registered Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-6846b5b5f-fr6bb Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container coredns Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.27:8181/ready": dial tcp 10.64.1.27:8181: connect: connection refused Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-fr6bb_kube-system(daf9ffd3-e380-4f4d-ad87-79e4ab4a4657) Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.28:8181/ready": dial tcp 10.64.1.28:8181: connect: connection refused Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.29:8181/ready": dial tcp 10.64.1.29:8181: connect: connection refused Jan 30 08:30:51.272: 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 08:30:51.272: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-fr6bb Jan 30 08:30:51.272: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-f4jgz Jan 30 08:30:51.272: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 1 Jan 30 08:30:51.272: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 2 from 1 Jan 30 08:30:51.272: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container etcd-container Jan 30 08:30:51.272: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container etcd-container Jan 30 08:30:51.272: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container etcd-container Jan 30 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container etcd-container Jan 30 08:30:51.272: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container etcd-container Jan 30 08:30:51.272: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe failed: Jan 30 08:30:51.272: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/etcd:3.5.7-0" already present on machine Jan 30 08:30:51.272: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_eac7a became leader Jan 30 08:30:51.272: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_b6cb3 became leader Jan 30 08:30:51.272: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_a9a9e became leader Jan 30 08:30:51.272: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_ab557 became leader Jan 30 08:30:51.272: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_46919 became leader Jan 30 08:30:51.272: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_d62f8 became leader Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-jzpmd to bootstrap-e2e-minion-group-70zb Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 596.974861ms (596.984979ms including waiting) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Killing: Stopping container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-pwpgn to bootstrap-e2e-minion-group-lzpl Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 616.72361ms (616.743908ms including waiting) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-pwpgn_kube-system(73d72a79-ab94-4213-a4e3-cc1b78ebf5e1) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-pwpgn_kube-system(73d72a79-ab94-4213-a4e3-cc1b78ebf5e1) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "http://10.64.3.11:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "http://10.64.3.14:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 08:30:51.272: INFO: event for konnectivity-agent-pwpgn: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-zfhmc to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 1.276962957s (1.276975297s including waiting) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container konnectivity-agent Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-zfhmc_kube-system(8e0c73bc-79ed-465e-9e1b-3d9d3b215fbd) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Liveness probe failed: Get "http://10.64.1.20:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:30:51.272: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-zfhmc Jan 30 08:30:51.272: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-jzpmd Jan 30 08:30:51.272: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-pwpgn Jan 30 08:30:51.272: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container konnectivity-server-container Jan 30 08:30:51.272: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container konnectivity-server-container Jan 30 08:30:51.272: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container konnectivity-server-container Jan 30 08:30:51.272: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-server:v0.1.1" already present on machine Jan 30 08:30:51.272: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-addon-manager Jan 30 08:30:51.272: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-addon-manager Jan 30 08:30:51.272: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-addon-manager Jan 30 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container kube-addon-manager in pod kube-addon-manager-bootstrap-e2e-master_kube-system(ecad253bdb3dfebf3d39882505699622) Jan 30 08:30:51.272: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 08:30:51.272: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-apiserver Jan 30 08:30:51.272: 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 08:30:51.272: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe failed: Get "https://127.0.0.1:443/livez?exclude=etcd&exclude=kms-provider-0&exclude=kms-provider-1": dial tcp 127.0.0.1:443: connect: connection refused Jan 30 08:30:51.272: 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 08:30:51.272: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-controller-manager Jan 30 08:30:51.272: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-controller-manager Jan 30 08:30:51.272: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-controller-manager Jan 30 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_eb52f13c-d35a-4660-ac4b-5487ea4674b4 became leader Jan 30 08:30:51.272: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_d7cd6907-4822-4c1e-ab3e-96a2a537c9c8 became leader Jan 30 08:30:51.272: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_f911ee3b-2fcd-4329-9631-7240c46847a2 became leader Jan 30 08:30:51.272: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_e9a6a3b8-afc2-40c9-88b5-1bffbed3472d became leader Jan 30 08:30:51.272: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_67d4675f-aab3-4535-8235-dca5abe9126b became leader Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-dns-autoscaler-5f6455f985-9xvq8 to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" in 1.290542065s (1.290556435s including waiting) Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container autoscaler in pod kube-dns-autoscaler-5f6455f985-9xvq8_kube-system(feddd70a-8a25-432a-bdec-943c9ac3981f) Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/kube-dns-autoscaler-5f6455f985-9xvq8 Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container autoscaler Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container autoscaler in pod kube-dns-autoscaler-5f6455f985-9xvq8_kube-system(feddd70a-8a25-432a-bdec-943c9ac3981f) Jan 30 08:30:51.272: 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 08:30:51.272: INFO: event for kube-dns-autoscaler-5f6455f985: {replicaset-controller } SuccessfulCreate: Created pod: kube-dns-autoscaler-5f6455f985-9xvq8 Jan 30 08:30:51.272: INFO: event for kube-dns-autoscaler: {deployment-controller } ScalingReplicaSet: Scaled up replica set kube-dns-autoscaler-5f6455f985 to 1 Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-4sww_kube-system(2a66a2cc36d62b3aeb028309b150fd28) Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-4sww_kube-system(2a66a2cc36d62b3aeb028309b150fd28) Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-70zb_kube-system(a4babc2e16d27b32a55d77ad17615418) Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-lzpl_kube-system(bb8aee5a88c070b1c20014b5786bd63b) Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container kube-proxy Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-lzpl_kube-system(bb8aee5a88c070b1c20014b5786bd63b) Jan 30 08:30:51.272: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: 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 08:30:51.272: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-scheduler Jan 30 08:30:51.272: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-scheduler Jan 30 08:30:51.272: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-scheduler Jan 30 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_2d942942-28fe-4c7b-bf8d-c8add0a5e06b became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_5f846ea0-d739-4bd9-b437-b9a92cd83f2e became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_a0fb5dc7-f249-47a8-8d3e-33ccabb95f6f became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_7415f67b-bfba-4fdd-9056-39d4c5856eb5 became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_d5208f23-af49-4f12-93ef-16ebe1f537c7 became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_2bdd6aa6-17b4-471f-8fda-40a08b27f8b4 became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_5271494a-3330-45b8-8161-3e097c9f15c7 became leader Jan 30 08:30:51.272: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_46a97a32-4de5-4aa0-ba77-5e6ce565bea7 became leader Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {default-scheduler } Scheduled: Successfully assigned kube-system/l7-default-backend-8549d69d99-sfzcc to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" in 689.339496ms (689.364815ms including waiting) Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container default-http-backend Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container default-http-backend Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container default-http-backend Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container default-http-backend Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container default-http-backend Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/l7-default-backend-8549d69d99-sfzcc Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container default-http-backend Jan 30 08:30:51.272: INFO: event for l7-default-backend-8549d69d99: {replicaset-controller } SuccessfulCreate: Created pod: l7-default-backend-8549d69d99-sfzcc Jan 30 08:30:51.272: INFO: event for l7-default-backend: {deployment-controller } ScalingReplicaSet: Scaled up replica set l7-default-backend-8549d69d99 to 1 Jan 30 08:30:51.272: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container l7-lb-controller Jan 30 08:30:51.272: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container l7-lb-controller Jan 30 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container l7-lb-controller Jan 30 08:30:51.272: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-2n86l to bootstrap-e2e-master Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 752.740258ms (752.748002ms including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.074248729s (2.074257418s including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-2x5bf to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 749.462052ms (749.507403ms including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.527604672s (1.527613918s including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-hs8dc to bootstrap-e2e-minion-group-lzpl Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 764.181591ms (764.191233ms including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.918416325s (1.918454047s including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-hs8dc: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-ntpwl to bootstrap-e2e-minion-group-70zb Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 710.312601ms (710.332713ms including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.813089082s (1.813114209s including waiting) Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container metadata-proxy Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container prometheus-to-sd-exporter Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1-ntpwl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-2n86l Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-2x5bf Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-ntpwl Jan 30 08:30:51.272: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-hs8dc Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-6764bf875c-mz4ml to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 2.739401416s (2.739412077s including waiting) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 3.5812862s (3.581293742s including waiting) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-6764bf875c-mz4ml Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulDelete: Deleted pod: metrics-server-v0.5.2-6764bf875c-mz4ml Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-867b8754b9-l4cmw to bootstrap-e2e-minion-group-lzpl Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 1.344954453s (1.344972808s including waiting) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 1.027183997s (1.027202082s including waiting) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.3:10250/readyz": dial tcp 10.64.3.3:10250: connect: connection refused Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.3:10250/livez": dial tcp 10.64.3.3:10250: connect: connection refused Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.3:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.3:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.4:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.6:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.6:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.7:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.7:10250/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.7:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/metrics-server-v0.5.2-867b8754b9-l4cmw Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Readiness probe failed: Get "https://10.64.3.10:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.10:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container metrics-server Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container metrics-server-nanny Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.10:10250/livez": dial tcp 10.64.3.10:10250: connect: connection refused Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container metrics-server in pod metrics-server-v0.5.2-867b8754b9-l4cmw_kube-system(edb88606-dea5-4d78-a129-394d7e5e1621) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container metrics-server-nanny in pod metrics-server-v0.5.2-867b8754b9-l4cmw_kube-system(edb88606-dea5-4d78-a129-394d7e5e1621) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.13:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {node-controller } NodeNotReady: Node is not ready Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/metrics-server-v0.5.2-867b8754b9-l4cmw Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9-l4cmw: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "https://10.64.3.17:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 30 08:30:51.272: INFO: event for metrics-server-v0.5.2-867b8754b9: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-867b8754b9-l4cmw Jan 30 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: 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 08:30:51.272: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {default-scheduler } Scheduled: Successfully assigned kube-system/volume-snapshot-controller-0 to bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" in 2.209540469s (2.209562216s including waiting) Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container volume-snapshot-controller Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container volume-snapshot-controller Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container volume-snapshot-controller Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(c6c6c7f7-c5e1-4952-92a4-213bd7b74a7d) Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container volume-snapshot-controller Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container volume-snapshot-controller Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container volume-snapshot-controller Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(c6c6c7f7-c5e1-4952-92a4-213bd7b74a7d) Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:30:51.272: INFO: event for volume-snapshot-controller-0: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/volume-snapshot-controller-0 Jan 30 08:30:51.272: 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 08:30:51.272 (58ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/30/23 08:30:51.272 Jan 30 08:30:51.272: 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 08:30:51.318 (46ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 08:30:51.318 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/30/23 08:30:51.318 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 08:30:51.318 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 08:30:51.319 STEP: Collecting events from namespace "reboot-8896". - test/e2e/framework/debug/dump.go:42 @ 01/30/23 08:30:51.319 STEP: Found 0 events. - test/e2e/framework/debug/dump.go:46 @ 01/30/23 08:30:51.368 Jan 30 08:30:51.411: INFO: POD NODE PHASE GRACE CONDITIONS Jan 30 08:30:51.411: INFO: Jan 30 08:30:51.455: INFO: Logging node info for node bootstrap-e2e-master Jan 30 08:30:51.499: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-master 25e3a9be-de28-4f0d-af40-b41298dcace3 3088 0 2023-01-30 08:04:04 +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 08:04:04 +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 08:04:12 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kube-controller-manager Update v1 2023-01-30 08:04:25 +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":{}}} } {kubelet Update v1 2023-01-30 08:26:58 +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-gci-gce-slow-1-3/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 08:04:12 +0000 UTC,LastTransitionTime:2023-01-30 08:04:12 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 08:26:58 +0000 UTC,LastTransitionTime:2023-01-30 08:04:04 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 08:26:58 +0000 UTC,LastTransitionTime:2023-01-30 08:04:04 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 08:26:58 +0000 UTC,LastTransitionTime:2023-01-30 08:04:04 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 08:26:58 +0000 UTC,LastTransitionTime:2023-01-30 08:04:25 +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:35.185.242.153,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-master.c.k8s-jkns-gci-gce-slow-1-3.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-master.c.k8s-jkns-gci-gce-slow-1-3.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:477868102422177d7f7415c3e373afa6,SystemUUID:47786810-2422-177d-7f74-15c3e373afa6,BootID:a3908d7b-f0bc-40bf-b765-9bf9e0b2edd5,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-17-g3695f29c3,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 08:30:51.500: INFO: Logging kubelet events for node bootstrap-e2e-master Jan 30 08:30:51.549: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-master Jan 30 08:30:51.624: INFO: kube-addon-manager-bootstrap-e2e-master started at 2023-01-30 08:03:36 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container kube-addon-manager ready: true, restart count 4 Jan 30 08:30:51.624: INFO: l7-lb-controller-bootstrap-e2e-master started at 2023-01-30 08:03:36 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container l7-lb-controller ready: false, restart count 7 Jan 30 08:30:51.624: INFO: kube-scheduler-bootstrap-e2e-master started at 2023-01-30 08:03:15 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container kube-scheduler ready: false, restart count 7 Jan 30 08:30:51.624: INFO: etcd-server-bootstrap-e2e-master started at 2023-01-30 08:03:15 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container etcd-container ready: true, restart count 3 Jan 30 08:30:51.624: INFO: konnectivity-server-bootstrap-e2e-master started at 2023-01-30 08:03:15 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container konnectivity-server-container ready: true, restart count 1 Jan 30 08:30:51.624: INFO: kube-apiserver-bootstrap-e2e-master started at 2023-01-30 08:03:15 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container kube-apiserver ready: true, restart count 2 Jan 30 08:30:51.624: INFO: kube-controller-manager-bootstrap-e2e-master started at 2023-01-30 08:03:15 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container kube-controller-manager ready: true, restart count 6 Jan 30 08:30:51.624: INFO: metadata-proxy-v0.1-2n86l started at 2023-01-30 08:04:47 +0000 UTC (0+2 container statuses recorded) Jan 30 08:30:51.624: INFO: Container metadata-proxy ready: true, restart count 0 Jan 30 08:30:51.624: INFO: Container prometheus-to-sd-exporter ready: true, restart count 0 Jan 30 08:30:51.624: INFO: etcd-server-events-bootstrap-e2e-master started at 2023-01-30 08:03:15 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.624: INFO: Container etcd-container ready: true, restart count 1 Jan 30 08:30:51.807: INFO: Latency metrics for node bootstrap-e2e-master Jan 30 08:30:51.807: INFO: Logging node info for node bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.850: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-4sww e5ebaefa-6c48-484d-bcca-ee34144f5220 3311 0 2023-01-30 08:04:10 +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-4sww 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 08: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":{}}} } {kube-controller-manager Update v1 2023-01-30 08:04:24 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kube-controller-manager Update v1 2023-01-30 08:13:26 +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\"":{}}}} } {node-problem-detector Update v1 2023-01-30 08:26:46 +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 08:28:46 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:memory":{}},"f:capacity":{"f:memory":{}},"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":{},"f:nodeInfo":{"f:bootID":{}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.1.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-gci-gce-slow-1-3/us-west1-b/bootstrap-e2e-minion-group-4sww,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: {{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:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 08:26:46 +0000 UTC,LastTransitionTime:2023-01-30 08:11:42 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 08:04:24 +0000 UTC,LastTransitionTime:2023-01-30 08:04:24 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:46 +0000 UTC,LastTransitionTime:2023-01-30 08:04:10 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:46 +0000 UTC,LastTransitionTime:2023-01-30 08:04:10 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:46 +0000 UTC,LastTransitionTime:2023-01-30 08:04:10 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 08:28:46 +0000 UTC,LastTransitionTime:2023-01-30 08:13:26 +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.127.116.58,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-4sww.c.k8s-jkns-gci-gce-slow-1-3.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-4sww.c.k8s-jkns-gci-gce-slow-1-3.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:1587ef0cadce15f90180f38710627777,SystemUUID:1587ef0c-adce-15f9-0180-f38710627777,BootID:fa460ea4-d0a2-4dbe-ab97-6c9aa2001dd9,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-17-g3695f29c3,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 08:30:51.851: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.943: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-4sww Jan 30 08:30:51.999: INFO: kube-proxy-bootstrap-e2e-minion-group-4sww started at 2023-01-30 08:04:10 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.999: INFO: Container kube-proxy ready: false, restart count 9 Jan 30 08:30:51.999: INFO: l7-default-backend-8549d69d99-sfzcc started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.999: INFO: Container default-http-backend ready: true, restart count 2 Jan 30 08:30:51.999: INFO: volume-snapshot-controller-0 started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.999: INFO: Container volume-snapshot-controller ready: false, restart count 5 Jan 30 08:30:51.999: INFO: kube-dns-autoscaler-5f6455f985-9xvq8 started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.999: INFO: Container autoscaler ready: true, restart count 7 Jan 30 08:30:51.999: INFO: coredns-6846b5b5f-fr6bb started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.999: INFO: Container coredns ready: true, restart count 10 Jan 30 08:30:51.999: INFO: metadata-proxy-v0.1-2x5bf started at 2023-01-30 08:04:11 +0000 UTC (0+2 container statuses recorded) Jan 30 08:30:51.999: INFO: Container metadata-proxy ready: true, restart count 2 Jan 30 08:30:51.999: INFO: Container prometheus-to-sd-exporter ready: true, restart count 2 Jan 30 08:30:51.999: INFO: konnectivity-agent-zfhmc started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:51.999: INFO: Container konnectivity-agent ready: false, restart count 2 Jan 30 08:30:52.173: INFO: Latency metrics for node bootstrap-e2e-minion-group-4sww Jan 30 08:30:52.173: INFO: Logging node info for node bootstrap-e2e-minion-group-70zb Jan 30 08:30:52.217: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-70zb 3c700f64-69ef-4f4a-9d26-cfc819dde532 3229 0 2023-01-30 08:04:10 +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-70zb 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 08: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":{}}} } {kube-controller-manager Update v1 2023-01-30 08:26:40 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}}}} status} {kube-controller-manager Update v1 2023-01-30 08:28:01 +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\"":{}}}} } {kubelet Update v1 2023-01-30 08:28:01 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:memory":{}},"f:capacity":{"f:memory":{}},"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":{},"f:nodeInfo":{"f:bootID":{}}}} status} {node-problem-detector Update v1 2023-01-30 08:28:01 +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-gci-gce-slow-1-3/us-west1-b/bootstrap-e2e-minion-group-70zb,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: {{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:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:16:28 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 08:04:24 +0000 UTC,LastTransitionTime:2023-01-30 08:04:24 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:28:01 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:28:01 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:28:01 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 08:28:01 +0000 UTC,LastTransitionTime:2023-01-30 08:28:01 +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.105.73.232,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-70zb.c.k8s-jkns-gci-gce-slow-1-3.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-70zb.c.k8s-jkns-gci-gce-slow-1-3.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:7f22ddd81920bdd3c04a64243a5643ef,SystemUUID:7f22ddd8-1920-bdd3-c04a-64243a5643ef,BootID:679fc1c1-66e6-4845-a9ee-b48426fcbc78,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-17-g3695f29c3,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 08:30:52.217: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-70zb Jan 30 08:30:52.276: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-70zb Jan 30 08:30:52.364: INFO: kube-proxy-bootstrap-e2e-minion-group-70zb started at 2023-01-30 08:04:10 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:52.364: INFO: Container kube-proxy ready: true, restart count 5 Jan 30 08:30:52.364: INFO: metadata-proxy-v0.1-ntpwl started at 2023-01-30 08:04:11 +0000 UTC (0+2 container statuses recorded) Jan 30 08:30:52.364: INFO: Container metadata-proxy ready: true, restart count 3 Jan 30 08:30:52.364: INFO: Container prometheus-to-sd-exporter ready: true, restart count 3 Jan 30 08:30:52.364: INFO: konnectivity-agent-jzpmd started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:52.364: INFO: Container konnectivity-agent ready: false, restart count 1 Jan 30 08:30:52.364: INFO: coredns-6846b5b5f-f4jgz started at 2023-01-30 08:04:28 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:52.364: INFO: Container coredns ready: true, restart count 5 Jan 30 08:30:52.527: INFO: Latency metrics for node bootstrap-e2e-minion-group-70zb Jan 30 08:30:52.527: INFO: Logging node info for node bootstrap-e2e-minion-group-lzpl Jan 30 08:30:52.570: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-lzpl a4c3b699-8691-4511-bcbb-47a3a1d6ae50 3230 0 2023-01-30 08:04:11 +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-lzpl 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 08:04:11 +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 08:26:35 +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 08:28:00 +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} {kube-controller-manager Update v1 2023-01-30 08:28:02 +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\"":{}}}} } {kubelet Update v1 2023-01-30 08:28:02 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:memory":{}},"f:capacity":{"f:memory":{}},"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":{},"f:nodeInfo":{"f:bootID":{}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.3.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-gci-gce-slow-1-3/us-west1-b/bootstrap-e2e-minion-group-lzpl,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:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-30 08:28:00 +0000 UTC,LastTransitionTime:2023-01-30 08:16:27 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-30 08:04:24 +0000 UTC,LastTransitionTime:2023-01-30 08:04:24 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:02 +0000 UTC,LastTransitionTime:2023-01-30 08:28:02 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:02 +0000 UTC,LastTransitionTime:2023-01-30 08:28:02 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-30 08:28:02 +0000 UTC,LastTransitionTime:2023-01-30 08:28:02 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-30 08:28:02 +0000 UTC,LastTransitionTime:2023-01-30 08:28:02 +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:104.198.98.143,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-lzpl.c.k8s-jkns-gci-gce-slow-1-3.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-lzpl.c.k8s-jkns-gci-gce-slow-1-3.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:8ed08c8f76fc2b446575644ca4d5d671,SystemUUID:8ed08c8f-76fc-2b44-6575-644ca4d5d671,BootID:1325252c-b17f-492b-a094-22a121e386a3,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-17-g3695f29c3,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 08:30:52.571: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-lzpl Jan 30 08:30:52.626: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-lzpl Jan 30 08:30:52.690: INFO: kube-proxy-bootstrap-e2e-minion-group-lzpl started at 2023-01-30 08:04:11 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:52.690: INFO: Container kube-proxy ready: true, restart count 7 Jan 30 08:30:52.690: INFO: metadata-proxy-v0.1-hs8dc started at 2023-01-30 08:04:12 +0000 UTC (0+2 container statuses recorded) Jan 30 08:30:52.690: INFO: Container metadata-proxy ready: true, restart count 3 Jan 30 08:30:52.690: INFO: Container prometheus-to-sd-exporter ready: true, restart count 3 Jan 30 08:30:52.690: INFO: konnectivity-agent-pwpgn started at 2023-01-30 08:04:24 +0000 UTC (0+1 container statuses recorded) Jan 30 08:30:52.690: INFO: Container konnectivity-agent ready: true, restart count 9 Jan 30 08:30:52.690: INFO: metrics-server-v0.5.2-867b8754b9-l4cmw started at 2023-01-30 08:04:46 +0000 UTC (0+2 container statuses recorded) Jan 30 08:30:52.690: INFO: Container metrics-server ready: false, restart count 8 Jan 30 08:30:52.690: INFO: Container metrics-server-nanny ready: false, restart count 9 Jan 30 08:30:52.873: INFO: Latency metrics for node bootstrap-e2e-minion-group-lzpl END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/30/23 08:30:52.873 (1.554s) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/30/23 08:30:52.873 (1.555s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 08:30:52.873 STEP: Destroying namespace "reboot-8896" for this suite. - test/e2e/framework/framework.go:347 @ 01/30/23 08:30:52.873 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/30/23 08:30:52.919 (46ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 08:30:52.92 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/30/23 08:30:52.92 (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 08:25:47.275
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 08:20:36.757 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/30/23 08:20:36.757 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 08:20:36.757 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/30/23 08:20:36.758 Jan 30 08:20:36.758: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/30/23 08:20:36.759 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/30/23 08:20:45.091 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/30/23 08:20:45.171 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/30/23 08:20:45.255 (8.498s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 08:20:45.255 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/30/23 08:20:45.255 (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 08:20:45.255 Jan 30 08:20:45.350: INFO: Getting bootstrap-e2e-minion-group-lzpl Jan 30 08:20:45.350: INFO: Getting bootstrap-e2e-minion-group-4sww Jan 30 08:20:45.350: INFO: Getting bootstrap-e2e-minion-group-70zb Jan 30 08:20:45.425: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-4sww condition Ready to be true Jan 30 08:20:45.425: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-70zb condition Ready to be true Jan 30 08:20:45.425: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-lzpl condition Ready to be true Jan 30 08:20:45.470: INFO: Node bootstrap-e2e-minion-group-4sww has 4 assigned pods with no liveness probes: [kube-dns-autoscaler-5f6455f985-9xvq8 kube-proxy-bootstrap-e2e-minion-group-4sww metadata-proxy-v0.1-2x5bf volume-snapshot-controller-0] Jan 30 08:20:45.470: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-9xvq8 kube-proxy-bootstrap-e2e-minion-group-4sww metadata-proxy-v0.1-2x5bf volume-snapshot-controller-0] Jan 30 08:20:45.470: INFO: Node bootstrap-e2e-minion-group-lzpl has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:20:45.470: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:20:45.470: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:20:45.470: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-hs8dc" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:20:45.470: INFO: Node bootstrap-e2e-minion-group-70zb has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-70zb metadata-proxy-v0.1-ntpwl] Jan 30 08:20:45.470: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-70zb metadata-proxy-v0.1-ntpwl] Jan 30 08:20:45.470: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-ntpwl" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:20:45.470: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-lzpl" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:20:45.470: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-4sww" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:20:45.470: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-2x5bf" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:20:45.470: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-9xvq8" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:20:45.470: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-70zb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:20:45.517: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 47.354566ms Jan 30 08:20:45.517: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:20:45.519: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8": Phase="Running", Reason="", readiness=true. Elapsed: 48.933306ms Jan 30 08:20:45.519: INFO: Pod "kube-dns-autoscaler-5f6455f985-9xvq8" satisfied condition "running and ready, or succeeded" Jan 30 08:20:45.519: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 49.214365ms Jan 30 08:20:45.519: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:20:45.519: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-70zb": Phase="Running", Reason="", readiness=true. Elapsed: 49.168794ms Jan 30 08:20:45.519: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-70zb" satisfied condition "running and ready, or succeeded" Jan 30 08:20:45.519: INFO: Pod "metadata-proxy-v0.1-hs8dc": Phase="Running", Reason="", readiness=true. Elapsed: 49.750087ms Jan 30 08:20:45.519: INFO: Pod "metadata-proxy-v0.1-hs8dc" satisfied condition "running and ready, or succeeded" Jan 30 08:20:45.519: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-lzpl": Phase="Running", Reason="", readiness=true. Elapsed: 49.587702ms Jan 30 08:20:45.519: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-lzpl" satisfied condition "running and ready, or succeeded" Jan 30 08:20:45.520: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:20:45.520: INFO: Getting external IP address for bootstrap-e2e-minion-group-lzpl Jan 30 08:20:45.520: 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-lzpl(104.198.98.143:22) Jan 30 08:20:45.520: INFO: Pod "metadata-proxy-v0.1-ntpwl": Phase="Running", Reason="", readiness=true. Elapsed: 49.863248ms Jan 30 08:20:45.520: INFO: Pod "metadata-proxy-v0.1-ntpwl" satisfied condition "running and ready, or succeeded" Jan 30 08:20:45.520: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-70zb metadata-proxy-v0.1-ntpwl] Jan 30 08:20:45.520: INFO: Pod "metadata-proxy-v0.1-2x5bf": Phase="Running", Reason="", readiness=true. Elapsed: 49.698346ms Jan 30 08:20:45.520: INFO: Getting external IP address for bootstrap-e2e-minion-group-70zb Jan 30 08:20:45.520: INFO: Pod "metadata-proxy-v0.1-2x5bf" satisfied condition "running and ready, or succeeded" Jan 30 08:20:45.520: 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-70zb(34.105.73.232:22) Jan 30 08:20:46.048: INFO: ssh prow@34.105.73.232: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 08:20:46.048: INFO: ssh prow@34.105.73.232:22: stdout: "" Jan 30 08:20:46.048: INFO: ssh prow@34.105.73.232:22: stderr: "" Jan 30 08:20:46.048: INFO: ssh prow@34.105.73.232:22: exit code: 0 Jan 30 08:20:46.048: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-70zb condition Ready to be false Jan 30 08:20:46.053: INFO: ssh prow@104.198.98.143: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 08:20:46.053: INFO: ssh prow@104.198.98.143:22: stdout: "" Jan 30 08:20:46.053: INFO: ssh prow@104.198.98.143:22: stderr: "" Jan 30 08:20:46.053: INFO: ssh prow@104.198.98.143:22: exit code: 0 Jan 30 08:20:46.053: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-lzpl condition Ready to be false Jan 30 08:20:46.092: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:46.096: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:47.563: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2.0931852s Jan 30 08:20:47.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:20:47.565: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2.094507742s Jan 30 08:20:47.565: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:20:48.136: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:48.141: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:49.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4.089089588s Jan 30 08:20:49.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:20:49.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 4.091817589s Jan 30 08:20:49.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:20:50.180: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:50.187: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:51.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 6.089988895s Jan 30 08:20:51.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:20:51.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 6.093717889s Jan 30 08:20:51.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:20:52.225: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:52.233: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:53.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 8.090718535s Jan 30 08:20:53.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:20:53.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 8.094100216s Jan 30 08:20:53.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:20:54.269: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:54.276: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:55.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 10.090263265s Jan 30 08:20:55.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:20:55.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 10.093538007s Jan 30 08:20:55.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:20:56.313: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:56.319: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:57.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 12.090109396s Jan 30 08:20:57.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:20:57.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 12.094090475s Jan 30 08:20:57.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:20:58.356: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:58.362: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:20:59.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 14.089061839s Jan 30 08:20:59.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:20:59.561: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 14.091334385s Jan 30 08:20:59.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:00.399: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:00.405: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:01.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 16.090450397s Jan 30 08:21:01.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:01.561: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 16.091171575s Jan 30 08:21:01.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:02.442: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:02.464: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:03.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 18.089638661s Jan 30 08:21:03.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:03.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 18.093034863s Jan 30 08:21:03.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:04.484: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:04.508: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:05.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 20.090108198s Jan 30 08:21:05.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:05.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 20.092315947s Jan 30 08:21:05.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:06.528: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:06.552: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:07.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 22.090459157s Jan 30 08:21:07.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:07.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 22.093660671s Jan 30 08:21:07.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:08.593: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:08.601: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:09.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 24.089566753s Jan 30 08:21:09.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:09.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 24.092456983s Jan 30 08:21:09.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:10.637: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:10.645: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:11.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 26.090056774s Jan 30 08:21:11.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:11.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 26.094328923s Jan 30 08:21:11.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:12.678: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:12.686: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:13.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 28.090474266s Jan 30 08:21:13.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:13.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 28.093928161s Jan 30 08:21:13.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:14.722: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:14.730: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:15.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 30.090582783s Jan 30 08:21:15.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:15.561: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 30.091414948s Jan 30 08:21:15.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:16.766: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:16.779: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:17.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 32.090297289s Jan 30 08:21:17.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:17.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 32.093468306s Jan 30 08:21:17.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:18.810: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:18.822: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:19.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 34.089770109s Jan 30 08:21:19.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:19.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 34.093194984s Jan 30 08:21:19.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:20.854: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:20.865: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:21.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 36.090478846s Jan 30 08:21:21.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:21.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 36.093351667s Jan 30 08:21:21.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:22.896: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:22.909: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:23.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 38.090278985s Jan 30 08:21:23.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:23.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 38.092426003s Jan 30 08:21:23.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:24.937: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:24.953: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:25.558: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 40.088545817s Jan 30 08:21:25.558: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:25.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 40.091577257s Jan 30 08:21:25.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:26.981: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:26.998: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:27.561: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 42.091251352s Jan 30 08:21:27.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:27.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 42.093684061s Jan 30 08:21:27.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:29.025: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:29.041: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:29.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 44.089642818s Jan 30 08:21:29.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:29.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 44.093999118s Jan 30 08:21:29.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:31.070: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:31.085: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:31.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 46.090760018s Jan 30 08:21:31.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:31.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 46.093394032s Jan 30 08:21:31.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:33.114: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:33.129: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 30 08:21:33.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 48.094167412s Jan 30 08:21:33.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:33.564: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 48.094659192s Jan 30 08:21:33.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:35.197: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-lzpl condition Ready to be true Jan 30 08:21:35.197: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-70zb condition Ready to be true Jan 30 08:21:35.256: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:21:35.257: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:21:35.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 50.089648424s Jan 30 08:21:35.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:35.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 50.092695241s Jan 30 08:21:35.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:37.298: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:21:37.301: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:21:37.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 52.089223364s Jan 30 08:21:37.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:37.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 52.09187098s Jan 30 08:21:37.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:39.345: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:21:39.345: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:21:39.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 54.090682382s Jan 30 08:21:39.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:39.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 54.093632105s Jan 30 08:21:39.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:41.391: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:21:41.391: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:21:41.561: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 56.09157739s Jan 30 08:21:41.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:41.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 56.09288897s Jan 30 08:21:41.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:43.436: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:21:43.436: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:21:43.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 58.090339609s Jan 30 08:21:43.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:43.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 58.09314406s Jan 30 08:21:43.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:45.480: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:21:45.481: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:21:45.562: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m0.092472082s Jan 30 08:21:45.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:45.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m0.094019537s Jan 30 08:21:45.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:47.526: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:21:47.526: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:21:47.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m2.089724768s Jan 30 08:21:47.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:47.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m2.092591153s Jan 30 08:21:47.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:49.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.089845161s Jan 30 08:21:49.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:49.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.093334738s Jan 30 08:21:49.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:49.571: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 30 08:21:49.571: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:21:51.563: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.093516098s Jan 30 08:21:51.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:51.565: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.09510296s Jan 30 08:21:51.565: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:51.617: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:21:51.621: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:21:53.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m8.090401846s Jan 30 08:21:53.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:53.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m8.093327057s Jan 30 08:21:53.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:53.661: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:21:53.664: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:21:55.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.089096399s Jan 30 08:21:55.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:55.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.091724214s Jan 30 08:21:55.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:55.703: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:21:55.707: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:21:57.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.089277659s Jan 30 08:21:57.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:57.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.091983151s Jan 30 08:21:57.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:57.747: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:21:57.750: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:21:59.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m14.089346656s Jan 30 08:21:59.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:21:59.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m14.092216609s Jan 30 08:21:59.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:21:59.789: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:21:59.792: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:01.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.089398998s Jan 30 08:22:01.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:01.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.09310928s Jan 30 08:22:01.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:01.834: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:01.836: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:03.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.089714462s Jan 30 08:22:03.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:03.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.092461723s Jan 30 08:22:03.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:03.878: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:03.879: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:05.561: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.090827167s Jan 30 08:22:05.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:05.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.091598923s Jan 30 08:22:05.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:05.925: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:05.926: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:07.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.089353826s Jan 30 08:22:07.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:07.561: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.091412816s Jan 30 08:22:07.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:07.966: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:07.970: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:09.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m24.089448173s Jan 30 08:22:09.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:09.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m24.091756978s Jan 30 08:22:09.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:10.010: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:10.013: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:11.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m26.090223233s Jan 30 08:22:11.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:11.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m26.093239899s Jan 30 08:22:11.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:12.052: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:12.056: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:13.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m28.089329999s Jan 30 08:22:13.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:13.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m28.092042913s Jan 30 08:22:13.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:14.095: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:14.100: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:15.577: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m30.107333693s Jan 30 08:22:15.577: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:15.579: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m30.10896328s Jan 30 08:22:15.579: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:16.139: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:16.144: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:17.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m32.090651428s Jan 30 08:22:17.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:17.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m32.0930308s Jan 30 08:22:17.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:18.183: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:18.188: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:19.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m34.089725328s Jan 30 08:22:19.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:19.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m34.093586754s Jan 30 08:22:19.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:20.226: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:20.231: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:21.561: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m36.091676539s Jan 30 08:22:21.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:21.565: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m36.094554426s Jan 30 08:22:21.565: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:22.269: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:22.274: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:23.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m38.090523548s Jan 30 08:22:23.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:23.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m38.093501851s Jan 30 08:22:23.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:24.313: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:24.319: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:25.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m40.089501799s Jan 30 08:22:25.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:25.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m40.092439608s Jan 30 08:22:25.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:26.370: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:26.372: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:27.562: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m42.092009199s Jan 30 08:22:27.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:27.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m42.093491477s Jan 30 08:22:27.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:28.432: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:28.432: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:29.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m44.090326346s Jan 30 08:22:29.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:29.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m44.092895192s Jan 30 08:22:29.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:30.476: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:30.477: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:31.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m46.089643632s Jan 30 08:22:31.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:31.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m46.093610821s Jan 30 08:22:31.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:32.519: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:32.521: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:33.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m48.089814186s Jan 30 08:22:33.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:33.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m48.092584941s Jan 30 08:22:33.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:34.561: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:34.564: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:35.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m50.089428464s Jan 30 08:22:35.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:35.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m50.092373096s Jan 30 08:22:35.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:36.604: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:36.608: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:37.561: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m52.091251081s Jan 30 08:22:37.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:37.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m52.093690773s Jan 30 08:22:37.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:38.647: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:38.651: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:39.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m54.089522505s Jan 30 08:22:39.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:39.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m54.092123722s Jan 30 08:22:39.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:40.691: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:40.700: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:41.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m56.090071492s Jan 30 08:22:41.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:41.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m56.093132475s Jan 30 08:22:41.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:42.733: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:42.744: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:43.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m58.08967603s Jan 30 08:22:43.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:43.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 1m58.093025026s Jan 30 08:22:43.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:44.776: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:44.789: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:45.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m0.08960451s Jan 30 08:22:45.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:45.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m0.092262019s Jan 30 08:22:45.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:46.820: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:46.832: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:47.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m2.090701244s Jan 30 08:22:47.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:47.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m2.092989788s Jan 30 08:22:47.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:48.878: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:48.880: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:49.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m4.089861145s Jan 30 08:22:49.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:49.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m4.092536868s Jan 30 08:22:49.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:50.925: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:50.925: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:51.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m6.090687536s Jan 30 08:22:51.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:51.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m6.093276406s Jan 30 08:22:51.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:52.969: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:52.969: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:53.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m8.089703367s Jan 30 08:22:53.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:53.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m8.092544047s Jan 30 08:22:53.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:55.013: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:55.013: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:55.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m10.09032102s Jan 30 08:22:55.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:55.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m10.092914198s Jan 30 08:22:55.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:57.058: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:57.058: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:57.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m12.090047036s Jan 30 08:22:57.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:57.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m12.093095888s Jan 30 08:22:57.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:22:59.103: INFO: Condition Ready of node bootstrap-e2e-minion-group-lzpl is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:50 +0000 UTC}]. Failure Jan 30 08:22:59.103: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-30 08:21:35 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:22:59.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m14.089762329s Jan 30 08:22:59.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:22:59.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m14.092621271s Jan 30 08:22:59.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:01.149: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:23:01.149: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-hs8dc" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:23:01.149: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:23:01.149: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-lzpl" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:23:01.194: INFO: Pod "metadata-proxy-v0.1-hs8dc": Phase="Running", Reason="", readiness=true. Elapsed: 45.577428ms Jan 30 08:23:01.194: INFO: Pod "metadata-proxy-v0.1-hs8dc" satisfied condition "running and ready, or succeeded" Jan 30 08:23:01.194: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-lzpl": Phase="Running", Reason="", readiness=true. Elapsed: 45.36065ms Jan 30 08:23:01.194: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-lzpl" satisfied condition "running and ready, or succeeded" Jan 30 08:23:01.194: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-lzpl metadata-proxy-v0.1-hs8dc] Jan 30 08:23:01.194: INFO: Reboot successful on node bootstrap-e2e-minion-group-lzpl Jan 30 08:23:01.561: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m16.091719962s Jan 30 08:23:01.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:01.565: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m16.094903688s Jan 30 08:23:01.565: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:03.193: INFO: Condition Ready of node bootstrap-e2e-minion-group-70zb is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoExecute 2023-01-30 08:21:40 +0000 UTC}]. Failure Jan 30 08:23:03.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m18.090306024s Jan 30 08:23:03.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:03.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m18.092746804s Jan 30 08:23:03.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:05.237: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-70zb metadata-proxy-v0.1-ntpwl] Jan 30 08:23:05.237: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-ntpwl" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:23:05.237: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-70zb" in namespace "kube-system" to be "running and ready, or succeeded" Jan 30 08:23:05.281: INFO: Pod "metadata-proxy-v0.1-ntpwl": Phase="Running", Reason="", readiness=true. Elapsed: 43.674534ms Jan 30 08:23:05.281: INFO: Pod "metadata-proxy-v0.1-ntpwl" satisfied condition "running and ready, or succeeded" Jan 30 08:23:05.281: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-70zb": Phase="Running", Reason="", readiness=true. Elapsed: 43.626227ms Jan 30 08:23:05.281: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-70zb" satisfied condition "running and ready, or succeeded" Jan 30 08:23:05.281: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-70zb metadata-proxy-v0.1-ntpwl] Jan 30 08:23:05.281: INFO: Reboot successful on node bootstrap-e2e-minion-group-70zb Jan 30 08:23:05.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m20.090024986s Jan 30 08:23:05.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:05.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m20.09292074s Jan 30 08:23:05.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:07.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m22.089112327s Jan 30 08:23:07.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:07.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m22.091770529s Jan 30 08:23:07.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:09.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m24.088955621s Jan 30 08:23:09.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:09.561: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m24.091423251s Jan 30 08:23:09.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:11.564: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m26.094525376s Jan 30 08:23:11.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:11.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m26.094355156s Jan 30 08:23:11.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:13.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m28.089738285s Jan 30 08:23:13.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:13.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m28.092699569s Jan 30 08:23:13.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:15.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m30.090447158s Jan 30 08:23:15.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:15.562: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m30.092470308s Jan 30 08:23:15.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:17.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m32.089776659s Jan 30 08:23:17.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:17.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m32.093309076s Jan 30 08:23:17.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:19.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m34.089639934s Jan 30 08:23:19.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:19.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m34.092574908s Jan 30 08:23:19.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:21.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m36.090463515s Jan 30 08:23:21.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:21.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m36.093027737s Jan 30 08:23:21.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:23.562: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m38.092044374s Jan 30 08:23:23.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:23.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m38.093652803s Jan 30 08:23:23.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:25.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m40.090644025s Jan 30 08:23:25.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:25.561: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=false. Elapsed: 2m40.091411767s Jan 30 08:23:25.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-4sww' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:20:32 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:10 +0000 UTC }] Jan 30 08:23:27.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m42.090063239s Jan 30 08:23:27.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:27.563: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww": Phase="Running", Reason="", readiness=true. Elapsed: 2m42.093468934s Jan 30 08:23:27.564: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-4sww" satisfied condition "running and ready, or succeeded" Jan 30 08:23:29.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m44.090303172s Jan 30 08:23:29.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:31.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m46.090587603s Jan 30 08:23:31.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:33.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m48.09001663s Jan 30 08:23:33.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:35.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m50.089656553s Jan 30 08:23:35.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:37.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m52.09041636s Jan 30 08:23:37.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:39.593: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m54.123449973s Jan 30 08:23:39.593: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:41.561: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m56.091613132s Jan 30 08:23:41.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:43.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m58.090698199s Jan 30 08:23:43.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:45.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m0.089559028s Jan 30 08:23:45.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:47.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m2.089244455s Jan 30 08:23:47.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:49.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m4.090288217s Jan 30 08:23:49.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:51.562: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m6.091923106s Jan 30 08:23:51.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:53.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m8.090556068s Jan 30 08:23:53.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:55.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m10.089788198s Jan 30 08:23:55.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:57.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m12.089285348s Jan 30 08:23:57.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:23:59.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m14.09032329s Jan 30 08:23:59.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:01.562: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m16.092308148s Jan 30 08:24:01.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:03.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m18.08988868s Jan 30 08:24:03.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:05.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m20.090505155s Jan 30 08:24:05.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:07.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m22.090723548s Jan 30 08:24:07.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:09.589: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m24.119564049s Jan 30 08:24:09.589: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:11.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m26.090284685s Jan 30 08:24:11.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:13.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m28.090517087s Jan 30 08:24:13.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:15.562: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m30.091926472s Jan 30 08:24:15.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:17.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m32.090768918s Jan 30 08:24:17.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:19.561: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m34.09083586s Jan 30 08:24:19.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:21.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m36.090627719s Jan 30 08:24:21.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:23.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m38.090166373s Jan 30 08:24:23.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:25.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m40.089064312s Jan 30 08:24:25.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:27.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m42.089806753s Jan 30 08:24:27.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:29.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m44.089885068s Jan 30 08:24:29.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:31.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m46.090755887s Jan 30 08:24:31.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:33.563: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m48.092920274s Jan 30 08:24:33.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:35.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m50.089465583s Jan 30 08:24:35.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:37.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m52.089742791s Jan 30 08:24:37.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:39.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m54.089808656s Jan 30 08:24:39.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:41.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m56.090706973s Jan 30 08:24:41.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:43.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m58.090258307s Jan 30 08:24:43.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:45.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m0.090303986s Jan 30 08:24:45.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:47.562: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m2.092338799s Jan 30 08:24:47.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:49.561: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m4.091092815s Jan 30 08:24:49.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:51.562: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m6.092493397s Jan 30 08:24:51.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:53.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m8.089660007s Jan 30 08:24:53.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:55.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m10.090436714s Jan 30 08:24:55.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:57.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m12.089509517s Jan 30 08:24:57.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:24:59.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m14.08937139s Jan 30 08:24:59.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:01.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m16.090500728s Jan 30 08:25:01.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:03.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m18.090382208s Jan 30 08:25:03.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:05.561: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m20.091534406s Jan 30 08:25:05.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:07.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m22.089190125s Jan 30 08:25:07.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:09.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m24.090648827s Jan 30 08:25:09.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:11.563: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m26.093373624s Jan 30 08:25:11.563: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:13.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m28.089998701s Jan 30 08:25:13.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:15.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m30.090669186s Jan 30 08:25:15.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:17.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m32.089327786s Jan 30 08:25:17.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:19.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m34.089691883s Jan 30 08:25:19.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:21.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m36.089222287s Jan 30 08:25:21.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:23.561: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m38.09085358s Jan 30 08:25:23.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:25.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m40.089319244s Jan 30 08:25:25.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:27.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m42.089443235s Jan 30 08:25:27.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:29.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m44.089876833s Jan 30 08:25:29.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:31.562: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m46.092697421s Jan 30 08:25:31.562: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:33.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m48.089231033s Jan 30 08:25:33.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:35.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m50.089848282s Jan 30 08:25:35.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:37.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m52.089707737s Jan 30 08:25:37.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:39.561: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m54.091221875s Jan 30 08:25:39.561: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:41.564: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m56.09448303s Jan 30 08:25:41.564: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:43.559: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4m58.089387122s Jan 30 08:25:43.559: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Automatically polling progress: [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] each node by dropping all outbound packets for a while and ensure they function afterwards (Spec Runtime: 5m8.499s) test/e2e/cloud/gcp/reboot.go:144 In [It] (Node Runtime: 5m0.001s) test/e2e/cloud/gcp/reboot.go:144 Spec Goroutine goroutine 7197 [semacquire, 6 minutes] sync.runtime_Semacquire(0xc003218948?) /usr/local/go/src/runtime/sema.go:62 sync.(*WaitGroup).Wait(0x7f5a5026a0f8?) /usr/local/go/src/sync/waitgroup.go:139 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot({0x7f5a5026a0f8?, 0xc00205cc00}, {0x8147128?, 0xc0046a0680}, {0xc0032601a0, 0x187}, 0xc0031f9fb0) test/e2e/cloud/gcp/reboot.go:181 > k8s.io/kubernetes/test/e2e/cloud/gcp.glob..func8.8({0x7f5a5026a0f8, 0xc00205cc00}) test/e2e/cloud/gcp/reboot.go:149 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func2({0x8111f08?, 0xc00205cc00}) vendor/github.com/onsi/ginkgo/v2/internal/node.go:452 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() vendor/github.com/onsi/ginkgo/v2/internal/suite.go:854 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.(*Suite).runNode vendor/github.com/onsi/ginkgo/v2/internal/suite.go:841 Goroutines of Interest goroutine 7199 [chan receive, 4 minutes] k8s.io/kubernetes/test/e2e/framework/pod.checkPodsCondition({0x7f5a5026a0f8?, 0xc00205cc00}, {0x8147128?, 0xc0046a0680}, {0x76d190b, 0xb}, {0xc0036d28c0, 0x4, 0x4}, 0x45d964b800, ...) test/e2e/framework/pod/resource.go:531 k8s.io/kubernetes/test/e2e/framework/pod.CheckPodsRunningReadyOrSucceeded(...) test/e2e/framework/pod/resource.go:508 > k8s.io/kubernetes/test/e2e/cloud/gcp.rebootNode({0x7f5a5026a0f8, 0xc00205cc00}, {0x8147128, 0xc0046a0680}, {0x7ffde098c5ee, 0x3}, {0xc0032424a0, 0x1f}, {0xc0032601a0, 0x187}) test/e2e/cloud/gcp/reboot.go:284 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x0) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 Jan 30 08:25:45.560: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 5m0.090068777s Jan 30 08:25:45.560: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:45.602: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 5m0.132200068s Jan 30 08:25:45.602: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-4sww' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:13:16 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-30 08:04:24 +0000 UTC }] Jan 30 08:25:45.602: INFO: Pod volume-snapshot-controller-0 failed to be running and ready, or succeeded. Jan 30 08:25:45.602: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: false. Pods: [kube-dns-autoscaler-5f6455f985-9xvq8 kube-proxy-bootstrap-e2e-minion-group-4sww metadata-proxy-v0.1-2x5bf volume-snapshot-controller-0] Jan 30 08:25:45.602: INFO: Status for not ready pod kube-system/kube-proxy-bootstrap-e2e-minion-group-4sww: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:04:10 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:20:32 +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 08:20:32 +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 08:04:10 +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 08:04:10 +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-4sww_kube-system(2a66a2cc36d62b3aeb028309b150fd28),} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-30 08:19:28 +0000 UTC,FinishedAt:2023-01-30 08:20:32 +0000 UTC,ContainerID:containerd://13bc0b126bcb3f1763d2f805afec00f15f81ac88a49acb3b2b9cde4c8f1adb81,}} Ready:false RestartCount:8 Image:registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4 ImageID:sha256:c4cd2f6a04c334ec2dfc72eb03fcaacc3231faaa0dfd84b73b8f65c5b0afa401 ContainerID:containerd://13bc0b126bcb3f1763d2f805afec00f15f81ac88a49acb3b2b9cde4c8f1adb81 Started:0xc00475555f}] QOSClass:Burstable EphemeralContainerStatuses:[]} Jan 30 08:25:45.663: INFO: Retrieving log for container kube-system/kube-proxy-bootstrap-e2e-minion-group-4sww/kube-proxy: Jan 30 08:25:45.663: INFO: Retrieving log for the last terminated container kube-system/kube-proxy-bootstrap-e2e-minion-group-4sww/kube-proxy: Jan 30 08:25:45.663: INFO: Status for not ready pod kube-system/volume-snapshot-controller-0: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:04:24 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:13:16 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-snapshot-controller]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:13:16 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [volume-snapshot-controller]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-30 08:04:24 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP: PodIPs:[] StartTime:2023-01-30 08:04:24 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:volume-snapshot-controller State:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:255,Signal:0,Reason:Unknown,Message:,StartedAt:2023-01-30 08:09:36 +0000 UTC,FinishedAt:2023-01-30 08:10:08 +0000 UTC,ContainerID:containerd://fc5fe498ab9f9ef05d29250867b55487c202cb13ae08f863960b97a4a70ab311,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:5 Image:registry.k8s.io/sig-storage/snapshot-controller:v6.1.0 ImageID:registry.k8s.io/sig-storage/snapshot-controller@sha256:823c75d0c45d1427f6d850070956d9ca657140a7bbf828381541d1d808475280 ContainerID:containerd://fc5fe498ab9f9ef05d29250867b55487c202cb13ae08f863960b97a4a70ab311 Started:0xc004755cd7}] QOSClass:BestEffort EphemeralContainerStatuses:[]} Jan 30 08:25:45.708: INFO: Retrieving log for container kube-system/volume-snapshot-controller-0/volume-snapshot-controller: Jan 30 08:25:45.708: INFO: Retrieving log for the last terminated container kube-system/volume-snapshot-controller-0/volume-snapshot-controller: Jan 30 08:25:45.708: INFO: Node bootstrap-e2e-minion-group-4sww failed reboot test. Jan 30 08:25:45.708: INFO: Executing termination hook on nodes Jan 30 08:25:45.708: INFO: Getting external IP address for bootstrap-e2e-minion-group-4sww Jan 30 08:25:45.708: INFO: SSH "cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log" on bootstrap-e2e-minion-group-4sww(34.127.116.58:22) Jan 30 08:25:46.236: INFO: ssh prow@34.127.116.58:22: command: cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log Jan 30 08:25:46.236: INFO: ssh prow@34.127.116.58:22: stdout: "" Jan 30 08:25:46.236: INFO: ssh prow@34.127.116.58:22: stderr: "cat: /tmp/drop-outbound.log: No such file or directory\n" Jan 30 08:25:46.236: INFO: ssh prow@34.127.116.58:22: exit code: 1 Jan 30 08:25:46.236: INFO: Error while issuing ssh command: failed running "cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log": <nil> (exit code 1, stderr cat: /tmp/drop-outbound.log: No such file or directory ) Jan 30 08:25:46.236: INFO: Getting external IP address for bootstrap-e2e-minion-group-70zb Jan 30 08:25:46.236: INFO: SSH "cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log" on bootstrap-e2e-minion-group-70zb(34.105.73.232:22) Jan 30 08:25:46.759: INFO: ssh prow@34.105.73.232:22: command: cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log Jan 30 08:25:46.759: INFO: ssh prow@34.105.73.232: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 08:20:56 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 08:25:46.759: INFO: ssh prow@34.105.73.232:22: stderr: "" Jan 30 08:25:46.759: INFO: ssh prow@34.105.73.232:22: exit code: 0 Jan 30 08:25:46.759: INFO: Getting external IP address for bootstrap-e2e-minion-group-lzpl Jan 30 08:25:46.759: INFO: SSH "cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log" on bootstrap-e2e-minion-group-lzpl(104.198.98.143:22) Jan 30 08:25:47.274: INFO: ssh prow@104.198.98.143:22: command: cat /tmp/drop-outbound.log && rm /tmp/drop-outbound.log Jan 30 08:25:47.274: INFO: ssh prow@104.198.98.143: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 08:20:56 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 08:25:47.274: INFO: ssh prow@104.198.98.143:22: stderr: "" Jan 30 08:25:47.274: INFO: ssh prow@104.198.98.143: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 08:25:47.275 < 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 08:25:47.275 (5m2.019s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/30/23 08:25:47.275 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/30/23 08:25:47.275 Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-f4jgz to bootstrap-e2e-minion-group-70zb Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 928.320713ms (928.329043ms including waiting) Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-6846b5b5f-f4jgz Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Unhealthy: Readiness probe failed: Get "http://10.64.2.7:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Unhealthy: Liveness probe failed: Get "http://10.64.2.7:8080/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {kubelet bootstrap-e2e-minion-group-70zb} Killing: Container coredns failed liveness probe, will be restarted Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-f4jgz: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-6846b5b5f-f4jgz Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-fr6bb to bootstrap-e2e-minion-group-4sww Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 2.34366857s (2.343676986s including waiting) Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.6:8181/ready": dial tcp 10.64.1.6:8181: connect: connection refused Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-fr6bb_kube-system(daf9ffd3-e380-4f4d-ad87-79e4ab4a4657) Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.13:8181/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container coredns Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.17:8181/ready": dial tcp 10.64.1.17:8181: connect: connection refused Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-fr6bb_kube-system(daf9ffd3-e380-4f4d-ad87-79e4ab4a4657) Jan 30 08:25:47.329: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.22:8181/ready": dial tcp 10.64.1.22:8181: connect: connection refused Jan 30 08:25:47.330: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:25:47.330: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} FailedMount: MountVolume.SetUp failed for volume "config-volume" : object "kube-system"/"coredns" not registered Jan 30 08:25:47.330: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 30 08:25:47.330: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container coredns Jan 30 08:25:47.330: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container coredns Jan 30 08:25:47.330: INFO: event for coredns-6846b5b5f-fr6bb: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-6846b5b5f-fr6bb Jan 30 08:25:47.330: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container coredns Jan 30 08:25:47.330: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.27:8181/ready": dial tcp 10.64.1.27:8181: connect: connection refused Jan 30 08:25:47.330: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-fr6bb_kube-system(daf9ffd3-e380-4f4d-ad87-79e4ab4a4657) Jan 30 08:25:47.330: INFO: event for coredns-6846b5b5f-fr6bb: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Readiness probe failed: Get "http://10.64.1.28:8181/ready": dial tcp 10.64.1.28:8181: connect: connection refused Jan 30 08:25:47.330: 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 08:25:47.330: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-fr6bb Jan 30 08:25:47.330: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-f4jgz Jan 30 08:25:47.330: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 1 Jan 30 08:25:47.330: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 2 from 1 Jan 30 08:25:47.330: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container etcd-container Jan 30 08:25:47.330: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container etcd-container Jan 30 08:25:47.330: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container etcd-container Jan 30 08:25:47.330: 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 08:25:47.330: 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 08:25:47.330: 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 08:25:47.330: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_eac7a became leader Jan 30 08:25:47.330: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_b6cb3 became leader Jan 30 08:25:47.330: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_a9a9e became leader Jan 30 08:25:47.330: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_ab557 became leader Jan 30 08:25:47.330: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_46919 became leader Jan 30 08:25:47.330: INFO: event for konnectivity-agent-jzpmd: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-jzpmd to bootstrap-e2e-minion-group-70zb Jan 30 08:25:47.330: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 08:25:47.330: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 596.974861ms (596.984979ms including waiting) Jan 30 08:25:47.330: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Killing: Stopping container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:25:47.330: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for konnectivity-agent-jzpmd: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-pwpgn to bootstrap-e2e-minion-group-lzpl Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 616.72361ms (616.743908ms including waiting) Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-pwpgn_kube-system(73d72a79-ab94-4213-a4e3-cc1b78ebf5e1) Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-pwpgn_kube-system(73d72a79-ab94-4213-a4e3-cc1b78ebf5e1) Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "http://10.64.3.11:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Unhealthy: Liveness probe failed: Get "http://10.64.3.14:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:25:47.330: INFO: event for konnectivity-agent-pwpgn: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Container konnectivity-agent failed liveness probe, will be restarted Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-zfhmc to bootstrap-e2e-minion-group-4sww Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 1.276962957s (1.276975297s including waiting) Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container konnectivity-agent Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-zfhmc_kube-system(8e0c73bc-79ed-465e-9e1b-3d9d3b215fbd) Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} Unhealthy: Liveness probe failed: Get "http://10.64.1.20:8093/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:25:47.330: INFO: event for konnectivity-agent-zfhmc: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-zfhmc Jan 30 08:25:47.330: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-jzpmd Jan 30 08:25:47.330: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-pwpgn Jan 30 08:25:47.330: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container konnectivity-server-container Jan 30 08:25:47.330: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container konnectivity-server-container Jan 30 08:25:47.330: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container konnectivity-server-container Jan 30 08:25:47.330: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-server:v0.1.1" already present on machine Jan 30 08:25:47.330: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-addon-manager Jan 30 08:25:47.330: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-addon-manager Jan 30 08:25:47.330: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-addon-manager Jan 30 08:25:47.330: 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 08:25:47.330: 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 08:25:47.330: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container kube-addon-manager in pod kube-addon-manager-bootstrap-e2e-master_kube-system(ecad253bdb3dfebf3d39882505699622) Jan 30 08:25:47.330: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 30 08:25:47.330: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-apiserver Jan 30 08:25:47.330: 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 08:25:47.330: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe failed: Get "https://127.0.0.1:443/livez?exclude=etcd&exclude=kms-provider-0&exclude=kms-provider-1": dial tcp 127.0.0.1:443: connect: connection refused Jan 30 08:25:47.330: 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 08:25:47.330: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-controller-manager Jan 30 08:25:47.330: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-controller-manager Jan 30 08:25:47.330: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-controller-manager Jan 30 08:25:47.330: 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 08:25:47.330: 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 08:25:47.330: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_eb52f13c-d35a-4660-ac4b-5487ea4674b4 became leader Jan 30 08:25:47.330: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_d7cd6907-4822-4c1e-ab3e-96a2a537c9c8 became leader Jan 30 08:25:47.330: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_f911ee3b-2fcd-4329-9631-7240c46847a2 became leader Jan 30 08:25:47.330: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_e9a6a3b8-afc2-40c9-88b5-1bffbed3472d became leader Jan 30 08:25:47.330: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_67d4675f-aab3-4535-8235-dca5abe9126b became leader Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-dns-autoscaler-5f6455f985-9xvq8 to bootstrap-e2e-minion-group-4sww Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" in 1.290542065s (1.290556435s including waiting) Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container autoscaler Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container autoscaler Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" already present on machine Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container autoscaler Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container autoscaler Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container autoscaler Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container autoscaler in pod kube-dns-autoscaler-5f6455f985-9xvq8_kube-system(feddd70a-8a25-432a-bdec-943c9ac3981f) Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" already present on machine Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container autoscaler Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container autoscaler Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/kube-dns-autoscaler-5f6455f985-9xvq8 Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container autoscaler Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985-9xvq8: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container autoscaler in pod kube-dns-autoscaler-5f6455f985-9xvq8_kube-system(feddd70a-8a25-432a-bdec-943c9ac3981f) Jan 30 08:25:47.330: 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 08:25:47.330: INFO: event for kube-dns-autoscaler-5f6455f985: {replicaset-controller } SuccessfulCreate: Created pod: kube-dns-autoscaler-5f6455f985-9xvq8 Jan 30 08:25:47.330: INFO: event for kube-dns-autoscaler: {deployment-controller } ScalingReplicaSet: Scaled up replica set kube-dns-autoscaler-5f6455f985 to 1 Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-4sww_kube-system(2a66a2cc36d62b3aeb028309b150fd28) Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} Killing: Stopping container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-4sww: {kubelet bootstrap-e2e-minion-group-4sww} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-4sww_kube-system(2a66a2cc36d62b3aeb028309b150fd28) Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Killing: Stopping container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-70zb_kube-system(a4babc2e16d27b32a55d77ad17615418) Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-70zb: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-lzpl_kube-system(bb8aee5a88c070b1c20014b5786bd63b) Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.88_7b243cef1a81f4" already present on machine Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} Killing: Stopping container kube-proxy Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {kubelet bootstrap-e2e-minion-group-lzpl} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-lzpl_kube-system(bb8aee5a88c070b1c20014b5786bd63b) Jan 30 08:25:47.330: INFO: event for kube-proxy-bootstrap-e2e-minion-group-lzpl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: 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 08:25:47.330: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-scheduler Jan 30 08:25:47.330: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-scheduler Jan 30 08:25:47.330: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-scheduler Jan 30 08:25:47.330: 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 08:25:47.330: 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 08:25:47.330: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_2d942942-28fe-4c7b-bf8d-c8add0a5e06b became leader Jan 30 08:25:47.330: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_5f846ea0-d739-4bd9-b437-b9a92cd83f2e became leader Jan 30 08:25:47.330: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_a0fb5dc7-f249-47a8-8d3e-33ccabb95f6f became leader Jan 30 08:25:47.330: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_7415f67b-bfba-4fdd-9056-39d4c5856eb5 became leader Jan 30 08:25:47.330: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_d5208f23-af49-4f12-93ef-16ebe1f537c7 became leader Jan 30 08:25:47.330: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_2bdd6aa6-17b4-471f-8fda-40a08b27f8b4 became leader Jan 30 08:25:47.330: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_5271494a-3330-45b8-8161-3e097c9f15c7 became leader Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {default-scheduler } Scheduled: Successfully assigned kube-system/l7-default-backend-8549d69d99-sfzcc to bootstrap-e2e-minion-group-4sww Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" in 689.339496ms (689.364815ms including waiting) Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container default-http-backend Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container default-http-backend Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container default-http-backend Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container default-http-backend Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} NetworkNotReady: network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container default-http-backend Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/l7-default-backend-8549d69d99-sfzcc Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99-sfzcc: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container default-http-backend Jan 30 08:25:47.330: INFO: event for l7-default-backend-8549d69d99: {replicaset-controller } SuccessfulCreate: Created pod: l7-default-backend-8549d69d99-sfzcc Jan 30 08:25:47.330: INFO: event for l7-default-backend: {deployment-controller } ScalingReplicaSet: Scaled up replica set l7-default-backend-8549d69d99 to 1 Jan 30 08:25:47.330: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container l7-lb-controller Jan 30 08:25:47.330: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container l7-lb-controller Jan 30 08:25:47.330: 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 08:25:47.330: 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 08:25:47.330: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container l7-lb-controller Jan 30 08:25:47.330: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2n86l: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-2n86l to bootstrap-e2e-master Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 752.740258ms (752.748002ms including waiting) Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Created: Created container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Started: Started container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.074248729s (2.074257418s including waiting) Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Created: Created container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2n86l: {kubelet bootstrap-e2e-master} Started: Started container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-2x5bf to bootstrap-e2e-minion-group-4sww Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 749.462052ms (749.507403ms including waiting) Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.527604672s (1.527613918s including waiting) Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Created: Created container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-2x5bf: {kubelet bootstrap-e2e-minion-group-4sww} Started: Started container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-hs8dc to bootstrap-e2e-minion-group-lzpl Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 764.181591ms (764.191233ms including waiting) Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.918416325s (1.918454047s including waiting) Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Created: Created container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {kubelet bootstrap-e2e-minion-group-lzpl} Started: Started container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-hs8dc: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-ntpwl to bootstrap-e2e-minion-group-70zb Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 710.312601ms (710.332713ms including waiting) Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.813089082s (1.813114209s including waiting) Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container metadata-proxy Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Created: Created container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {kubelet bootstrap-e2e-minion-group-70zb} Started: Started container prometheus-to-sd-exporter Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1-ntpwl: {node-controller } NodeNotReady: Node is not ready Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-2n86l Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-2x5bf Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-ntpwl Jan 30 08:25:47.330: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-hs8dc Jan 30 08:25:47.330: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 30 08:25:47.330: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) were unschedulable. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 30 08:25:47.330: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-6764bf875c-mz4ml to bootstrap-e2e-minion-group-4sww Jan 30 08:25:47.330: INFO: event for metrics-server-v0.5.2-6764bf875c-mz4ml: {kubelet bootstrap-e2e-minion-group-4sww} Pulling: Pulling image "registry.k8s.io/