ci-cri-containerd-e2e-cos-gce-reboot #1619498145580847104
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/29/23 01:26:53.798from ginkgo_report.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/29/23 01:21:51.417 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/29/23 01:21:51.417 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/29/23 01:21:51.417 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/29/23 01:21:51.417 Jan 29 01:21:51.417: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/29/23 01:21:51.422 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/29/23 01:21:51.553 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/29/23 01:21:51.635 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/29/23 01:21:51.717 (301ms) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/29/23 01:21:51.717 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/29/23 01:21:51.718 (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/29/23 01:21:51.718 Jan 29 01:21:51.831: INFO: Getting bootstrap-e2e-minion-group-rv7m Jan 29 01:21:51.831: INFO: Getting bootstrap-e2e-minion-group-nh1n Jan 29 01:21:51.831: INFO: Getting bootstrap-e2e-minion-group-g5dw Jan 29 01:21:51.907: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-nh1n condition Ready to be true Jan 29 01:21:51.907: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-rv7m condition Ready to be true Jan 29 01:21:51.907: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-g5dw condition Ready to be true Jan 29 01:21:51.952: INFO: Node bootstrap-e2e-minion-group-rv7m has 4 assigned pods with no liveness probes: [kube-dns-autoscaler-5f6455f985-q8wlx kube-proxy-bootstrap-e2e-minion-group-rv7m metadata-proxy-v0.1-ghdmf volume-snapshot-controller-0] Jan 29 01:21:51.952: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-q8wlx kube-proxy-bootstrap-e2e-minion-group-rv7m metadata-proxy-v0.1-ghdmf volume-snapshot-controller-0] Jan 29 01:21:51.952: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.952: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-rv7m" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-q8wlx" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.952: INFO: Node bootstrap-e2e-minion-group-g5dw has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-g5dw metadata-proxy-v0.1-dvtn5] Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-g5dw metadata-proxy-v0.1-dvtn5] Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-dvtn5" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-ghdmf" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-g5dw" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.953: INFO: Node bootstrap-e2e-minion-group-nh1n has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-nh1n metadata-proxy-v0.1-tdckz] Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-nh1n metadata-proxy-v0.1-tdckz] Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-tdckz" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-nh1n" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:52.001: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 48.649333ms Jan 29 01:21:52.001: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:52.001: INFO: Pod "metadata-proxy-v0.1-dvtn5": Phase="Running", Reason="", readiness=true. Elapsed: 48.519322ms Jan 29 01:21:52.001: INFO: Pod "metadata-proxy-v0.1-dvtn5" satisfied condition "running and ready, or succeeded" Jan 29 01:21:52.002: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 49.106253ms Jan 29 01:21:52.002: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:52.003: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-nh1n": Phase="Running", Reason="", readiness=true. Elapsed: 50.098793ms Jan 29 01:21:52.003: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-nh1n" satisfied condition "running and ready, or succeeded" Jan 29 01:21:52.003: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 50.359343ms Jan 29 01:21:52.003: INFO: Pod "metadata-proxy-v0.1-tdckz": Phase="Running", Reason="", readiness=true. Elapsed: 50.312087ms Jan 29 01:21:52.003: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:21:52.003: INFO: Pod "metadata-proxy-v0.1-tdckz" satisfied condition "running and ready, or succeeded" Jan 29 01:21:52.003: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-nh1n metadata-proxy-v0.1-tdckz] Jan 29 01:21:52.003: INFO: Getting external IP address for bootstrap-e2e-minion-group-nh1n Jan 29 01:21:52.003: INFO: Pod "metadata-proxy-v0.1-ghdmf": Phase="Running", Reason="", readiness=true. Elapsed: 50.466836ms Jan 29 01:21:52.003: INFO: Pod "metadata-proxy-v0.1-ghdmf" satisfied condition "running and ready, or succeeded" Jan 29 01:21:52.003: 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-nh1n(35.230.114.56:22) Jan 29 01:21:52.003: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 50.806994ms Jan 29 01:21:52.003: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:21:52.558: INFO: ssh prow@35.230.114.56: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 29 01:21:52.558: INFO: ssh prow@35.230.114.56:22: stdout: "" Jan 29 01:21:52.558: INFO: ssh prow@35.230.114.56:22: stderr: "" Jan 29 01:21:52.558: INFO: ssh prow@35.230.114.56:22: exit code: 0 Jan 29 01:21:52.558: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-nh1n condition Ready to be false Jan 29 01:21:52.600: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:21:54.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2.092899446s Jan 29 01:21:54.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2.09272055s Jan 29 01:21:54.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:54.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:54.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 2.095913912s Jan 29 01:21:54.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:21:54.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 2.096044547s Jan 29 01:21:54.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:21:54.644: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:21:56.049: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4.096204615s Jan 29 01:21:56.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:56.050: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4.097300065s Jan 29 01:21:56.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:56.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 4.097130438s Jan 29 01:21:56.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:21:56.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 4.097527162s Jan 29 01:21:56.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:21:56.688: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:21:58.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 6.093568679s Jan 29 01:21:58.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:58.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 6.093915675s Jan 29 01:21:58.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:58.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 6.09548999s Jan 29 01:21:58.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:21:58.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 6.095908305s Jan 29 01:21:58.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:21:58.731: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:00.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 8.092341542s Jan 29 01:22:00.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:00.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 8.093222342s Jan 29 01:22:00.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:00.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 8.095547499s Jan 29 01:22:00.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:00.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 8.097795945s Jan 29 01:22:00.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:00.774: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:02.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 10.091060308s Jan 29 01:22:02.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:02.049: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 10.095964676s Jan 29 01:22:02.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:02.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 10.096409585s Jan 29 01:22:02.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:02.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 10.09625703s Jan 29 01:22:02.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:02.818: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:04.048: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 12.095552722s Jan 29 01:22:04.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:04.048: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 12.095499679s Jan 29 01:22:04.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:04.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 12.096452379s Jan 29 01:22:04.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:04.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 12.096189813s Jan 29 01:22:04.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:04.862: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:06.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 14.093718924s Jan 29 01:22:06.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:06.048: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 14.095078905s Jan 29 01:22:06.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:06.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 14.096680195s Jan 29 01:22:06.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:06.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 14.097945937s Jan 29 01:22:06.051: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:06.908: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:08.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 16.092967776s Jan 29 01:22:08.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:08.048: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 16.09521184s Jan 29 01:22:08.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:08.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 16.09661099s Jan 29 01:22:08.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:08.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 16.096586006s Jan 29 01:22:08.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:08.951: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:10.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 18.093270533s Jan 29 01:22:10.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:10.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 18.094134834s Jan 29 01:22:10.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:10.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 18.096088958s Jan 29 01:22:10.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:10.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 18.096627335s Jan 29 01:22:10.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:10.994: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:12.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 20.093295486s Jan 29 01:22:12.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:12.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 20.09438779s Jan 29 01:22:12.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:12.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 20.096973141s Jan 29 01:22:12.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 20.096671404s Jan 29 01:22:12.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:12.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:13.077: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:14.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 22.0911756s Jan 29 01:22:14.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:14.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 22.094885503s Jan 29 01:22:14.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:14.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 22.095858368s Jan 29 01:22:14.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:14.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=true. Elapsed: 22.096460175s Jan 29 01:22:14.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw" satisfied condition "running and ready, or succeeded" Jan 29 01:22:14.049: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-g5dw metadata-proxy-v0.1-dvtn5] Jan 29 01:22:14.049: INFO: Getting external IP address for bootstrap-e2e-minion-group-g5dw Jan 29 01:22:14.049: 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-g5dw(34.82.165.19:22) Jan 29 01:22:14.595: INFO: ssh prow@34.82.165.19: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 29 01:22:14.595: INFO: ssh prow@34.82.165.19:22: stdout: "" Jan 29 01:22:14.595: INFO: ssh prow@34.82.165.19:22: stderr: "" Jan 29 01:22:14.595: INFO: ssh prow@34.82.165.19:22: exit code: 0 Jan 29 01:22:14.595: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-g5dw condition Ready to be false Jan 29 01:22:14.638: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:15.122: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:16.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 24.093585743s Jan 29 01:22:16.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:16.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 24.093951063s Jan 29 01:22:16.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:16.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 24.095776779s Jan 29 01:22:16.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:16.680: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:17.167: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:18.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 26.092786195s Jan 29 01:22:18.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:18.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 26.093019938s Jan 29 01:22:18.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:18.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 26.095910866s Jan 29 01:22:18.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:18.722: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:19.210: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:20.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 28.091027561s Jan 29 01:22:20.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:20.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 28.092247325s Jan 29 01:22:20.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:20.047: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 28.094437284s Jan 29 01:22:20.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:20.766: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:21.270: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:22.071: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 30.118870968s Jan 29 01:22:22.071: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:22.072: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 30.119564628s Jan 29 01:22:22.072: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:22.076: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 30.1236619s Jan 29 01:22:22.076: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:22.810: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:23.314: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:24.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 32.092775455s Jan 29 01:22:24.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:24.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 32.093885977s Jan 29 01:22:24.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:24.047: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 32.094341935s Jan 29 01:22:24.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:24.853: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:25.357: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:26.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 34.091938473s Jan 29 01:22:26.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:26.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 34.093950721s Jan 29 01:22:26.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:26.047: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 34.09446359s Jan 29 01:22:26.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:26.897: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:27.401: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:28.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 36.091856227s Jan 29 01:22:28.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:28.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 36.093308638s Jan 29 01:22:28.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:28.047: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 36.094930308s Jan 29 01:22:28.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:28.941: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:29.445: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:30.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 38.093512909s Jan 29 01:22:30.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:30.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 38.094114137s Jan 29 01:22:30.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:30.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 38.096722456s Jan 29 01:22:30.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:30.984: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:31.488: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:32.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 40.093894966s Jan 29 01:22:32.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:32.049: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 40.096039493s Jan 29 01:22:32.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:32.054: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 40.10116259s Jan 29 01:22:32.054: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:33.028: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:33.532: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:34.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 42.090372921s Jan 29 01:22:34.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:34.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 42.091252734s Jan 29 01:22:34.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:34.046: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 42.093415862s Jan 29 01:22:34.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:35.074: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:35.576: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:36.047: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 44.094722119s Jan 29 01:22:36.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:36.048: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 44.094946907s Jan 29 01:22:36.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:36.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 44.095164092s Jan 29 01:22:36.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:37.120: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:37.620: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:38.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 46.092319849s Jan 29 01:22:38.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:38.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 46.093758437s Jan 29 01:22:38.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:38.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 46.095584198s Jan 29 01:22:38.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:39.163: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:39.664: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:40.048: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 48.095439969s Jan 29 01:22:40.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:40.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 48.097052911s Jan 29 01:22:40.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:40.050: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 48.09745494s Jan 29 01:22:40.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:41.207: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:41.707: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:42.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 50.092530349s Jan 29 01:22:42.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:42.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 50.093216028s Jan 29 01:22:42.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:42.047: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 50.094898477s Jan 29 01:22:42.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:43.250: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:43.750: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:44.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 52.091844454s Jan 29 01:22:44.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:44.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 52.093800427s Jan 29 01:22:44.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:44.047: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 52.094808856s Jan 29 01:22:44.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:45.296: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:45.793: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:46.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 54.092181993s Jan 29 01:22:46.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:46.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 54.093833627s Jan 29 01:22:46.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:46.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 54.095079497s Jan 29 01:22:46.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:47.339: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:47.837: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:48.047: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 56.094280096s Jan 29 01:22:48.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:48.048: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 56.094902493s Jan 29 01:22:48.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:48.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 56.09507242s Jan 29 01:22:48.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:49.392: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:49.882: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:50.047: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 58.094144691s Jan 29 01:22:50.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:50.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 58.094872715s Jan 29 01:22:50.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:50.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 58.097247345s Jan 29 01:22:50.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:51.436: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:51.925: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:52.050: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m0.096894534s Jan 29 01:22:52.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:52.050: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m0.097920557s Jan 29 01:22:52.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:52.051: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=true. Elapsed: 1m0.098895094s Jan 29 01:22:52.051: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m" satisfied condition "running and ready, or succeeded" Jan 29 01:22:53.480: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:53.970: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:54.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m2.092656899s Jan 29 01:22:54.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:54.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m2.09288788s Jan 29 01:22:54.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:55.527: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:56.015: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:56.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.093790458s Jan 29 01:22:56.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:56.048: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.095211657s Jan 29 01:22:56.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:57.570: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:58.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.091022108s Jan 29 01:22:58.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:58.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.092259184s Jan 29 01:22:58.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:58.066: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:59.614: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:00.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m8.093827214s Jan 29 01:23:00.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:00.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m8.093749352s Jan 29 01:23:00.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:00.110: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:01.658: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:02.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.093077791s Jan 29 01:23:02.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:02.047: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.094136811s Jan 29 01:23:02.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:02.154: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:03.702: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:04.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.090989488s Jan 29 01:23:04.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:04.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.091957204s Jan 29 01:23:04.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:04.197: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:05.746: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:06.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m14.092327795s Jan 29 01:23:06.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:06.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m14.093855625s Jan 29 01:23:06.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:06.240: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:07.789: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:08.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.092030368s Jan 29 01:23:08.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:08.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.093816746s Jan 29 01:23:08.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:08.282: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:09.832: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:10.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.092482785s Jan 29 01:23:10.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.092304736s Jan 29 01:23:10.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:10.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:10.326: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:11.876: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:12.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.092712676s Jan 29 01:23:12.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:12.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.094070795s Jan 29 01:23:12.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:12.370: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:13.921: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:14.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.091419121s Jan 29 01:23:14.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.091632372s Jan 29 01:23:14.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:14.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:14.414: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:15.964: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:16.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m24.091804453s Jan 29 01:23:16.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:16.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m24.09323422s Jan 29 01:23:16.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:16.458: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:18.006: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:18.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m26.092188822s Jan 29 01:23:18.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:18.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m26.092539722s Jan 29 01:23:18.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:18.501: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:20.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m28.093114811s Jan 29 01:23:20.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:20.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m28.093390815s Jan 29 01:23:20.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:20.050: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:20.544: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:22.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m30.091326575s Jan 29 01:23:22.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:22.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m30.092264708s Jan 29 01:23:22.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:22.092: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:22.587: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:24.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m32.092152644s Jan 29 01:23:24.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m32.091990912s Jan 29 01:23:24.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:24.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:24.135: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:24.630: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:26.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m34.090824667s Jan 29 01:23:26.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:26.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m34.092363931s Jan 29 01:23:26.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:26.179: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:26.673: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:28.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m36.092658792s Jan 29 01:23:28.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:28.047: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m36.094144401s Jan 29 01:23:28.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:28.222: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:28.717: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:30.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m38.093096034s Jan 29 01:23:30.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:30.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m38.093042617s Jan 29 01:23:30.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:30.266: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:30.759: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:32.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m40.091740674s Jan 29 01:23:32.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:32.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m40.093273504s Jan 29 01:23:32.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:32.309: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:32.821: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:34.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m42.090773656s Jan 29 01:23:34.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:34.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m42.091724081s Jan 29 01:23:34.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:34.353: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:34.865: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:36.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m44.092153106s Jan 29 01:23:36.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:36.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m44.092180231s Jan 29 01:23:36.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:36.395: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:36.909: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:38.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m46.090653966s Jan 29 01:23:38.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:38.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m46.091952511s Jan 29 01:23:38.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:38.439: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:38.951: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:40.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m48.092430555s Jan 29 01:23:40.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:40.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m48.092353568s Jan 29 01:23:40.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:40.482: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:40.995: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:42.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m50.093330113s Jan 29 01:23:42.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:42.047: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m50.094821094s Jan 29 01:23:42.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:42.528: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:43.038: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:44.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m52.09074008s Jan 29 01:23:44.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:44.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m52.092327725s Jan 29 01:23:44.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:44.572: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:45.080: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:46.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m54.090378059s Jan 29 01:23:46.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:46.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m54.091608638s Jan 29 01:23:46.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:46.615: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:47.123: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:48.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m56.092396054s Jan 29 01:23:48.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:48.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m56.093788342s Jan 29 01:23:48.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:48.658: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:49.167: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:50.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m58.092523963s Jan 29 01:23:50.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:50.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m58.092496002s Jan 29 01:23:50.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:50.702: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:51.210: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:52.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m0.09254421s Jan 29 01:23:52.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m0.092382305s Jan 29 01:23:52.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:52.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:52.745: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:53.211: INFO: Node bootstrap-e2e-minion-group-nh1n didn't reach desired Ready condition status (false) within 2m0s Jan 29 01:23:54.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m2.090647034s Jan 29 01:23:54.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:54.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m2.092359833s Jan 29 01:23:54.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:54.788: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:56.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m4.091426787s Jan 29 01:23:56.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:56.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m4.092147719s Jan 29 01:23:56.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:56.831: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:58.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m6.090534011s Jan 29 01:23:58.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:58.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m6.091758805s Jan 29 01:23:58.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:58.874: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:00.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m8.092108586s Jan 29 01:24:00.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m8.091936546s Jan 29 01:24:00.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:00.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:00.916: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:02.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m10.090647858s Jan 29 01:24:02.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:02.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m10.091933937s Jan 29 01:24:02.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:02.959: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:04.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m12.090751367s Jan 29 01:24:04.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:04.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m12.092428669s Jan 29 01:24:04.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:05.006: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:06.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m14.092400319s Jan 29 01:24:06.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m14.092234645s Jan 29 01:24:06.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:06.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:07.049: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:08.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m16.091884417s Jan 29 01:24:08.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:08.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m16.092895991s Jan 29 01:24:08.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:09.092: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:10.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m18.091124482s Jan 29 01:24:10.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:10.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m18.092050141s Jan 29 01:24:10.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:11.134: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:12.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m20.091107724s Jan 29 01:24:12.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:12.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m20.092199097s Jan 29 01:24:12.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:13.177: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:14.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m22.090373784s Jan 29 01:24:14.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:14.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m22.091579941s Jan 29 01:24:14.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:15.178: INFO: Node bootstrap-e2e-minion-group-g5dw didn't reach desired Ready condition status (false) within 2m0s Jan 29 01:24:16.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m24.090358141s Jan 29 01:24:16.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:16.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m24.091714039s Jan 29 01:24:16.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:18.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m26.090955556s Jan 29 01:24:18.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:18.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m26.091923217s Jan 29 01:24:18.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:20.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m28.09047215s Jan 29 01:24:20.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:20.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m28.091746733s Jan 29 01:24:20.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:22.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m30.092787501s Jan 29 01:24:22.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:22.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m30.092713228s Jan 29 01:24:22.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:24.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m32.091827124s Jan 29 01:24:24.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:24.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m32.09215354s Jan 29 01:24:24.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:26.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m34.091118549s Jan 29 01:24:26.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:26.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m34.092742265s Jan 29 01:24:26.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:28.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m36.092943831s Jan 29 01:24:28.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m36.093133422s Jan 29 01:24:28.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:28.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:30.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m38.092525253s Jan 29 01:24:30.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:30.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m38.092798063s Jan 29 01:24:30.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:32.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m40.09072277s Jan 29 01:24:32.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:32.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m40.092154018s Jan 29 01:24:32.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:34.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m42.090637771s Jan 29 01:24:34.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:34.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m42.092001698s Jan 29 01:24:34.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:36.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m44.091892081s Jan 29 01:24:36.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:36.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m44.093518891s Jan 29 01:24:36.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:38.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m46.092060112s Jan 29 01:24:38.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:38.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m46.091998521s Jan 29 01:24:38.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:40.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m48.092174318s Jan 29 01:24:40.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:40.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m48.092235382s Jan 29 01:24:40.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:42.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m50.092092326s Jan 29 01:24:42.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:42.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m50.093485782s Jan 29 01:24:42.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:44.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m52.090652972s Jan 29 01:24:44.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:44.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m52.092386032s Jan 29 01:24:44.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:46.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m54.092281466s Jan 29 01:24:46.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:46.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m54.093846164s Jan 29 01:24:46.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:48.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m56.093119846s Jan 29 01:24:48.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:48.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m56.093093182s Jan 29 01:24:48.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:50.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m58.093165474s Jan 29 01:24:50.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:50.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m58.093110529s Jan 29 01:24:50.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:52.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m0.091082852s Jan 29 01:24:52.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:52.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m0.092127874s Jan 29 01:24:52.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:54.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m2.091747916s Jan 29 01:24:54.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m2.091932304s Jan 29 01:24:54.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:54.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:56.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m4.091937321s Jan 29 01:24:56.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 3m4.092130233s Jan 29 01:24:56.045: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 29 01:24:56.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:58.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m6.091620214s Jan 29 01:24:58.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:00.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m8.093010459s Jan 29 01:25:00.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:02.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m10.092231598s Jan 29 01:25:02.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:04.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m12.090958524s Jan 29 01:25:04.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:06.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m14.091065144s Jan 29 01:25:06.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:08.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m16.090935409s Jan 29 01:25:08.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:10.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m18.093033794s Jan 29 01:25:10.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:12.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m20.091221773s Jan 29 01:25:12.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:14.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m22.090960945s Jan 29 01:25:14.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:16.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m24.091373424s Jan 29 01:25:16.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:18.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m26.092120167s Jan 29 01:25:18.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:20.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m28.092444123s Jan 29 01:25:20.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:22.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m30.09201793s Jan 29 01:25:22.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:24.063: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m32.110395866s Jan 29 01:25:24.063: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:26.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m34.092061068s Jan 29 01:25:26.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:28.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m36.092489918s Jan 29 01:25:28.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:30.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m38.092400272s Jan 29 01:25:30.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:32.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m40.092403534s Jan 29 01:25:32.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:34.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m42.093091723s Jan 29 01:25:34.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:36.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m44.091555211s Jan 29 01:25:36.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:38.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m46.092629818s Jan 29 01:25:38.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:40.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m48.093265227s Jan 29 01:25:40.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:42.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m50.091541386s Jan 29 01:25:42.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:44.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m52.091326706s Jan 29 01:25:44.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:46.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m54.091070139s Jan 29 01:25:46.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:48.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m56.090895621s Jan 29 01:25:48.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:50.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m58.092773383s Jan 29 01:25:50.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:52.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m0.092296055s Jan 29 01:25:52.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:54.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m2.0923814s Jan 29 01:25:54.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:56.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m4.091588284s Jan 29 01:25:56.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:58.043: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m6.090755166s Jan 29 01:25:58.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:00.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m8.092394137s Jan 29 01:26:00.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:02.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m10.091344502s Jan 29 01:26:02.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:04.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m12.092227113s Jan 29 01:26:04.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:06.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m14.091397262s Jan 29 01:26:06.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:08.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m16.092989285s Jan 29 01:26:08.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:10.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m18.093395951s Jan 29 01:26:10.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:12.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m20.092132767s Jan 29 01:26:12.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:14.043: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m22.090893092s Jan 29 01:26:14.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:16.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m24.091076495s Jan 29 01:26:16.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:18.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m26.091016193s Jan 29 01:26:18.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:20.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m28.092549525s Jan 29 01:26:20.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:22.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m30.091301125s Jan 29 01:26:22.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:24.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m32.092340646s Jan 29 01:26:24.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:26.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m34.091088418s Jan 29 01:26:26.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:28.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m36.092691047s Jan 29 01:26:28.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:30.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m38.092836258s Jan 29 01:26:30.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:32.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m40.091377683s Jan 29 01:26:32.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:34.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m42.09133447s Jan 29 01:26:34.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:36.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m44.091842602s Jan 29 01:26:36.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:38.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m46.091304971s Jan 29 01:26:38.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:40.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m48.094368856s Jan 29 01:26:40.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:42.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m50.090963948s Jan 29 01:26:42.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:44.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m52.092578524s Jan 29 01:26:44.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:46.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m54.091513593s Jan 29 01:26:46.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:48.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m56.091214826s Jan 29 01:26:48.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:50.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m58.092336327s Jan 29 01:26:50.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +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.302s) test/e2e/cloud/gcp/reboot.go:136 In [It] (Node Runtime: 5m0.001s) test/e2e/cloud/gcp/reboot.go:136 Spec Goroutine goroutine 7990 [semacquire, 5 minutes] sync.runtime_Semacquire(0xc0049288a0?) /usr/local/go/src/runtime/sema.go:62 sync.(*WaitGroup).Wait(0x7fafbe533008?) /usr/local/go/src/sync/waitgroup.go:139 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot({0x7fafbe533008?, 0xc003b04300}, {0x8147108?, 0xc005a42000}, {0xc000290820, 0x182}, 0xc004bf4360) test/e2e/cloud/gcp/reboot.go:181 > k8s.io/kubernetes/test/e2e/cloud/gcp.glob..func8.7({0x7fafbe533008, 0xc003b04300}) test/e2e/cloud/gcp/reboot.go:141 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func2({0x8111ee8?, 0xc003b04300}) 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 7994 [chan receive, 2 minutes] k8s.io/kubernetes/test/e2e/framework/pod.checkPodsCondition({0x7fafbe533008?, 0xc003b04300}, {0x8147108?, 0xc005a42000}, {0x76d190b, 0xb}, {0xc005a52c00, 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({0x7fafbe533008, 0xc003b04300}, {0x8147108, 0xc005a42000}, {0x7ffd6cdb95f2, 0x3}, {0xc00004e720, 0x1f}, {0xc000290820, 0x182}) test/e2e/cloud/gcp/reboot.go:284 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x2) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 Jan 29 01:26:52.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 5m0.092058211s Jan 29 01:26:52.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:52.086: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 5m0.133612681s Jan 29 01:26:52.086: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:52.086: INFO: Pod kube-dns-autoscaler-5f6455f985-q8wlx failed to be running and ready, or succeeded. Jan 29 01:26:52.086: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: false. Pods: [kube-dns-autoscaler-5f6455f985-q8wlx kube-proxy-bootstrap-e2e-minion-group-rv7m metadata-proxy-v0.1-ghdmf volume-snapshot-controller-0] Jan 29 01:26:52.086: INFO: Status for not ready pod kube-system/kube-dns-autoscaler-5f6455f985-q8wlx: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 00:56:44 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 01:01: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-29 01:01: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-29 00:56:44 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP: PodIPs:[] StartTime:2023-01-29 00:56:44 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:autoscaler State:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-29 01:01:17 +0000 UTC,FinishedAt:2023-01-29 01:01:18 +0000 UTC,ContainerID:containerd://5a508a2954b644f87b9aad92582ca582be3b89489ba6973cabe09fc07d5230c2,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:2 Image:registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4 ImageID:registry.k8s.io/cpa/cluster-proportional-autoscaler@sha256:fd636b33485c7826fb20ef0688a83ee0910317dbb6c0c6f3ad14661c1db25def ContainerID:containerd://5a508a2954b644f87b9aad92582ca582be3b89489ba6973cabe09fc07d5230c2 Started:0xc004db5a7f}] QOSClass:Burstable EphemeralContainerStatuses:[]} Jan 29 01:26:52.131: INFO: Retrieving log for container kube-system/kube-dns-autoscaler-5f6455f985-q8wlx/autoscaler, err: an error on the server ("unknown") has prevented the request from succeeding (get pods kube-dns-autoscaler-5f6455f985-q8wlx): Jan 29 01:26:52.131: INFO: Retrieving log for the last terminated container kube-system/kube-dns-autoscaler-5f6455f985-q8wlx/autoscaler, err: an error on the server ("unknown") has prevented the request from succeeding (get pods kube-dns-autoscaler-5f6455f985-q8wlx): Jan 29 01:26:52.131: INFO: Status for not ready pod kube-system/kube-proxy-bootstrap-e2e-minion-group-rv7m: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 00:56:35 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 01:20:00 +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-29 01:20:00 +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-29 00:56:35 +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-29 00:56:35 +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-rv7m_kube-system(e73c874f32f53e94265ad545cac1eda7),} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-29 01:16:07 +0000 UTC,FinishedAt:2023-01-29 01:19:59 +0000 UTC,ContainerID:containerd://c8052c1724b207686da01aaecdf4f106e1b95696ca4702311649b5ee69e71cb0,}} Ready:false RestartCount:7 Image:registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2 ImageID:sha256:ef97fd17575d534d8bc2960bbf1e744379f3ac6e86b9b97974e086f1516b75e5 ContainerID:containerd://c8052c1724b207686da01aaecdf4f106e1b95696ca4702311649b5ee69e71cb0 Started:0xc004db5d0f}] QOSClass:Burstable EphemeralContainerStatuses:[]} Jan 29 01:26:52.176: INFO: Retrieving log for container kube-system/kube-proxy-bootstrap-e2e-minion-group-rv7m/kube-proxy, err: an error on the server ("unknown") has prevented the request from succeeding (get pods kube-proxy-bootstrap-e2e-minion-group-rv7m): Jan 29 01:26:52.176: INFO: Retrieving log for the last terminated container kube-system/kube-proxy-bootstrap-e2e-minion-group-rv7m/kube-proxy, err: an error on the server ("unknown") has prevented the request from succeeding (get pods kube-proxy-bootstrap-e2e-minion-group-rv7m): Jan 29 01:26:52.176: 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-29 00:56:44 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 01:19:47 +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-29 01:19:47 +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-29 00:56:44 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP:10.64.0.53 PodIPs:[{IP:10.64.0.53}] StartTime:2023-01-29 00:56:44 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:volume-snapshot-controller State:{Waiting:&ContainerStateWaiting{Reason:CrashLoopBackOff,Message:back-off 5m0s restarting failed container=volume-snapshot-controller pod=volume-snapshot-controller-0_kube-system(0c51547a-104f-4b7e-b495-4722734ddb26),} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-29 01:18:35 +0000 UTC,FinishedAt:2023-01-29 01:19:46 +0000 UTC,ContainerID:containerd://c4f3770023f8628ca6f3d27c03d3ebd8e674a9c6d3e4d4c9f2489422ef1612dd,}} Ready:false RestartCount:12 Image:registry.k8s.io/sig-storage/snapshot-controller:v6.1.0 ImageID:registry.k8s.io/sig-storage/snapshot-controller@sha256:823c75d0c45d1427f6d850070956d9ca657140a7bbf828381541d1d808475280 ContainerID:containerd://c4f3770023f8628ca6f3d27c03d3ebd8e674a9c6d3e4d4c9f2489422ef1612dd Started:0xc00592446f}] QOSClass:BestEffort EphemeralContainerStatuses:[]} Jan 29 01:26:52.221: INFO: Retrieving log for container kube-system/volume-snapshot-controller-0/volume-snapshot-controller, err: an error on the server ("unknown") has prevented the request from succeeding (get pods volume-snapshot-controller-0): Jan 29 01:26:52.221: INFO: Retrieving log for the last terminated container kube-system/volume-snapshot-controller-0/volume-snapshot-controller, err: an error on the server ("unknown") has prevented the request from succeeding (get pods volume-snapshot-controller-0): Jan 29 01:26:52.222: INFO: Node bootstrap-e2e-minion-group-g5dw failed reboot test. Jan 29 01:26:52.222: INFO: Node bootstrap-e2e-minion-group-nh1n failed reboot test. Jan 29 01:26:52.222: INFO: Node bootstrap-e2e-minion-group-rv7m failed reboot test. Jan 29 01:26:52.222: INFO: Executing termination hook on nodes Jan 29 01:26:52.222: INFO: Getting external IP address for bootstrap-e2e-minion-group-g5dw Jan 29 01:26:52.222: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-g5dw(34.82.165.19:22) Jan 29 01:26:52.747: INFO: ssh prow@34.82.165.19:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 29 01:26:52.747: INFO: ssh prow@34.82.165.19: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\nSun Jan 29 01:22:24 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 29 01:26:52.747: INFO: ssh prow@34.82.165.19:22: stderr: "" Jan 29 01:26:52.747: INFO: ssh prow@34.82.165.19:22: exit code: 0 Jan 29 01:26:52.747: INFO: Getting external IP address for bootstrap-e2e-minion-group-nh1n Jan 29 01:26:52.747: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-nh1n(35.230.114.56:22) Jan 29 01:26:53.275: INFO: ssh prow@35.230.114.56:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 29 01:26:53.275: INFO: ssh prow@35.230.114.56: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\nSun Jan 29 01:22:02 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 29 01:26:53.275: INFO: ssh prow@35.230.114.56:22: stderr: "" Jan 29 01:26:53.275: INFO: ssh prow@35.230.114.56:22: exit code: 0 Jan 29 01:26:53.275: INFO: Getting external IP address for bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.275: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-rv7m(34.105.95.109:22) Jan 29 01:26:53.798: INFO: ssh prow@34.105.95.109:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 29 01:26:53.798: INFO: ssh prow@34.105.95.109:22: stdout: "" Jan 29 01:26:53.798: INFO: ssh prow@34.105.95.109:22: stderr: "cat: /tmp/drop-inbound.log: No such file or directory\n" Jan 29 01:26:53.798: INFO: ssh prow@34.105.95.109:22: exit code: 1 Jan 29 01:26:53.798: 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 ) [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/29/23 01:26:53.798 < 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/29/23 01:26:53.798 (5m2.08s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/29/23 01:26:53.798 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/29/23 01:26:53.798 Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-5mldm to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 3.251905895s (3.251916602s including waiting) Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: Get "http://10.64.0.18:8181/ready": dial tcp 10.64.0.18:8181: connect: connection refused Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-5mldm_kube-system(460fb526-17a9-4c77-b280-98d8f5313ec6) Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-6846b5b5f-5mldm Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: Get "http://10.64.0.31:8181/ready": dial tcp 10.64.0.31:8181: connect: connection refused Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-5mldm_kube-system(460fb526-17a9-4c77-b280-98d8f5313ec6) Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-t7kt4 to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: Get "http://10.64.0.8:8181/ready": dial tcp 10.64.0.8:8181: connect: connection refused Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: Get "http://10.64.0.13:8181/ready": dial tcp 10.64.0.13:8181: connect: connection refused Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-t7kt4_kube-system(448ac129-a4a8-4121-bd3e-3b4d496219a2) Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: Get "http://10.64.0.22:8181/ready": dial tcp 10.64.0.22:8181: connect: connection refused Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-t7kt4_kube-system(448ac129-a4a8-4121-bd3e-3b4d496219a2) Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-6846b5b5f-t7kt4 Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-t7kt4_kube-system(448ac129-a4a8-4121-bd3e-3b4d496219a2) Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: Get "http://10.64.0.40:8181/ready": dial tcp 10.64.0.40:8181: connect: connection refused Jan 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-5mldm Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-t7kt4 Jan 29 01:26:53.852: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 1 Jan 29 01:26:53.852: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 2 from 1 Jan 29 01:26:53.852: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container etcd-container Jan 29 01:26:53.852: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container etcd-container Jan 29 01:26:53.852: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container etcd-container Jan 29 01:26:53.852: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: 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 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container etcd-container Jan 29 01:26:53.852: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container etcd-container Jan 29 01:26:53.852: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container etcd-container Jan 29 01:26:53.852: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe errored: rpc error: code = NotFound desc = failed to exec in container: failed to load task: no running task found: task c0e4964a6618e28860cb2feb2d888ee478fb57974e5227745331db243d5d6214 not found: not found Jan 29 01:26:53.852: 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 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container etcd-container in pod etcd-server-events-bootstrap-e2e-master_kube-system(9f090652556c0eb7722415ec1d3682eb) Jan 29 01:26:53.852: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_eff40 became leader Jan 29 01:26:53.852: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_dbd05 became leader Jan 29 01:26:53.852: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_df796 became leader Jan 29 01:26:53.852: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_d4e3d became leader Jan 29 01:26:53.852: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_688f3 became leader Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-hrwgh to bootstrap-e2e-minion-group-g5dw Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 607.221734ms (607.233291ms including waiting) Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Killing: Stopping container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-hrwgh_kube-system(e5ba1730-1fc4-4a47-9676-3232346230a4) Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-vt26n to bootstrap-e2e-minion-group-nh1n Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 640.482136ms (640.492658ms including waiting) Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-vt26n_kube-system(be5719b0-08d3-4d11-99c8-a4bb292d7a70) Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-xb8th to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 1.893509533s (1.893518578s including waiting) Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-xb8th_kube-system(22da266b-c1de-453b-9421-152e16982294) Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-xb8th_kube-system(22da266b-c1de-453b-9421-152e16982294) Jan 29 01:26:53.852: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-xb8th Jan 29 01:26:53.852: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-hrwgh Jan 29 01:26:53.852: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-vt26n Jan 29 01:26:53.852: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container konnectivity-server-container Jan 29 01:26:53.852: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container konnectivity-server-container Jan 29 01:26:53.852: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container konnectivity-server-container Jan 29 01:26:53.852: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container konnectivity-server-container in pod konnectivity-server-bootstrap-e2e-master_kube-system(122c336be1dd86824540422433813d8a) Jan 29 01:26:53.852: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-addon-manager Jan 29 01:26:53.852: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-addon-manager Jan 29 01:26:53.852: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-addon-manager Jan 29 01:26:53.852: 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 29 01:26:53.852: 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 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 29 01:26:53.852: 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.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-controller-manager Jan 29 01:26:53.852: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-controller-manager Jan 29 01:26:53.852: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-controller-manager Jan 29 01:26:53.852: 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 29 01:26:53.852: 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(a9901ac1fc908c01cd17c25062859343) Jan 29 01:26:53.852: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_e5910642-3cec-41bb-86e3-b6287f7e96f1 became leader Jan 29 01:26:53.852: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_eb1eb016-6b07-4a59-8227-08c665e9a103 became leader Jan 29 01:26:53.852: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_340e04c7-8f81-4372-9559-eb8718fb5d3b became leader Jan 29 01:26:53.852: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_ffaa1eb5-2e65-4943-8e74-0ec13fd46592 became leader Jan 29 01:26:53.852: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_6badf177-8bbb-4583-875c-aa41b992d5db became leader Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-dns-autoscaler-5f6455f985-q8wlx to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" in 3.257319276s (3.25733442s including waiting) Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container autoscaler Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container autoscaler Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" already present on machine Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container autoscaler Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container autoscaler Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container autoscaler Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container autoscaler in pod kube-dns-autoscaler-5f6455f985-q8wlx_kube-system(55334095-1e4d-4edc-8b27-9cc4df9ecbd3) Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/kube-dns-autoscaler-5f6455f985-q8wlx Jan 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985: {replicaset-controller } SuccessfulCreate: Created pod: kube-dns-autoscaler-5f6455f985-q8wlx Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler: {deployment-controller } ScalingReplicaSet: Scaled up replica set kube-dns-autoscaler-5f6455f985 to 1 Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-g5dw_kube-system(e39fd6ebeea66df97e7d4159e056ca89) Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-g5dw_kube-system(e39fd6ebeea66df97e7d4159e056ca89) Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} DNSConfigForming: Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 1.1.1.1 8.8.8.8 1.0.0.1 Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-g5dw_kube-system(e39fd6ebeea66df97e7d4159e056ca89) Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-nh1n_kube-system(104cab07fdbff6cd1903c2461a9ed07c) Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-nh1n_kube-system(104cab07fdbff6cd1903c2461a9ed07c) Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} DNSConfigForming: Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 1.1.1.1 8.8.8.8 1.0.0.1 Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-rv7m_kube-system(e73c874f32f53e94265ad545cac1eda7) Jan 29 01:26:53.852: 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.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-scheduler Jan 29 01:26:53.852: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-scheduler Jan 29 01:26:53.852: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-scheduler Jan 29 01:26:53.852: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: 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(b286b0d19b475d76fb3eba5bf7889986) Jan 29 01:26:53.852: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_387c967a-2bea-42c5-8d9d-29752e15ad1e became leader Jan 29 01:26:53.852: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_5629d3d6-315a-4014-9ea2-880de5dc36cb became leader Jan 29 01:26:53.852: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_9e80c6f9-7dfe-4bf1-b855-7b6e2cb9f58f became leader Jan 29 01:26:53.852: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_4a934c05-3be8-41bd-a143-bb43e3c6db0f became leader Jan 29 01:26:53.852: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_76e7c4f7-1b27-465e-8e19-1fa4bd808ad9 became leader Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {default-scheduler } Scheduled: Successfully assigned kube-system/l7-default-backend-8549d69d99-4x6fk to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" in 561.173126ms (561.189036ms including waiting) Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container default-http-backend Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container default-http-backend Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container default-http-backend Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container default-http-backend Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/l7-default-backend-8549d69d99-4x6fk Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container default-http-backend Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99: {replicaset-controller } SuccessfulCreate: Created pod: l7-default-backend-8549d69d99-4x6fk Jan 29 01:26:53.852: INFO: event for l7-default-backend: {deployment-controller } ScalingReplicaSet: Scaled up replica set l7-default-backend-8549d69d99 to 1 Jan 29 01:26:53.852: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container l7-lb-controller Jan 29 01:26:53.852: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container l7-lb-controller Jan 29 01:26:53.852: 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 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container l7-lb-controller Jan 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-dvtn5 to bootstrap-e2e-minion-group-g5dw Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 711.133904ms (711.172606ms including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.895066142s (1.895075509s including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} DNSConfigForming: Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 1.1.1.1 8.8.8.8 1.0.0.1 Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-gcl7f to bootstrap-e2e-master Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 754.286639ms (754.296219ms including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.036284591s (2.036292283s including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-ghdmf to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 780.74172ms (780.754027ms including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.00237082s (2.002396906s including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-tdckz to bootstrap-e2e-minion-group-nh1n Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 779.441797ms (779.481299ms including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.928968958s (1.929001469s including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} DNSConfigForming: Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 1.1.1.1 8.8.8.8 1.0.0.1 Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-ghdmf Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-gcl7f Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-tdckz Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-dvtn5 Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-6764bf875c-zcmcd to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 1.894622627s (1.894645738s including waiting) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 2.971768754s (2.971778948s including waiting) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container metrics-server in pod metrics-server-v0.5.2-6764bf875c-zcmcd_kube-system(51f812ec-6d0a-45bb-9ff5-261329977c3d) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container metrics-server-nanny in pod metrics-server-v0.5.2-6764bf875c-zcmcd_kube-system(51f812ec-6d0a-45bb-9ff5-261329977c3d) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-6764bf875c-zcmcd Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulDelete: Deleted pod: metrics-server-v0.5.2-6764bf875c-zcmcd Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: { } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-867b8754b9-9p9nx to bootstrap-e2e-minion-group-nh1n Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 1.375361805s (1.375372092s including waiting) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 1.029212495s (1.029231089s including waiting) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.3:10250/readyz": dial tcp 10.64.2.3:10250: connect: connection refused Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Liveness probe failed: Get "https://10.64.2.3:10250/livez": dial tcp 10.64.2.3:10250: connect: connection refused Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.3:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Liveness probe failed: Get "https://10.64.2.3:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/metrics-server-v0.5.2-867b8754b9-9p9nx Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.4:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.7:10250/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Liveness probe failed: Get "https://10.64.2.7:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.7:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} BackOff: Back-off restarting failed container metrics-server in pod metrics-server-v0.5.2-867b8754b9-9p9nx_kube-system(12c6e9b1-49f1-4dcd-844a-53879548296f) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} BackOff: Back-off restarting failed container metrics-server-nanny in pod metrics-server-v0.5.2-867b8754b9-9p9nx_kube-system(12c6e9b1-49f1-4dcd-844a-53879548296f) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: (combined from similar events): Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/metrics-server-v0.5.2-867b8754b9-9p9nx Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.11:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.11:10250/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Liveness probe failed: Get "https://10.64.2.11:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Container metrics-server failed liveness probe, will be restarted Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Failed: Error: failed to get sandbox container task: no running task found: task b32daf6ccf79d96010928de0e5c6d14f251f0f859fc2fd24cd0d2ef2b0a55cff not found: not found Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} BackOff: Back-off restarting failed container metrics-server in pod metrics-server-v0.5.2-867b8754b9-9p9nx_kube-system(12c6e9b1-49f1-4dcd-844a-53879548296f) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-867b8754b9-9p9nx Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-v0.5.2-6764bf875c to 1 Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-v0.5.2-867b8754b9 to 1 Jan 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {default-scheduler } Scheduled: Successfully assigned kube-system/volume-snapshot-controller-0 to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" in 3.526692937s (3.526702972s including waiting) Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(0c51547a-104f-4b7e-b495-4722734ddb26) Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(0c51547a-104f-4b7e-b495-4722734ddb26) Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/volume-snapshot-controller-0 Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(0c51547a-104f-4b7e-b495-4722734ddb26) Jan 29 01:26:53.852: 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/29/23 01:26:53.852 (54ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/29/23 01:26:53.852 Jan 29 01:26:53.852: 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/29/23 01:26:53.895 (43ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/29/23 01:26:53.895 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/29/23 01:26:53.895 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/29/23 01:26:53.895 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/29/23 01:26:53.896 STEP: Collecting events from namespace "reboot-1201". - test/e2e/framework/debug/dump.go:42 @ 01/29/23 01:26:53.896 STEP: Found 0 events. - test/e2e/framework/debug/dump.go:46 @ 01/29/23 01:26:53.937 Jan 29 01:26:53.981: INFO: POD NODE PHASE GRACE CONDITIONS Jan 29 01:26:53.981: INFO: Jan 29 01:26:54.024: INFO: Logging node info for node bootstrap-e2e-master Jan 29 01:26:54.140: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-master 11da0fa8-1a8b-4cc5-8d12-b293d7c50bd8 3905 0 2023-01-29 00:56:38 +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-29 00:56:38 +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-29 00:56:56 +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-29 00:57:03 +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\"":{}},"f:taints":{}}} } {kubelet Update v1 2023-01-29 01:23:01 +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.1.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-ubuntu/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.1.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-29 00:56:56 +0000 UTC,LastTransitionTime:2023-01-29 00:56:56 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-29 01:23:01 +0000 UTC,LastTransitionTime:2023-01-29 00:56:38 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-29 01:23:01 +0000 UTC,LastTransitionTime:2023-01-29 00:56:38 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-29 01:23:01 +0000 UTC,LastTransitionTime:2023-01-29 00:56:38 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-29 01:23:01 +0000 UTC,LastTransitionTime:2023-01-29 00:56:59 +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.197.23.89,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-master.c.k8s-jkns-e2e-gce-ubuntu.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-master.c.k8s-jkns-e2e-gce-ubuntu.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:bb30a7522713b1d3fb0ea758b3e0db97,SystemUUID:bb30a752-2713-b1d3-fb0e-a758b3e0db97,BootID:e3506071-57f4-4335-a9f0-5097284b165b,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-2-gaccb53cab,KubeletVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,KubeProxyVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-apiserver-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2],SizeBytes:135952851,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2],SizeBytes:125275449,},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.73_8e642d3d0deab2],SizeBytes:57552184,},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 29 01:26:54.140: INFO: Logging kubelet events for node bootstrap-e2e-master Jan 29 01:26:54.194: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-master Jan 29 01:26:54.243: INFO: Unable to retrieve kubelet pods for node bootstrap-e2e-master: error trying to reach service: No agent available Jan 29 01:26:54.243: INFO: Logging node info for node bootstrap-e2e-minion-group-g5dw Jan 29 01:26:54.298: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-g5dw ad80a01d-7a39-41e6-a452-8c1a441f9ba8 4052 0 2023-01-29 00:56:40 +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-g5dw 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-29 00:56:40 +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-29 01:18:06 +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-29 01:18:43 +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-29 01:24:25 +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-29 01:24:28 +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.3.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-ubuntu/us-west1-b/bootstrap-e2e-minion-group-g5dw,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: {{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:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-29 00:56:56 +0000 UTC,LastTransitionTime:2023-01-29 00:56:56 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-29 01:24:25 +0000 UTC,LastTransitionTime:2023-01-29 01:18:43 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-29 01:24:25 +0000 UTC,LastTransitionTime:2023-01-29 01:18:43 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-29 01:24:25 +0000 UTC,LastTransitionTime:2023-01-29 01:18:43 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-29 01:24:25 +0000 UTC,LastTransitionTime:2023-01-29 01:18:43 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.3,},NodeAddress{Type:ExternalIP,Address:34.82.165.19,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-g5dw.c.k8s-jkns-e2e-gce-ubuntu.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-g5dw.c.k8s-jkns-e2e-gce-ubuntu.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:fcd9c1d4705412851774a846f798e37b,SystemUUID:fcd9c1d4-7054-1285-1774-a846f798e37b,BootID:c10731fd-30bc-4c7d-9adc-1303f79a1fbb,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-2-gaccb53cab,KubeletVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,KubeProxyVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2],SizeBytes:66989256,},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/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 29 01:26:54.298: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-g5dw Jan 29 01:26:54.354: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-g5dw Jan 29 01:26:54.440: INFO: Unable to retrieve kubelet pods for node bootstrap-e2e-minion-group-g5dw: error trying to reach service: No agent available Jan 29 01:26:54.440: INFO: Logging node info for node bootstrap-e2e-minion-group-nh1n Jan 29 01:26:54.486: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-nh1n b9139680-2ebc-4c9b-b071-8d99a2c3eb72 4009 0 2023-01-29 00:56:38 +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-nh1n 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-29 00:56:38 +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-29 01:17:46 +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-29 01:18:28 +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-29 01:24:03 +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-29 01:24:03 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.2.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-ubuntu/us-west1-b/bootstrap-e2e-minion-group-nh1n,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.2.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815438336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553294336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-29 00:56:56 +0000 UTC,LastTransitionTime:2023-01-29 00:56:56 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-29 01:24:03 +0000 UTC,LastTransitionTime:2023-01-29 01:18:28 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-29 01:24:03 +0000 UTC,LastTransitionTime:2023-01-29 01:18:28 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-29 01:24:03 +0000 UTC,LastTransitionTime:2023-01-29 01:18:28 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-29 01:24:03 +0000 UTC,LastTransitionTime:2023-01-29 01:18:28 +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:35.230.114.56,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-nh1n.c.k8s-jkns-e2e-gce-ubuntu.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-nh1n.c.k8s-jkns-e2e-gce-ubuntu.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:2aed66ad76d7b78e16e13073a095e31a,SystemUUID:2aed66ad-76d7-b78e-16e1-3073a095e31a,BootID:933d589b-aca7-4290-9b0f-b063e2972d9d,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-2-gaccb53cab,KubeletVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,KubeProxyVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2],SizeBytes:66989256,},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 29 01:26:54.486: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-nh1n Jan 29 01:26:54.545: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-nh1n Jan 29 01:26:54.594: INFO: Unable to retrieve kubelet pods for node bootstrap-e2e-minion-group-nh1n: error trying to reach service: No agent available Jan 29 01:26:54.594: INFO: Logging node info for node bootstrap-e2e-minion-group-rv7m Jan 29 01:26:54.637: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-rv7m 4dbab00b-ec6a-408f-8d83-d0f6e496b11d 3920 0 2023-01-29 00:56:35 +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-rv7m 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-29 00:56:35 +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-29 01:02:01 +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-29 01:02:42 +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\"":{}}}} } {node-problem-detector Update v1 2023-01-29 01:22:45 +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-29 01:23:07 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{},"f:nodeInfo":{"f:bootID":{}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.0.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-ubuntu/us-west1-b/bootstrap-e2e-minion-group-rv7m,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.0.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:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-29 00:56:44 +0000 UTC,LastTransitionTime:2023-01-29 00:56:44 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-29 01:23:07 +0000 UTC,LastTransitionTime:2023-01-29 01:02:42 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-29 01:23:07 +0000 UTC,LastTransitionTime:2023-01-29 01:02:42 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-29 01:23:07 +0000 UTC,LastTransitionTime:2023-01-29 01:02:42 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-29 01:23:07 +0000 UTC,LastTransitionTime:2023-01-29 01:02:42 +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.105.95.109,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-rv7m.c.k8s-jkns-e2e-gce-ubuntu.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-rv7m.c.k8s-jkns-e2e-gce-ubuntu.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:646286d0db94eda1af78c3035cef9a0b,SystemUUID:646286d0-db94-eda1-af78-c3035cef9a0b,BootID:98c06424-41ae-40f7-975a-b5e68745d8d4,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-2-gaccb53cab,KubeletVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,KubeProxyVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2],SizeBytes:66989256,},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 29 01:26:54.639: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-rv7m Jan 29 01:26:54.700: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-rv7m Jan 29 01:26:54.748: INFO: Unable to retrieve kubelet pods for node bootstrap-e2e-minion-group-rv7m: error trying to reach service: No agent available END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/29/23 01:26:54.748 (852ms) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/29/23 01:26:54.748 (852ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/29/23 01:26:54.748 STEP: Destroying namespace "reboot-1201" for this suite. - test/e2e/framework/framework.go:347 @ 01/29/23 01:26:54.748 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/29/23 01:26:54.799 (52ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/29/23 01:26:54.8 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/29/23 01:26:54.8 (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/29/23 01:26:53.798from junit_01.xml
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/29/23 01:21:51.417 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/29/23 01:21:51.417 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/29/23 01:21:51.417 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/29/23 01:21:51.417 Jan 29 01:21:51.417: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/29/23 01:21:51.422 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/29/23 01:21:51.553 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/29/23 01:21:51.635 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/29/23 01:21:51.717 (301ms) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/29/23 01:21:51.717 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/29/23 01:21:51.718 (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/29/23 01:21:51.718 Jan 29 01:21:51.831: INFO: Getting bootstrap-e2e-minion-group-rv7m Jan 29 01:21:51.831: INFO: Getting bootstrap-e2e-minion-group-nh1n Jan 29 01:21:51.831: INFO: Getting bootstrap-e2e-minion-group-g5dw Jan 29 01:21:51.907: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-nh1n condition Ready to be true Jan 29 01:21:51.907: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-rv7m condition Ready to be true Jan 29 01:21:51.907: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-g5dw condition Ready to be true Jan 29 01:21:51.952: INFO: Node bootstrap-e2e-minion-group-rv7m has 4 assigned pods with no liveness probes: [kube-dns-autoscaler-5f6455f985-q8wlx kube-proxy-bootstrap-e2e-minion-group-rv7m metadata-proxy-v0.1-ghdmf volume-snapshot-controller-0] Jan 29 01:21:51.952: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [kube-dns-autoscaler-5f6455f985-q8wlx kube-proxy-bootstrap-e2e-minion-group-rv7m metadata-proxy-v0.1-ghdmf volume-snapshot-controller-0] Jan 29 01:21:51.952: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.952: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-rv7m" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-q8wlx" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.952: INFO: Node bootstrap-e2e-minion-group-g5dw has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-g5dw metadata-proxy-v0.1-dvtn5] Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-g5dw metadata-proxy-v0.1-dvtn5] Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-dvtn5" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-ghdmf" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-g5dw" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.953: INFO: Node bootstrap-e2e-minion-group-nh1n has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-nh1n metadata-proxy-v0.1-tdckz] Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-nh1n metadata-proxy-v0.1-tdckz] Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-tdckz" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:51.953: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-nh1n" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:21:52.001: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 48.649333ms Jan 29 01:21:52.001: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:52.001: INFO: Pod "metadata-proxy-v0.1-dvtn5": Phase="Running", Reason="", readiness=true. Elapsed: 48.519322ms Jan 29 01:21:52.001: INFO: Pod "metadata-proxy-v0.1-dvtn5" satisfied condition "running and ready, or succeeded" Jan 29 01:21:52.002: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 49.106253ms Jan 29 01:21:52.002: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:52.003: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-nh1n": Phase="Running", Reason="", readiness=true. Elapsed: 50.098793ms Jan 29 01:21:52.003: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-nh1n" satisfied condition "running and ready, or succeeded" Jan 29 01:21:52.003: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 50.359343ms Jan 29 01:21:52.003: INFO: Pod "metadata-proxy-v0.1-tdckz": Phase="Running", Reason="", readiness=true. Elapsed: 50.312087ms Jan 29 01:21:52.003: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:21:52.003: INFO: Pod "metadata-proxy-v0.1-tdckz" satisfied condition "running and ready, or succeeded" Jan 29 01:21:52.003: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-nh1n metadata-proxy-v0.1-tdckz] Jan 29 01:21:52.003: INFO: Getting external IP address for bootstrap-e2e-minion-group-nh1n Jan 29 01:21:52.003: INFO: Pod "metadata-proxy-v0.1-ghdmf": Phase="Running", Reason="", readiness=true. Elapsed: 50.466836ms Jan 29 01:21:52.003: INFO: Pod "metadata-proxy-v0.1-ghdmf" satisfied condition "running and ready, or succeeded" Jan 29 01:21:52.003: 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-nh1n(35.230.114.56:22) Jan 29 01:21:52.003: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 50.806994ms Jan 29 01:21:52.003: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:21:52.558: INFO: ssh prow@35.230.114.56: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 29 01:21:52.558: INFO: ssh prow@35.230.114.56:22: stdout: "" Jan 29 01:21:52.558: INFO: ssh prow@35.230.114.56:22: stderr: "" Jan 29 01:21:52.558: INFO: ssh prow@35.230.114.56:22: exit code: 0 Jan 29 01:21:52.558: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-nh1n condition Ready to be false Jan 29 01:21:52.600: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:21:54.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2.092899446s Jan 29 01:21:54.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2.09272055s Jan 29 01:21:54.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:54.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:54.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 2.095913912s Jan 29 01:21:54.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:21:54.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 2.096044547s Jan 29 01:21:54.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:21:54.644: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:21:56.049: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4.096204615s Jan 29 01:21:56.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:56.050: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4.097300065s Jan 29 01:21:56.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:56.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 4.097130438s Jan 29 01:21:56.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:21:56.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 4.097527162s Jan 29 01:21:56.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:21:56.688: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:21:58.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 6.093568679s Jan 29 01:21:58.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:58.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 6.093915675s Jan 29 01:21:58.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:21:58.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 6.09548999s Jan 29 01:21:58.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:21:58.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 6.095908305s Jan 29 01:21:58.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:21:58.731: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:00.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 8.092341542s Jan 29 01:22:00.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:00.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 8.093222342s Jan 29 01:22:00.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:00.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 8.095547499s Jan 29 01:22:00.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:00.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 8.097795945s Jan 29 01:22:00.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:00.774: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:02.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 10.091060308s Jan 29 01:22:02.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:02.049: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 10.095964676s Jan 29 01:22:02.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:02.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 10.096409585s Jan 29 01:22:02.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:02.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 10.09625703s Jan 29 01:22:02.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:02.818: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:04.048: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 12.095552722s Jan 29 01:22:04.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:04.048: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 12.095499679s Jan 29 01:22:04.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:04.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 12.096452379s Jan 29 01:22:04.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:04.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 12.096189813s Jan 29 01:22:04.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:04.862: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:06.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 14.093718924s Jan 29 01:22:06.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:06.048: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 14.095078905s Jan 29 01:22:06.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:06.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 14.096680195s Jan 29 01:22:06.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:06.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 14.097945937s Jan 29 01:22:06.051: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:06.908: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:08.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 16.092967776s Jan 29 01:22:08.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:08.048: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 16.09521184s Jan 29 01:22:08.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:08.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 16.09661099s Jan 29 01:22:08.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:08.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 16.096586006s Jan 29 01:22:08.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:08.951: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:10.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 18.093270533s Jan 29 01:22:10.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:10.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 18.094134834s Jan 29 01:22:10.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:10.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 18.096088958s Jan 29 01:22:10.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:10.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 18.096627335s Jan 29 01:22:10.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:10.994: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:12.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 20.093295486s Jan 29 01:22:12.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:12.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 20.09438779s Jan 29 01:22:12.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:12.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 20.096973141s Jan 29 01:22:12.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=false. Elapsed: 20.096671404s Jan 29 01:22:12.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-g5dw' on 'bootstrap-e2e-minion-group-g5dw' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:21:44 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:40 +0000 UTC }] Jan 29 01:22:12.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:13.077: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:14.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 22.0911756s Jan 29 01:22:14.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:14.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 22.094885503s Jan 29 01:22:14.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:14.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 22.095858368s Jan 29 01:22:14.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:14.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=true. Elapsed: 22.096460175s Jan 29 01:22:14.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw" satisfied condition "running and ready, or succeeded" Jan 29 01:22:14.049: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-g5dw metadata-proxy-v0.1-dvtn5] Jan 29 01:22:14.049: INFO: Getting external IP address for bootstrap-e2e-minion-group-g5dw Jan 29 01:22:14.049: 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-g5dw(34.82.165.19:22) Jan 29 01:22:14.595: INFO: ssh prow@34.82.165.19: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 29 01:22:14.595: INFO: ssh prow@34.82.165.19:22: stdout: "" Jan 29 01:22:14.595: INFO: ssh prow@34.82.165.19:22: stderr: "" Jan 29 01:22:14.595: INFO: ssh prow@34.82.165.19:22: exit code: 0 Jan 29 01:22:14.595: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-g5dw condition Ready to be false Jan 29 01:22:14.638: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:15.122: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:16.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 24.093585743s Jan 29 01:22:16.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:16.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 24.093951063s Jan 29 01:22:16.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:16.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 24.095776779s Jan 29 01:22:16.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:16.680: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:17.167: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:18.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 26.092786195s Jan 29 01:22:18.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:18.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 26.093019938s Jan 29 01:22:18.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:18.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 26.095910866s Jan 29 01:22:18.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:18.722: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:19.210: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:20.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 28.091027561s Jan 29 01:22:20.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:20.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 28.092247325s Jan 29 01:22:20.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:20.047: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 28.094437284s Jan 29 01:22:20.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:20.766: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:21.270: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:22.071: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 30.118870968s Jan 29 01:22:22.071: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:22.072: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 30.119564628s Jan 29 01:22:22.072: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:22.076: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 30.1236619s Jan 29 01:22:22.076: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:22.810: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:23.314: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:24.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 32.092775455s Jan 29 01:22:24.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:24.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 32.093885977s Jan 29 01:22:24.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:24.047: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 32.094341935s Jan 29 01:22:24.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:24.853: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:25.357: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:26.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 34.091938473s Jan 29 01:22:26.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:26.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 34.093950721s Jan 29 01:22:26.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:26.047: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 34.09446359s Jan 29 01:22:26.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:26.897: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:27.401: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:28.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 36.091856227s Jan 29 01:22:28.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:28.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 36.093308638s Jan 29 01:22:28.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:28.047: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 36.094930308s Jan 29 01:22:28.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:28.941: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:29.445: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:30.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 38.093512909s Jan 29 01:22:30.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:30.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 38.094114137s Jan 29 01:22:30.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:30.049: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 38.096722456s Jan 29 01:22:30.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:30.984: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:31.488: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:32.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 40.093894966s Jan 29 01:22:32.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:32.049: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 40.096039493s Jan 29 01:22:32.049: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:32.054: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 40.10116259s Jan 29 01:22:32.054: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:33.028: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:33.532: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:34.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 42.090372921s Jan 29 01:22:34.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:34.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 42.091252734s Jan 29 01:22:34.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:34.046: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 42.093415862s Jan 29 01:22:34.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:35.074: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:35.576: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:36.047: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 44.094722119s Jan 29 01:22:36.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:36.048: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 44.094946907s Jan 29 01:22:36.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:36.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 44.095164092s Jan 29 01:22:36.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:37.120: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:37.620: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:38.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 46.092319849s Jan 29 01:22:38.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:38.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 46.093758437s Jan 29 01:22:38.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:38.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 46.095584198s Jan 29 01:22:38.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:39.163: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:39.664: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:40.048: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 48.095439969s Jan 29 01:22:40.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:40.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 48.097052911s Jan 29 01:22:40.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:40.050: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 48.09745494s Jan 29 01:22:40.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:41.207: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:41.707: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:42.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 50.092530349s Jan 29 01:22:42.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:42.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 50.093216028s Jan 29 01:22:42.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:42.047: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 50.094898477s Jan 29 01:22:42.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:43.250: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:43.750: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:44.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 52.091844454s Jan 29 01:22:44.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:44.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 52.093800427s Jan 29 01:22:44.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:44.047: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 52.094808856s Jan 29 01:22:44.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:45.296: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:45.793: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:46.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 54.092181993s Jan 29 01:22:46.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:46.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 54.093833627s Jan 29 01:22:46.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:46.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 54.095079497s Jan 29 01:22:46.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:47.339: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:47.837: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:48.047: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 56.094280096s Jan 29 01:22:48.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:48.048: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 56.094902493s Jan 29 01:22:48.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:48.048: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 56.09507242s Jan 29 01:22:48.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:49.392: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:49.882: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:50.047: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 58.094144691s Jan 29 01:22:50.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:50.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 58.094872715s Jan 29 01:22:50.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:50.050: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 58.097247345s Jan 29 01:22:50.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:20:00 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:22:51.436: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:51.925: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:52.050: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m0.096894534s Jan 29 01:22:52.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:52.050: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m0.097920557s Jan 29 01:22:52.050: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:52.051: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=true. Elapsed: 1m0.098895094s Jan 29 01:22:52.051: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m" satisfied condition "running and ready, or succeeded" Jan 29 01:22:53.480: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:53.970: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:54.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m2.092656899s Jan 29 01:22:54.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:54.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m2.09288788s Jan 29 01:22:54.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:55.527: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:56.015: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:56.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.093790458s Jan 29 01:22:56.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:56.048: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.095211657s Jan 29 01:22:56.048: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:57.570: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:58.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.091022108s Jan 29 01:22:58.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:58.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.092259184s Jan 29 01:22:58.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:22:58.066: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:22:59.614: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:00.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m8.093827214s Jan 29 01:23:00.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:00.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m8.093749352s Jan 29 01:23:00.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:00.110: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:01.658: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:02.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.093077791s Jan 29 01:23:02.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:02.047: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.094136811s Jan 29 01:23:02.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:02.154: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:03.702: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:04.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.090989488s Jan 29 01:23:04.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:04.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.091957204s Jan 29 01:23:04.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:04.197: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:05.746: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:06.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m14.092327795s Jan 29 01:23:06.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:06.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m14.093855625s Jan 29 01:23:06.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:06.240: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:07.789: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:08.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.092030368s Jan 29 01:23:08.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:08.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.093816746s Jan 29 01:23:08.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:08.282: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:09.832: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:10.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.092482785s Jan 29 01:23:10.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.092304736s Jan 29 01:23:10.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:10.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:10.326: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:11.876: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:12.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.092712676s Jan 29 01:23:12.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:12.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.094070795s Jan 29 01:23:12.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:12.370: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:13.921: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:14.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.091419121s Jan 29 01:23:14.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.091632372s Jan 29 01:23:14.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:14.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:14.414: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:15.964: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:16.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m24.091804453s Jan 29 01:23:16.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:16.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m24.09323422s Jan 29 01:23:16.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:16.458: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:18.006: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:18.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m26.092188822s Jan 29 01:23:18.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:18.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m26.092539722s Jan 29 01:23:18.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:18.501: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:20.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m28.093114811s Jan 29 01:23:20.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:20.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m28.093390815s Jan 29 01:23:20.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:20.050: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:20.544: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:22.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m30.091326575s Jan 29 01:23:22.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:22.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m30.092264708s Jan 29 01:23:22.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:22.092: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:22.587: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:24.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m32.092152644s Jan 29 01:23:24.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m32.091990912s Jan 29 01:23:24.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:24.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:24.135: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:24.630: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:26.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m34.090824667s Jan 29 01:23:26.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:26.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m34.092363931s Jan 29 01:23:26.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:26.179: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:26.673: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:28.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m36.092658792s Jan 29 01:23:28.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:28.047: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m36.094144401s Jan 29 01:23:28.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:28.222: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:28.717: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:30.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m38.093096034s Jan 29 01:23:30.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:30.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m38.093042617s Jan 29 01:23:30.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:30.266: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:30.759: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:32.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m40.091740674s Jan 29 01:23:32.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:32.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m40.093273504s Jan 29 01:23:32.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:32.309: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:32.821: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:34.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m42.090773656s Jan 29 01:23:34.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:34.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m42.091724081s Jan 29 01:23:34.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:34.353: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:34.865: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:36.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m44.092153106s Jan 29 01:23:36.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:36.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m44.092180231s Jan 29 01:23:36.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:36.395: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:36.909: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:38.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m46.090653966s Jan 29 01:23:38.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:38.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m46.091952511s Jan 29 01:23:38.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:38.439: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:38.951: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:40.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m48.092430555s Jan 29 01:23:40.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:40.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m48.092353568s Jan 29 01:23:40.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:40.482: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:40.995: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:42.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m50.093330113s Jan 29 01:23:42.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:42.047: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m50.094821094s Jan 29 01:23:42.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:42.528: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:43.038: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:44.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m52.09074008s Jan 29 01:23:44.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:44.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m52.092327725s Jan 29 01:23:44.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:44.572: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:45.080: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:46.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m54.090378059s Jan 29 01:23:46.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:46.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m54.091608638s Jan 29 01:23:46.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:46.615: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:47.123: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:48.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m56.092396054s Jan 29 01:23:48.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:48.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m56.093788342s Jan 29 01:23:48.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:48.658: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:49.167: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:50.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 1m58.092523963s Jan 29 01:23:50.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:50.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m58.092496002s Jan 29 01:23:50.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:50.702: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:51.210: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:52.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m0.09254421s Jan 29 01:23:52.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m0.092382305s Jan 29 01:23:52.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:52.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:52.745: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:53.211: INFO: Node bootstrap-e2e-minion-group-nh1n didn't reach desired Ready condition status (false) within 2m0s Jan 29 01:23:54.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m2.090647034s Jan 29 01:23:54.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:54.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m2.092359833s Jan 29 01:23:54.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:54.788: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:56.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m4.091426787s Jan 29 01:23:56.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:56.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m4.092147719s Jan 29 01:23:56.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:56.831: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:23:58.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m6.090534011s Jan 29 01:23:58.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:58.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m6.091758805s Jan 29 01:23:58.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:23:58.874: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:00.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m8.092108586s Jan 29 01:24:00.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m8.091936546s Jan 29 01:24:00.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:00.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:00.916: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:02.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m10.090647858s Jan 29 01:24:02.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:02.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m10.091933937s Jan 29 01:24:02.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:02.959: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:04.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m12.090751367s Jan 29 01:24:04.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:04.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m12.092428669s Jan 29 01:24:04.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:05.006: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:06.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m14.092400319s Jan 29 01:24:06.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m14.092234645s Jan 29 01:24:06.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:06.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:07.049: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:08.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m16.091884417s Jan 29 01:24:08.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:08.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m16.092895991s Jan 29 01:24:08.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:09.092: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:10.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m18.091124482s Jan 29 01:24:10.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:10.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m18.092050141s Jan 29 01:24:10.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:11.134: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:12.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m20.091107724s Jan 29 01:24:12.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:12.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m20.092199097s Jan 29 01:24:12.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:13.177: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:24:14.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m22.090373784s Jan 29 01:24:14.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:14.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m22.091579941s Jan 29 01:24:14.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:15.178: INFO: Node bootstrap-e2e-minion-group-g5dw didn't reach desired Ready condition status (false) within 2m0s Jan 29 01:24:16.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m24.090358141s Jan 29 01:24:16.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:16.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m24.091714039s Jan 29 01:24:16.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:18.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m26.090955556s Jan 29 01:24:18.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:18.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m26.091923217s Jan 29 01:24:18.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:20.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m28.09047215s Jan 29 01:24:20.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:20.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m28.091746733s Jan 29 01:24:20.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:22.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m30.092787501s Jan 29 01:24:22.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:22.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m30.092713228s Jan 29 01:24:22.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:24.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m32.091827124s Jan 29 01:24:24.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:24.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m32.09215354s Jan 29 01:24:24.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:26.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m34.091118549s Jan 29 01:24:26.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:26.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m34.092742265s Jan 29 01:24:26.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:28.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m36.092943831s Jan 29 01:24:28.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m36.093133422s Jan 29 01:24:28.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:28.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:30.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m38.092525253s Jan 29 01:24:30.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:30.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m38.092798063s Jan 29 01:24:30.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:32.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m40.09072277s Jan 29 01:24:32.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:32.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m40.092154018s Jan 29 01:24:32.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:34.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m42.090637771s Jan 29 01:24:34.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:34.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m42.092001698s Jan 29 01:24:34.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:36.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m44.091892081s Jan 29 01:24:36.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:36.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m44.093518891s Jan 29 01:24:36.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:38.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m46.092060112s Jan 29 01:24:38.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:38.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m46.091998521s Jan 29 01:24:38.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:40.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m48.092174318s Jan 29 01:24:40.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:40.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m48.092235382s Jan 29 01:24:40.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:42.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m50.092092326s Jan 29 01:24:42.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:42.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m50.093485782s Jan 29 01:24:42.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:44.043: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m52.090652972s Jan 29 01:24:44.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:44.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m52.092386032s Jan 29 01:24:44.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:46.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m54.092281466s Jan 29 01:24:46.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:46.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m54.093846164s Jan 29 01:24:46.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:48.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m56.093119846s Jan 29 01:24:48.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:48.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m56.093093182s Jan 29 01:24:48.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:50.046: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2m58.093165474s Jan 29 01:24:50.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:50.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m58.093110529s Jan 29 01:24:50.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:52.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m0.091082852s Jan 29 01:24:52.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:52.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m0.092127874s Jan 29 01:24:52.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:54.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m2.091747916s Jan 29 01:24:54.044: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 3m2.091932304s Jan 29 01:24:54.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:54.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:19:47 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:56.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m4.091937321s Jan 29 01:24:56.045: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 3m4.092130233s Jan 29 01:24:56.045: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 29 01:24:56.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:24:58.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m6.091620214s Jan 29 01:24:58.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:00.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m8.093010459s Jan 29 01:25:00.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:02.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m10.092231598s Jan 29 01:25:02.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:04.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m12.090958524s Jan 29 01:25:04.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:06.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m14.091065144s Jan 29 01:25:06.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:08.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m16.090935409s Jan 29 01:25:08.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:10.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m18.093033794s Jan 29 01:25:10.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:12.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m20.091221773s Jan 29 01:25:12.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:14.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m22.090960945s Jan 29 01:25:14.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:16.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m24.091373424s Jan 29 01:25:16.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:18.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m26.092120167s Jan 29 01:25:18.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:20.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m28.092444123s Jan 29 01:25:20.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:22.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m30.09201793s Jan 29 01:25:22.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:24.063: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m32.110395866s Jan 29 01:25:24.063: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:26.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m34.092061068s Jan 29 01:25:26.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:28.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m36.092489918s Jan 29 01:25:28.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:30.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m38.092400272s Jan 29 01:25:30.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:32.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m40.092403534s Jan 29 01:25:32.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:34.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m42.093091723s Jan 29 01:25:34.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:36.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m44.091555211s Jan 29 01:25:36.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:38.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m46.092629818s Jan 29 01:25:38.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:40.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m48.093265227s Jan 29 01:25:40.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:42.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m50.091541386s Jan 29 01:25:42.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:44.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m52.091326706s Jan 29 01:25:44.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:46.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m54.091070139s Jan 29 01:25:46.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:48.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m56.090895621s Jan 29 01:25:48.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:50.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m58.092773383s Jan 29 01:25:50.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:52.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m0.092296055s Jan 29 01:25:52.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:54.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m2.0923814s Jan 29 01:25:54.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:56.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m4.091588284s Jan 29 01:25:56.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:25:58.043: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m6.090755166s Jan 29 01:25:58.043: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:00.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m8.092394137s Jan 29 01:26:00.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:02.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m10.091344502s Jan 29 01:26:02.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:04.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m12.092227113s Jan 29 01:26:04.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:06.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m14.091397262s Jan 29 01:26:06.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:08.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m16.092989285s Jan 29 01:26:08.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:10.046: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m18.093395951s Jan 29 01:26:10.046: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:12.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m20.092132767s Jan 29 01:26:12.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:14.043: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m22.090893092s Jan 29 01:26:14.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:16.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m24.091076495s Jan 29 01:26:16.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:18.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m26.091016193s Jan 29 01:26:18.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:20.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m28.092549525s Jan 29 01:26:20.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:22.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m30.091301125s Jan 29 01:26:22.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:24.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m32.092340646s Jan 29 01:26:24.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:26.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m34.091088418s Jan 29 01:26:26.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:28.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m36.092691047s Jan 29 01:26:28.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:30.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m38.092836258s Jan 29 01:26:30.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:32.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m40.091377683s Jan 29 01:26:32.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:34.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m42.09133447s Jan 29 01:26:34.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:36.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m44.091842602s Jan 29 01:26:36.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:38.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m46.091304971s Jan 29 01:26:38.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:40.047: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m48.094368856s Jan 29 01:26:40.047: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:42.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m50.090963948s Jan 29 01:26:42.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:44.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m52.092578524s Jan 29 01:26:44.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:46.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m54.091513593s Jan 29 01:26:46.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:48.044: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m56.091214826s Jan 29 01:26:48.044: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:50.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m58.092336327s Jan 29 01:26:50.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +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.302s) test/e2e/cloud/gcp/reboot.go:136 In [It] (Node Runtime: 5m0.001s) test/e2e/cloud/gcp/reboot.go:136 Spec Goroutine goroutine 7990 [semacquire, 5 minutes] sync.runtime_Semacquire(0xc0049288a0?) /usr/local/go/src/runtime/sema.go:62 sync.(*WaitGroup).Wait(0x7fafbe533008?) /usr/local/go/src/sync/waitgroup.go:139 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot({0x7fafbe533008?, 0xc003b04300}, {0x8147108?, 0xc005a42000}, {0xc000290820, 0x182}, 0xc004bf4360) test/e2e/cloud/gcp/reboot.go:181 > k8s.io/kubernetes/test/e2e/cloud/gcp.glob..func8.7({0x7fafbe533008, 0xc003b04300}) test/e2e/cloud/gcp/reboot.go:141 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func2({0x8111ee8?, 0xc003b04300}) 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 7994 [chan receive, 2 minutes] k8s.io/kubernetes/test/e2e/framework/pod.checkPodsCondition({0x7fafbe533008?, 0xc003b04300}, {0x8147108?, 0xc005a42000}, {0x76d190b, 0xb}, {0xc005a52c00, 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({0x7fafbe533008, 0xc003b04300}, {0x8147108, 0xc005a42000}, {0x7ffd6cdb95f2, 0x3}, {0xc00004e720, 0x1f}, {0xc000290820, 0x182}) test/e2e/cloud/gcp/reboot.go:284 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot.func2(0x2) test/e2e/cloud/gcp/reboot.go:173 > k8s.io/kubernetes/test/e2e/cloud/gcp.testReboot test/e2e/cloud/gcp/reboot.go:169 Jan 29 01:26:52.045: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 5m0.092058211s Jan 29 01:26:52.045: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:52.086: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 5m0.133612681s Jan 29 01:26:52.086: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:26:52.086: INFO: Pod kube-dns-autoscaler-5f6455f985-q8wlx failed to be running and ready, or succeeded. Jan 29 01:26:52.086: INFO: Wanted all 4 pods to be running and ready, or succeeded. Result: false. Pods: [kube-dns-autoscaler-5f6455f985-q8wlx kube-proxy-bootstrap-e2e-minion-group-rv7m metadata-proxy-v0.1-ghdmf volume-snapshot-controller-0] Jan 29 01:26:52.086: INFO: Status for not ready pod kube-system/kube-dns-autoscaler-5f6455f985-q8wlx: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 00:56:44 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 01:01: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-29 01:01: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-29 00:56:44 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP: PodIPs:[] StartTime:2023-01-29 00:56:44 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:autoscaler State:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-29 01:01:17 +0000 UTC,FinishedAt:2023-01-29 01:01:18 +0000 UTC,ContainerID:containerd://5a508a2954b644f87b9aad92582ca582be3b89489ba6973cabe09fc07d5230c2,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:2 Image:registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4 ImageID:registry.k8s.io/cpa/cluster-proportional-autoscaler@sha256:fd636b33485c7826fb20ef0688a83ee0910317dbb6c0c6f3ad14661c1db25def ContainerID:containerd://5a508a2954b644f87b9aad92582ca582be3b89489ba6973cabe09fc07d5230c2 Started:0xc004db5a7f}] QOSClass:Burstable EphemeralContainerStatuses:[]} Jan 29 01:26:52.131: INFO: Retrieving log for container kube-system/kube-dns-autoscaler-5f6455f985-q8wlx/autoscaler, err: an error on the server ("unknown") has prevented the request from succeeding (get pods kube-dns-autoscaler-5f6455f985-q8wlx): Jan 29 01:26:52.131: INFO: Retrieving log for the last terminated container kube-system/kube-dns-autoscaler-5f6455f985-q8wlx/autoscaler, err: an error on the server ("unknown") has prevented the request from succeeding (get pods kube-dns-autoscaler-5f6455f985-q8wlx): Jan 29 01:26:52.131: INFO: Status for not ready pod kube-system/kube-proxy-bootstrap-e2e-minion-group-rv7m: {Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 00:56:35 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 01:20:00 +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-29 01:20:00 +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-29 00:56:35 +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-29 00:56:35 +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-rv7m_kube-system(e73c874f32f53e94265ad545cac1eda7),} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-29 01:16:07 +0000 UTC,FinishedAt:2023-01-29 01:19:59 +0000 UTC,ContainerID:containerd://c8052c1724b207686da01aaecdf4f106e1b95696ca4702311649b5ee69e71cb0,}} Ready:false RestartCount:7 Image:registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2 ImageID:sha256:ef97fd17575d534d8bc2960bbf1e744379f3ac6e86b9b97974e086f1516b75e5 ContainerID:containerd://c8052c1724b207686da01aaecdf4f106e1b95696ca4702311649b5ee69e71cb0 Started:0xc004db5d0f}] QOSClass:Burstable EphemeralContainerStatuses:[]} Jan 29 01:26:52.176: INFO: Retrieving log for container kube-system/kube-proxy-bootstrap-e2e-minion-group-rv7m/kube-proxy, err: an error on the server ("unknown") has prevented the request from succeeding (get pods kube-proxy-bootstrap-e2e-minion-group-rv7m): Jan 29 01:26:52.176: INFO: Retrieving log for the last terminated container kube-system/kube-proxy-bootstrap-e2e-minion-group-rv7m/kube-proxy, err: an error on the server ("unknown") has prevented the request from succeeding (get pods kube-proxy-bootstrap-e2e-minion-group-rv7m): Jan 29 01:26:52.176: 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-29 00:56:44 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-29 01:19:47 +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-29 01:19:47 +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-29 00:56:44 +0000 UTC Reason: Message:}] Message: Reason: NominatedNodeName: HostIP:10.138.0.4 PodIP:10.64.0.53 PodIPs:[{IP:10.64.0.53}] StartTime:2023-01-29 00:56:44 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:volume-snapshot-controller State:{Waiting:&ContainerStateWaiting{Reason:CrashLoopBackOff,Message:back-off 5m0s restarting failed container=volume-snapshot-controller pod=volume-snapshot-controller-0_kube-system(0c51547a-104f-4b7e-b495-4722734ddb26),} Running:nil Terminated:nil} LastTerminationState:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:2,Signal:0,Reason:Error,Message:,StartedAt:2023-01-29 01:18:35 +0000 UTC,FinishedAt:2023-01-29 01:19:46 +0000 UTC,ContainerID:containerd://c4f3770023f8628ca6f3d27c03d3ebd8e674a9c6d3e4d4c9f2489422ef1612dd,}} Ready:false RestartCount:12 Image:registry.k8s.io/sig-storage/snapshot-controller:v6.1.0 ImageID:registry.k8s.io/sig-storage/snapshot-controller@sha256:823c75d0c45d1427f6d850070956d9ca657140a7bbf828381541d1d808475280 ContainerID:containerd://c4f3770023f8628ca6f3d27c03d3ebd8e674a9c6d3e4d4c9f2489422ef1612dd Started:0xc00592446f}] QOSClass:BestEffort EphemeralContainerStatuses:[]} Jan 29 01:26:52.221: INFO: Retrieving log for container kube-system/volume-snapshot-controller-0/volume-snapshot-controller, err: an error on the server ("unknown") has prevented the request from succeeding (get pods volume-snapshot-controller-0): Jan 29 01:26:52.221: INFO: Retrieving log for the last terminated container kube-system/volume-snapshot-controller-0/volume-snapshot-controller, err: an error on the server ("unknown") has prevented the request from succeeding (get pods volume-snapshot-controller-0): Jan 29 01:26:52.222: INFO: Node bootstrap-e2e-minion-group-g5dw failed reboot test. Jan 29 01:26:52.222: INFO: Node bootstrap-e2e-minion-group-nh1n failed reboot test. Jan 29 01:26:52.222: INFO: Node bootstrap-e2e-minion-group-rv7m failed reboot test. Jan 29 01:26:52.222: INFO: Executing termination hook on nodes Jan 29 01:26:52.222: INFO: Getting external IP address for bootstrap-e2e-minion-group-g5dw Jan 29 01:26:52.222: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-g5dw(34.82.165.19:22) Jan 29 01:26:52.747: INFO: ssh prow@34.82.165.19:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 29 01:26:52.747: INFO: ssh prow@34.82.165.19: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\nSun Jan 29 01:22:24 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 29 01:26:52.747: INFO: ssh prow@34.82.165.19:22: stderr: "" Jan 29 01:26:52.747: INFO: ssh prow@34.82.165.19:22: exit code: 0 Jan 29 01:26:52.747: INFO: Getting external IP address for bootstrap-e2e-minion-group-nh1n Jan 29 01:26:52.747: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-nh1n(35.230.114.56:22) Jan 29 01:26:53.275: INFO: ssh prow@35.230.114.56:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 29 01:26:53.275: INFO: ssh prow@35.230.114.56: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\nSun Jan 29 01:22:02 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 29 01:26:53.275: INFO: ssh prow@35.230.114.56:22: stderr: "" Jan 29 01:26:53.275: INFO: ssh prow@35.230.114.56:22: exit code: 0 Jan 29 01:26:53.275: INFO: Getting external IP address for bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.275: INFO: SSH "cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log" on bootstrap-e2e-minion-group-rv7m(34.105.95.109:22) Jan 29 01:26:53.798: INFO: ssh prow@34.105.95.109:22: command: cat /tmp/drop-inbound.log && rm /tmp/drop-inbound.log Jan 29 01:26:53.798: INFO: ssh prow@34.105.95.109:22: stdout: "" Jan 29 01:26:53.798: INFO: ssh prow@34.105.95.109:22: stderr: "cat: /tmp/drop-inbound.log: No such file or directory\n" Jan 29 01:26:53.798: INFO: ssh prow@34.105.95.109:22: exit code: 1 Jan 29 01:26:53.798: 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 ) [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/29/23 01:26:53.798 < 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/29/23 01:26:53.798 (5m2.08s) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:68 @ 01/29/23 01:26:53.798 STEP: Collecting events from namespace "kube-system". - test/e2e/cloud/gcp/reboot.go:73 @ 01/29/23 01:26:53.798 Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-5mldm to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/coredns/coredns:v1.10.0" Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/coredns/coredns:v1.10.0" in 3.251905895s (3.251916602s including waiting) Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: Get "http://10.64.0.18:8181/ready": dial tcp 10.64.0.18:8181: connect: connection refused Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-5mldm_kube-system(460fb526-17a9-4c77-b280-98d8f5313ec6) Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-6846b5b5f-5mldm Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: Get "http://10.64.0.31:8181/ready": dial tcp 10.64.0.31:8181: connect: connection refused Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-5mldm: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-5mldm_kube-system(460fb526-17a9-4c77-b280-98d8f5313ec6) Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-6846b5b5f-t7kt4 to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: Get "http://10.64.0.8:8181/ready": dial tcp 10.64.0.8:8181: connect: connection refused Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: Get "http://10.64.0.13:8181/ready": dial tcp 10.64.0.13:8181: connect: connection refused Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-t7kt4_kube-system(448ac129-a4a8-4121-bd3e-3b4d496219a2) Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: Get "http://10.64.0.22:8181/ready": dial tcp 10.64.0.22:8181: connect: connection refused Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-t7kt4_kube-system(448ac129-a4a8-4121-bd3e-3b4d496219a2) Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-6846b5b5f-t7kt4 Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container coredns Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503 Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container coredns in pod coredns-6846b5b5f-t7kt4_kube-system(448ac129-a4a8-4121-bd3e-3b4d496219a2) Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f-t7kt4: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: Get "http://10.64.0.40:8181/ready": dial tcp 10.64.0.40:8181: connect: connection refused Jan 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-5mldm Jan 29 01:26:53.852: INFO: event for coredns-6846b5b5f: {replicaset-controller } SuccessfulCreate: Created pod: coredns-6846b5b5f-t7kt4 Jan 29 01:26:53.852: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 1 Jan 29 01:26:53.852: INFO: event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-6846b5b5f to 2 from 1 Jan 29 01:26:53.852: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container etcd-container Jan 29 01:26:53.852: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container etcd-container Jan 29 01:26:53.852: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container etcd-container Jan 29 01:26:53.852: INFO: event for etcd-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: 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 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container etcd-container Jan 29 01:26:53.852: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container etcd-container Jan 29 01:26:53.852: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container etcd-container Jan 29 01:26:53.852: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Liveness probe errored: rpc error: code = NotFound desc = failed to exec in container: failed to load task: no running task found: task c0e4964a6618e28860cb2feb2d888ee478fb57974e5227745331db243d5d6214 not found: not found Jan 29 01:26:53.852: 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 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for etcd-server-events-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container etcd-container in pod etcd-server-events-bootstrap-e2e-master_kube-system(9f090652556c0eb7722415ec1d3682eb) Jan 29 01:26:53.852: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_eff40 became leader Jan 29 01:26:53.852: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_dbd05 became leader Jan 29 01:26:53.852: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_df796 became leader Jan 29 01:26:53.852: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_d4e3d became leader Jan 29 01:26:53.852: INFO: event for ingress-gce-lock: {loadbalancer-controller } LeaderElection: bootstrap-e2e-master_688f3 became leader Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-hrwgh to bootstrap-e2e-minion-group-g5dw Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 607.221734ms (607.233291ms including waiting) Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} Killing: Stopping container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-hrwgh_kube-system(e5ba1730-1fc4-4a47-9676-3232346230a4) Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-hrwgh: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-vt26n to bootstrap-e2e-minion-group-nh1n Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 640.482136ms (640.492658ms including waiting) Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-vt26n_kube-system(be5719b0-08d3-4d11-99c8-a4bb292d7a70) Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-vt26n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {default-scheduler } Scheduled: Successfully assigned kube-system/konnectivity-agent-xb8th to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" in 1.893509533s (1.893518578s including waiting) Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-xb8th_kube-system(22da266b-c1de-453b-9421-152e16982294) Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/kas-network-proxy/proxy-agent:v0.1.1" already present on machine Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container konnectivity-agent Jan 29 01:26:53.852: INFO: event for konnectivity-agent-xb8th: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container konnectivity-agent in pod konnectivity-agent-xb8th_kube-system(22da266b-c1de-453b-9421-152e16982294) Jan 29 01:26:53.852: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-xb8th Jan 29 01:26:53.852: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-hrwgh Jan 29 01:26:53.852: INFO: event for konnectivity-agent: {daemonset-controller } SuccessfulCreate: Created pod: konnectivity-agent-vt26n Jan 29 01:26:53.852: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container konnectivity-server-container Jan 29 01:26:53.852: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container konnectivity-server-container Jan 29 01:26:53.852: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container konnectivity-server-container Jan 29 01:26:53.852: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for konnectivity-server-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} BackOff: Back-off restarting failed container konnectivity-server-container in pod konnectivity-server-bootstrap-e2e-master_kube-system(122c336be1dd86824540422433813d8a) Jan 29 01:26:53.852: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-addon-manager Jan 29 01:26:53.852: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-addon-manager Jan 29 01:26:53.852: INFO: event for kube-addon-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-addon-manager Jan 29 01:26:53.852: 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 29 01:26:53.852: 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 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for kube-apiserver-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 29 01:26:53.852: 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.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-controller-manager Jan 29 01:26:53.852: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-controller-manager Jan 29 01:26:53.852: INFO: event for kube-controller-manager-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-controller-manager Jan 29 01:26:53.852: 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 29 01:26:53.852: 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(a9901ac1fc908c01cd17c25062859343) Jan 29 01:26:53.852: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_e5910642-3cec-41bb-86e3-b6287f7e96f1 became leader Jan 29 01:26:53.852: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_eb1eb016-6b07-4a59-8227-08c665e9a103 became leader Jan 29 01:26:53.852: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_340e04c7-8f81-4372-9559-eb8718fb5d3b became leader Jan 29 01:26:53.852: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_ffaa1eb5-2e65-4943-8e74-0ec13fd46592 became leader Jan 29 01:26:53.852: INFO: event for kube-controller-manager: {kube-controller-manager } LeaderElection: bootstrap-e2e-master_6badf177-8bbb-4583-875c-aa41b992d5db became leader Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/network-unavailable: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-dns-autoscaler-5f6455f985-q8wlx to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" in 3.257319276s (3.25733442s including waiting) Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container autoscaler Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container autoscaler Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.4" already present on machine Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container autoscaler Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container autoscaler Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container autoscaler Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container autoscaler in pod kube-dns-autoscaler-5f6455f985-q8wlx_kube-system(55334095-1e4d-4edc-8b27-9cc4df9ecbd3) Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985-q8wlx: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/kube-dns-autoscaler-5f6455f985-q8wlx Jan 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for kube-dns-autoscaler-5f6455f985: {replicaset-controller } SuccessfulCreate: Created pod: kube-dns-autoscaler-5f6455f985-q8wlx Jan 29 01:26:53.852: INFO: event for kube-dns-autoscaler: {deployment-controller } ScalingReplicaSet: Scaled up replica set kube-dns-autoscaler-5f6455f985 to 1 Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-g5dw_kube-system(e39fd6ebeea66df97e7d4159e056ca89) Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-g5dw_kube-system(e39fd6ebeea66df97e7d4159e056ca89) Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} DNSConfigForming: Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 1.1.1.1 8.8.8.8 1.0.0.1 Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-g5dw: {kubelet bootstrap-e2e-minion-group-g5dw} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-g5dw_kube-system(e39fd6ebeea66df97e7d4159e056ca89) Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-nh1n_kube-system(104cab07fdbff6cd1903c2461a9ed07c) Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-nh1n_kube-system(104cab07fdbff6cd1903c2461a9ed07c) Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} DNSConfigForming: Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 1.1.1.1 8.8.8.8 1.0.0.1 Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-nh1n: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container kube-proxy Jan 29 01:26:53.852: INFO: event for kube-proxy-bootstrap-e2e-minion-group-rv7m: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container kube-proxy in pod kube-proxy-bootstrap-e2e-minion-group-rv7m_kube-system(e73c874f32f53e94265ad545cac1eda7) Jan 29 01:26:53.852: 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.73_8e642d3d0deab2" already present on machine Jan 29 01:26:53.852: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container kube-scheduler Jan 29 01:26:53.852: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container kube-scheduler Jan 29 01:26:53.852: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container kube-scheduler Jan 29 01:26:53.852: INFO: event for kube-scheduler-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: 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(b286b0d19b475d76fb3eba5bf7889986) Jan 29 01:26:53.852: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_387c967a-2bea-42c5-8d9d-29752e15ad1e became leader Jan 29 01:26:53.852: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_5629d3d6-315a-4014-9ea2-880de5dc36cb became leader Jan 29 01:26:53.852: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_9e80c6f9-7dfe-4bf1-b855-7b6e2cb9f58f became leader Jan 29 01:26:53.852: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_4a934c05-3be8-41bd-a143-bb43e3c6db0f became leader Jan 29 01:26:53.852: INFO: event for kube-scheduler: {default-scheduler } LeaderElection: bootstrap-e2e-master_76e7c4f7-1b27-465e-8e19-1fa4bd808ad9 became leader Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {default-scheduler } Scheduled: Successfully assigned kube-system/l7-default-backend-8549d69d99-4x6fk to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" in 561.173126ms (561.189036ms including waiting) Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container default-http-backend Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container default-http-backend Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container default-http-backend Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/networking/ingress-gce-404-server-with-metrics-amd64:v1.10.11" already present on machine Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container default-http-backend Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/l7-default-backend-8549d69d99-4x6fk Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99-4x6fk: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container default-http-backend Jan 29 01:26:53.852: INFO: event for l7-default-backend-8549d69d99: {replicaset-controller } SuccessfulCreate: Created pod: l7-default-backend-8549d69d99-4x6fk Jan 29 01:26:53.852: INFO: event for l7-default-backend: {deployment-controller } ScalingReplicaSet: Scaled up replica set l7-default-backend-8549d69d99 to 1 Jan 29 01:26:53.852: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Created: Created container l7-lb-controller Jan 29 01:26:53.852: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Started: Started container l7-lb-controller Jan 29 01:26:53.852: 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 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for l7-lb-controller-bootstrap-e2e-master: {kubelet bootstrap-e2e-master} Killing: Stopping container l7-lb-controller Jan 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-dvtn5 to bootstrap-e2e-minion-group-g5dw Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 711.133904ms (711.172606ms including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.895066142s (1.895075509s including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} DNSConfigForming: Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 1.1.1.1 8.8.8.8 1.0.0.1 Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-dvtn5: {kubelet bootstrap-e2e-minion-group-g5dw} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-gcl7f to bootstrap-e2e-master Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 754.286639ms (754.296219ms including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.036284591s (2.036292283s including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-gcl7f: {kubelet bootstrap-e2e-master} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-ghdmf to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 780.74172ms (780.754027ms including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 2.00237082s (2.002396906s including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-ghdmf: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {default-scheduler } Scheduled: Successfully assigned kube-system/metadata-proxy-v0.1-tdckz to bootstrap-e2e-minion-group-nh1n Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulling: Pulling image "registry.k8s.io/metadata-proxy:v0.1.12" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Successfully pulled image "registry.k8s.io/metadata-proxy:v0.1.12" in 779.441797ms (779.481299ms including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulling: Pulling image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Successfully pulled image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" in 1.928968958s (1.929001469s including waiting) Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} DNSConfigForming: Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 1.1.1.1 8.8.8.8 1.0.0.1 Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/metadata-proxy:v0.1.12" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metadata-proxy Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "gke.gcr.io/prometheus-to-sd:v0.11.1-gke.1" already present on machine Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1-tdckz: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container prometheus-to-sd-exporter Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-ghdmf Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-gcl7f Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-tdckz Jan 29 01:26:53.852: INFO: event for metadata-proxy-v0.1: {daemonset-controller } SuccessfulCreate: Created pod: metadata-proxy-v0.1-dvtn5 Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-6764bf875c-zcmcd to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 1.894622627s (1.894645738s including waiting) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 2.971768754s (2.971778948s including waiting) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container metrics-server in pod metrics-server-v0.5.2-6764bf875c-zcmcd_kube-system(51f812ec-6d0a-45bb-9ff5-261329977c3d) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c-zcmcd: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container metrics-server-nanny in pod metrics-server-v0.5.2-6764bf875c-zcmcd_kube-system(51f812ec-6d0a-45bb-9ff5-261329977c3d) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-6764bf875c-zcmcd Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-6764bf875c: {replicaset-controller } SuccessfulDelete: Deleted pod: metrics-server-v0.5.2-6764bf875c-zcmcd Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: { } Scheduled: Successfully assigned kube-system/metrics-server-v0.5.2-867b8754b9-9p9nx to bootstrap-e2e-minion-group-nh1n Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulling: Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Successfully pulled image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" in 1.375361805s (1.375372092s including waiting) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulling: Pulling image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Successfully pulled image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" in 1.029212495s (1.029231089s including waiting) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.3:10250/readyz": dial tcp 10.64.2.3:10250: connect: connection refused Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Liveness probe failed: Get "https://10.64.2.3:10250/livez": dial tcp 10.64.2.3:10250: connect: connection refused Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.3:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Liveness probe failed: Get "https://10.64.2.3:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/metrics-server-v0.5.2-867b8754b9-9p9nx Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.4:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.7:10250/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Liveness probe failed: Get "https://10.64.2.7:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.7:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} BackOff: Back-off restarting failed container metrics-server in pod metrics-server-v0.5.2-867b8754b9-9p9nx_kube-system(12c6e9b1-49f1-4dcd-844a-53879548296f) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} BackOff: Back-off restarting failed container metrics-server-nanny in pod metrics-server-v0.5.2-867b8754b9-9p9nx_kube-system(12c6e9b1-49f1-4dcd-844a-53879548296f) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: (combined from similar events): Readiness probe failed: HTTP probe failed with statuscode: 500 Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/metrics-server/metrics-server:v0.5.2" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/metrics-server-v0.5.2-867b8754b9-9p9nx Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Pulled: Container image "registry.k8s.io/autoscaling/addon-resizer:1.8.14" already present on machine Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Created: Created container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Started: Started container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.11:10250/readyz": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Readiness probe failed: Get "https://10.64.2.11:10250/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Unhealthy: Liveness probe failed: Get "https://10.64.2.11:10250/livez": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container metrics-server Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Stopping container metrics-server-nanny Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Killing: Container metrics-server failed liveness probe, will be restarted Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} Failed: Error: failed to get sandbox container task: no running task found: task b32daf6ccf79d96010928de0e5c6d14f251f0f859fc2fd24cd0d2ef2b0a55cff not found: not found Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9-9p9nx: {kubelet bootstrap-e2e-minion-group-nh1n} BackOff: Back-off restarting failed container metrics-server in pod metrics-server-v0.5.2-867b8754b9-9p9nx_kube-system(12c6e9b1-49f1-4dcd-844a-53879548296f) Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2-867b8754b9: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-v0.5.2-867b8754b9-9p9nx Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-v0.5.2-6764bf875c to 1 Jan 29 01:26:53.852: INFO: event for metrics-server-v0.5.2: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-v0.5.2-867b8754b9 to 1 Jan 29 01:26:53.852: 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 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: no nodes available to schedule pods Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {default-scheduler } Scheduled: Successfully assigned kube-system/volume-snapshot-controller-0 to bootstrap-e2e-minion-group-rv7m Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Pulling: Pulling image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Successfully pulled image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" in 3.526692937s (3.526702972s including waiting) Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(0c51547a-104f-4b7e-b495-4722734ddb26) Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(0c51547a-104f-4b7e-b495-4722734ddb26) Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {node-controller } NodeNotReady: Node is not ready Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} SandboxChanged: Pod sandbox changed, it will be killed and re-created. Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Pulled: Container image "registry.k8s.io/sig-storage/snapshot-controller:v6.1.0" already present on machine Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/volume-snapshot-controller-0 Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Created: Created container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Started: Started container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} Killing: Stopping container volume-snapshot-controller Jan 29 01:26:53.852: INFO: event for volume-snapshot-controller-0: {kubelet bootstrap-e2e-minion-group-rv7m} BackOff: Back-off restarting failed container volume-snapshot-controller in pod volume-snapshot-controller-0_kube-system(0c51547a-104f-4b7e-b495-4722734ddb26) Jan 29 01:26:53.852: 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/29/23 01:26:53.852 (54ms) > Enter [AfterEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/node/init/init.go:33 @ 01/29/23 01:26:53.852 Jan 29 01:26:53.852: 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/29/23 01:26:53.895 (43ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/29/23 01:26:53.895 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:35 @ 01/29/23 01:26:53.895 (0s) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/29/23 01:26:53.895 STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/29/23 01:26:53.896 STEP: Collecting events from namespace "reboot-1201". - test/e2e/framework/debug/dump.go:42 @ 01/29/23 01:26:53.896 STEP: Found 0 events. - test/e2e/framework/debug/dump.go:46 @ 01/29/23 01:26:53.937 Jan 29 01:26:53.981: INFO: POD NODE PHASE GRACE CONDITIONS Jan 29 01:26:53.981: INFO: Jan 29 01:26:54.024: INFO: Logging node info for node bootstrap-e2e-master Jan 29 01:26:54.140: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-master 11da0fa8-1a8b-4cc5-8d12-b293d7c50bd8 3905 0 2023-01-29 00:56:38 +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-29 00:56:38 +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-29 00:56:56 +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-29 00:57:03 +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\"":{}},"f:taints":{}}} } {kubelet Update v1 2023-01-29 01:23:01 +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.1.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-ubuntu/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.1.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-29 00:56:56 +0000 UTC,LastTransitionTime:2023-01-29 00:56:56 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-29 01:23:01 +0000 UTC,LastTransitionTime:2023-01-29 00:56:38 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-29 01:23:01 +0000 UTC,LastTransitionTime:2023-01-29 00:56:38 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-29 01:23:01 +0000 UTC,LastTransitionTime:2023-01-29 00:56:38 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-29 01:23:01 +0000 UTC,LastTransitionTime:2023-01-29 00:56:59 +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.197.23.89,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-master.c.k8s-jkns-e2e-gce-ubuntu.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-master.c.k8s-jkns-e2e-gce-ubuntu.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:bb30a7522713b1d3fb0ea758b3e0db97,SystemUUID:bb30a752-2713-b1d3-fb0e-a758b3e0db97,BootID:e3506071-57f4-4335-a9f0-5097284b165b,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-2-gaccb53cab,KubeletVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,KubeProxyVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-apiserver-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2],SizeBytes:135952851,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2],SizeBytes:125275449,},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.73_8e642d3d0deab2],SizeBytes:57552184,},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 29 01:26:54.140: INFO: Logging kubelet events for node bootstrap-e2e-master Jan 29 01:26:54.194: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-master Jan 29 01:26:54.243: INFO: Unable to retrieve kubelet pods for node bootstrap-e2e-master: error trying to reach service: No agent available Jan 29 01:26:54.243: INFO: Logging node info for node bootstrap-e2e-minion-group-g5dw Jan 29 01:26:54.298: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-g5dw ad80a01d-7a39-41e6-a452-8c1a441f9ba8 4052 0 2023-01-29 00:56:40 +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-g5dw 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-29 00:56:40 +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-29 01:18:06 +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-29 01:18:43 +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-29 01:24:25 +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-29 01:24:28 +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.3.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-ubuntu/us-west1-b/bootstrap-e2e-minion-group-g5dw,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: {{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:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-29 01:24:13 +0000 UTC,LastTransitionTime:2023-01-29 01:18:42 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-29 00:56:56 +0000 UTC,LastTransitionTime:2023-01-29 00:56:56 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-29 01:24:25 +0000 UTC,LastTransitionTime:2023-01-29 01:18:43 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-29 01:24:25 +0000 UTC,LastTransitionTime:2023-01-29 01:18:43 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-29 01:24:25 +0000 UTC,LastTransitionTime:2023-01-29 01:18:43 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-29 01:24:25 +0000 UTC,LastTransitionTime:2023-01-29 01:18:43 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:10.138.0.3,},NodeAddress{Type:ExternalIP,Address:34.82.165.19,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-g5dw.c.k8s-jkns-e2e-gce-ubuntu.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-g5dw.c.k8s-jkns-e2e-gce-ubuntu.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:fcd9c1d4705412851774a846f798e37b,SystemUUID:fcd9c1d4-7054-1285-1774-a846f798e37b,BootID:c10731fd-30bc-4c7d-9adc-1303f79a1fbb,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-2-gaccb53cab,KubeletVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,KubeProxyVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2],SizeBytes:66989256,},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/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 29 01:26:54.298: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-g5dw Jan 29 01:26:54.354: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-g5dw Jan 29 01:26:54.440: INFO: Unable to retrieve kubelet pods for node bootstrap-e2e-minion-group-g5dw: error trying to reach service: No agent available Jan 29 01:26:54.440: INFO: Logging node info for node bootstrap-e2e-minion-group-nh1n Jan 29 01:26:54.486: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-nh1n b9139680-2ebc-4c9b-b071-8d99a2c3eb72 4009 0 2023-01-29 00:56:38 +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-nh1n 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-29 00:56:38 +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-29 01:17:46 +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-29 01:18:28 +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-29 01:24:03 +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-29 01:24:03 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"CorruptDockerOverlay2\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentContainerdRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentDockerRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentKubeletRestart\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"FrequentUnregisterNetDevice\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"KernelDeadlock\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"ReadonlyFilesystem\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.2.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-ubuntu/us-west1-b/bootstrap-e2e-minion-group-nh1n,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.2.0/24],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{101203873792 0} {<nil>} 98831908Ki BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7815438336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-gce-pd: {{127 0} {<nil>} 127 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{91083486262 0} {<nil>} 91083486262 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{7553294336 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-29 01:23:58 +0000 UTC,LastTransitionTime:2023-01-29 01:18:27 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-29 00:56:56 +0000 UTC,LastTransitionTime:2023-01-29 00:56:56 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-29 01:24:03 +0000 UTC,LastTransitionTime:2023-01-29 01:18:28 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-29 01:24:03 +0000 UTC,LastTransitionTime:2023-01-29 01:18:28 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-29 01:24:03 +0000 UTC,LastTransitionTime:2023-01-29 01:18:28 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-29 01:24:03 +0000 UTC,LastTransitionTime:2023-01-29 01:18:28 +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:35.230.114.56,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-nh1n.c.k8s-jkns-e2e-gce-ubuntu.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-nh1n.c.k8s-jkns-e2e-gce-ubuntu.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:2aed66ad76d7b78e16e13073a095e31a,SystemUUID:2aed66ad-76d7-b78e-16e1-3073a095e31a,BootID:933d589b-aca7-4290-9b0f-b063e2972d9d,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-2-gaccb53cab,KubeletVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,KubeProxyVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2],SizeBytes:66989256,},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 29 01:26:54.486: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-nh1n Jan 29 01:26:54.545: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-nh1n Jan 29 01:26:54.594: INFO: Unable to retrieve kubelet pods for node bootstrap-e2e-minion-group-nh1n: error trying to reach service: No agent available Jan 29 01:26:54.594: INFO: Logging node info for node bootstrap-e2e-minion-group-rv7m Jan 29 01:26:54.637: INFO: Node Info: &Node{ObjectMeta:{bootstrap-e2e-minion-group-rv7m 4dbab00b-ec6a-408f-8d83-d0f6e496b11d 3920 0 2023-01-29 00:56:35 +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-rv7m 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-29 00:56:35 +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-29 01:02:01 +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-29 01:02:42 +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\"":{}}}} } {node-problem-detector Update v1 2023-01-29 01:22:45 +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-29 01:23:07 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{},"f:nodeInfo":{"f:bootID":{}}}} status}]},Spec:NodeSpec{PodCIDR:10.64.0.0/24,DoNotUseExternalID:,ProviderID:gce://k8s-jkns-e2e-gce-ubuntu/us-west1-b/bootstrap-e2e-minion-group-rv7m,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[10.64.0.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:KernelDeadlock,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:KernelHasNoDeadlock,Message:kernel has no deadlock,},NodeCondition{Type:ReadonlyFilesystem,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:FilesystemIsNotReadOnly,Message:Filesystem is not read-only,},NodeCondition{Type:FrequentKubeletRestart,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:NoFrequentKubeletRestart,Message:kubelet is functioning properly,},NodeCondition{Type:FrequentDockerRestart,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:NoFrequentDockerRestart,Message:docker is functioning properly,},NodeCondition{Type:FrequentContainerdRestart,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:NoFrequentContainerdRestart,Message:containerd is functioning properly,},NodeCondition{Type:FrequentUnregisterNetDevice,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:NoFrequentUnregisterNetDevice,Message:node is functioning properly,},NodeCondition{Type:CorruptDockerOverlay2,Status:False,LastHeartbeatTime:2023-01-29 01:22:45 +0000 UTC,LastTransitionTime:2023-01-29 01:02:41 +0000 UTC,Reason:NoCorruptDockerOverlay2,Message:docker overlay2 is functioning properly,},NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-29 00:56:44 +0000 UTC,LastTransitionTime:2023-01-29 00:56:44 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-29 01:23:07 +0000 UTC,LastTransitionTime:2023-01-29 01:02:42 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-29 01:23:07 +0000 UTC,LastTransitionTime:2023-01-29 01:02:42 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-29 01:23:07 +0000 UTC,LastTransitionTime:2023-01-29 01:02:42 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-29 01:23:07 +0000 UTC,LastTransitionTime:2023-01-29 01:02:42 +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.105.95.109,},NodeAddress{Type:InternalDNS,Address:bootstrap-e2e-minion-group-rv7m.c.k8s-jkns-e2e-gce-ubuntu.internal,},NodeAddress{Type:Hostname,Address:bootstrap-e2e-minion-group-rv7m.c.k8s-jkns-e2e-gce-ubuntu.internal,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:646286d0db94eda1af78c3035cef9a0b,SystemUUID:646286d0-db94-eda1-af78-c3035cef9a0b,BootID:98c06424-41ae-40f7-975a-b5e68745d8d4,KernelVersion:5.10.123+,OSImage:Container-Optimized OS from Google,ContainerRuntimeVersion:containerd://1.7.0-beta.3-2-gaccb53cab,KubeletVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,KubeProxyVersion:v1.27.0-alpha.1.73+8e642d3d0deab2,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/kube-proxy-amd64:v1.27.0-alpha.1.73_8e642d3d0deab2],SizeBytes:66989256,},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 29 01:26:54.639: INFO: Logging kubelet events for node bootstrap-e2e-minion-group-rv7m Jan 29 01:26:54.700: INFO: Logging pods the kubelet thinks is on node bootstrap-e2e-minion-group-rv7m Jan 29 01:26:54.748: INFO: Unable to retrieve kubelet pods for node bootstrap-e2e-minion-group-rv7m: error trying to reach service: No agent available END STEP: dump namespace information after failure - test/e2e/framework/framework.go:284 @ 01/29/23 01:26:54.748 (852ms) < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - dump namespaces | framework.go:206 @ 01/29/23 01:26:54.748 (852ms) > Enter [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/29/23 01:26:54.748 STEP: Destroying namespace "reboot-1201" for this suite. - test/e2e/framework/framework.go:347 @ 01/29/23 01:26:54.748 < Exit [DeferCleanup (Each)] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - tear down framework | framework.go:203 @ 01/29/23 01:26:54.799 (52ms) > Enter [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/29/23 01:26:54.8 < Exit [ReportAfterEach] TOP-LEVEL - test/e2e/e2e_test.go:144 @ 01/29/23 01:26:54.8 (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/29/23 01:12:52.495
> Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/29/23 01:07:49.991 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/cloud/gcp/reboot.go:60 @ 01/29/23 01:07:49.991 (0s) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/29/23 01:07:49.991 STEP: Creating a kubernetes client - test/e2e/framework/framework.go:208 @ 01/29/23 01:07:49.991 Jan 29 01:07:49.991: INFO: >>> kubeConfig: /workspace/.kube/config STEP: Building a namespace api object, basename reboot - test/e2e/framework/framework.go:247 @ 01/29/23 01:07:49.996 STEP: Waiting for a default service account to be provisioned in namespace - test/e2e/framework/framework.go:256 @ 01/29/23 01:07:50.131 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace - test/e2e/framework/framework.go:259 @ 01/29/23 01:07:50.22 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - set up framework | framework.go:188 @ 01/29/23 01:07:50.313 (322ms) > Enter [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/29/23 01:07:50.313 < Exit [BeforeEach] [sig-cloud-provider-gcp] Reboot [Disruptive] [Feature:Reboot] - test/e2e/framework/metrics/init/init.go:33 @ 01/29/23 01:07:50.313 (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/29/23 01:07:50.313 Jan 29 01:07:50.427: INFO: Getting bootstrap-e2e-minion-group-g5dw Jan 29 01:07:50.462: INFO: Getting bootstrap-e2e-minion-group-rv7m Jan 29 01:07:50.475: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-g5dw condition Ready to be true Jan 29 01:07:50.475: INFO: Getting bootstrap-e2e-minion-group-nh1n Jan 29 01:07:50.509: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-rv7m condition Ready to be true Jan 29 01:07:50.522: INFO: Node bootstrap-e2e-minion-group-g5dw has 2 assigned pods with no liveness probes: [kube-proxy-bootstrap-e2e-minion-group-g5dw metadata-proxy-v0.1-dvtn5] Jan 29 01:07:50.522: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-g5dw metadata-proxy-v0.1-dvtn5] Jan 29 01:07:50.522: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-dvtn5" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:07:50.522: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-g5dw" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:07:50.525: INFO: Waiting up to 20s for node bootstrap-e2e-minion-group-nh1n condition Ready to be true Jan 29 01:07:50.557: INFO: Node bootstrap-e2e-minion-group-rv7m has 4 assigned pods with no liveness probes: [metadata-proxy-v0.1-ghdmf volume-snapshot-controller-0 kube-dns-autoscaler-5f6455f985-q8wlx kube-proxy-bootstrap-e2e-minion-group-rv7m] Jan 29 01:07:50.557: INFO: Waiting up to 5m0s for 4 pods to be running and ready, or succeeded: [metadata-proxy-v0.1-ghdmf volume-snapshot-controller-0 kube-dns-autoscaler-5f6455f985-q8wlx kube-proxy-bootstrap-e2e-minion-group-rv7m] Jan 29 01:07:50.557: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-rv7m" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:07:50.560: INFO: Waiting up to 5m0s for pod "volume-snapshot-controller-0" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:07:50.560: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-ghdmf" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:07:50.561: INFO: Waiting up to 5m0s for pod "kube-dns-autoscaler-5f6455f985-q8wlx" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:07:50.577: INFO: Pod "metadata-proxy-v0.1-dvtn5": Phase="Running", Reason="", readiness=true. Elapsed: 55.079809ms Jan 29 01:07:50.577: INFO: Pod "metadata-proxy-v0.1-dvtn5" satisfied condition "running and ready, or succeeded" Jan 29 01:07:50.577: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=true. Elapsed: 54.67097ms Jan 29 01:07:50.577: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw" satisfied condition "running and ready, or succeeded" Jan 29 01:07:50.577: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-g5dw metadata-proxy-v0.1-dvtn5] Jan 29 01:07:50.577: INFO: Getting external IP address for bootstrap-e2e-minion-group-g5dw Jan 29 01:07:50.577: 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-g5dw(34.82.165.19:22) Jan 29 01:07:50.578: INFO: Node bootstrap-e2e-minion-group-nh1n has 2 assigned pods with no liveness probes: [metadata-proxy-v0.1-tdckz kube-proxy-bootstrap-e2e-minion-group-nh1n] Jan 29 01:07:50.578: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [metadata-proxy-v0.1-tdckz kube-proxy-bootstrap-e2e-minion-group-nh1n] Jan 29 01:07:50.578: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-nh1n" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:07:50.578: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-tdckz" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:07:50.607: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 46.517658ms Jan 29 01:07:50.607: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:07:50.607: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 46.54022ms Jan 29 01:07:50.607: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:07:50.607: INFO: Pod "metadata-proxy-v0.1-ghdmf": Phase="Running", Reason="", readiness=true. Elapsed: 47.054299ms Jan 29 01:07:50.607: INFO: Pod "metadata-proxy-v0.1-ghdmf" satisfied condition "running and ready, or succeeded" Jan 29 01:07:50.607: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 50.199987ms Jan 29 01:07:50.607: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:07:39 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:07:39 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:07:50.634: INFO: Pod "metadata-proxy-v0.1-tdckz": Phase="Running", Reason="", readiness=true. Elapsed: 55.514815ms Jan 29 01:07:50.634: INFO: Pod "metadata-proxy-v0.1-tdckz" satisfied condition "running and ready, or succeeded" Jan 29 01:07:50.634: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-nh1n": Phase="Running", Reason="", readiness=true. Elapsed: 56.467223ms Jan 29 01:07:50.634: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-nh1n" satisfied condition "running and ready, or succeeded" Jan 29 01:07:50.634: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [metadata-proxy-v0.1-tdckz kube-proxy-bootstrap-e2e-minion-group-nh1n] Jan 29 01:07:50.634: INFO: Getting external IP address for bootstrap-e2e-minion-group-nh1n Jan 29 01:07:50.634: 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-nh1n(35.230.114.56:22) Jan 29 01:07:51.129: INFO: ssh prow@34.82.165.19: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 29 01:07:51.129: INFO: ssh prow@34.82.165.19:22: stdout: "" Jan 29 01:07:51.129: INFO: ssh prow@34.82.165.19:22: stderr: "" Jan 29 01:07:51.129: INFO: ssh prow@34.82.165.19:22: exit code: 0 Jan 29 01:07:51.129: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-g5dw condition Ready to be false Jan 29 01:07:51.176: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:07:51.204: INFO: ssh prow@35.230.114.56: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 29 01:07:51.204: INFO: ssh prow@35.230.114.56:22: stdout: "" Jan 29 01:07:51.204: INFO: ssh prow@35.230.114.56:22: stderr: "" Jan 29 01:07:51.204: INFO: ssh prow@35.230.114.56:22: exit code: 0 Jan 29 01:07:51.204: INFO: Waiting up to 2m0s for node bootstrap-e2e-minion-group-nh1n condition Ready to be false Jan 29 01:07:51.248: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:07:52.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2.090182501s Jan 29 01:07:52.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:07:52.651: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 2.091215249s Jan 29 01:07:52.652: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:07:52.661: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=false. Elapsed: 2.104098357s Jan 29 01:07:52.662: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-proxy-bootstrap-e2e-minion-group-rv7m' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:07:39 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:07:39 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:35 +0000 UTC }] Jan 29 01:07:53.224: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:07:53.295: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:07:54.656: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 4.095754717s Jan 29 01:07:54.660: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m": Phase="Running", Reason="", readiness=true. Elapsed: 4.102625251s Jan 29 01:07:54.660: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-rv7m" satisfied condition "running and ready, or succeeded" Jan 29 01:07:54.660: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:07:54.661: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4.100464373s Jan 29 01:07:54.661: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:07:55.301: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:07:55.350: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:07:56.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 6.092293255s Jan 29 01:07:56.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:07:56.653: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 6.093051877s Jan 29 01:07:56.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:07:57.353: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:07:57.397: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:07:58.653: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 8.092686314s Jan 29 01:07:58.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:07:58.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 8.092614253s Jan 29 01:07:58.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:07:59.399: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:07:59.444: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:00.655: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 10.094333332s Jan 29 01:08:00.655: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:00.655: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 10.095230501s Jan 29 01:08:00.656: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:01.445: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:01.492: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:02.657: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 12.096715042s Jan 29 01:08:02.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:02.660: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 12.099767899s Jan 29 01:08:02.660: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:03.491: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:03.544: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:04.692: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 14.131354169s Jan 29 01:08:04.692: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:04.692: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 14.131456534s Jan 29 01:08:04.692: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:05.536: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:05.589: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:06.653: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 16.092694802s Jan 29 01:08:06.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:06.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 16.092862183s Jan 29 01:08:06.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:07.583: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:07.635: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:08.653: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 18.092848189s Jan 29 01:08:08.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:08.654: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 18.09300357s Jan 29 01:08:08.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:09.631: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:09.680: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:10.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 20.09283318s Jan 29 01:08:10.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:10.654: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 20.093564701s Jan 29 01:08:10.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:11.681: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:11.725: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:12.660: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 22.099280681s Jan 29 01:08:12.660: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:12.677: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 22.116328645s Jan 29 01:08:12.677: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:13.729: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:13.773: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:14.654: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 24.09363374s Jan 29 01:08:14.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:14.655: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 24.094351704s Jan 29 01:08:14.655: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:15.775: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:15.818: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:16.658: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 26.097011906s Jan 29 01:08:16.658: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:16.658: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 26.097957703s Jan 29 01:08:16.658: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:17.821: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:17.873: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:18.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 28.092524723s Jan 29 01:08:18.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:18.653: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 28.093198291s Jan 29 01:08:18.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:19.869: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:19.919: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:20.654: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 30.093682822s Jan 29 01:08:20.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:20.654: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 30.093781589s Jan 29 01:08:20.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:21.921: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:21.964: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:22.653: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 32.093105759s Jan 29 01:08:22.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:22.654: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 32.092938126s Jan 29 01:08:22.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:23.965: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:24.014: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:24.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 34.092618065s Jan 29 01:08:24.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:24.656: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 34.095507893s Jan 29 01:08:24.656: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:26.009: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:26.057: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:26.652: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=false. Elapsed: 36.091488857s Jan 29 01:08:26.652: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'volume-snapshot-controller-0' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:06:55 +0000 UTC ContainersNotReady containers with unready status: [volume-snapshot-controller]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:26.652: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 36.091470463s Jan 29 01:08:26.652: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:28.055: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:28.103: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:28.665: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 38.104241108s Jan 29 01:08:28.665: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:28.665: INFO: Pod "volume-snapshot-controller-0": Phase="Running", Reason="", readiness=true. Elapsed: 38.104789167s Jan 29 01:08:28.665: INFO: Pod "volume-snapshot-controller-0" satisfied condition "running and ready, or succeeded" Jan 29 01:08:30.101: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:30.160: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:30.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 40.0899537s Jan 29 01:08:30.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:32.149: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:32.206: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:32.652: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 42.091010513s Jan 29 01:08:32.652: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:34.197: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:34.255: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true instead of false. Reason: KubeletReady, message: kubelet is posting ready status. AppArmor enabled Jan 29 01:08:34.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 44.092126973s Jan 29 01:08:34.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:36.243: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-g5dw condition Ready to be true Jan 29 01:08:36.290: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 29 01:08:36.325: INFO: Waiting up to 5m0s for node bootstrap-e2e-minion-group-nh1n condition Ready to be true Jan 29 01:08:36.369: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 29 01:08:36.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 46.090237141s Jan 29 01:08:36.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:38.343: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 29 01:08:38.416: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 29 01:08:38.658: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 48.09707365s Jan 29 01:08:38.658: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:40.399: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:08:40.460: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 29 01:08:40.655: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 50.094792963s Jan 29 01:08:40.655: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:42.453: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:08:42.509: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 29 01:08:42.655: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 52.094703798s Jan 29 01:08:42.655: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:44.501: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:08:44.556: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 29 01:08:44.654: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 54.093014375s Jan 29 01:08:44.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:46.549: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:08:46.612: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 29 01:08:46.656: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 56.095651133s Jan 29 01:08:46.656: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:48.593: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:08:48.655: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 58.09395921s Jan 29 01:08:48.655: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:48.663: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false instead of true. Reason: NodeStatusUnknown, message: Kubelet stopped posting node status. Jan 29 01:08:50.641: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:08:50.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m0.089864321s Jan 29 01:08:50.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:50.718: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:08:52.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m2.090562143s Jan 29 01:08:52.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:52.693: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:08:52.768: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:08:54.654: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m4.093872294s Jan 29 01:08:54.655: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:54.745: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:08:54.821: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:08:56.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m6.089504862s Jan 29 01:08:56.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:56.804: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:08:56.865: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:08:58.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m8.092845198s Jan 29 01:08:58.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:08:58.850: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:08:58.913: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:09:00.654: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m10.093510414s Jan 29 01:09:00.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:09:00.895: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:09:00.958: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:09:02.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m12.092238831s Jan 29 01:09:02.655: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:09:02.941: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:09:03.009: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:09:04.654: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m14.093003242s Jan 29 01:09:04.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:09:04.987: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:09:05.057: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:09:06.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m16.092384482s Jan 29 01:09:06.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:09:07.036: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:09:07.101: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:09:08.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m18.090396728s Jan 29 01:09:08.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:09:09.084: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:09:09.153: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:09:10.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m20.089995278s Jan 29 01:09:10.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:09:11.129: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:09:11.198: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:09:12.654: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m22.092918565s Jan 29 01:09:12.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:09:13.181: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:09:13.248: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:09:14.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m24.092879727s Jan 29 01:09:14.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:09:15.230: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:09:15.295: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:09:16.658: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 1m26.097015611s Jan 29 01:09:16.658: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:09:58.083: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:09:58.083: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:00.130: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:00.130: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is false, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:01.405: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m10.84392815s Jan 29 01:10:01.405: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:02.177: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:02.180: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:02.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m12.089408782s Jan 29 01:10:02.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:04.223: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:04.229: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:04.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m14.091969543s Jan 29 01:10:04.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:06.273: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:06.275: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:06.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m16.089340854s Jan 29 01:10:06.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:08.321: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:08.334: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:08.654: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m18.093842957s Jan 29 01:10:08.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:10.365: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:10.380: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:10.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m20.090745318s Jan 29 01:10:10.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:12.409: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:12.423: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:12.649: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m22.088556566s Jan 29 01:10:12.649: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:14.455: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:14.471: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:14.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m24.089216097s Jan 29 01:10:14.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:16.501: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:16.521: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:16.656: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m26.095588378s Jan 29 01:10:16.656: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:18.544: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:18.564: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:18.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m28.089805615s Jan 29 01:10:18.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:20.589: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:20.612: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:20.654: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m30.093307463s Jan 29 01:10:20.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:22.632: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:22.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m32.089355356s Jan 29 01:10:22.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:22.656: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:24.656: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m34.095873821s Jan 29 01:10:24.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:24.679: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:24.698: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:26.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m36.089290885s Jan 29 01:10:26.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:26.722: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:26.741: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:28.656: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m38.095906417s Jan 29 01:10:28.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:28.767: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:28.786: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:30.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m40.091982492s Jan 29 01:10:30.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:30.811: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:30.829: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:32.649: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m42.088644025s Jan 29 01:10:32.649: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:32.854: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:32.875: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:34.652: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m44.091893739s Jan 29 01:10:34.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:34.901: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:34.921: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:36.657: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m46.095978406s Jan 29 01:10:36.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:36.943: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:36.964: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:38.656: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m48.095908476s Jan 29 01:10:38.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:38.989: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:39.011: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:40.649: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m50.088169809s Jan 29 01:10:40.649: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:41.032: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:41.054: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:42.649: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m52.088542525s Jan 29 01:10:42.649: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:43.077: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:43.097: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:44.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m54.092139402s Jan 29 01:10:44.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:45.120: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:45.140: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:46.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m56.092130604s Jan 29 01:10:46.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:47.165: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:47.185: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:48.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 2m58.08925605s Jan 29 01:10:48.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:49.208: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:49.227: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:50.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m0.089612269s Jan 29 01:10:50.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:51.252: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:51.269: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:52.652: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m2.091904923s Jan 29 01:10:52.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:53.297: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:53.312: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:54.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m4.090046763s Jan 29 01:10:54.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:55.345: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:55.361: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:56.677: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m6.116276642s Jan 29 01:10:56.677: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:57.393: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:57.409: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:10:58.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m8.091957774s Jan 29 01:10:58.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:10:59.441: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:10:59.456: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:11:00.649: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m10.088602584s Jan 29 01:11:00.649: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:01.484: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:11:01.498: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:11:02.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m12.091929431s Jan 29 01:11:02.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:03.528: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:11:03.545: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:11:04.657: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m14.096016435s Jan 29 01:11:04.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:05.572: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:11:05.592: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:11:06.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m16.091943768s Jan 29 01:11:06.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:07.621: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:11:07.641: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:11:08.649: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m18.088885622s Jan 29 01:11:08.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:09.673: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:11:09.688: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:11:10.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m20.092050043s Jan 29 01:11:10.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:11.717: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:11:11.731: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:11:12.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m22.090004873s Jan 29 01:11:12.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:13.761: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:11:13.775: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:11:14.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m24.092118986s Jan 29 01:11:14.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:15.813: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:11:15.821: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:11:16.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m26.089295821s Jan 29 01:11:16.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:17.861: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:11:17.868: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:11:18.657: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m28.09597241s Jan 29 01:11:18.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:19.906: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:11:19.916: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:11:20.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m30.089182615s Jan 29 01:11:20.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:21.953: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:11:21.961: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:11:22.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m32.089290533s Jan 29 01:11:22.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:24.001: INFO: Condition Ready of node bootstrap-e2e-minion-group-nh1n is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:50 +0000 UTC}]. Failure Jan 29 01:11:24.007: INFO: Condition Ready of node bootstrap-e2e-minion-group-g5dw is true, but Node is tainted by NodeController with [{node.kubernetes.io/unreachable NoSchedule 2023-01-29 01:08:34 +0000 UTC} {node.kubernetes.io/unreachable NoExecute 2023-01-29 01:08:40 +0000 UTC}]. Failure Jan 29 01:11:24.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m34.091996762s Jan 29 01:11:24.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:26.044: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [metadata-proxy-v0.1-tdckz kube-proxy-bootstrap-e2e-minion-group-nh1n] Jan 29 01:11:26.044: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-nh1n" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:11:26.044: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-tdckz" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:11:26.050: INFO: Waiting up to 5m0s for 2 pods to be running and ready, or succeeded: [kube-proxy-bootstrap-e2e-minion-group-g5dw metadata-proxy-v0.1-dvtn5] Jan 29 01:11:26.050: INFO: Waiting up to 5m0s for pod "metadata-proxy-v0.1-dvtn5" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:11:26.050: INFO: Waiting up to 5m0s for pod "kube-proxy-bootstrap-e2e-minion-group-g5dw" in namespace "kube-system" to be "running and ready, or succeeded" Jan 29 01:11:26.088: INFO: Pod "metadata-proxy-v0.1-tdckz": Phase="Running", Reason="", readiness=true. Elapsed: 43.312176ms Jan 29 01:11:26.088: INFO: Pod "metadata-proxy-v0.1-tdckz" satisfied condition "running and ready, or succeeded" Jan 29 01:11:26.088: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-nh1n": Phase="Running", Reason="", readiness=true. Elapsed: 43.725171ms Jan 29 01:11:26.088: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-nh1n" satisfied condition "running and ready, or succeeded" Jan 29 01:11:26.088: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [metadata-proxy-v0.1-tdckz kube-proxy-bootstrap-e2e-minion-group-nh1n] Jan 29 01:11:26.088: INFO: Reboot successful on node bootstrap-e2e-minion-group-nh1n Jan 29 01:11:26.093: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw": Phase="Running", Reason="", readiness=true. Elapsed: 42.788199ms Jan 29 01:11:26.093: INFO: Pod "kube-proxy-bootstrap-e2e-minion-group-g5dw" satisfied condition "running and ready, or succeeded" Jan 29 01:11:26.093: INFO: Pod "metadata-proxy-v0.1-dvtn5": Phase="Running", Reason="", readiness=true. Elapsed: 43.141515ms Jan 29 01:11:26.093: INFO: Pod "metadata-proxy-v0.1-dvtn5" satisfied condition "running and ready, or succeeded" Jan 29 01:11:26.093: INFO: Wanted all 2 pods to be running and ready, or succeeded. Result: true. Pods: [kube-proxy-bootstrap-e2e-minion-group-g5dw metadata-proxy-v0.1-dvtn5] Jan 29 01:11:26.093: INFO: Reboot successful on node bootstrap-e2e-minion-group-g5dw Jan 29 01:11:26.657: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m36.096509734s Jan 29 01:11:26.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:28.649: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m38.088834148s Jan 29 01:11:28.649: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:30.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m40.091955395s Jan 29 01:11:30.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:32.660: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m42.099906962s Jan 29 01:11:32.661: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:34.657: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m44.095933932s Jan 29 01:11:34.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:36.650: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m46.089645702s Jan 29 01:11:36.650: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:38.657: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m48.095981445s Jan 29 01:11:38.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:40.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m50.090520139s Jan 29 01:11:40.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:42.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m52.091919026s Jan 29 01:11:42.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:44.657: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m54.095939134s Jan 29 01:11:44.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:46.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m56.09194497s Jan 29 01:11:46.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:48.661: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 3m58.099956249s Jan 29 01:11:48.661: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:50.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m0.09016296s Jan 29 01:11:50.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:52.660: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m2.099856422s Jan 29 01:11:52.661: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:54.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m4.090762551s Jan 29 01:11:54.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:56.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m6.091922832s Jan 29 01:11:56.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:11:58.655: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m8.093960008s Jan 29 01:11:58.655: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:00.652: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m10.091887366s Jan 29 01:12:00.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:02.656: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m12.095883616s Jan 29 01:12:02.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:04.659: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m14.098100816s Jan 29 01:12:04.659: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:06.655: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m16.094428365s Jan 29 01:12:06.655: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:08.654: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m18.09358565s Jan 29 01:12:08.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:10.676: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m20.11591565s Jan 29 01:12:10.677: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:12.652: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m22.091883617s Jan 29 01:12:12.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:14.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m24.090678235s Jan 29 01:12:14.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:16.652: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m26.091888422s Jan 29 01:12:16.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:18.654: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m28.093697229s Jan 29 01:12:18.654: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:20.652: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m30.091265805s Jan 29 01:12:20.652: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:22.652: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m32.091884166s Jan 29 01:12:22.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:24.657: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m34.095925835s Jan 29 01:12:24.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:26.657: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m36.095986113s Jan 29 01:12:26.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:28.657: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m38.09605054s Jan 29 01:12:28.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:30.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m40.092090615s Jan 29 01:12:30.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:32.652: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m42.091593046s Jan 29 01:12:32.652: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:34.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m44.091998274s Jan 29 01:12:34.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:36.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m46.092021179s Jan 29 01:12:36.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:38.652: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m48.091066241s Jan 29 01:12:38.652: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:40.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m50.091993488s Jan 29 01:12:40.653: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:42.661: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m52.099968317s Jan 29 01:12:42.661: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:44.657: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m54.096008788s Jan 29 01:12:44.657: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:46.651: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="", readiness=false. Elapsed: 4m56.090264564s Jan 29 01:12:46.651: INFO: Error evaluating pod condition running and ready, or succeeded: pod 'kube-dns-autoscaler-5f6455f985-q8wlx' on 'bootstrap-e2e-minion-group-rv7m' didn't have condition {Ready True}; conditions: [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-29 01:01:19 +0000 UTC ContainersNotReady containers with unready status: [autoscaler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-29 00:56:44 +0000 UTC }] Jan 29 01:12:48.653: INFO: Pod "kube-dns-autoscaler-5f6455f985-q8wlx": Phase="Running", Reason="