e2e-kops-grid-kubenet-u2004-k23-ko26-docker #1611830599394267136
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 91 failed / 700 succeeded |
| Started | |
| Elapsed | 59m21s |
| Revision | master |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\sExternal\sStorage\s\[Driver\:\sebs\.csi\.aws\.com\]\s\[Testpattern\:\sDynamic\sPV\s\(block\svolmode\)\]\svolumeMode\sshould\snot\smount\s\/\smap\sunused\svolumes\sin\sa\spod\s\[LinuxOnly\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:32:23.445: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_12.xml
[BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51 [BeforeEach] [Testpattern: Dynamic PV (block volmode)] volumeMode /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:28:57.422: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename volumemode �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] should not mount / map unused volumes in a pod [LinuxOnly] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumemode.go:352 Jan 7 21:28:57.640: INFO: Creating resource for dynamic PV Jan 7 21:28:57.640: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} �[1mSTEP�[0m: creating a StorageClass volumemode-4861-e2e-sc8mm8r �[1mSTEP�[0m: creating a claim �[1mSTEP�[0m: Creating pod �[1mSTEP�[0m: Listing mounted volumes in the pod Jan 7 21:29:09.998: INFO: ExecWithOptions {Command:[nsenter --mount=/rootfs/proc/1/ns/mnt -- sh -c test ! -d /var/lib/kubelet/pods/aaa531da-88e4-4de3-bb05-473260395815/volumes] Namespace:volumemode-4861 PodName:hostexec-ip-172-20-54-171.ec2.internal-f2d7m ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false} Jan 7 21:29:09.998: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:29:09.999: INFO: ExecWithOptions: Clientset creation Jan 7 21:29:09.999: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/volumemode-4861/pods/hostexec-ip-172-20-54-171.ec2.internal-f2d7m/exec?command=nsenter&command=--mount%3D%2Frootfs%2Fproc%2F1%2Fns%2Fmnt&command=--&command=sh&command=-c&command=test+%21+-d+%2Fvar%2Flib%2Fkubelet%2Fpods%2Faaa531da-88e4-4de3-bb05-473260395815%2Fvolumes&container=agnhost-container&container=agnhost-container&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:29:10.351: INFO: exec ip-172-20-54-171.ec2.internal: command: test ! -d /var/lib/kubelet/pods/aaa531da-88e4-4de3-bb05-473260395815/volumes Jan 7 21:29:10.351: INFO: exec ip-172-20-54-171.ec2.internal: stdout: "" Jan 7 21:29:10.351: INFO: exec ip-172-20-54-171.ec2.internal: stderr: "" Jan 7 21:29:10.351: INFO: exec ip-172-20-54-171.ec2.internal: exit code: 0 Jan 7 21:29:10.351: INFO: ExecWithOptions {Command:[nsenter --mount=/rootfs/proc/1/ns/mnt -- sh -c find /var/lib/kubelet/pods/aaa531da-88e4-4de3-bb05-473260395815/volumes -mindepth 2 -maxdepth 2] Namespace:volumemode-4861 PodName:hostexec-ip-172-20-54-171.ec2.internal-f2d7m ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false} Jan 7 21:29:10.351: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:29:10.352: INFO: ExecWithOptions: Clientset creation Jan 7 21:29:10.352: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/volumemode-4861/pods/hostexec-ip-172-20-54-171.ec2.internal-f2d7m/exec?command=nsenter&command=--mount%3D%2Frootfs%2Fproc%2F1%2Fns%2Fmnt&command=--&command=sh&command=-c&command=find+%2Fvar%2Flib%2Fkubelet%2Fpods%2Faaa531da-88e4-4de3-bb05-473260395815%2Fvolumes+-mindepth+2+-maxdepth+2&container=agnhost-container&container=agnhost-container&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:29:10.671: INFO: ExecWithOptions {Command:[nsenter --mount=/rootfs/proc/1/ns/mnt -- sh -c test ! -d /var/lib/kubelet/pods/aaa531da-88e4-4de3-bb05-473260395815/volumeDevices] Namespace:volumemode-4861 PodName:hostexec-ip-172-20-54-171.ec2.internal-f2d7m ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false} Jan 7 21:29:10.671: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:29:10.672: INFO: ExecWithOptions: Clientset creation Jan 7 21:29:10.672: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/volumemode-4861/pods/hostexec-ip-172-20-54-171.ec2.internal-f2d7m/exec?command=nsenter&command=--mount%3D%2Frootfs%2Fproc%2F1%2Fns%2Fmnt&command=--&command=sh&command=-c&command=test+%21+-d+%2Fvar%2Flib%2Fkubelet%2Fpods%2Faaa531da-88e4-4de3-bb05-473260395815%2FvolumeDevices&container=agnhost-container&container=agnhost-container&stderr=true&stdout=true %!s(MISSING)) �[1mSTEP�[0m: Checking that volume plugin kubernetes.io/csi is not used in pod directory �[1mSTEP�[0m: Deleting pod hostexec-ip-172-20-54-171.ec2.internal-f2d7m in namespace volumemode-4861 Jan 7 21:29:11.015: INFO: Deleting pod "pod-db18e411-fa6b-4496-a67f-06d33057e917" in namespace "volumemode-4861" Jan 7 21:29:11.054: INFO: Wait up to 5m0s for pod "pod-db18e411-fa6b-4496-a67f-06d33057e917" to be fully deleted �[1mSTEP�[0m: Deleting pvc Jan 7 21:29:13.181: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.com4dkzn" Jan 7 21:29:13.215: INFO: Waiting up to 3m0s for PersistentVolume pvc-b58befa4-5a82-4ae6-b39b-54ee640d2e81 to get deleted Jan 7 21:29:13.246: INFO: PersistentVolume pvc-b58befa4-5a82-4ae6-b39b-54ee640d2e81 found and phase=Released (30.783531ms) Jan 7 21:29:18.279: INFO: PersistentVolume pvc-b58befa4-5a82-4ae6-b39b-54ee640d2e81 found and phase=Released (5.063907254s) Jan 7 21:29:23.312: INFO: PersistentVolume pvc-b58befa4-5a82-4ae6-b39b-54ee640d2e81 was removed �[1mSTEP�[0m: Deleting sc [AfterEach] [Testpattern: Dynamic PV (block volmode)] volumeMode /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:29:23.347: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:29:23.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:25.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:27.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:29.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:31.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:33.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:35.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:37.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:39.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:41.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:43.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:45.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:47.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:49.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:51.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:53.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:55.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:57.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:59.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:01.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:03.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:05.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:07.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:09.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:11.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:13.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:15.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:17.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:19.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:21.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:23.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:25.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:27.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:29.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:31.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:33.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:35.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:37.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:39.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:41.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:43.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:45.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:47.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:49.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:51.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:53.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:55.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:57.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:59.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:01.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:03.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:05.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:07.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:09.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:11.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:13.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:15.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:17.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:19.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:21.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:23.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:25.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:27.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:29.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:31.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:33.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:35.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:37.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:39.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:41.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:43.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:45.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:47.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:49.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:51.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:53.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:55.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:57.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:59.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:01.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:03.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:05.412: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:07.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:09.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:11.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:13.414: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:15.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:17.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:19.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:21.415: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:23.411: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:23.444: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:23.445: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0xc) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc00078c340, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "volumemode-4861" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\sExternal\sStorage\s\[Driver\:\sebs\.csi\.aws\.com\]\s\[Testpattern\:\sDynamic\sPV\s\(default\sfs\)\]\sfsgroupchangepolicy\s\(OnRootMismatch\)\[LinuxOnly\]\,\spod\screated\swith\san\sinitial\sfsgroup\,\svolume\scontents\sownership\schanged\svia\schgrp\sin\sfirst\spod\,\snew\spod\swith\ssame\sfsgroup\sskips\sownership\schanges\sto\sthe\svolume\scontents$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:36:09.583: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_06.xml
[BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51 [BeforeEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:32:07.360: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename fsgroupchangepolicy �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, volume contents ownership changed via chgrp in first pod, new pod with same fsgroup skips ownership changes to the volume contents /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/fsgroupchangepolicy.go:214 Jan 7 21:32:07.579: INFO: Creating resource for dynamic PV Jan 7 21:32:07.579: INFO: Using claimSize:1Gi, test suite supported size:{ 1Mi}, driver(ebs.csi.aws.com) supported size:{ 1Mi} �[1mSTEP�[0m: creating a StorageClass fsgroupchangepolicy-603-e2e-sc8xg7b �[1mSTEP�[0m: creating a claim Jan 7 21:32:07.613: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil �[1mSTEP�[0m: Creating Pod in namespace fsgroupchangepolicy-603 with fsgroup 1000 Jan 7 21:32:23.807: INFO: Pod fsgroupchangepolicy-603/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 started successfully �[1mSTEP�[0m: Creating a sub-directory and file, and verifying their ownership is 1000 Jan 7 21:32:23.807: INFO: ExecWithOptions {Command:[/bin/sh -c touch /mnt/volume1/file1] Namespace:fsgroupchangepolicy-603 PodName:pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:32:23.807: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:32:23.808: INFO: ExecWithOptions: Clientset creation Jan 7 21:32:23.808: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/fsgroupchangepolicy-603/pods/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8/exec?command=%2Fbin%2Fsh&command=-c&command=touch+%2Fmnt%2Fvolume1%2Ffile1&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:32:24.095: INFO: ExecWithOptions {Command:[/bin/sh -c ls -l /mnt/volume1/file1] Namespace:fsgroupchangepolicy-603 PodName:pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:32:24.095: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:32:24.096: INFO: ExecWithOptions: Clientset creation Jan 7 21:32:24.096: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/fsgroupchangepolicy-603/pods/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8/exec?command=%2Fbin%2Fsh&command=-c&command=ls+-l+%2Fmnt%2Fvolume1%2Ffile1&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:32:24.398: INFO: pod fsgroupchangepolicy-603/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 exec for cmd ls -l /mnt/volume1/file1, stdout: -rw-r--r-- 1 root 1000 0 Jan 7 21:32 /mnt/volume1/file1, stderr: Jan 7 21:32:24.398: INFO: stdout split: [-rw-r--r-- 1 root 1000 0 Jan 7 21:32 /mnt/volume1/file1], expected gid: 1000 Jan 7 21:32:24.399: INFO: ExecWithOptions {Command:[/bin/sh -c mkdir /mnt/volume1/subdir] Namespace:fsgroupchangepolicy-603 PodName:pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:32:24.399: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:32:24.399: INFO: ExecWithOptions: Clientset creation Jan 7 21:32:24.399: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/fsgroupchangepolicy-603/pods/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8/exec?command=%2Fbin%2Fsh&command=-c&command=mkdir+%2Fmnt%2Fvolume1%2Fsubdir&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:32:24.676: INFO: ExecWithOptions {Command:[/bin/sh -c touch /mnt/volume1/subdir/file2] Namespace:fsgroupchangepolicy-603 PodName:pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:32:24.676: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:32:24.677: INFO: ExecWithOptions: Clientset creation Jan 7 21:32:24.677: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/fsgroupchangepolicy-603/pods/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8/exec?command=%2Fbin%2Fsh&command=-c&command=touch+%2Fmnt%2Fvolume1%2Fsubdir%2Ffile2&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:32:24.936: INFO: ExecWithOptions {Command:[/bin/sh -c ls -l /mnt/volume1/subdir/file2] Namespace:fsgroupchangepolicy-603 PodName:pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:32:24.936: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:32:24.937: INFO: ExecWithOptions: Clientset creation Jan 7 21:32:24.937: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/fsgroupchangepolicy-603/pods/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8/exec?command=%2Fbin%2Fsh&command=-c&command=ls+-l+%2Fmnt%2Fvolume1%2Fsubdir%2Ffile2&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:32:25.192: INFO: pod fsgroupchangepolicy-603/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 exec for cmd ls -l /mnt/volume1/subdir/file2, stdout: -rw-r--r-- 1 root 1000 0 Jan 7 21:32 /mnt/volume1/subdir/file2, stderr: Jan 7 21:32:25.192: INFO: stdout split: [-rw-r--r-- 1 root 1000 0 Jan 7 21:32 /mnt/volume1/subdir/file2], expected gid: 1000 �[1mSTEP�[0m: Changing the root directory file ownership to 2000 Jan 7 21:32:25.192: INFO: ExecWithOptions {Command:[/bin/sh -c chgrp 2000 /mnt/volume1/file1] Namespace:fsgroupchangepolicy-603 PodName:pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:32:25.192: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:32:25.192: INFO: ExecWithOptions: Clientset creation Jan 7 21:32:25.192: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/fsgroupchangepolicy-603/pods/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8/exec?command=%2Fbin%2Fsh&command=-c&command=chgrp+2000+%2Fmnt%2Fvolume1%2Ffile1&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:32:25.467: INFO: ExecWithOptions {Command:[/bin/sh -c ls -l /mnt/volume1/file1] Namespace:fsgroupchangepolicy-603 PodName:pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:32:25.467: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:32:25.468: INFO: ExecWithOptions: Clientset creation Jan 7 21:32:25.468: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/fsgroupchangepolicy-603/pods/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8/exec?command=%2Fbin%2Fsh&command=-c&command=ls+-l+%2Fmnt%2Fvolume1%2Ffile1&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:32:25.721: INFO: pod fsgroupchangepolicy-603/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 exec for cmd ls -l /mnt/volume1/file1, stdout: -rw-r--r-- 1 root 2000 0 Jan 7 21:32 /mnt/volume1/file1, stderr: Jan 7 21:32:25.721: INFO: stdout split: [-rw-r--r-- 1 root 2000 0 Jan 7 21:32 /mnt/volume1/file1], expected gid: 2000 �[1mSTEP�[0m: Changing the sub-directory file ownership to 3000 Jan 7 21:32:25.721: INFO: ExecWithOptions {Command:[/bin/sh -c chgrp 3000 /mnt/volume1/subdir/file2] Namespace:fsgroupchangepolicy-603 PodName:pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:32:25.721: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:32:25.722: INFO: ExecWithOptions: Clientset creation Jan 7 21:32:25.722: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/fsgroupchangepolicy-603/pods/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8/exec?command=%2Fbin%2Fsh&command=-c&command=chgrp+3000+%2Fmnt%2Fvolume1%2Fsubdir%2Ffile2&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:32:25.992: INFO: ExecWithOptions {Command:[/bin/sh -c ls -l /mnt/volume1/subdir/file2] Namespace:fsgroupchangepolicy-603 PodName:pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:32:25.992: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:32:25.993: INFO: ExecWithOptions: Clientset creation Jan 7 21:32:25.993: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/fsgroupchangepolicy-603/pods/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8/exec?command=%2Fbin%2Fsh&command=-c&command=ls+-l+%2Fmnt%2Fvolume1%2Fsubdir%2Ffile2&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:32:26.298: INFO: pod fsgroupchangepolicy-603/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 exec for cmd ls -l /mnt/volume1/subdir/file2, stdout: -rw-r--r-- 1 root 3000 0 Jan 7 21:32 /mnt/volume1/subdir/file2, stderr: Jan 7 21:32:26.298: INFO: stdout split: [-rw-r--r-- 1 root 3000 0 Jan 7 21:32 /mnt/volume1/subdir/file2], expected gid: 3000 �[1mSTEP�[0m: Deleting Pod fsgroupchangepolicy-603/pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8 Jan 7 21:32:26.298: INFO: Deleting pod "pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8" in namespace "fsgroupchangepolicy-603" Jan 7 21:32:26.332: INFO: Wait up to 5m0s for pod "pod-bb3ec295-f474-4b5d-9533-5c6e081c7ab8" to be fully deleted �[1mSTEP�[0m: Creating Pod in namespace fsgroupchangepolicy-603 with fsgroup 1000 Jan 7 21:32:46.534: INFO: Pod fsgroupchangepolicy-603/pod-de0cbe3c-a11b-481f-9102-ff4ab696d27a started successfully �[1mSTEP�[0m: Verifying the ownership of root directory file is 2000 Jan 7 21:32:46.535: INFO: ExecWithOptions {Command:[/bin/sh -c ls -l /mnt/volume1/file1] Namespace:fsgroupchangepolicy-603 PodName:pod-de0cbe3c-a11b-481f-9102-ff4ab696d27a ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:32:46.535: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:32:46.535: INFO: ExecWithOptions: Clientset creation Jan 7 21:32:46.535: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/fsgroupchangepolicy-603/pods/pod-de0cbe3c-a11b-481f-9102-ff4ab696d27a/exec?command=%2Fbin%2Fsh&command=-c&command=ls+-l+%2Fmnt%2Fvolume1%2Ffile1&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:32:46.822: INFO: pod fsgroupchangepolicy-603/pod-de0cbe3c-a11b-481f-9102-ff4ab696d27a exec for cmd ls -l /mnt/volume1/file1, stdout: -rw-r--r-- 1 root 2000 0 Jan 7 21:32 /mnt/volume1/file1, stderr: Jan 7 21:32:46.822: INFO: stdout split: [-rw-r--r-- 1 root 2000 0 Jan 7 21:32 /mnt/volume1/file1], expected gid: 2000 �[1mSTEP�[0m: Verifying the ownership of sub directory file is 3000 Jan 7 21:32:46.822: INFO: ExecWithOptions {Command:[/bin/sh -c ls -l /mnt/volume1/subdir/file2] Namespace:fsgroupchangepolicy-603 PodName:pod-de0cbe3c-a11b-481f-9102-ff4ab696d27a ContainerName:write-pod Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:32:46.822: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:32:46.823: INFO: ExecWithOptions: Clientset creation Jan 7 21:32:46.823: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/fsgroupchangepolicy-603/pods/pod-de0cbe3c-a11b-481f-9102-ff4ab696d27a/exec?command=%2Fbin%2Fsh&command=-c&command=ls+-l+%2Fmnt%2Fvolume1%2Fsubdir%2Ffile2&container=write-pod&container=write-pod&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:32:47.083: INFO: pod fsgroupchangepolicy-603/pod-de0cbe3c-a11b-481f-9102-ff4ab696d27a exec for cmd ls -l /mnt/volume1/subdir/file2, stdout: -rw-r--r-- 1 root 3000 0 Jan 7 21:32 /mnt/volume1/subdir/file2, stderr: Jan 7 21:32:47.083: INFO: stdout split: [-rw-r--r-- 1 root 3000 0 Jan 7 21:32 /mnt/volume1/subdir/file2], expected gid: 3000 �[1mSTEP�[0m: Deleting Pod fsgroupchangepolicy-603/pod-de0cbe3c-a11b-481f-9102-ff4ab696d27a Jan 7 21:32:47.083: INFO: Deleting pod "pod-de0cbe3c-a11b-481f-9102-ff4ab696d27a" in namespace "fsgroupchangepolicy-603" Jan 7 21:32:47.119: INFO: Wait up to 5m0s for pod "pod-de0cbe3c-a11b-481f-9102-ff4ab696d27a" to be fully deleted �[1mSTEP�[0m: Deleting pvc Jan 7 21:32:49.248: INFO: Deleting PersistentVolumeClaim "ebs.csi.aws.comsvkn5" Jan 7 21:32:49.283: INFO: Waiting up to 3m0s for PersistentVolume pvc-6d7182a9-f71e-4e43-bb32-ca1699eef284 to get deleted Jan 7 21:32:49.314: INFO: PersistentVolume pvc-6d7182a9-f71e-4e43-bb32-ca1699eef284 found and phase=Released (31.204736ms) Jan 7 21:32:54.347: INFO: PersistentVolume pvc-6d7182a9-f71e-4e43-bb32-ca1699eef284 found and phase=Released (5.064063552s) Jan 7 21:32:59.381: INFO: PersistentVolume pvc-6d7182a9-f71e-4e43-bb32-ca1699eef284 found and phase=Released (10.097609786s) Jan 7 21:33:04.413: INFO: PersistentVolume pvc-6d7182a9-f71e-4e43-bb32-ca1699eef284 found and phase=Released (15.129807401s) Jan 7 21:33:09.447: INFO: PersistentVolume pvc-6d7182a9-f71e-4e43-bb32-ca1699eef284 was removed �[1mSTEP�[0m: Deleting sc [AfterEach] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:33:09.481: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:33:09.517: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:11.552: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:13.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:15.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:17.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:19.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:21.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:23.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:25.552: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:27.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:29.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:31.552: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:33.555: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:35.552: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:37.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:39.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:41.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:43.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:45.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:47.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:49.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:51.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:53.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:55.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:57.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:59.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:01.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:03.552: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:05.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:07.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:09.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:11.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:13.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:15.552: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:17.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:19.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:21.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:23.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:25.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:27.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:29.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:31.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:33.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:35.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:37.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:39.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:41.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:43.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:45.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:47.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:49.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:51.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:53.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:55.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:57.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:59.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:01.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:03.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:05.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:07.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:09.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:11.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:13.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:15.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:17.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:19.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:21.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:23.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:25.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:27.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:29.552: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:31.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:33.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:35.552: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:37.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:39.552: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:41.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:43.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:45.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:47.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:49.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:51.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:53.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:55.552: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:57.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:59.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:01.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:03.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:05.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:07.551: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:09.550: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:09.582: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:09.583: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x2000100000002) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc00028b860, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "fsgroupchangepolicy-603" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\sExternal\sStorage\s\[Driver\:\sebs\.csi\.aws\.com\]\s\[Testpattern\:\sDynamic\sPV\s\(default\sfs\)\]\sprovisioning\sshould\sprovision\sstorage\swith\smount\soptions$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:33:24.194: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_17.xml
[BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51 [BeforeEach] [Testpattern: Dynamic PV (default fs)] provisioning /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:29:16.322: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename provisioning �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] should provision storage with mount options /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/provisioning.go:180 Jan 7 21:29:16.528: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil Jan 7 21:29:16.528: INFO: Warning: Making PVC: VolumeMode specified as invalid empty string, treating as nil Jan 7 21:29:16.528: INFO: In creating storage class object and pvc objects for driver - sc: &StorageClass{ObjectMeta:{provisioning-5257-e2e-scb5g9c 0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] [] []},Provisioner:ebs.csi.aws.com,Parameters:map[string]string{encrypted: true,type: gp3,},ReclaimPolicy:nil,MountOptions:[],AllowVolumeExpansion:*true,VolumeBindingMode:*WaitForFirstConsumer,AllowedTopologies:[]TopologySelectorTerm{},}, pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5257 0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] [] []},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*provisioning-5257-e2e-scb5g9c,VolumeMode:nil,DataSource:nil,DataSourceRef:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},AllocatedResources:ResourceList{},ResizeStatus:nil,},}, src-pvc: &PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5257 0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] [] []},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*provisioning-5257-e2e-scb5g9c,VolumeMode:nil,DataSource:nil,DataSourceRef:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},AllocatedResources:ResourceList{},ResizeStatus:nil,},} �[1mSTEP�[0m: Creating a StorageClass �[1mSTEP�[0m: creating claim=&PersistentVolumeClaim{ObjectMeta:{ pvc- provisioning-5257 0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] [] []},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*provisioning-5257-e2e-scb5g9c,VolumeMode:nil,DataSource:nil,DataSourceRef:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},AllocatedResources:ResourceList{},ResizeStatus:nil,},} �[1mSTEP�[0m: creating a pod referring to the class=&StorageClass{ObjectMeta:{provisioning-5257-e2e-scb5g9c 6c41dcc3-a66f-47d5-b208-fed9765b91fd 39821 0 2023-01-07 21:29:16 +0000 UTC <nil> <nil> map[] map[] [] [] [{e2e.test Update storage.k8s.io/v1 2023-01-07 21:29:16 +0000 UTC FieldsV1 {"f:allowVolumeExpansion":{},"f:mountOptions":{},"f:parameters":{".":{},"f:encrypted":{},"f:type":{}},"f:provisioner":{},"f:reclaimPolicy":{},"f:volumeBindingMode":{}} }]},Provisioner:ebs.csi.aws.com,Parameters:map[string]string{encrypted: true,type: gp3,},ReclaimPolicy:*Delete,MountOptions:[dirsync],AllowVolumeExpansion:*true,VolumeBindingMode:*WaitForFirstConsumer,AllowedTopologies:[]TopologySelectorTerm{},} claim=&PersistentVolumeClaim{ObjectMeta:{pvc-knn96 pvc- provisioning-5257 8470f3c5-59b2-4d90-9585-357e9fcb3d4b 39822 0 2023-01-07 21:29:16 +0000 UTC <nil> <nil> map[] map[] [] [kubernetes.io/pvc-protection] [{e2e.test Update v1 2023-01-07 21:29:16 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{}},"f:spec":{"f:accessModes":{},"f:resources":{"f:requests":{".":{},"f:storage":{}}},"f:storageClassName":{},"f:volumeMode":{}}} }]},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*provisioning-5257-e2e-scb5g9c,VolumeMode:*Filesystem,DataSource:nil,DataSourceRef:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},AllocatedResources:ResourceList{},ResizeStatus:nil,},} �[1mSTEP�[0m: Deleting pod pod-5b21ac76-2f52-422a-84ac-aa9eadddb55d in namespace provisioning-5257 �[1mSTEP�[0m: checking the created volume is writable on node {Name: Selector:map[] Affinity:nil} Jan 7 21:29:30.867: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-writer-dx9rg" in namespace "provisioning-5257" to be "Succeeded or Failed" Jan 7 21:29:30.896: INFO: Pod "pvc-volume-tester-writer-dx9rg": Phase="Pending", Reason="", readiness=false. Elapsed: 29.051072ms Jan 7 21:29:32.926: INFO: Pod "pvc-volume-tester-writer-dx9rg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.058901763s Jan 7 21:29:34.957: INFO: Pod "pvc-volume-tester-writer-dx9rg": Phase="Pending", Reason="", readiness=false. Elapsed: 4.089689808s Jan 7 21:29:36.987: INFO: Pod "pvc-volume-tester-writer-dx9rg": Phase="Pending", Reason="", readiness=false. Elapsed: 6.119522012s Jan 7 21:29:39.018: INFO: Pod "pvc-volume-tester-writer-dx9rg": Phase="Pending", Reason="", readiness=false. Elapsed: 8.150721984s Jan 7 21:29:41.048: INFO: Pod "pvc-volume-tester-writer-dx9rg": Phase="Pending", Reason="", readiness=false. Elapsed: 10.18079286s Jan 7 21:29:43.078: INFO: Pod "pvc-volume-tester-writer-dx9rg": Phase="Pending", Reason="", readiness=false. Elapsed: 12.210916095s Jan 7 21:29:45.109: INFO: Pod "pvc-volume-tester-writer-dx9rg": Phase="Pending", Reason="", readiness=false. Elapsed: 14.242068569s Jan 7 21:29:47.140: INFO: Pod "pvc-volume-tester-writer-dx9rg": Phase="Pending", Reason="", readiness=false. Elapsed: 16.272941464s Jan 7 21:29:49.171: INFO: Pod "pvc-volume-tester-writer-dx9rg": Phase="Pending", Reason="", readiness=false. Elapsed: 18.304016619s Jan 7 21:29:51.202: INFO: Pod "pvc-volume-tester-writer-dx9rg": Phase="Pending", Reason="", readiness=false. Elapsed: 20.33458961s Jan 7 21:29:53.231: INFO: Pod "pvc-volume-tester-writer-dx9rg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.36435232s �[1mSTEP�[0m: Saw pod success Jan 7 21:29:53.231: INFO: Pod "pvc-volume-tester-writer-dx9rg" satisfied condition "Succeeded or Failed" Jan 7 21:29:53.295: INFO: Pod pvc-volume-tester-writer-dx9rg has the following logs: Jan 7 21:29:53.295: INFO: Deleting pod "pvc-volume-tester-writer-dx9rg" in namespace "provisioning-5257" Jan 7 21:29:53.332: INFO: Wait up to 5m0s for pod "pvc-volume-tester-writer-dx9rg" to be fully deleted �[1mSTEP�[0m: checking the created volume has the correct mount options, is readable and retains data on the same node "ip-172-20-51-5.ec2.internal" Jan 7 21:29:53.452: INFO: Waiting up to 15m0s for pod "pvc-volume-tester-reader-dvwlq" in namespace "provisioning-5257" to be "Succeeded or Failed" Jan 7 21:29:53.484: INFO: Pod "pvc-volume-tester-reader-dvwlq": Phase="Pending", Reason="", readiness=false. Elapsed: 31.264841ms Jan 7 21:29:55.514: INFO: Pod "pvc-volume-tester-reader-dvwlq": Phase="Pending", Reason="", readiness=false. Elapsed: 2.06191341s Jan 7 21:29:57.545: INFO: Pod "pvc-volume-tester-reader-dvwlq": Phase="Pending", Reason="", readiness=false. Elapsed: 4.092874266s Jan 7 21:29:59.576: INFO: Pod "pvc-volume-tester-reader-dvwlq": Phase="Pending", Reason="", readiness=false. Elapsed: 6.123602399s Jan 7 21:30:01.607: INFO: Pod "pvc-volume-tester-reader-dvwlq": Phase="Pending", Reason="", readiness=false. Elapsed: 8.154459213s Jan 7 21:30:03.636: INFO: Pod "pvc-volume-tester-reader-dvwlq": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.184029344s �[1mSTEP�[0m: Saw pod success Jan 7 21:30:03.637: INFO: Pod "pvc-volume-tester-reader-dvwlq" satisfied condition "Succeeded or Failed" Jan 7 21:30:03.699: INFO: Pod pvc-volume-tester-reader-dvwlq has the following logs: hello world Jan 7 21:30:03.699: INFO: Deleting pod "pvc-volume-tester-reader-dvwlq" in namespace "provisioning-5257" Jan 7 21:30:03.738: INFO: Wait up to 5m0s for pod "pvc-volume-tester-reader-dvwlq" to be fully deleted Jan 7 21:30:03.767: INFO: Waiting up to timeout=5m0s for PersistentVolumeClaims [pvc-knn96] to have phase Bound Jan 7 21:30:03.797: INFO: PersistentVolumeClaim pvc-knn96 found and phase=Bound (29.15963ms) �[1mSTEP�[0m: checking the claim �[1mSTEP�[0m: checking the PV �[1mSTEP�[0m: deleting claim "provisioning-5257"/"pvc-knn96" �[1mSTEP�[0m: deleting the claim's PV "pvc-8470f3c5-59b2-4d90-9585-357e9fcb3d4b" Jan 7 21:30:03.887: INFO: Waiting up to 20m0s for PersistentVolume pvc-8470f3c5-59b2-4d90-9585-357e9fcb3d4b to get deleted Jan 7 21:30:03.917: INFO: PersistentVolume pvc-8470f3c5-59b2-4d90-9585-357e9fcb3d4b found and phase=Released (29.107389ms) Jan 7 21:30:08.946: INFO: PersistentVolume pvc-8470f3c5-59b2-4d90-9585-357e9fcb3d4b found and phase=Released (5.058575007s) Jan 7 21:30:13.977: INFO: PersistentVolume pvc-8470f3c5-59b2-4d90-9585-357e9fcb3d4b found and phase=Released (10.089261957s) Jan 7 21:30:19.008: INFO: PersistentVolume pvc-8470f3c5-59b2-4d90-9585-357e9fcb3d4b found and phase=Released (15.120364206s) Jan 7 21:30:24.039: INFO: PersistentVolume pvc-8470f3c5-59b2-4d90-9585-357e9fcb3d4b was removed Jan 7 21:30:24.039: INFO: deleting claim "provisioning-5257"/"pvc-knn96" Jan 7 21:30:24.068: INFO: deleting storage class provisioning-5257-e2e-scb5g9c [AfterEach] [Testpattern: Dynamic PV (default fs)] provisioning /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:30:24.099: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:30:24.130: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:26.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:28.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:30.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:32.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:34.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:36.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:38.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:40.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:42.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:44.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:46.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:48.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:50.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:52.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:54.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:56.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:58.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:00.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:02.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:04.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:06.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:08.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:10.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:12.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:14.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:16.166: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:18.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:20.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:22.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:24.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:26.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:28.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:30.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:32.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:34.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:36.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:38.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:40.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:42.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:44.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:46.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:48.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:50.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:52.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:54.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:56.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:58.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:00.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:02.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:04.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:06.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:08.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:10.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:12.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:14.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:16.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:18.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:20.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:22.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:24.165: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:26.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:28.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:30.163: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:32.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:34.163: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:36.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:38.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:40.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:42.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:44.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:46.163: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:48.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:50.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:52.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:54.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:56.163: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:58.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:00.163: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:02.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:04.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:06.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:08.160: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:10.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:12.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:14.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:16.162: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:18.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:20.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:22.161: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:24.164: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:24.194: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:24.194: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x0) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000c34820, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "provisioning-5257" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\sExternal\sStorage\s\[Driver\:\sebs\.csi\.aws\.com\]\s\[Testpattern\:\sGeneric\sEphemeral\-volume\s\(block\svolmode\)\s\(late\-binding\)\]\sephemeral\sshould\screate\sread\/write\sinline\sephemeral\svolume$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:28:57.304: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_12.xml
[BeforeEach] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51 [BeforeEach] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:24:45.904: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename ephemeral �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] should create read/write inline ephemeral volume /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:194 Jan 7 21:24:46.187: INFO: Pod inline-volume-n4c9q has the following logs: Jan 7 21:24:46.218: INFO: Deleting pod "inline-volume-n4c9q" in namespace "ephemeral-7035" Jan 7 21:24:46.252: INFO: Wait up to 5m0s for pod "inline-volume-n4c9q" to be fully deleted Jan 7 21:24:48.316: INFO: Creating resource for dynamic PV Jan 7 21:24:48.316: INFO: Using claimSize:1Gi, test suite supported size:{ }, driver(ebs.csi.aws.com) supported size:{ } �[1mSTEP�[0m: creating a StorageClass ephemeral-7035-e2e-scqq7qd �[1mSTEP�[0m: checking the requested inline volume exists in the pod running on node {Name: Selector:map[] Affinity:nil} Jan 7 21:25:04.490: INFO: ExecWithOptions {Command:[/bin/sh -c if ! [ -b /mnt/test-0 ]; then echo /mnt/test-0 is not a block device; exit 1; fi] Namespace:ephemeral-7035 PodName:inline-volume-tester-lhxzr ContainerName:csi-volume-tester Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:25:04.490: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:25:04.490: INFO: ExecWithOptions: Clientset creation Jan 7 21:25:04.490: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/ephemeral-7035/pods/inline-volume-tester-lhxzr/exec?command=%2Fbin%2Fsh&command=-c&command=if+%21+%5B+-b+%2Fmnt%2Ftest-0+%5D%3B+then+echo+%2Fmnt%2Ftest-0+is+not+a+block+device%3B+exit+1%3B+fi&container=csi-volume-tester&container=csi-volume-tester&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:25:04.799: INFO: Pod inline-volume-tester-lhxzr has the following logs: Jan 7 21:25:04.862: INFO: Deleting pod "inline-volume-tester-lhxzr" in namespace "ephemeral-7035" Jan 7 21:25:04.899: INFO: Wait up to 5m0s for pod "inline-volume-tester-lhxzr" to be fully deleted Jan 7 21:25:36.962: INFO: Wait up to 5m0s for pod PV pvc-e0506489-ab72-4b4c-b5ff-5e98a56dba33 to be fully deleted Jan 7 21:25:36.962: INFO: Waiting up to 5m0s for PersistentVolume pvc-e0506489-ab72-4b4c-b5ff-5e98a56dba33 to get deleted Jan 7 21:25:36.993: INFO: PersistentVolume pvc-e0506489-ab72-4b4c-b5ff-5e98a56dba33 found and phase=Released (31.077847ms) Jan 7 21:25:42.024: INFO: PersistentVolume pvc-e0506489-ab72-4b4c-b5ff-5e98a56dba33 found and phase=Released (5.062626625s) Jan 7 21:25:47.078: INFO: PersistentVolume pvc-e0506489-ab72-4b4c-b5ff-5e98a56dba33 found and phase=Released (10.116606636s) Jan 7 21:25:52.111: INFO: PersistentVolume pvc-e0506489-ab72-4b4c-b5ff-5e98a56dba33 found and phase=Released (15.14916508s) Jan 7 21:25:57.142: INFO: PersistentVolume pvc-e0506489-ab72-4b4c-b5ff-5e98a56dba33 was removed �[1mSTEP�[0m: Deleting sc [AfterEach] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:25:57.206: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:25:57.239: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:25:59.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:01.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:03.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:05.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:07.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:09.275: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:11.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:13.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:15.274: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:17.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:19.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:21.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:23.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:25.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:27.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:29.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:31.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:33.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:35.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:37.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:39.276: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:41.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:43.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:45.276: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:47.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:49.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:51.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:53.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:55.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:57.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:59.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:01.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:03.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:05.281: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:07.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:09.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:11.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:13.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:15.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:17.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:19.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:21.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:23.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:25.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:27.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:29.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:31.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:33.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:35.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:37.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:39.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:41.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:43.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:45.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:47.277: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:49.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:51.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:53.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:55.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:57.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:59.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:01.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:03.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:05.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:07.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:09.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:11.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:13.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:15.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:17.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:19.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:21.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:23.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:25.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:27.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:29.274: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:31.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:33.273: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:35.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:37.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:39.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:41.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:43.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:45.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:47.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:49.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:51.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:53.272: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:55.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:57.271: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:57.304: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:57.304: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0xc) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc00078c340, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "ephemeral-7035" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\sExternal\sStorage\s\[Driver\:\sebs\.csi\.aws\.com\]\s\[Testpattern\:\sGeneric\sEphemeral\-volume\s\(block\svolmode\)\s\(late\-binding\)\]\sephemeral\sshould\ssupport\smultiple\sinline\sephemeral\svolumes$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:42:20.859: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_17.xml
[BeforeEach] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/framework/testsuite.go:51 [BeforeEach] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:38:18.819: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename ephemeral �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] should support multiple inline ephemeral volumes /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/ephemeral.go:252 Jan 7 21:38:19.088: INFO: Pod inline-volume-djhcz has the following logs: Jan 7 21:38:19.118: INFO: Deleting pod "inline-volume-djhcz" in namespace "ephemeral-1924" Jan 7 21:38:19.150: INFO: Wait up to 5m0s for pod "inline-volume-djhcz" to be fully deleted Jan 7 21:38:19.179: INFO: Creating resource for dynamic PV Jan 7 21:38:19.179: INFO: Using claimSize:1Gi, test suite supported size:{ }, driver(ebs.csi.aws.com) supported size:{ } �[1mSTEP�[0m: creating a StorageClass ephemeral-1924-e2e-sc7fkwz �[1mSTEP�[0m: checking the requested inline volume exists in the pod running on node {Name: Selector:map[] Affinity:nil} Jan 7 21:38:31.371: INFO: Pod inline-volume-tester-5gghl has the following logs: Jan 7 21:38:31.459: INFO: Deleting pod "inline-volume-tester-5gghl" in namespace "ephemeral-1924" Jan 7 21:38:31.491: INFO: Wait up to 5m0s for pod "inline-volume-tester-5gghl" to be fully deleted Jan 7 21:39:05.550: INFO: Wait up to 5m0s for pod PV pvc-80619ff2-1cb4-4f30-9b9e-881f3d328ff0 to be fully deleted Jan 7 21:39:05.551: INFO: Waiting up to 5m0s for PersistentVolume pvc-80619ff2-1cb4-4f30-9b9e-881f3d328ff0 to get deleted Jan 7 21:39:05.580: INFO: PersistentVolume pvc-80619ff2-1cb4-4f30-9b9e-881f3d328ff0 found and phase=Released (29.224361ms) Jan 7 21:39:10.611: INFO: PersistentVolume pvc-80619ff2-1cb4-4f30-9b9e-881f3d328ff0 found and phase=Released (5.060369239s) Jan 7 21:39:15.644: INFO: PersistentVolume pvc-80619ff2-1cb4-4f30-9b9e-881f3d328ff0 found and phase=Released (10.093296697s) Jan 7 21:39:20.674: INFO: PersistentVolume pvc-80619ff2-1cb4-4f30-9b9e-881f3d328ff0 was removed Jan 7 21:39:20.674: INFO: Wait up to 5m0s for pod PV pvc-a80ff60e-30c5-4847-ae3f-bf256ad3c6dc to be fully deleted Jan 7 21:39:20.674: INFO: Waiting up to 5m0s for PersistentVolume pvc-a80ff60e-30c5-4847-ae3f-bf256ad3c6dc to get deleted Jan 7 21:39:20.704: INFO: PersistentVolume pvc-a80ff60e-30c5-4847-ae3f-bf256ad3c6dc was removed �[1mSTEP�[0m: Deleting sc [AfterEach] [Testpattern: Generic Ephemeral-volume (block volmode) (late-binding)] ephemeral /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:39:20.766: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:39:20.797: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:22.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:24.831: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:26.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:28.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:30.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:32.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:34.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:36.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:38.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:40.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:42.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:44.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:46.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:48.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:50.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:52.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:54.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:56.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:58.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:00.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:02.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:04.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:06.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:08.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:10.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:12.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:14.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:16.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:18.834: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:20.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:22.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:24.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:26.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:28.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:30.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:32.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:34.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:36.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:38.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:40.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:42.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:44.831: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:46.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:48.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:50.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:52.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:54.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:56.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:58.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:00.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:02.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:04.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:06.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:08.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:10.832: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:12.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:14.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:16.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:18.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:20.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:22.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:24.833: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:26.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:28.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:30.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:32.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:34.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:36.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:38.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:40.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:42.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:44.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:46.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:48.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:50.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:52.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:54.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:56.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:58.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:00.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:02.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:04.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:06.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:08.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:10.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:12.829: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:14.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:16.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:18.830: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:20.828: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:20.859: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:20.859: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x0) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000c34820, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "ephemeral-1924" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-api\-machinery\]\sAdmissionWebhook\s\[Privileged\:ClusterAdmin\]\sshould\sbe\sable\sto\sdeny\sattaching\spod\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:39:57.088: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_11.xml
{"msg":"FAILED [sig-node] Container Runtime blackbox test on terminated container should report termination message if TerminationMessagePath is set [Excluded:WindowsDocker] [NodeConformance]","total":-1,"completed":26,"skipped":197,"failed":3,"failures":["[sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Inline-volume (default fs)] subPath should support readOnly directory specified in the volumeMount","[sig-node] Security Context when creating containers with AllowPrivilegeEscalation should allow privilege escalation when true [LinuxOnly] [NodeConformance]","[sig-node] Container Runtime blackbox test on terminated container should report termination message if TerminationMessagePath is set [Excluded:WindowsDocker] [NodeConformance]"]} [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:36:50.581: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename webhook �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:87 �[1mSTEP�[0m: Setting up server cert �[1mSTEP�[0m: Create role binding to let webhook read extension-apiserver-authentication �[1mSTEP�[0m: Deploying the webhook pod �[1mSTEP�[0m: Wait for the deployment to be ready Jan 7 21:36:51.396: INFO: deployment status: v1.DeploymentStatus{ObservedGeneration:1, Replicas:1, UpdatedReplicas:1, ReadyReplicas:0, AvailableReplicas:0, UnavailableReplicas:1, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:"Available", Status:"False", LastUpdateTime:time.Date(2023, time.January, 7, 21, 36, 51, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 7, 21, 36, 51, 0, time.Local), Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 7, 21, 36, 51, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 7, 21, 36, 51, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"sample-webhook-deployment-6c69dbd86b\" is progressing."}}, CollisionCount:(*int32)(nil)} �[1mSTEP�[0m: Deploying the webhook service �[1mSTEP�[0m: Verifying the service has paired with the endpoint Jan 7 21:36:54.467: INFO: Waiting for amount of service:e2e-test-webhook endpoints to be 1 [It] should be able to deny attaching pod [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 �[1mSTEP�[0m: Registering the webhook via the AdmissionRegistration API �[1mSTEP�[0m: create a pod �[1mSTEP�[0m: 'kubectl attach' the pod, should be denied by the webhook Jan 7 21:36:56.679: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=webhook-1130 attach --namespace=webhook-1130 to-be-attached-pod -i -c=container1' Jan 7 21:36:56.960: INFO: rc: 1 [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:36:56.993: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:36:57.024: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:59.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:01.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:03.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:05.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:07.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:09.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:11.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:13.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:15.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:17.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:19.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:21.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:23.068: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:25.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:27.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:29.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:31.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:33.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:35.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:37.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:39.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:41.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:43.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:45.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:47.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:49.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:51.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:53.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:55.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:57.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:59.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:01.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:03.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:05.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:07.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:09.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:11.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:13.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:15.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:17.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:19.061: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:21.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:23.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:25.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:27.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:29.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:31.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:33.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:35.060: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:37.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:39.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:41.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:43.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:45.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:47.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:49.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:51.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:53.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:55.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:57.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:59.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:01.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:03.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:05.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:07.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:09.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:11.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:13.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:15.060: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:17.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:19.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:21.064: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:23.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:25.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:27.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:29.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:31.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:33.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:35.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:37.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:39.058: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:41.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:43.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:45.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:47.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:49.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:51.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:53.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:55.057: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:57.056: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:57.088: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:57.088: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x6f702f65646f6e2f) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc0003ed040, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "webhook-1130" for this suite. �[1mSTEP�[0m: Destroying namespace "webhook-1130-markers" for this suite. [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:102
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-api\-machinery\]\sCustomResourceDefinition\sWatch\s\[Privileged\:ClusterAdmin\]\sCustomResourceDefinition\sWatch\swatch\son\scustom\sresource\sdefinition\sobjects\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:41:07.620: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_03.xml
[BeforeEach] [sig-api-machinery] CustomResourceDefinition Watch [Privileged:ClusterAdmin] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:37:04.774: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename crd-watch �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] watch on custom resource definition objects [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 Jan 7 21:37:04.992: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Creating first CR Jan 7 21:37:07.271: INFO: Got : ADDED &{map[apiVersion:mygroup.example.com/v1beta1 content:map[key:value] kind:WishIHadChosenNoxu metadata:map[creationTimestamp:2023-01-07T21:37:07Z generation:1 managedFields:[map[apiVersion:mygroup.example.com/v1beta1 fieldsType:FieldsV1 fieldsV1:map[f:content:map[.:map[] f:key:map[]] f:num:map[.:map[] f:num1:map[] f:num2:map[]]] manager:e2e.test operation:Update time:2023-01-07T21:37:07Z]] name:name1 resourceVersion:43153 uid:1f1f0869-939e-4fbd-906d-3dc2ae75b04d] num:map[num1:9223372036854775807 num2:1000000]]} �[1mSTEP�[0m: Creating second CR Jan 7 21:37:17.304: INFO: Got : ADDED &{map[apiVersion:mygroup.example.com/v1beta1 content:map[key:value] kind:WishIHadChosenNoxu metadata:map[creationTimestamp:2023-01-07T21:37:17Z generation:1 managedFields:[map[apiVersion:mygroup.example.com/v1beta1 fieldsType:FieldsV1 fieldsV1:map[f:content:map[.:map[] f:key:map[]] f:num:map[.:map[] f:num1:map[] f:num2:map[]]] manager:e2e.test operation:Update time:2023-01-07T21:37:17Z]] name:name2 resourceVersion:43200 uid:f1e74015-ae23-42d7-a18c-c217684b5ffa] num:map[num1:9223372036854775807 num2:1000000]]} �[1mSTEP�[0m: Modifying first CR Jan 7 21:37:27.339: INFO: Got : MODIFIED &{map[apiVersion:mygroup.example.com/v1beta1 content:map[key:value] dummy:test kind:WishIHadChosenNoxu metadata:map[creationTimestamp:2023-01-07T21:37:07Z generation:2 managedFields:[map[apiVersion:mygroup.example.com/v1beta1 fieldsType:FieldsV1 fieldsV1:map[f:content:map[.:map[] f:key:map[]] f:dummy:map[] f:num:map[.:map[] f:num1:map[] f:num2:map[]]] manager:e2e.test operation:Update time:2023-01-07T21:37:27Z]] name:name1 resourceVersion:43241 uid:1f1f0869-939e-4fbd-906d-3dc2ae75b04d] num:map[num1:9223372036854775807 num2:1000000]]} �[1mSTEP�[0m: Modifying second CR Jan 7 21:37:37.375: INFO: Got : MODIFIED &{map[apiVersion:mygroup.example.com/v1beta1 content:map[key:value] dummy:test kind:WishIHadChosenNoxu metadata:map[creationTimestamp:2023-01-07T21:37:17Z generation:2 managedFields:[map[apiVersion:mygroup.example.com/v1beta1 fieldsType:FieldsV1 fieldsV1:map[f:content:map[.:map[] f:key:map[]] f:dummy:map[] f:num:map[.:map[] f:num1:map[] f:num2:map[]]] manager:e2e.test operation:Update time:2023-01-07T21:37:37Z]] name:name2 resourceVersion:43368 uid:f1e74015-ae23-42d7-a18c-c217684b5ffa] num:map[num1:9223372036854775807 num2:1000000]]} �[1mSTEP�[0m: Deleting first CR Jan 7 21:37:47.410: INFO: Got : DELETED &{map[apiVersion:mygroup.example.com/v1beta1 content:map[key:value] dummy:test kind:WishIHadChosenNoxu metadata:map[creationTimestamp:2023-01-07T21:37:07Z generation:2 managedFields:[map[apiVersion:mygroup.example.com/v1beta1 fieldsType:FieldsV1 fieldsV1:map[f:content:map[.:map[] f:key:map[]] f:dummy:map[] f:num:map[.:map[] f:num1:map[] f:num2:map[]]] manager:e2e.test operation:Update time:2023-01-07T21:37:27Z]] name:name1 resourceVersion:43422 uid:1f1f0869-939e-4fbd-906d-3dc2ae75b04d] num:map[num1:9223372036854775807 num2:1000000]]} �[1mSTEP�[0m: Deleting second CR Jan 7 21:37:57.458: INFO: Got : DELETED &{map[apiVersion:mygroup.example.com/v1beta1 content:map[key:value] dummy:test kind:WishIHadChosenNoxu metadata:map[creationTimestamp:2023-01-07T21:37:17Z generation:2 managedFields:[map[apiVersion:mygroup.example.com/v1beta1 fieldsType:FieldsV1 fieldsV1:map[f:content:map[.:map[] f:key:map[]] f:dummy:map[] f:num:map[.:map[] f:num1:map[] f:num2:map[]]] manager:e2e.test operation:Update time:2023-01-07T21:37:37Z]] name:name2 resourceVersion:43563 uid:f1e74015-ae23-42d7-a18c-c217684b5ffa] num:map[num1:9223372036854775807 num2:1000000]]} [AfterEach] [sig-api-machinery] CustomResourceDefinition Watch [Privileged:ClusterAdmin] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:38:07.523: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:38:07.556: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:09.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:11.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:13.590: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:15.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:17.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:19.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:21.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:23.593: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:25.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:27.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:29.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:31.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:33.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:35.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:37.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:39.590: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:41.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:43.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:45.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:47.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:49.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:51.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:53.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:55.590: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:57.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:59.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:01.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:03.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:05.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:07.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:09.590: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:11.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:13.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:15.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:17.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:19.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:21.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:23.590: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:25.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:27.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:29.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:31.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:33.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:35.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:37.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:39.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:41.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:43.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:45.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:47.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:49.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:51.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:53.590: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:55.594: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:57.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:59.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:01.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:03.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:05.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:07.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:09.590: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:11.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:13.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:15.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:17.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:19.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:21.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:23.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:25.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:27.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:29.592: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:31.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:33.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:35.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:37.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:39.590: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:41.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:43.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:45.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:47.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:49.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:51.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:53.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:55.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:57.589: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:59.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:01.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:03.590: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:05.590: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:07.588: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:07.620: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:07.620: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x243a8f9) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc0001da820, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "crd-watch-7665" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-api\-machinery\]\sGarbage\scollector\sshould\snot\sbe\sblocked\sby\sdependency\scircle\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:37:57.874: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_10.xml
[BeforeEach] [sig-api-machinery] Garbage collector /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:34:52.295: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename gc �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] should not be blocked by dependency circle [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 Jan 7 21:34:52.645: INFO: pod1.ObjectMeta.OwnerReferences=[]v1.OwnerReference{v1.OwnerReference{APIVersion:"v1", Kind:"Pod", Name:"pod3", UID:"4bdb734a-a62a-4890-b839-a9a1b215a0bd", Controller:(*bool)(0xc00487a3da), BlockOwnerDeletion:(*bool)(0xc00487a3db)}} Jan 7 21:34:52.678: INFO: pod2.ObjectMeta.OwnerReferences=[]v1.OwnerReference{v1.OwnerReference{APIVersion:"v1", Kind:"Pod", Name:"pod1", UID:"5d9e2419-36a1-4fc1-865a-2204adb1ec00", Controller:(*bool)(0xc00410be1e), BlockOwnerDeletion:(*bool)(0xc00410be1f)}} Jan 7 21:34:52.712: INFO: pod3.ObjectMeta.OwnerReferences=[]v1.OwnerReference{v1.OwnerReference{APIVersion:"v1", Kind:"Pod", Name:"pod2", UID:"1263ea58-0b09-4713-9b8d-2486ffe1324d", Controller:(*bool)(0xc00405e0a6), BlockOwnerDeletion:(*bool)(0xc00405e0a7)}} [AfterEach] [sig-api-machinery] Garbage collector /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:34:57.777: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:34:57.809: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:59.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:01.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:03.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:05.844: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:07.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:09.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:11.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:13.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:15.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:17.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:19.843: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:21.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:23.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:25.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:27.843: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:29.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:31.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:33.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:35.843: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:37.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:39.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:41.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:43.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:45.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:47.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:49.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:51.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:53.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:55.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:57.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:59.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:01.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:03.847: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:05.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:07.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:09.843: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:11.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:13.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:15.843: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:17.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:19.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:21.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:23.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:25.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:27.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:29.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:31.840: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:33.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:35.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:37.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:39.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:41.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:43.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:45.843: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:47.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:49.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:51.890: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:53.843: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:55.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:57.840: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:59.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:01.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:03.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:05.843: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:07.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:09.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:11.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:13.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:15.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:17.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:19.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:21.840: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:23.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:25.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:27.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:29.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:31.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:33.843: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:35.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:37.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:39.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:41.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:43.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:45.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:47.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:49.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:51.843: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:53.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:55.842: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:57.841: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:57.873: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:57.874: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x243a8f9) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000bda4e0, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "gc-4597" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-api\-machinery\]\sWatchers\sshould\sbe\sable\sto\sstart\swatching\sfrom\sa\sspecific\sresource\sversion\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:34:51.252: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_18.xml
[BeforeEach] [sig-api-machinery] Watchers /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:31:50.721: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename watch �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] should be able to start watching from a specific resource version [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 �[1mSTEP�[0m: creating a new configmap �[1mSTEP�[0m: modifying the configmap once �[1mSTEP�[0m: modifying the configmap a second time �[1mSTEP�[0m: deleting the configmap �[1mSTEP�[0m: creating a watch on configmaps from the resource version returned by the first update �[1mSTEP�[0m: Expecting to observe notifications for all changes to the configmap after the first update Jan 7 21:31:51.156: INFO: Got : MODIFIED &ConfigMap{ObjectMeta:{e2e-watch-test-resource-version watch-6808 eac40286-786e-4dcc-9369-a3a4e41a7a95 40795 0 2023-01-07 21:31:50 +0000 UTC <nil> <nil> map[watch-this-configmap:from-resource-version] map[] [] [] [{e2e.test Update v1 2023-01-07 21:31:50 +0000 UTC FieldsV1 {"f:data":{".":{},"f:mutation":{}},"f:metadata":{"f:labels":{".":{},"f:watch-this-configmap":{}}}} }]},Data:map[string]string{mutation: 2,},BinaryData:map[string][]byte{},Immutable:nil,} Jan 7 21:31:51.156: INFO: Got : DELETED &ConfigMap{ObjectMeta:{e2e-watch-test-resource-version watch-6808 eac40286-786e-4dcc-9369-a3a4e41a7a95 40796 0 2023-01-07 21:31:50 +0000 UTC <nil> <nil> map[watch-this-configmap:from-resource-version] map[] [] [] [{e2e.test Update v1 2023-01-07 21:31:50 +0000 UTC FieldsV1 {"f:data":{".":{},"f:mutation":{}},"f:metadata":{"f:labels":{".":{},"f:watch-this-configmap":{}}}} }]},Data:map[string]string{mutation: 2,},BinaryData:map[string][]byte{},Immutable:nil,} [AfterEach] [sig-api-machinery] Watchers /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:31:51.156: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:31:51.188: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:53.223: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:55.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:57.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:59.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:01.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:03.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:05.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:07.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:09.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:11.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:13.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:15.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:17.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:19.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:21.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:23.229: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:25.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:27.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:29.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:31.224: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:33.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:35.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:37.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:39.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:41.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:43.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:45.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:47.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:49.227: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:51.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:53.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:55.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:57.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:59.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:01.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:03.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:05.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:07.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:09.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:11.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:13.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:15.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:17.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:19.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:21.225: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:23.235: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:25.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:27.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:29.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:31.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:33.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:35.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:37.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:39.225: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:41.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:43.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:45.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:47.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:49.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:51.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:53.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:55.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:57.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:59.224: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:01.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:03.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:05.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:07.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:09.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:11.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:13.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:15.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:17.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:19.225: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:21.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:23.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:25.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:27.224: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:29.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:31.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:33.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:35.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:37.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:39.222: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:41.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:43.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:45.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:47.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:49.223: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:51.220: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:51.252: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:51.252: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x243a8f9) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000c36820, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "watch-6808" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sDeployment\sRollingUpdateDeployment\sshould\sdelete\sold\spods\sand\screate\snew\sones\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:38:34.959: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_12.xml
[BeforeEach] [sig-apps] Deployment /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:35:28.192: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename deployment �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [BeforeEach] [sig-apps] Deployment /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/deployment.go:89 [It] RollingUpdateDeployment should delete old pods and create new ones [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 Jan 7 21:35:28.410: INFO: Creating replica set "test-rolling-update-controller" (going to be adopted) Jan 7 21:35:28.478: INFO: Pod name sample-pod: Found 1 pods out of 1 �[1mSTEP�[0m: ensuring each pod is running Jan 7 21:35:30.541: INFO: Creating deployment "test-rolling-update-deployment" Jan 7 21:35:30.575: INFO: Ensuring deployment "test-rolling-update-deployment" gets the next revision from the one the adopted replica set "test-rolling-update-controller" has Jan 7 21:35:30.642: INFO: Ensuring status for deployment "test-rolling-update-deployment" is the expected Jan 7 21:35:30.674: INFO: deployment status: v1.DeploymentStatus{ObservedGeneration:1, Replicas:2, UpdatedReplicas:1, ReadyReplicas:1, AvailableReplicas:1, UnavailableReplicas:1, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:"Available", Status:"True", LastUpdateTime:time.Date(2023, time.January, 7, 21, 35, 30, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 7, 21, 35, 30, 0, time.Local), Reason:"MinimumReplicasAvailable", Message:"Deployment has minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 7, 21, 35, 30, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 7, 21, 35, 30, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"test-rolling-update-deployment-8656fc4b57\" is progressing."}}, CollisionCount:(*int32)(nil)} Jan 7 21:35:32.706: INFO: deployment status: v1.DeploymentStatus{ObservedGeneration:1, Replicas:2, UpdatedReplicas:1, ReadyReplicas:1, AvailableReplicas:1, UnavailableReplicas:1, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:"Available", Status:"True", LastUpdateTime:time.Date(2023, time.January, 7, 21, 35, 30, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 7, 21, 35, 30, 0, time.Local), Reason:"MinimumReplicasAvailable", Message:"Deployment has minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:time.Date(2023, time.January, 7, 21, 35, 30, 0, time.Local), LastTransitionTime:time.Date(2023, time.January, 7, 21, 35, 30, 0, time.Local), Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"test-rolling-update-deployment-8656fc4b57\" is progressing."}}, CollisionCount:(*int32)(nil)} Jan 7 21:35:34.706: INFO: Ensuring deployment "test-rolling-update-deployment" has one old replica set (the one it adopted) [AfterEach] [sig-apps] Deployment /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/deployment.go:83 Jan 7 21:35:34.798: INFO: Deployment "test-rolling-update-deployment": &Deployment{ObjectMeta:{test-rolling-update-deployment deployment-8397 7cf2232d-8c2a-4e74-b2a3-c89e4c73e303 42552 1 2023-01-07 21:35:30 +0000 UTC <nil> <nil> map[name:sample-pod] map[deployment.kubernetes.io/revision:3546343826724305833] [] [] [{e2e.test Update apps/v1 2023-01-07 21:35:30 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{".":{},"f:name":{}}},"f:spec":{"f:progressDeadlineSeconds":{},"f:replicas":{},"f:revisionHistoryLimit":{},"f:selector":{},"f:strategy":{"f:rollingUpdate":{".":{},"f:maxSurge":{},"f:maxUnavailable":{}},"f:type":{}},"f:template":{"f:metadata":{"f:labels":{".":{},"f:name":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"agnhost\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}}}} } {kube-controller-manager Update apps/v1 2023-01-07 21:35:33 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:deployment.kubernetes.io/revision":{}}},"f:status":{"f:availableReplicas":{},"f:conditions":{".":{},"k:{\"type\":\"Available\"}":{".":{},"f:lastTransitionTime":{},"f:lastUpdateTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Progressing\"}":{".":{},"f:lastTransitionTime":{},"f:lastUpdateTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:observedGeneration":{},"f:readyReplicas":{},"f:replicas":{},"f:updatedReplicas":{}}} status}]},Spec:DeploymentSpec{Replicas:*1,Selector:&v1.LabelSelector{MatchLabels:map[string]string{name: sample-pod,},MatchExpressions:[]LabelSelectorRequirement{},},Template:{{ 0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[name:sample-pod] map[] [] [] []} {[] [] [{agnhost k8s.gcr.io/e2e-test-images/agnhost:2.39 [] [] [] [] [] {map[] map[]} [] [] nil nil nil nil /dev/termination-log File IfNotPresent SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,} false false false}] [] Always 0xc004ad6d68 <nil> ClusterFirst map[] <nil> false false false <nil> &PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,} [] nil default-scheduler [] [] <nil> nil [] <nil> <nil> <nil> map[] [] <nil> nil}},Strategy:DeploymentStrategy{Type:RollingUpdate,RollingUpdate:&RollingUpdateDeployment{MaxUnavailable:25%!,(MISSING)MaxSurge:25%!,(MISSING)},},MinReadySeconds:0,RevisionHistoryLimit:*10,Paused:false,ProgressDeadlineSeconds:*600,},Status:DeploymentStatus{ObservedGeneration:1,Replicas:1,UpdatedReplicas:1,AvailableReplicas:1,UnavailableReplicas:0,Conditions:[]DeploymentCondition{DeploymentCondition{Type:Available,Status:True,Reason:MinimumReplicasAvailable,Message:Deployment has minimum availability.,LastUpdateTime:2023-01-07 21:35:30 +0000 UTC,LastTransitionTime:2023-01-07 21:35:30 +0000 UTC,},DeploymentCondition{Type:Progressing,Status:True,Reason:NewReplicaSetAvailable,Message:ReplicaSet "test-rolling-update-deployment-8656fc4b57" has successfully progressed.,LastUpdateTime:2023-01-07 21:35:33 +0000 UTC,LastTransitionTime:2023-01-07 21:35:30 +0000 UTC,},},ReadyReplicas:1,CollisionCount:nil,},} Jan 7 21:35:34.830: INFO: New ReplicaSet "test-rolling-update-deployment-8656fc4b57" of Deployment "test-rolling-update-deployment": &ReplicaSet{ObjectMeta:{test-rolling-update-deployment-8656fc4b57 deployment-8397 67684bc2-fb43-4c55-a62e-b239b3747495 42545 1 2023-01-07 21:35:30 +0000 UTC <nil> <nil> map[name:sample-pod pod-template-hash:8656fc4b57] map[deployment.kubernetes.io/desired-replicas:1 deployment.kubernetes.io/max-replicas:2 deployment.kubernetes.io/revision:3546343826724305833] [{apps/v1 Deployment test-rolling-update-deployment 7cf2232d-8c2a-4e74-b2a3-c89e4c73e303 0xc004ad7237 0xc004ad7238}] [] [{kube-controller-manager Update apps/v1 2023-01-07 21:35:30 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:deployment.kubernetes.io/desired-replicas":{},"f:deployment.kubernetes.io/max-replicas":{},"f:deployment.kubernetes.io/revision":{}},"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"7cf2232d-8c2a-4e74-b2a3-c89e4c73e303\"}":{}}},"f:spec":{"f:replicas":{},"f:selector":{},"f:template":{"f:metadata":{"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"agnhost\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}}}} } {kube-controller-manager Update apps/v1 2023-01-07 21:35:33 +0000 UTC FieldsV1 {"f:status":{"f:availableReplicas":{},"f:fullyLabeledReplicas":{},"f:observedGeneration":{},"f:readyReplicas":{},"f:replicas":{}}} status}]},Spec:ReplicaSetSpec{Replicas:*1,Selector:&v1.LabelSelector{MatchLabels:map[string]string{name: sample-pod,pod-template-hash: 8656fc4b57,},MatchExpressions:[]LabelSelectorRequirement{},},Template:{{ 0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[name:sample-pod pod-template-hash:8656fc4b57] map[] [] [] []} {[] [] [{agnhost k8s.gcr.io/e2e-test-images/agnhost:2.39 [] [] [] [] [] {map[] map[]} [] [] nil nil nil nil /dev/termination-log File IfNotPresent SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,} false false false}] [] Always 0xc004ad72e8 <nil> ClusterFirst map[] <nil> false false false <nil> &PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,} [] nil default-scheduler [] [] <nil> nil [] <nil> <nil> <nil> map[] [] <nil> nil}},MinReadySeconds:0,},Status:ReplicaSetStatus{Replicas:1,FullyLabeledReplicas:1,ObservedGeneration:1,ReadyReplicas:1,AvailableReplicas:1,Conditions:[]ReplicaSetCondition{},},} Jan 7 21:35:34.830: INFO: All old ReplicaSets of Deployment "test-rolling-update-deployment": Jan 7 21:35:34.830: INFO: &ReplicaSet{ObjectMeta:{test-rolling-update-controller deployment-8397 bef04c97-bdb3-4e32-9423-031bde337d83 42551 2 2023-01-07 21:35:28 +0000 UTC <nil> <nil> map[name:sample-pod pod:httpd] map[deployment.kubernetes.io/desired-replicas:1 deployment.kubernetes.io/max-replicas:2 deployment.kubernetes.io/revision:3546343826724305832] [{apps/v1 Deployment test-rolling-update-deployment 7cf2232d-8c2a-4e74-b2a3-c89e4c73e303 0xc004ad7107 0xc004ad7108}] [] [{e2e.test Update apps/v1 2023-01-07 21:35:28 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:deployment.kubernetes.io/revision":{}},"f:labels":{".":{},"f:name":{},"f:pod":{}}},"f:spec":{"f:selector":{},"f:template":{"f:metadata":{"f:labels":{".":{},"f:name":{},"f:pod":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"httpd\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}}}} } {kube-controller-manager Update apps/v1 2023-01-07 21:35:33 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:deployment.kubernetes.io/desired-replicas":{},"f:deployment.kubernetes.io/max-replicas":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"7cf2232d-8c2a-4e74-b2a3-c89e4c73e303\"}":{}}},"f:spec":{"f:replicas":{}}} } {kube-controller-manager Update apps/v1 2023-01-07 21:35:33 +0000 UTC FieldsV1 {"f:status":{"f:observedGeneration":{},"f:replicas":{}}} status}]},Spec:ReplicaSetSpec{Replicas:*0,Selector:&v1.LabelSelector{MatchLabels:map[string]string{name: sample-pod,pod: httpd,},MatchExpressions:[]LabelSelectorRequirement{},},Template:{{ 0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[name:sample-pod pod:httpd] map[] [] [] []} {[] [] [{httpd k8s.gcr.io/e2e-test-images/httpd:2.4.38-2 [] [] [] [] [] {map[] map[]} [] [] nil nil nil nil /dev/termination-log File IfNotPresent nil false false false}] [] Always 0xc004ad71c8 <nil> ClusterFirst map[] <nil> false false false <nil> PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,} [] nil default-scheduler [] [] <nil> nil [] <nil> <nil> <nil> map[] [] <nil> nil}},MinReadySeconds:0,},Status:ReplicaSetStatus{Replicas:0,FullyLabeledReplicas:0,ObservedGeneration:2,ReadyReplicas:0,AvailableReplicas:0,Conditions:[]ReplicaSetCondition{},},} Jan 7 21:35:34.862: INFO: Pod "test-rolling-update-deployment-8656fc4b57-9m7j6" is available: &Pod{ObjectMeta:{test-rolling-update-deployment-8656fc4b57-9m7j6 test-rolling-update-deployment-8656fc4b57- deployment-8397 d777663b-d3e2-4766-830c-5c25576eb655 42544 0 2023-01-07 21:35:30 +0000 UTC <nil> <nil> map[name:sample-pod pod-template-hash:8656fc4b57] map[] [{apps/v1 ReplicaSet test-rolling-update-deployment-8656fc4b57 67684bc2-fb43-4c55-a62e-b239b3747495 0xc004c5e0d7 0xc004c5e0d8}] [] [{kube-controller-manager Update v1 2023-01-07 21:35:30 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{},"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"67684bc2-fb43-4c55-a62e-b239b3747495\"}":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"agnhost\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}} } {kubelet Update v1 2023-01-07 21:35:33 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"ContainersReady\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Initialized\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:status":{},"f:type":{}}},"f:containerStatuses":{},"f:hostIP":{},"f:phase":{},"f:podIP":{},"f:podIPs":{".":{},"k:{\"ip\":\"100.96.2.82\"}":{".":{},"f:ip":{}}},"f:startTime":{}}} status}]},Spec:PodSpec{Volumes:[]Volume{Volume{Name:kube-api-access-zfsgh,VolumeSource:VolumeSource{HostPath:nil,EmptyDir:nil,GCEPersistentDisk:nil,AWSElasticBlockStore:nil,GitRepo:nil,Secret:nil,NFS:nil,ISCSI:nil,Glusterfs:nil,PersistentVolumeClaim:nil,RBD:nil,FlexVolume:nil,Cinder:nil,CephFS:nil,Flocker:nil,DownwardAPI:nil,FC:nil,AzureFile:nil,ConfigMap:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Projected:&ProjectedVolumeSource{Sources:[]VolumeProjection{VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:nil,ServiceAccountToken:&ServiceAccountTokenProjection{Audience:,ExpirationSeconds:*3607,Path:token,},},VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:&ConfigMapProjection{LocalObjectReference:LocalObjectReference{Name:kube-root-ca.crt,},Items:[]KeyToPath{KeyToPath{Key:ca.crt,Path:ca.crt,Mode:nil,},},Optional:nil,},ServiceAccountToken:nil,},VolumeProjection{Secret:nil,DownwardAPI:&DownwardAPIProjection{Items:[]DownwardAPIVolumeFile{DownwardAPIVolumeFile{Path:namespace,FieldRef:&ObjectFieldSelector{APIVersion:v1,FieldPath:metadata.namespace,},ResourceFieldRef:nil,Mode:nil,},},},ConfigMap:nil,ServiceAccountToken:nil,},},DefaultMode:*420,},StorageOS:nil,CSI:nil,Ephemeral:nil,},},},Containers:[]Container{Container{Name:agnhost,Image:k8s.gcr.io/e2e-test-images/agnhost:2.39,Command:[],Args:[],WorkingDir:,Ports:[]ContainerPort{},Env:[]EnvVar{},Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},},VolumeMounts:[]VolumeMount{VolumeMount{Name:kube-api-access-zfsgh,ReadOnly:true,MountPath:/var/run/secrets/kubernetes.io/serviceaccount,SubPath:,MountPropagation:nil,SubPathExpr:,},},LivenessProbe:nil,ReadinessProbe:nil,Lifecycle:nil,TerminationMessagePath:/dev/termination-log,ImagePullPolicy:IfNotPresent,SecurityContext:&SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,},Stdin:false,StdinOnce:false,TTY:false,EnvFrom:[]EnvFromSource{},TerminationMessagePolicy:File,VolumeDevices:[]VolumeDevice{},StartupProbe:nil,},},RestartPolicy:Always,TerminationGracePeriodSeconds:*0,ActiveDeadlineSeconds:nil,DNSPolicy:ClusterFirst,NodeSelector:map[string]string{},ServiceAccountName:default,DeprecatedServiceAccount:default,NodeName:ip-172-20-51-5.ec2.internal,HostNetwork:false,HostPID:false,HostIPC:false,SecurityContext:&PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,},ImagePullSecrets:[]LocalObjectReference{},Hostname:,Subdomain:,Affinity:nil,SchedulerName:default-scheduler,InitContainers:[]Container{},AutomountServiceAccountToken:nil,Tolerations:[]Toleration{Toleration{Key:node.kubernetes.io/not-ready,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},Toleration{Key:node.kubernetes.io/unreachable,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},},HostAliases:[]HostAlias{},PriorityClassName:,Priority:*0,DNSConfig:nil,ShareProcessNamespace:nil,ReadinessGates:[]PodReadinessGate{},RuntimeClassName:nil,EnableServiceLinks:*true,PreemptionPolicy:*PreemptLowerPriority,Overhead:ResourceList{},TopologySpreadConstraints:[]TopologySpreadConstraint{},EphemeralContainers:[]EphemeralContainer{},SetHostnameAsFQDN:nil,OS:nil,},Status:PodStatus{Phase:Running,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-01-07 21:35:30 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-01-07 21:35:33 +0000 UTC,Reason:,Message:,},PodCondition{Type:ContainersReady,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-01-07 21:35:33 +0000 UTC,Reason:,Message:,},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2023-01-07 21:35:30 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:172.20.51.5,PodIP:100.96.2.82,StartTime:2023-01-07 21:35:30 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:agnhost,State:ContainerState{Waiting:nil,Running:&ContainerStateRunning{StartedAt:2023-01-07 21:35:32 +0000 UTC,},Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:true,RestartCount:0,Image:k8s.gcr.io/e2e-test-images/agnhost:2.39,ImageID:docker-pullable://k8s.gcr.io/e2e-test-images/agnhost@sha256:7e8bdd271312fd25fc5ff5a8f04727be84044eb3d7d8d03611972a6752e2e11e,ContainerID:docker://22f5867625eed95169ec8647013b4619766a564d3b0e12d5130c5d8929211566,Started:*true,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:100.96.2.82,},},EphemeralContainerStatuses:[]ContainerStatus{},},} [AfterEach] [sig-apps] Deployment /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:35:34.862: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:35:34.894: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:36.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:38.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:40.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:42.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:44.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:46.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:48.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:50.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:52.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:54.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:56.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:58.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:00.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:02.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:04.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:06.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:08.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:10.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:12.926: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:14.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:16.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:18.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:20.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:22.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:24.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:26.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:28.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:30.929: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:32.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:34.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:36.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:38.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:40.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:42.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:44.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:46.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:48.926: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:50.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:52.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:54.931: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:56.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:58.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:00.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:02.926: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:04.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:06.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:08.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:10.929: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:12.929: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:14.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:16.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:18.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:20.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:22.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:24.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:26.926: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:28.926: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:30.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:32.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:34.929: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:36.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:38.929: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:40.929: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:42.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:44.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:46.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:48.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:50.929: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:52.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:54.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:56.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:58.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:00.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:02.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:04.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:06.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:08.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:10.944: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:12.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:14.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:16.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:18.929: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:20.929: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:22.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:24.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:26.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:28.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:30.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:32.928: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:34.927: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:34.959: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:34.959: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0xc) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc00078c340, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "deployment-8397" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sDisruptionController\sshould\sblock\san\seviction\suntil\sthe\sPDB\sis\supdated\sto\sallow\sit\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:53:53.369: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_01.xml
[BeforeEach] [sig-apps] DisruptionController /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:43:12.266: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename disruption �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [BeforeEach] [sig-apps] DisruptionController /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/disruption.go:69 [It] should block an eviction until the PDB is updated to allow it [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 �[1mSTEP�[0m: Creating a pdb that targets all three pods in a test replica set �[1mSTEP�[0m: Waiting for the pdb to be processed �[1mSTEP�[0m: First trying to evict a pod which shouldn't be evictable �[1mSTEP�[0m: Waiting for all pods to be running Jan 7 21:43:12.612: INFO: running pods: 0 < 3 Jan 7 21:43:14.645: INFO: running pods: 0 < 3 Jan 7 21:43:16.646: INFO: running pods: 0 < 3 Jan 7 21:43:18.649: INFO: running pods: 0 < 3 Jan 7 21:43:20.644: INFO: running pods: 1 < 3 Jan 7 21:43:22.645: INFO: running pods: 2 < 3 Jan 7 21:43:24.645: INFO: running pods: 2 < 3 Jan 7 21:43:26.644: INFO: running pods: 2 < 3 Jan 7 21:43:28.644: INFO: running pods: 2 < 3 Jan 7 21:43:30.644: INFO: running pods: 2 < 3 Jan 7 21:43:32.644: INFO: running pods: 2 < 3 Jan 7 21:43:34.652: INFO: running pods: 2 < 3 Jan 7 21:43:36.645: INFO: running pods: 2 < 3 Jan 7 21:43:38.644: INFO: running pods: 2 < 3 Jan 7 21:43:40.646: INFO: running pods: 2 < 3 Jan 7 21:43:42.645: INFO: running pods: 2 < 3 Jan 7 21:43:44.645: INFO: running pods: 2 < 3 Jan 7 21:43:46.644: INFO: running pods: 2 < 3 Jan 7 21:43:48.651: INFO: running pods: 2 < 3 Jan 7 21:43:50.645: INFO: running pods: 2 < 3 Jan 7 21:43:52.644: INFO: running pods: 2 < 3 Jan 7 21:43:54.645: INFO: running pods: 2 < 3 Jan 7 21:43:56.644: INFO: running pods: 2 < 3 Jan 7 21:43:58.644: INFO: running pods: 2 < 3 Jan 7 21:44:00.646: INFO: running pods: 2 < 3 Jan 7 21:44:02.645: INFO: running pods: 2 < 3 Jan 7 21:44:04.645: INFO: running pods: 2 < 3 Jan 7 21:44:06.645: INFO: running pods: 2 < 3 Jan 7 21:44:08.644: INFO: running pods: 2 < 3 Jan 7 21:44:10.644: INFO: running pods: 2 < 3 Jan 7 21:44:12.644: INFO: running pods: 2 < 3 Jan 7 21:44:14.645: INFO: running pods: 2 < 3 Jan 7 21:44:16.645: INFO: running pods: 2 < 3 Jan 7 21:44:18.645: INFO: running pods: 2 < 3 Jan 7 21:44:20.644: INFO: running pods: 2 < 3 Jan 7 21:44:22.644: INFO: running pods: 2 < 3 Jan 7 21:44:24.646: INFO: running pods: 2 < 3 Jan 7 21:44:26.645: INFO: running pods: 2 < 3 Jan 7 21:44:28.645: INFO: running pods: 2 < 3 Jan 7 21:44:30.646: INFO: running pods: 2 < 3 Jan 7 21:44:32.644: INFO: running pods: 2 < 3 Jan 7 21:44:34.644: INFO: running pods: 2 < 3 Jan 7 21:44:36.644: INFO: running pods: 2 < 3 Jan 7 21:44:38.644: INFO: running pods: 2 < 3 Jan 7 21:44:40.647: INFO: running pods: 2 < 3 Jan 7 21:44:42.644: INFO: running pods: 2 < 3 Jan 7 21:44:44.645: INFO: running pods: 2 < 3 Jan 7 21:44:46.644: INFO: running pods: 2 < 3 Jan 7 21:44:48.646: INFO: running pods: 2 < 3 Jan 7 21:44:50.644: INFO: running pods: 2 < 3 Jan 7 21:44:52.644: INFO: running pods: 2 < 3 Jan 7 21:44:54.646: INFO: running pods: 2 < 3 Jan 7 21:44:56.644: INFO: running pods: 2 < 3 Jan 7 21:44:58.647: INFO: running pods: 2 < 3 Jan 7 21:45:00.646: INFO: running pods: 2 < 3 Jan 7 21:45:02.644: INFO: running pods: 2 < 3 Jan 7 21:45:04.651: INFO: running pods: 2 < 3 Jan 7 21:45:06.645: INFO: running pods: 2 < 3 Jan 7 21:45:08.645: INFO: running pods: 2 < 3 Jan 7 21:45:10.644: INFO: running pods: 2 < 3 Jan 7 21:45:12.644: INFO: running pods: 2 < 3 Jan 7 21:45:14.644: INFO: running pods: 2 < 3 Jan 7 21:45:16.644: INFO: running pods: 2 < 3 Jan 7 21:45:18.644: INFO: running pods: 2 < 3 Jan 7 21:45:20.647: INFO: running pods: 2 < 3 Jan 7 21:45:22.644: INFO: running pods: 2 < 3 Jan 7 21:45:24.645: INFO: running pods: 2 < 3 Jan 7 21:45:26.650: INFO: running pods: 2 < 3 Jan 7 21:45:28.645: INFO: running pods: 2 < 3 Jan 7 21:45:30.644: INFO: running pods: 2 < 3 Jan 7 21:45:32.644: INFO: running pods: 2 < 3 Jan 7 21:45:34.644: INFO: running pods: 2 < 3 Jan 7 21:45:36.644: INFO: running pods: 2 < 3 Jan 7 21:45:38.645: INFO: running pods: 2 < 3 Jan 7 21:45:40.644: INFO: running pods: 2 < 3 Jan 7 21:45:42.644: INFO: running pods: 2 < 3 Jan 7 21:45:44.644: INFO: running pods: 2 < 3 Jan 7 21:45:46.644: INFO: running pods: 2 < 3 Jan 7 21:45:48.645: INFO: running pods: 2 < 3 Jan 7 21:45:50.643: INFO: running pods: 2 < 3 Jan 7 21:45:52.643: INFO: running pods: 2 < 3 Jan 7 21:45:54.644: INFO: running pods: 2 < 3 Jan 7 21:45:56.644: INFO: running pods: 2 < 3 Jan 7 21:45:58.643: INFO: running pods: 2 < 3 Jan 7 21:46:00.645: INFO: running pods: 2 < 3 Jan 7 21:46:02.644: INFO: running pods: 2 < 3 Jan 7 21:46:04.645: INFO: running pods: 2 < 3 Jan 7 21:46:06.644: INFO: running pods: 2 < 3 Jan 7 21:46:08.644: INFO: running pods: 2 < 3 Jan 7 21:46:10.644: INFO: running pods: 2 < 3 Jan 7 21:46:12.644: INFO: running pods: 2 < 3 Jan 7 21:46:14.643: INFO: running pods: 2 < 3 Jan 7 21:46:16.644: INFO: running pods: 2 < 3 Jan 7 21:46:18.645: INFO: running pods: 2 < 3 Jan 7 21:46:20.645: INFO: running pods: 2 < 3 Jan 7 21:46:22.643: INFO: running pods: 2 < 3 Jan 7 21:46:24.655: INFO: running pods: 2 < 3 Jan 7 21:46:26.644: INFO: running pods: 2 < 3 Jan 7 21:46:28.644: INFO: running pods: 2 < 3 Jan 7 21:46:30.644: INFO: running pods: 2 < 3 Jan 7 21:46:32.644: INFO: running pods: 2 < 3 Jan 7 21:46:34.644: INFO: running pods: 2 < 3 Jan 7 21:46:36.644: INFO: running pods: 2 < 3 Jan 7 21:46:38.645: INFO: running pods: 2 < 3 Jan 7 21:46:40.644: INFO: running pods: 2 < 3 Jan 7 21:46:42.644: INFO: running pods: 2 < 3 Jan 7 21:46:44.644: INFO: running pods: 2 < 3 Jan 7 21:46:46.644: INFO: running pods: 2 < 3 Jan 7 21:46:48.644: INFO: running pods: 2 < 3 Jan 7 21:46:50.645: INFO: running pods: 2 < 3 Jan 7 21:46:52.643: INFO: running pods: 2 < 3 Jan 7 21:46:54.643: INFO: running pods: 2 < 3 Jan 7 21:46:56.644: INFO: running pods: 2 < 3 Jan 7 21:46:58.643: INFO: running pods: 2 < 3 Jan 7 21:47:00.643: INFO: running pods: 2 < 3 Jan 7 21:47:02.643: INFO: running pods: 2 < 3 Jan 7 21:47:04.645: INFO: running pods: 2 < 3 Jan 7 21:47:06.649: INFO: running pods: 2 < 3 Jan 7 21:47:08.644: INFO: running pods: 2 < 3 Jan 7 21:47:10.645: INFO: running pods: 2 < 3 Jan 7 21:47:12.644: INFO: running pods: 2 < 3 Jan 7 21:47:14.645: INFO: running pods: 2 < 3 Jan 7 21:47:16.643: INFO: running pods: 2 < 3 Jan 7 21:47:18.643: INFO: running pods: 2 < 3 Jan 7 21:47:20.643: INFO: running pods: 2 < 3 Jan 7 21:47:22.651: INFO: running pods: 2 < 3 Jan 7 21:47:24.645: INFO: running pods: 2 < 3 Jan 7 21:47:26.644: INFO: running pods: 2 < 3 Jan 7 21:47:28.644: INFO: running pods: 2 < 3 Jan 7 21:47:30.645: INFO: running pods: 2 < 3 Jan 7 21:47:32.644: INFO: running pods: 2 < 3 Jan 7 21:47:34.644: INFO: running pods: 2 < 3 Jan 7 21:47:36.644: INFO: running pods: 2 < 3 Jan 7 21:47:38.645: INFO: running pods: 2 < 3 Jan 7 21:47:40.643: INFO: running pods: 2 < 3 Jan 7 21:47:42.644: INFO: running pods: 2 < 3 Jan 7 21:47:44.644: INFO: running pods: 2 < 3 Jan 7 21:47:46.643: INFO: running pods: 2 < 3 Jan 7 21:47:48.643: INFO: running pods: 2 < 3 Jan 7 21:47:50.644: INFO: running pods: 2 < 3 Jan 7 21:47:52.644: INFO: running pods: 2 < 3 Jan 7 21:47:54.644: INFO: running pods: 2 < 3 Jan 7 21:47:56.643: INFO: running pods: 2 < 3 Jan 7 21:47:58.645: INFO: running pods: 2 < 3 Jan 7 21:48:00.645: INFO: running pods: 2 < 3 Jan 7 21:48:02.643: INFO: running pods: 2 < 3 Jan 7 21:48:04.644: INFO: running pods: 2 < 3 Jan 7 21:48:06.644: INFO: running pods: 2 < 3 Jan 7 21:48:08.644: INFO: running pods: 2 < 3 Jan 7 21:48:10.644: INFO: running pods: 2 < 3 Jan 7 21:48:12.643: INFO: running pods: 2 < 3 Jan 7 21:48:14.645: INFO: running pods: 2 < 3 Jan 7 21:48:16.644: INFO: running pods: 2 < 3 Jan 7 21:48:18.643: INFO: running pods: 2 < 3 Jan 7 21:48:20.644: INFO: running pods: 2 < 3 Jan 7 21:48:22.643: INFO: running pods: 2 < 3 Jan 7 21:48:24.645: INFO: running pods: 2 < 3 Jan 7 21:48:26.643: INFO: running pods: 2 < 3 Jan 7 21:48:28.644: INFO: running pods: 2 < 3 Jan 7 21:48:30.644: INFO: running pods: 2 < 3 Jan 7 21:48:32.644: INFO: running pods: 2 < 3 Jan 7 21:48:34.644: INFO: running pods: 2 < 3 Jan 7 21:48:36.644: INFO: running pods: 2 < 3 Jan 7 21:48:38.645: INFO: running pods: 2 < 3 Jan 7 21:48:40.645: INFO: running pods: 2 < 3 Jan 7 21:48:42.643: INFO: running pods: 2 < 3 Jan 7 21:48:44.646: INFO: running pods: 2 < 3 Jan 7 21:48:46.644: INFO: running pods: 2 < 3 Jan 7 21:48:48.644: INFO: running pods: 2 < 3 Jan 7 21:48:50.644: INFO: running pods: 2 < 3 Jan 7 21:48:52.644: INFO: running pods: 2 < 3 Jan 7 21:48:54.646: INFO: running pods: 2 < 3 Jan 7 21:48:56.644: INFO: running pods: 2 < 3 Jan 7 21:48:58.644: INFO: running pods: 2 < 3 Jan 7 21:49:00.646: INFO: running pods: 2 < 3 Jan 7 21:49:02.645: INFO: running pods: 2 < 3 Jan 7 21:49:04.644: INFO: running pods: 2 < 3 Jan 7 21:49:06.645: INFO: running pods: 2 < 3 Jan 7 21:49:08.644: INFO: running pods: 2 < 3 Jan 7 21:49:10.644: INFO: running pods: 2 < 3 Jan 7 21:49:12.645: INFO: running pods: 2 < 3 Jan 7 21:49:14.644: INFO: running pods: 2 < 3 Jan 7 21:49:16.645: INFO: running pods: 2 < 3 Jan 7 21:49:18.645: INFO: running pods: 2 < 3 Jan 7 21:49:20.646: INFO: running pods: 2 < 3 Jan 7 21:49:22.644: INFO: running pods: 2 < 3 Jan 7 21:49:24.646: INFO: running pods: 2 < 3 Jan 7 21:49:26.644: INFO: running pods: 2 < 3 Jan 7 21:49:28.644: INFO: running pods: 2 < 3 Jan 7 21:49:30.644: INFO: running pods: 2 < 3 Jan 7 21:49:32.644: INFO: running pods: 2 < 3 Jan 7 21:49:34.645: INFO: running pods: 2 < 3 Jan 7 21:49:36.644: INFO: running pods: 2 < 3 Jan 7 21:49:38.646: INFO: running pods: 2 < 3 Jan 7 21:49:40.644: INFO: running pods: 2 < 3 Jan 7 21:49:42.644: INFO: running pods: 2 < 3 Jan 7 21:49:44.645: INFO: running pods: 2 < 3 Jan 7 21:49:46.645: INFO: running pods: 2 < 3 Jan 7 21:49:48.645: INFO: running pods: 2 < 3 Jan 7 21:49:50.644: INFO: running pods: 2 < 3 Jan 7 21:49:52.644: INFO: running pods: 2 < 3 Jan 7 21:49:54.646: INFO: running pods: 2 < 3 Jan 7 21:49:56.645: INFO: running pods: 2 < 3 Jan 7 21:49:58.645: INFO: running pods: 2 < 3 Jan 7 21:50:00.645: INFO: running pods: 2 < 3 Jan 7 21:50:02.644: INFO: running pods: 2 < 3 Jan 7 21:50:04.645: INFO: running pods: 2 < 3 Jan 7 21:50:06.644: INFO: running pods: 2 < 3 Jan 7 21:50:08.645: INFO: running pods: 2 < 3 Jan 7 21:50:10.644: INFO: running pods: 2 < 3 Jan 7 21:50:12.644: INFO: running pods: 2 < 3 Jan 7 21:50:14.644: INFO: running pods: 2 < 3 Jan 7 21:50:16.645: INFO: running pods: 2 < 3 Jan 7 21:50:18.644: INFO: running pods: 2 < 3 Jan 7 21:50:20.644: INFO: running pods: 2 < 3 Jan 7 21:50:22.645: INFO: running pods: 2 < 3 Jan 7 21:50:24.648: INFO: running pods: 2 < 3 Jan 7 21:50:26.644: INFO: running pods: 2 < 3 Jan 7 21:50:28.646: INFO: running pods: 2 < 3 Jan 7 21:50:30.646: INFO: running pods: 2 < 3 Jan 7 21:50:32.644: INFO: running pods: 2 < 3 Jan 7 21:50:34.644: INFO: running pods: 2 < 3 Jan 7 21:50:36.645: INFO: running pods: 2 < 3 Jan 7 21:50:38.645: INFO: running pods: 2 < 3 Jan 7 21:50:40.644: INFO: running pods: 2 < 3 Jan 7 21:50:42.644: INFO: running pods: 2 < 3 Jan 7 21:50:44.644: INFO: running pods: 2 < 3 Jan 7 21:50:46.644: INFO: running pods: 2 < 3 Jan 7 21:50:48.644: INFO: running pods: 2 < 3 �[1mSTEP�[0m: locating a running pod �[1mSTEP�[0m: Updating the pdb to allow a pod to be evicted �[1mSTEP�[0m: Waiting for the pdb to be processed �[1mSTEP�[0m: Trying to evict the same pod we tried earlier which should now be evictable �[1mSTEP�[0m: Waiting for all pods to be running �[1mSTEP�[0m: Waiting for the pdb to observed all healthy pods �[1mSTEP�[0m: Patching the pdb to disallow a pod to be evicted �[1mSTEP�[0m: Waiting for the pdb to be processed �[1mSTEP�[0m: Waiting for all pods to be running Jan 7 21:50:51.038: INFO: running pods: 2 < 3 �[1mSTEP�[0m: locating a running pod �[1mSTEP�[0m: Deleting the pdb to allow a pod to be evicted �[1mSTEP�[0m: Waiting for the pdb to be deleted �[1mSTEP�[0m: Trying to evict the same pod we tried earlier which should now be evictable �[1mSTEP�[0m: Waiting for all pods to be running [AfterEach] [sig-apps] DisruptionController /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:50:53.269: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:50:53.302: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:50:55.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:50:57.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:50:59.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:01.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:03.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:05.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:07.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:09.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:11.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:13.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:15.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:17.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:19.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:21.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:23.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:25.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:27.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:29.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:31.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:33.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:35.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:37.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:39.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:41.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:43.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:45.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:47.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:49.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:51.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:53.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:55.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:57.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:51:59.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:01.337: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:03.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:05.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:07.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:09.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:11.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:13.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:15.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:17.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:19.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:21.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:23.350: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:25.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:27.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:29.337: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:31.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:33.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:35.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:37.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:39.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:41.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:43.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:45.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:47.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:49.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:51.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:53.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:55.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:57.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:52:59.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:01.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:03.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:05.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:07.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:09.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:11.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:13.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:15.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:17.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:19.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:21.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:23.338: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:25.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:27.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:29.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:31.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:33.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:35.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:37.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:39.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:41.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:43.334: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:45.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:47.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:49.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:51.335: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:53.336: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:53.368: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:45:44 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:45:48 +0000 UTC}]. Failure Jan 7 21:53:53.369: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x243a8f9) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000103d40, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "disruption-2275" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sReplicaSet\sshould\sserve\sa\sbasic\simage\son\seach\sreplica\swith\sa\spublic\simage\s\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:41:42.554: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_12.xml
[BeforeEach] [sig-apps] ReplicaSet /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:38:35.018: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename replicaset �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] should serve a basic image on each replica with a public image [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 Jan 7 21:38:35.235: INFO: Creating ReplicaSet my-hostname-basic-119ae8e4-66e5-41fc-b87e-ebd0514d7dbe Jan 7 21:38:35.299: INFO: Pod name my-hostname-basic-119ae8e4-66e5-41fc-b87e-ebd0514d7dbe: Found 1 pods out of 1 Jan 7 21:38:35.299: INFO: Ensuring a pod for ReplicaSet "my-hostname-basic-119ae8e4-66e5-41fc-b87e-ebd0514d7dbe" is running Jan 7 21:38:37.361: INFO: Pod "my-hostname-basic-119ae8e4-66e5-41fc-b87e-ebd0514d7dbe-xb8sz" is running (conditions: [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-07 21:38:35 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-07 21:38:35 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [my-hostname-basic-119ae8e4-66e5-41fc-b87e-ebd0514d7dbe]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-07 21:38:35 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [my-hostname-basic-119ae8e4-66e5-41fc-b87e-ebd0514d7dbe]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-07 21:38:35 +0000 UTC Reason: Message:}]) Jan 7 21:38:37.361: INFO: Trying to dial the pod Jan 7 21:38:42.457: INFO: Controller my-hostname-basic-119ae8e4-66e5-41fc-b87e-ebd0514d7dbe: Got expected result from replica 1 [my-hostname-basic-119ae8e4-66e5-41fc-b87e-ebd0514d7dbe-xb8sz]: "my-hostname-basic-119ae8e4-66e5-41fc-b87e-ebd0514d7dbe-xb8sz", 1 of 1 required successes so far [AfterEach] [sig-apps] ReplicaSet /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:38:42.457: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:38:42.489: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:44.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:46.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:48.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:50.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:52.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:54.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:56.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:58.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:00.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:02.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:04.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:06.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:08.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:10.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:12.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:14.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:16.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:18.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:20.544: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:22.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:24.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:26.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:28.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:30.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:32.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:34.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:36.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:38.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:40.527: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:42.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:44.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:46.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:48.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:50.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:52.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:54.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:56.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:58.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:00.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:02.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:04.526: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:06.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:08.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:10.524: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:12.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:14.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:16.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:18.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:20.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:22.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:24.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:26.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:28.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:30.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:32.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:34.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:36.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:38.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:40.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:42.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:44.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:46.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:48.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:50.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:52.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:54.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:56.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:58.524: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:00.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:02.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:04.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:06.528: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:08.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:10.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:12.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:14.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:16.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:18.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:20.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:22.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:24.527: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:26.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:28.524: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:30.521: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:32.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:34.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:36.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:38.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:40.523: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:42.522: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:42.554: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:42.554: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0xc) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc00078c340, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "replicaset-2783" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sReplicationController\sshould\srelease\sno\slonger\smatching\spods\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:36:31.702: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_14.xml
[BeforeEach] [sig-apps] ReplicationController /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:33:31.232: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename replication-controller �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [BeforeEach] [sig-apps] ReplicationController /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/rc.go:54 [It] should release no longer matching pods [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 �[1mSTEP�[0m: Given a ReplicationController is created �[1mSTEP�[0m: When the matched label of one of its pods change Jan 7 21:33:31.509: INFO: Pod name pod-release: Found 1 pods out of 1 �[1mSTEP�[0m: Then the pod is released [AfterEach] [sig-apps] ReplicationController /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:33:31.607: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:33:31.638: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:33.678: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:35.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:37.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:39.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:41.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:43.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:45.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:47.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:49.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:51.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:53.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:55.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:57.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:59.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:01.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:03.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:05.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:07.676: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:09.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:11.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:13.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:15.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:17.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:19.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:21.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:23.673: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:25.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:27.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:29.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:31.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:33.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:35.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:37.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:39.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:41.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:43.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:45.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:47.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:49.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:51.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:53.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:55.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:57.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:59.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:01.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:03.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:05.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:07.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:09.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:11.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:13.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:15.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:17.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:19.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:21.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:23.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:25.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:27.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:29.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:31.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:33.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:35.685: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:37.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:39.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:41.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:43.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:45.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:47.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:49.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:51.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:53.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:55.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:57.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:59.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:01.674: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:03.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:05.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:07.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:09.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:11.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:13.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:15.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:17.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:19.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:21.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:23.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:25.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:27.672: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:29.670: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:31.671: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:31.702: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:31.702: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x450d0a1112021053) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc00069f6c0, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "replication-controller-823" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sPort\sforwarding\sWith\sa\sserver\slistening\son\slocalhost\sshould\ssupport\sforwarding\sover\swebsockets$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:34:22.178: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_08.xml
{"msg":"FAILED [sig-network] Networking Granular Checks: Services should function for pod-Service: http","total":-1,"completed":16,"skipped":184,"failed":1,"failures":["[sig-network] Networking Granular Checks: Services should function for pod-Service: http"]} [BeforeEach] [sig-cli] Kubectl Port forwarding /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:31:15.559: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename port-forwarding �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] should support forwarding over websockets /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/portforward.go:490 Jan 7 21:31:15.772: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Creating the pod Jan 7 21:31:15.837: INFO: The status of Pod pfpod is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:31:17.871: INFO: The status of Pod pfpod is Running (Ready = false) Jan 7 21:31:19.869: INFO: The status of Pod pfpod is Running (Ready = false) Jan 7 21:31:21.868: INFO: The status of Pod pfpod is Running (Ready = true) �[1mSTEP�[0m: Sending the expected data to the local port �[1mSTEP�[0m: Reading data from the local port �[1mSTEP�[0m: Verifying logs [AfterEach] [sig-cli] Kubectl Port forwarding /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:31:22.083: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:31:22.115: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:24.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:26.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:28.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:30.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:32.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:34.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:36.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:38.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:40.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:42.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:44.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:46.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:48.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:50.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:52.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:54.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:56.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:58.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:00.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:02.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:04.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:06.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:08.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:10.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:12.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:14.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:16.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:18.149: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:20.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:22.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:24.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:26.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:28.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:30.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:32.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:34.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:36.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:38.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:40.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:42.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:44.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:46.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:48.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:50.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:52.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:54.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:56.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:58.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:00.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:02.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:04.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:06.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:08.149: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:10.149: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:12.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:14.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:16.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:18.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:20.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:22.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:24.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:26.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:28.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:30.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:32.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:34.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:36.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:38.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:40.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:42.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:44.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:46.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:48.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:50.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:52.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:54.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:56.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:58.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:00.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:02.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:04.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:06.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:08.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:10.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:12.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:14.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:16.146: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:18.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:20.148: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:22.147: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:22.178: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:22.178: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x243a8f9) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000d5c340, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "port-forwarding-6763" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sclient\sKubectl\screate\squota\sshould\screate\sa\squota\swithout\sscopes$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:37:16.247: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_07.xml
[BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:34:15.724: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename kubectl �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:244 [It] should create a quota without scopes /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:1784 �[1mSTEP�[0m: calling kubectl quota Jan 7 21:34:15.930: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-1167 create quota million --hard=pods=1000000,services=1000000' Jan 7 21:34:16.126: INFO: stderr: "" Jan 7 21:34:16.126: INFO: stdout: "resourcequota/million created\n" �[1mSTEP�[0m: verifying that the quota was created [AfterEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:34:16.155: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:34:16.185: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:18.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:20.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:22.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:24.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:26.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:28.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:30.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:32.218: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:34.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:36.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:38.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:40.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:42.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:44.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:46.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:48.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:50.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:52.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:54.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:56.221: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:58.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:00.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:02.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:04.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:06.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:08.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:10.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:12.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:14.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:16.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:18.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:20.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:22.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:24.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:26.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:28.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:30.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:32.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:34.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:36.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:38.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:40.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:42.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:44.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:46.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:48.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:50.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:52.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:54.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:56.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:58.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:00.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:02.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:04.218: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:06.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:08.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:10.218: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:12.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:14.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:16.219: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:18.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:20.218: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:22.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:24.218: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:26.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:28.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:30.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:32.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:34.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:36.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:38.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:40.215: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:42.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:44.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:46.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:48.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:50.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:52.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:54.230: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:56.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:58.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:00.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:02.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:04.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:06.218: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:08.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:10.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:12.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:14.216: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:16.217: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:16.247: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:16.247: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x0) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000c7da00, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "kubectl-1167" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sclient\sKubectl\sdescribe\sshould\scheck\sif\skubectl\sdescribe\sprints\srelevant\sinformation\sfor\src\sand\spods\s\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:28:51.434: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_19.xml
[BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:25:46.480: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename kubectl �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:244 [It] should check if kubectl describe prints relevant information for rc and pods [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 Jan 7 21:25:46.685: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-647 create -f -' Jan 7 21:25:47.559: INFO: stderr: "" Jan 7 21:25:47.559: INFO: stdout: "replicationcontroller/agnhost-primary created\n" Jan 7 21:25:47.559: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-647 create -f -' Jan 7 21:25:47.881: INFO: stderr: "" Jan 7 21:25:47.881: INFO: stdout: "service/agnhost-primary created\n" �[1mSTEP�[0m: Waiting for Agnhost primary to start. Jan 7 21:25:48.911: INFO: Selector matched 1 pods for map[app:agnhost] Jan 7 21:25:48.911: INFO: Found 0 / 1 Jan 7 21:25:49.912: INFO: Selector matched 1 pods for map[app:agnhost] Jan 7 21:25:49.912: INFO: Found 1 / 1 Jan 7 21:25:49.912: INFO: WaitFor completed with timeout 5m0s. Pods found = 1 out of 1 Jan 7 21:25:49.942: INFO: Selector matched 1 pods for map[app:agnhost] Jan 7 21:25:49.942: INFO: ForEach: Found 1 pods from the filter. Now looping through them. Jan 7 21:25:49.942: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-647 describe pod agnhost-primary-2257h' Jan 7 21:25:50.175: INFO: stderr: "" Jan 7 21:25:50.175: INFO: stdout: "Name: agnhost-primary-2257h\nNamespace: kubectl-647\nPriority: 0\nNode: ip-172-20-60-128.ec2.internal/172.20.60.128\nStart Time: Sat, 07 Jan 2023 21:25:47 +0000\nLabels: app=agnhost\n role=primary\nAnnotations: <none>\nStatus: Running\nIP: 100.96.1.99\nIPs:\n IP: 100.96.1.99\nControlled By: ReplicationController/agnhost-primary\nContainers:\n agnhost-primary:\n Container ID: docker://0d37846ad8c3b52219ba44debeef2c6fa20bac9b1f9eb77cde5eb9b213f83ad7\n Image: k8s.gcr.io/e2e-test-images/agnhost:2.39\n Image ID: docker-pullable://k8s.gcr.io/e2e-test-images/agnhost@sha256:7e8bdd271312fd25fc5ff5a8f04727be84044eb3d7d8d03611972a6752e2e11e\n Port: 6379/TCP\n Host Port: 0/TCP\n State: Running\n Started: Sat, 07 Jan 2023 21:25:48 +0000\n Ready: True\n Restart Count: 0\n Environment: <none>\n Mounts:\n /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-94g5p (ro)\nConditions:\n Type Status\n Initialized True \n Ready True \n ContainersReady True \n PodScheduled True \nVolumes:\n kube-api-access-94g5p:\n Type: Projected (a volume that contains injected data from multiple sources)\n TokenExpirationSeconds: 3607\n ConfigMapName: kube-root-ca.crt\n ConfigMapOptional: <nil>\n DownwardAPI: true\nQoS Class: BestEffort\nNode-Selectors: <none>\nTolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s\n node.kubernetes.io/unreachable:NoExecute op=Exists for 300s\nEvents:\n Type Reason Age From Message\n ---- ------ ---- ---- -------\n Normal Scheduled 3s default-scheduler Successfully assigned kubectl-647/agnhost-primary-2257h to ip-172-20-60-128.ec2.internal\n Normal Pulled 2s kubelet Container image \"k8s.gcr.io/e2e-test-images/agnhost:2.39\" already present on machine\n Normal Created 2s kubelet Created container agnhost-primary\n Normal Started 2s kubelet Started container agnhost-primary\n" Jan 7 21:25:50.175: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-647 describe rc agnhost-primary' Jan 7 21:25:50.456: INFO: stderr: "" Jan 7 21:25:50.456: INFO: stdout: "Name: agnhost-primary\nNamespace: kubectl-647\nSelector: app=agnhost,role=primary\nLabels: app=agnhost\n role=primary\nAnnotations: <none>\nReplicas: 1 current / 1 desired\nPods Status: 1 Running / 0 Waiting / 0 Succeeded / 0 Failed\nPod Template:\n Labels: app=agnhost\n role=primary\n Containers:\n agnhost-primary:\n Image: k8s.gcr.io/e2e-test-images/agnhost:2.39\n Port: 6379/TCP\n Host Port: 0/TCP\n Environment: <none>\n Mounts: <none>\n Volumes: <none>\nEvents:\n Type Reason Age From Message\n ---- ------ ---- ---- -------\n Normal SuccessfulCreate 3s replication-controller Created pod: agnhost-primary-2257h\n" Jan 7 21:25:50.456: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-647 describe service agnhost-primary' Jan 7 21:25:50.718: INFO: stderr: "" Jan 7 21:25:50.718: INFO: stdout: "Name: agnhost-primary\nNamespace: kubectl-647\nLabels: app=agnhost\n role=primary\nAnnotations: <none>\nSelector: app=agnhost,role=primary\nType: ClusterIP\nIP Family Policy: SingleStack\nIP Families: IPv4\nIP: 100.66.31.4\nIPs: 100.66.31.4\nPort: <unset> 6379/TCP\nTargetPort: agnhost-server/TCP\nEndpoints: 100.96.1.99:6379\nSession Affinity: None\nEvents: <none>\n" Jan 7 21:25:50.749: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-647 describe node ip-172-20-45-194.ec2.internal' Jan 7 21:25:51.079: INFO: stderr: "" Jan 7 21:25:51.079: INFO: stdout: "Name: ip-172-20-45-194.ec2.internal\nRoles: node\nLabels: beta.kubernetes.io/arch=amd64\n beta.kubernetes.io/instance-type=t3.medium\n beta.kubernetes.io/os=linux\n failure-domain.beta.kubernetes.io/region=us-east-1\n failure-domain.beta.kubernetes.io/zone=us-east-1a\n io.kubernetes.storage.mock/node=some-mock-node\n kubernetes.io/arch=amd64\n kubernetes.io/hostname=ip-172-20-45-194.ec2.internal\n kubernetes.io/os=linux\n kubernetes.io/role=node\n node-role.kubernetes.io/node=\n node.kubernetes.io/instance-type=t3.medium\n topology.ebs.csi.aws.com/zone=us-east-1a\n topology.hostpath.csi/node=ip-172-20-45-194.ec2.internal\n topology.kubernetes.io/region=us-east-1\n topology.kubernetes.io/zone=us-east-1a\nAnnotations: csi.volume.kubernetes.io/nodeid:\n {\"csi-hostpath-provisioning-1997\":\"ip-172-20-45-194.ec2.internal\",\"csi-mock-csi-mock-volumes-175\":\"csi-mock-csi-mock-volumes-175\",\"ebs.csi...\n node.alpha.kubernetes.io/ttl: 0\n volumes.kubernetes.io/controller-managed-attach-detach: true\nCreationTimestamp: Sat, 07 Jan 2023 21:08:32 +0000\nTaints: node.kubernetes.io/not-ready:NoExecute\n node.kubernetes.io/not-ready:NoSchedule\nUnschedulable: false\nLease:\n HolderIdentity: ip-172-20-45-194.ec2.internal\n AcquireTime: <unset>\n RenewTime: Sat, 07 Jan 2023 21:25:45 +0000\nConditions:\n Type Status LastHeartbeatTime LastTransitionTime Reason Message\n ---- ------ ----------------- ------------------ ------ -------\n NetworkUnavailable False Sat, 07 Jan 2023 21:08:36 +0000 Sat, 07 Jan 2023 21:08:36 +0000 RouteCreated RouteController created a route\n MemoryPressure False Sat, 07 Jan 2023 21:25:47 +0000 Sat, 07 Jan 2023 21:08:32 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available\n DiskPressure False Sat, 07 Jan 2023 21:25:47 +0000 Sat, 07 Jan 2023 21:08:32 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure\n PIDPressure False Sat, 07 Jan 2023 21:25:47 +0000 Sat, 07 Jan 2023 21:08:32 +0000 KubeletHasSufficientPID kubelet has sufficient PID available\n Ready False Sat, 07 Jan 2023 21:25:47 +0000 Sat, 07 Jan 2023 21:25:47 +0000 KubeletNotReady PLEG is not healthy: pleg was last seen active 3m10.312228914s ago; threshold is 3m0s\nAddresses:\n InternalIP: 172.20.45.194\n ExternalIP: 54.236.7.150\n Hostname: ip-172-20-45-194.ec2.internal\n InternalDNS: ip-172-20-45-194.ec2.internal\n ExternalDNS: ec2-54-236-7-150.compute-1.amazonaws.com\nCapacity:\n cpu: 2\n ephemeral-storage: 48587704Ki\n hugepages-1Gi: 0\n hugepages-2Mi: 0\n memory: 3956720Ki\n pods: 110\nAllocatable:\n cpu: 2\n ephemeral-storage: 44778427933\n hugepages-1Gi: 0\n hugepages-2Mi: 0\n memory: 3854320Ki\n pods: 110\nSystem Info:\n Machine ID: ec24bb589b457eb3b4afdc626cf69edf\n System UUID: ec24bb58-9b45-7eb3-b4af-dc626cf69edf\n Boot ID: 68f14ed2-ff8d-4978-b5cd-d4945ee14a0a\n Kernel Version: 5.15.0-1026-aws\n OS Image: Ubuntu 20.04.5 LTS\n Operating System: linux\n Architecture: amd64\n Container Runtime Version: docker://20.10.17\n Kubelet Version: v1.23.15\n Kube-Proxy Version: v1.23.15\nPodCIDR: 100.96.4.0/24\nPodCIDRs: 100.96.4.0/24\nProviderID: aws:///us-east-1a/i-0c3946b9dc49ba9d8\nNon-terminated Pods: (28 in total)\n Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age\n --------- ---- ------------ ---------- --------------- ------------- ---\n apply-5167 test-pod 0 (0%) 0 (0%) 0 (0%) 0 (0%) 4m33s\n conntrack-6846 pod-server-1 0 (0%) 0 (0%) 0 (0%) 0 (0%) 31s\n csi-mock-volumes-175-9574 csi-mockplugin-0 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m20s\n csi-mock-volumes-175-9574 csi-mockplugin-attacher-0 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m20s\n csi-mock-volumes-175-9574 csi-mockplugin-resizer-0 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m20s\n csi-mock-volumes-175 pvc-volume-tester-pqj4n 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m8s\n csi-mock-volumes-7983-1191 csi-mockplugin-0 0 (0%) 0 (0%) 0 (0%) 0 (0%) 81s\n csi-mock-volumes-7983-1191 csi-mockplugin-attacher-0 0 (0%) 0 (0%) 0 (0%) 0 (0%) 81s\n deployment-7773 test-deployment-5ddd8b47d8-rnwtg 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m1s\n deployment-7773 test-deployment-6d7ffcf7fb-78jb9 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m23s\n ephemeral-6850-3245 csi-hostpathplugin-0 0 (0%) 0 (0%) 0 (0%) 0 (0%) 83s\n kube-system ebs-csi-node-nxhjh 0 (0%) 0 (0%) 0 (0%) 0 (0%) 17m\n kube-system kube-proxy-ip-172-20-45-194.ec2.internal 100m (5%) 0 (0%) 0 (0%) 0 (0%) 17m\n nettest-1331 netserver-0 0 (0%) 0 (0%) 0 (0%) 0 (0%) 2m38s\n nettest-3707 netserver-0 0 (0%) 0 (0%) 0 (0%) 0 (0%) 92s\n nettest-5349 netserver-0 0 (0%) 0 (0%) 0 (0%) 0 (0%) 104s\n nettest-5684 netserver-0 0 (0%) 0 (0%) 0 (0%) 0 (0%) 2m56s\n persistent-local-volumes-test-3180 hostexec-ip-172-20-45-194.ec2.internal-s99fb 0 (0%) 0 (0%) 0 (0%) 0 (0%) 2m38s\n pod-network-test-2643 netserver-0 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m7s\n projected-9420 pod-projected-configmaps-11cccafa-c260-4582-b722-247f8db041ec 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m16s\n provisioning-1997-9862 csi-hostpathplugin-0 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m56s\n provisioning-1997 hostpath-injector 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m56s\n provisioning-7309 hostexec-ip-172-20-45-194.ec2.internal-9crcb 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m17s\n provisioning-7368 hostpath-symlink-prep-provisioning-7368 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m14s\n provisioning-8986 hostexec-ip-172-20-45-194.ec2.internal-d8ldr 0 (0%) 0 (0%) 0 (0%) 0 (0%) 2m3s\n pvc-protection-1086 pvc-tester-ld5k2 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m27s\n volume-2927 exec-volume-test-preprovisionedpv-fngf 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m3s\n volume-2927 hostexec-ip-172-20-45-194.ec2.internal-bgsdg 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m26s\nAllocated resources:\n (Total limits may be over 100 percent, i.e., overcommitted.)\n Resource Requests Limits\n -------- -------- ------\n cpu 100m (5%) 0 (0%)\n memory 0 (0%) 0 (0%)\n ephemeral-storage 0 (0%) 0 (0%)\n hugepages-1Gi 0 (0%) 0 (0%)\n hugepages-2Mi 0 (0%) 0 (0%)\nEvents:\n Type Reason Age From Message\n ---- ------ ---- ---- -------\n Normal Starting 17m kube-proxy \n Normal Starting 17m kubelet Starting kubelet.\n Normal NodeHasSufficientMemory 17m (x2 over 17m) kubelet Node ip-172-20-45-194.ec2.internal status is now: NodeHasSufficientMemory\n Normal NodeHasNoDiskPressure 17m (x2 over 17m) kubelet Node ip-172-20-45-194.ec2.internal status is now: NodeHasNoDiskPressure\n Normal NodeHasSufficientPID 17m (x2 over 17m) kubelet Node ip-172-20-45-194.ec2.internal status is now: NodeHasSufficientPID\n Normal NodeAllocatableEnforced 17m kubelet Updated Node Allocatable limit across pods\n Normal NodeReady 17m kubelet Node ip-172-20-45-194.ec2.internal status is now: NodeReady\n Normal NodeNotReady 4s kubelet Node ip-172-20-45-194.ec2.internal status is now: NodeNotReady\n" Jan 7 21:25:51.080: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-647 describe namespace kubectl-647' Jan 7 21:25:51.343: INFO: stderr: "" Jan 7 21:25:51.343: INFO: stdout: "Name: kubectl-647\nLabels: e2e-framework=kubectl\n e2e-run=83c61455-6970-4414-889f-6c23d43115b2\n kubernetes.io/metadata.name=kubectl-647\nAnnotations: <none>\nStatus: Active\n\nNo resource quota.\n\nNo LimitRange resource.\n" [AfterEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:25:51.343: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:25:51.373: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:25:53.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:25:55.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:25:57.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:25:59.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:01.408: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:03.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:05.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:07.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:09.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:11.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:13.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:15.413: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:17.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:19.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:21.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:23.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:25.406: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:27.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:29.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:31.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:33.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:35.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:37.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:39.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:41.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:43.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:45.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:47.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:49.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:51.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:53.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:55.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:57.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:59.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:01.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:03.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:05.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:07.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:09.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:11.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:13.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:15.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:17.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:19.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:21.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:23.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:25.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:27.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:29.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:31.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:33.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:35.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:37.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:39.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:41.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:43.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:45.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:47.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:49.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:51.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:53.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:55.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:57.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:59.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:01.407: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:03.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:05.406: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:07.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:09.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:11.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:13.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:15.410: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:17.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:19.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:21.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:23.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:25.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:27.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:29.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:31.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:33.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:35.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:37.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:39.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:41.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:43.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:45.405: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:47.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:49.403: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:51.404: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:51.434: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:51.434: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x0) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000ce64e0, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "kubectl-647" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sclient\sSimple\spod\sshould\ssupport\sexec\sthrough\skubectl\sproxy$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:35:23.419: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_21.xml
[BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:32:09.112: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename kubectl �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:244 [BeforeEach] Simple pod /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:381 �[1mSTEP�[0m: creating the pod from Jan 7 21:32:09.315: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7424 create -f -' Jan 7 21:32:09.657: INFO: stderr: "" Jan 7 21:32:09.657: INFO: stdout: "pod/httpd created\n" Jan 7 21:32:09.657: INFO: Waiting up to 5m0s for 1 pods to be running and ready: [httpd] Jan 7 21:32:09.657: INFO: Waiting up to 5m0s for pod "httpd" in namespace "kubectl-7424" to be "running and ready" Jan 7 21:32:09.686: INFO: Pod "httpd": Phase="Pending", Reason="", readiness=false. Elapsed: 28.789331ms Jan 7 21:32:11.717: INFO: Pod "httpd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.059747977s Jan 7 21:32:13.747: INFO: Pod "httpd": Phase="Running", Reason="", readiness=false. Elapsed: 4.089566384s Jan 7 21:32:15.777: INFO: Pod "httpd": Phase="Running", Reason="", readiness=false. Elapsed: 6.11924314s Jan 7 21:32:17.807: INFO: Pod "httpd": Phase="Running", Reason="", readiness=false. Elapsed: 8.149465852s Jan 7 21:32:19.838: INFO: Pod "httpd": Phase="Running", Reason="", readiness=false. Elapsed: 10.180338618s Jan 7 21:32:21.867: INFO: Pod "httpd": Phase="Running", Reason="", readiness=true. Elapsed: 12.209700253s Jan 7 21:32:21.867: INFO: Pod "httpd" satisfied condition "running and ready" Jan 7 21:32:21.867: INFO: Wanted all 1 pods to be running and ready. Result: true. Pods: [httpd] [It] should support exec through kubectl proxy /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:473 �[1mSTEP�[0m: Starting kubectl proxy Jan 7 21:32:21.867: INFO: Asynchronously running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl /home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7424 proxy -p 0 --disable-filter' �[1mSTEP�[0m: Running kubectl via kubectl proxy using --server=http://127.0.0.1:34397 Jan 7 21:32:21.917: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7424 --server=http://127.0.0.1:34397 exec --pod-running-timeout=2m0s httpd -- echo running in container' Jan 7 21:32:22.698: INFO: stderr: "" Jan 7 21:32:22.698: INFO: stdout: "running in container\n" [AfterEach] Simple pod /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:387 �[1mSTEP�[0m: using delete to clean up resources Jan 7 21:32:22.698: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7424 delete --grace-period=0 --force -f -' Jan 7 21:32:22.920: INFO: stderr: "warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely.\n" Jan 7 21:32:22.920: INFO: stdout: "pod \"httpd\" force deleted\n" Jan 7 21:32:22.920: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7424 get rc,svc -l name=httpd --no-headers' Jan 7 21:32:23.140: INFO: stderr: "No resources found in kubectl-7424 namespace.\n" Jan 7 21:32:23.140: INFO: stdout: "" Jan 7 21:32:23.140: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-7424 get pods -l name=httpd -o go-template={{ range .items }}{{ if not .metadata.deletionTimestamp }}{{ .metadata.name }}{{ "\n" }}{{ end }}{{ end }}' Jan 7 21:32:23.328: INFO: stderr: "" Jan 7 21:32:23.328: INFO: stdout: "" [AfterEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:32:23.328: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:32:23.359: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:25.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:27.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:29.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:31.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:33.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:35.391: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:37.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:39.391: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:41.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:43.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:45.391: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:47.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:49.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:51.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:53.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:55.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:57.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:59.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:01.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:03.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:05.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:07.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:09.392: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:11.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:13.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:15.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:17.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:19.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:21.391: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:23.391: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:25.391: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:27.392: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:29.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:31.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:33.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:35.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:37.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:39.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:41.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:43.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:45.391: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:47.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:49.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:51.391: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:53.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:55.391: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:57.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:59.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:01.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:03.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:05.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:07.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:09.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:11.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:13.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:15.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:17.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:19.393: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:21.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:23.392: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:25.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:27.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:29.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:31.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:33.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:35.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:37.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:39.391: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:41.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:43.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:45.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:47.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:49.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:51.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:53.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:55.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:57.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:59.391: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:01.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:03.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:05.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:07.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:09.392: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:11.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:13.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:15.391: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:17.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:19.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:21.390: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:23.389: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:23.419: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:35:23.419: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x0) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000800d00, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "kubectl-7424" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sclient\sSimple\spod\sshould\ssupport\sport\-forward$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:42:34.571: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_09.xml
[BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:39:20.066: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename kubectl �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:244 [BeforeEach] Simple pod /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:381 �[1mSTEP�[0m: creating the pod from Jan 7 21:39:20.264: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-8621 create -f -' Jan 7 21:39:21.200: INFO: stderr: "" Jan 7 21:39:21.200: INFO: stdout: "pod/httpd created\n" Jan 7 21:39:21.200: INFO: Waiting up to 5m0s for 1 pods to be running and ready: [httpd] Jan 7 21:39:21.200: INFO: Waiting up to 5m0s for pod "httpd" in namespace "kubectl-8621" to be "running and ready" Jan 7 21:39:21.228: INFO: Pod "httpd": Phase="Pending", Reason="", readiness=false. Elapsed: 28.200759ms Jan 7 21:39:23.257: INFO: Pod "httpd": Phase="Running", Reason="", readiness=false. Elapsed: 2.057005316s Jan 7 21:39:25.286: INFO: Pod "httpd": Phase="Running", Reason="", readiness=false. Elapsed: 4.086634187s Jan 7 21:39:27.316: INFO: Pod "httpd": Phase="Running", Reason="", readiness=false. Elapsed: 6.116242381s Jan 7 21:39:29.345: INFO: Pod "httpd": Phase="Running", Reason="", readiness=false. Elapsed: 8.145189573s Jan 7 21:39:31.374: INFO: Pod "httpd": Phase="Running", Reason="", readiness=false. Elapsed: 10.173912455s Jan 7 21:39:33.402: INFO: Pod "httpd": Phase="Running", Reason="", readiness=true. Elapsed: 12.202269659s Jan 7 21:39:33.402: INFO: Pod "httpd" satisfied condition "running and ready" Jan 7 21:39:33.402: INFO: Wanted all 1 pods to be running and ready. Result: true. Pods: [httpd] [It] should support port-forward /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:637 �[1mSTEP�[0m: forwarding the container port to a local port Jan 7 21:39:33.402: INFO: starting port-forward command and streaming output Jan 7 21:39:33.402: INFO: Asynchronously running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl /home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-8621 port-forward --namespace=kubectl-8621 httpd :80' Jan 7 21:39:33.403: INFO: reading from `kubectl port-forward` command's stdout �[1mSTEP�[0m: curling local port output Jan 7 21:39:33.872: INFO: got: <html><body><h1>It works!</h1></body></html> [AfterEach] Simple pod /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:387 �[1mSTEP�[0m: using delete to clean up resources Jan 7 21:39:33.877: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-8621 delete --grace-period=0 --force -f -' Jan 7 21:39:34.095: INFO: stderr: "warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely.\n" Jan 7 21:39:34.095: INFO: stdout: "pod \"httpd\" force deleted\n" Jan 7 21:39:34.095: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-8621 get rc,svc -l name=httpd --no-headers' Jan 7 21:39:34.304: INFO: stderr: "No resources found in kubectl-8621 namespace.\n" Jan 7 21:39:34.304: INFO: stdout: "" Jan 7 21:39:34.304: INFO: Running '/home/prow/go/src/k8s.io/kops/_rundir/909d8c6f-8ece-11ed-84f7-72cdabe2d9ae/kubectl --server=https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io --kubeconfig=/root/.kube/config --namespace=kubectl-8621 get pods -l name=httpd -o go-template={{ range .items }}{{ if not .metadata.deletionTimestamp }}{{ .metadata.name }}{{ "\n" }}{{ end }}{{ end }}' Jan 7 21:39:34.480: INFO: stderr: "" Jan 7 21:39:34.480: INFO: stdout: "" [AfterEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:39:34.480: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:39:34.509: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:36.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:38.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:40.546: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:42.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:44.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:46.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:48.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:50.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:52.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:54.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:56.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:58.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:00.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:02.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:04.544: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:06.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:08.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:10.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:12.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:14.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:16.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:18.543: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:20.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:22.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:24.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:26.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:28.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:30.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:32.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:34.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:36.543: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:38.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:40.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:42.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:44.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:46.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:48.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:50.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:52.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:54.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:56.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:58.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:00.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:02.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:04.542: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:06.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:08.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:10.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:12.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:14.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:16.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:18.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:20.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:22.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:24.548: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:26.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:28.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:30.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:32.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:34.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:36.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:38.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:40.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:42.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:44.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:46.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:48.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:50.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:52.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:54.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:56.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:41:58.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:00.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:02.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:04.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:06.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:08.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:10.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:12.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:14.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:16.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:18.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:20.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:22.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:24.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:26.539: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:28.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:30.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:32.540: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:34.541: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:34.571: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:42:34.571: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x243a8f9) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000dca340, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "kubectl-8621" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-instrumentation\]\sEvents\sshould\sdelete\sa\scollection\sof\sevents\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:31:57.663: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_20.xml
[BeforeEach] [sig-instrumentation] Events /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:28:57.135: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename events �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] should delete a collection of events [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 �[1mSTEP�[0m: Create set of events Jan 7 21:28:57.396: INFO: created test-event-1 Jan 7 21:28:57.428: INFO: created test-event-2 Jan 7 21:28:57.464: INFO: created test-event-3 �[1mSTEP�[0m: get a list of Events with a label in the current namespace �[1mSTEP�[0m: delete collection of events Jan 7 21:28:57.495: INFO: requesting DeleteCollection of events �[1mSTEP�[0m: check that the list of events matches the requested quantity Jan 7 21:28:57.533: INFO: requesting list of events to confirm quantity [AfterEach] [sig-instrumentation] Events /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:28:57.566: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:28:57.598: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:59.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:01.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:03.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:05.634: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:07.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:09.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:11.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:13.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:15.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:17.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:19.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:21.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:23.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:25.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:27.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:29.635: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:31.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:33.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:35.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:37.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:39.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:41.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:43.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:45.633: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:47.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:49.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:51.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:53.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:55.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:57.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:59.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:01.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:03.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:05.633: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:07.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:09.630: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:11.633: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:13.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:15.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:17.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:19.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:21.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:23.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:25.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:27.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:29.630: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:31.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:33.630: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:35.634: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:37.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:39.630: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:41.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:43.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:45.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:47.630: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:49.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:51.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:53.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:55.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:57.630: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:59.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:01.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:03.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:05.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:07.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:09.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:11.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:13.633: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:15.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:17.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:19.634: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:21.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:23.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:25.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:27.630: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:29.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:31.630: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:33.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:35.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:37.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:39.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:41.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:43.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:45.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:47.632: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:49.630: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:51.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:53.630: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:55.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:57.631: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:57.663: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:57.663: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x243a8f9) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc0009dc340, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "events-3904" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-instrumentation\]\sEvents\sshould\sensure\sthat\san\sevent\scan\sbe\sfetched\,\spatched\,\sdeleted\,\sand\slisted\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:34:15.591: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_07.xml
{"msg":"FAILED [sig-storage] PersistentVolumes-local [Volume type: dir-bindmounted] Two pods mounting a local volume one after the other should be able to write from pod1 and read from pod2","total":-1,"completed":31,"skipped":299,"failed":1,"failures":["[sig-storage] PersistentVolumes-local [Volume type: dir-bindmounted] Two pods mounting a local volume one after the other should be able to write from pod1 and read from pod2"]} [BeforeEach] [sig-instrumentation] Events /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:31:15.099: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename events �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] should ensure that an event can be fetched, patched, deleted, and listed [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 �[1mSTEP�[0m: creating a test event �[1mSTEP�[0m: listing all events in all namespaces �[1mSTEP�[0m: patching the test event �[1mSTEP�[0m: fetching the test event �[1mSTEP�[0m: deleting the test event �[1mSTEP�[0m: listing all events in all namespaces [AfterEach] [sig-instrumentation] Events /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:31:15.497: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:31:15.527: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:17.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:19.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:21.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:23.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:25.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:27.557: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:29.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:31.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:33.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:35.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:37.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:39.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:41.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:43.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:45.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:47.560: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:49.560: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:51.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:53.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:55.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:57.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:59.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:01.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:03.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:05.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:07.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:09.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:11.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:13.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:15.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:17.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:19.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:21.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:23.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:25.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:27.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:29.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:31.557: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:33.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:35.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:37.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:39.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:41.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:43.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:45.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:47.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:49.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:51.561: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:53.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:55.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:57.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:59.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:01.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:03.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:05.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:07.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:09.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:11.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:13.557: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:15.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:17.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:19.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:21.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:23.557: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:25.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:27.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:29.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:31.557: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:33.563: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:35.557: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:37.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:39.557: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:41.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:43.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:45.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:47.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:49.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:51.557: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:53.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:55.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:57.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:59.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:01.557: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:03.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:05.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:07.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:09.557: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:11.558: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:13.559: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:15.561: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:15.591: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:34:15.591: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x0) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000c7da00, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "events-3811" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sConntrack\sshould\sbe\sable\sto\spreserve\sUDP\straffic\swhen\sserver\spod\scycles\sfor\sa\sNodePort\sservice$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/conntrack.go:130 Jan 7 21:30:20.242: Unexpected error: <*errors.errorString | 0xc0002422b0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/pods.go:107from junit_25.xml
[BeforeEach] [sig-network] Conntrack /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:25:17.665: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename conntrack �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [BeforeEach] [sig-network] Conntrack /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/conntrack.go:96 [It] should be able to preserve UDP traffic when server pod cycles for a NodePort service /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/conntrack.go:130 �[1mSTEP�[0m: creating a UDP service svc-udp with type=NodePort in conntrack-6846 �[1mSTEP�[0m: creating a client pod for probing the service svc-udp Jan 7 21:25:18.012: INFO: The status of Pod pod-client is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:20.043: INFO: The status of Pod pod-client is Running (Ready = true) Jan 7 21:25:20.110: INFO: Pod client logs: Sat Jan 7 21:25:18 UTC 2023 Sat Jan 7 21:25:18 UTC 2023 Try: 1 Sat Jan 7 21:25:18 UTC 2023 Try: 2 Sat Jan 7 21:25:18 UTC 2023 Try: 3 Sat Jan 7 21:25:18 UTC 2023 Try: 4 Sat Jan 7 21:25:18 UTC 2023 Try: 5 Sat Jan 7 21:25:18 UTC 2023 Try: 6 Sat Jan 7 21:25:18 UTC 2023 Try: 7 �[1mSTEP�[0m: creating a backend pod pod-server-1 for the service svc-udp Jan 7 21:25:20.179: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:22.209: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:24.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:26.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:28.209: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:30.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:32.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:34.212: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:36.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:38.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:40.209: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:42.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:44.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:46.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:48.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:50.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:52.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:54.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:56.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:58.209: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:00.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:02.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:04.209: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:06.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:08.212: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:10.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:12.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:14.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:16.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:18.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:20.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:22.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:24.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:26.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:28.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:30.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:32.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:34.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:36.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:38.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:40.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:42.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:44.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:46.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:48.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:50.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:52.213: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:54.212: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:56.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:26:58.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:00.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:02.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:04.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:06.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:08.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:10.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:12.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:14.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:16.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:18.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:20.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:22.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:24.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:26.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:28.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:30.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:32.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:34.212: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:36.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:38.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:40.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:42.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:44.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:46.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:48.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:50.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:52.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:54.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:56.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:27:58.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:00.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:02.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:04.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:06.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:08.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:10.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:12.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:14.209: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:16.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:18.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:20.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:22.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:24.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:26.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:28.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:30.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:32.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:34.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:36.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:38.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:40.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:42.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:44.212: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:46.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:48.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:50.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:52.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:54.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:56.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:28:58.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:00.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:02.213: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:04.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:06.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:08.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:10.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:12.212: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:14.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:16.212: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:18.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:20.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:22.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:24.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:26.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:28.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:30.212: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:32.212: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:34.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:36.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:38.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:40.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:42.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:44.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:46.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:48.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:50.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:52.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:54.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:56.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:29:58.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:30:00.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:30:02.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:30:04.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:30:06.209: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:30:08.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:30:10.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:30:12.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:30:14.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:30:16.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:30:18.210: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:30:20.211: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:30:20.242: INFO: The status of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:30:20.242: FAIL: Unexpected error: <*errors.errorString | 0xc0002422b0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred Full Stack Trace k8s.io/kubernetes/test/e2e/framework.(*PodClient).CreateSync(0xc003992d20, 0xc00370f6c0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/pods.go:107 +0x94 k8s.io/kubernetes/test/e2e/network.glob..func1.3() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/conntrack.go:164 +0x652 k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0xc) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc0007fdba0, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a [AfterEach] [sig-network] Conntrack /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 �[1mSTEP�[0m: Collecting events from namespace "conntrack-6846". �[1mSTEP�[0m: Found 6 events. Jan 7 21:30:20.273: INFO: At 2023-01-07 21:25:17 +0000 UTC - event for pod-client: {default-scheduler } Scheduled: Successfully assigned conntrack-6846/pod-client to ip-172-20-60-128.ec2.internal Jan 7 21:30:20.273: INFO: At 2023-01-07 21:25:18 +0000 UTC - event for pod-client: {kubelet ip-172-20-60-128.ec2.internal} Pulled: Container image "k8s.gcr.io/e2e-test-images/agnhost:2.39" already present on machine Jan 7 21:30:20.273: INFO: At 2023-01-07 21:25:18 +0000 UTC - event for pod-client: {kubelet ip-172-20-60-128.ec2.internal} Created: Created container pod-client Jan 7 21:30:20.273: INFO: At 2023-01-07 21:25:18 +0000 UTC - event for pod-client: {kubelet ip-172-20-60-128.ec2.internal} Started: Started container pod-client Jan 7 21:30:20.273: INFO: At 2023-01-07 21:25:20 +0000 UTC - event for pod-server-1: {default-scheduler } Scheduled: Successfully assigned conntrack-6846/pod-server-1 to ip-172-20-45-194.ec2.internal Jan 7 21:30:20.273: INFO: At 2023-01-07 21:27:20 +0000 UTC - event for pod-server-1: {kubelet ip-172-20-45-194.ec2.internal} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "pod-server-1": operation timeout: context deadline exceeded Jan 7 21:30:20.304: INFO: POD NODE PHASE GRACE CONDITIONS Jan 7 21:30:20.304: INFO: pod-client ip-172-20-60-128.ec2.internal Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-07 21:25:17 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-07 21:25:19 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-07 21:25:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-07 21:25:17 +0000 UTC }] Jan 7 21:30:20.304: INFO: pod-server-1 ip-172-20-45-194.ec2.internal Pending [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-07 21:25:20 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-07 21:25:20 +0000 UTC ContainersNotReady containers with unready status: [agnhost-container]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-07 21:25:20 +0000 UTC ContainersNotReady containers with unready status: [agnhost-container]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-07 21:25:20 +0000 UTC }] Jan 7 21:30:20.304: INFO: Jan 7 21:30:20.374: INFO: Unable to fetch conntrack-6846/pod-server-1/agnhost-container logs: the server rejected our request for an unknown reason (get pods pod-server-1) Jan 7 21:30:20.405: INFO: Logging node info for node ip-172-20-45-194.ec2.internal Jan 7 21:30:20.435: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-45-194.ec2.internal 09282867-f021-4260-9aeb-a3ea49ae8629 40193 0 2023-01-07 21:08:32 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:us-east-1 failure-domain.beta.kubernetes.io/zone:us-east-1a io.kubernetes.storage.mock/node:some-mock-node kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-45-194.ec2.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:us-east-1a topology.hostpath.csi/node:ip-172-20-45-194.ec2.internal topology.kubernetes.io/region:us-east-1 topology.kubernetes.io/zone:us-east-1a] map[csi.volume.kubernetes.io/nodeid:{"csi-hostpath-provisioning-1997":"ip-172-20-45-194.ec2.internal","csi-mock-csi-mock-volumes-175":"csi-mock-csi-mock-volumes-175","ebs.csi.aws.com":"i-0c3946b9dc49ba9d8"} node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-07 21:08:32 +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: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":{}}} } {kops-controller Update v1 2023-01-07 21:08:33 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}} } {kubelet Update v1 2023-01-07 21:17:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:io.kubernetes.storage.mock/node":{},"f:topology.ebs.csi.aws.com/zone":{},"f:topology.hostpath.csi/node":{}}},"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:capacity":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{},"f:volumesInUse":{}}} status} {kube-controller-manager Update v1 2023-01-07 21:17:18 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:volumesAttached":{}}} status} {kube-controller-manager Update v1 2023-01-07 21:25:47 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.4.0/24\"":{}},"f:taints":{}}} }]},Spec:NodeSpec{PodCIDR:100.96.4.0/24,DoNotUseExternalID:,ProviderID:aws:///us-east-1a/i-0c3946b9dc49ba9d8,Unschedulable:false,Taints:[]Taint{Taint{Key:node.kubernetes.io/not-ready,Value:,Effect:NoSchedule,TimeAdded:2023-01-07 21:25:47 +0000 UTC,},Taint{Key:node.kubernetes.io/not-ready,Value:,Effect:NoExecute,TimeAdded:2023-01-07 21:25:47 +0000 UTC,},},ConfigSource:nil,PodCIDRs:[100.96.4.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49753808896 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4051681280 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44778427933 0} {<nil>} 44778427933 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3946823680 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-07 21:08:36 +0000 UTC,LastTransitionTime:2023-01-07 21:08:36 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-07 21:30:12 +0000 UTC,LastTransitionTime:2023-01-07 21:08:32 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-07 21:30:12 +0000 UTC,LastTransitionTime:2023-01-07 21:08:32 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-07 21:30:12 +0000 UTC,LastTransitionTime:2023-01-07 21:08:32 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:False,LastHeartbeatTime:2023-01-07 21:30:12 +0000 UTC,LastTransitionTime:2023-01-07 21:25:47 +0000 UTC,Reason:KubeletNotReady,Message:PLEG is not healthy: pleg was last seen active 7m35.443538146s ago; threshold is 3m0s,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.45.194,},NodeAddress{Type:ExternalIP,Address:54.236.7.150,},NodeAddress{Type:Hostname,Address:ip-172-20-45-194.ec2.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-45-194.ec2.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-54-236-7-150.compute-1.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec24bb589b457eb3b4afdc626cf69edf,SystemUUID:ec24bb58-9b45-7eb3-b4af-dc626cf69edf,BootID:68f14ed2-ff8d-4978-b5cd-d4945ee14a0a,KernelVersion:5.15.0-1026-aws,OSImage:Ubuntu 20.04.5 LTS,ContainerRuntimeVersion:docker://20.10.17,KubeletVersion:v1.23.15,KubeProxyVersion:v1.23.15,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/e2e-test-images/httpd@sha256:20f25f275d46aa728f7615a1ccc19c78b2ed89435bf943a44b339f70f45508e6 k8s.gcr.io/e2e-test-images/httpd:2.4.39-2],SizeBytes:126894770,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:7e8bdd271312fd25fc5ff5a8f04727be84044eb3d7d8d03611972a6752e2e11e k8s.gcr.io/e2e-test-images/agnhost:2.39],SizeBytes:126872991,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/httpd@sha256:1b9d1b2f36cb2dbee1960e82a9344aeb11bd4c4c03abf5e1853e0559c23855e3 k8s.gcr.io/e2e-test-images/httpd:2.4.38-2],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-proxy-amd64:v1.23.15 registry.k8s.io/kube-proxy-amd64:v1.23.15],SizeBytes:112336036,},ContainerImage{Names:[registry.k8s.io/provider-aws/aws-ebs-csi-driver@sha256:10e231cf07c82dfab5141c1afe548dc734e5fc1f67665ec3982a325d1bd31a9a registry.k8s.io/provider-aws/aws-ebs-csi-driver:v1.14.0],SizeBytes:94471559,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-provisioner@sha256:c8e03f60afa90a28e4bb6ec9a8d0fc36d89de4b7475cf2d613afa793ec969fe0 k8s.gcr.io/sig-storage/csi-provisioner:v2.2.0],SizeBytes:56382329,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-provisioner@sha256:4e74c0492bceddc598de1c90cc5bc14dcda94cb49fa9c5bad9d117c4834b5e08 k8s.gcr.io/sig-storage/csi-provisioner:v2.2.1],SizeBytes:56379269,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-resizer@sha256:36c31f7e1f433c9634d24f876353e8646246d81a03c4e351202c2644daff1620 k8s.gcr.io/sig-storage/csi-resizer:v1.2.0],SizeBytes:53956308,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-snapshotter@sha256:ed98431376c9e944e19a465fe8ea944806714dd95416a0821096c78d66b579bd k8s.gcr.io/sig-storage/csi-snapshotter:v4.1.1],SizeBytes:53531990,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-attacher@sha256:c5be65d6679efabb969d9b019300d187437ae876f992c40911fd2892bbef3b36 k8s.gcr.io/sig-storage/csi-attacher:v3.2.0],SizeBytes:53500826,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-attacher@sha256:60ab9b3e6a030d3038c87c0d6bca2930f58d1d72823e6a4af09767dc83b696a2 k8s.gcr.io/sig-storage/csi-attacher:v3.2.1],SizeBytes:53499570,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-resizer@sha256:7a5ba58a44e0d749e0767e4e37315bcf6a61f33ce3185c1991848af4db0fb70a k8s.gcr.io/sig-storage/csi-resizer:v1.1.0],SizeBytes:49176472,},ContainerImage{Names:[k8s.gcr.io/sig-storage/hostpathplugin@sha256:232fe80174d60d520d36043103853a1d7ab4b7f3782cf43e45034f04ccda58ce k8s.gcr.io/sig-storage/hostpathplugin:v1.7.1],SizeBytes:29977921,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:19662887,},ContainerImage{Names:[registry.k8s.io/sig-storage/csi-node-driver-registrar@sha256:0103eee7c35e3e0b5cd8cdca9850dc71c793cdeb6669d8be7a89440da2d06ae4 registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.5.1],SizeBytes:19582112,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:2dee3fe5fe861bb66c3a4ac51114f3447a4cd35870e0f2e2b558c7a400d89589 k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.2.0],SizeBytes:18699436,},ContainerImage{Names:[k8s.gcr.io/sig-storage/mock-driver@sha256:a7b517f9e0f42ffade802eef9cefa271372386b85f55b702b493241e58459793 k8s.gcr.io/sig-storage/mock-driver:v4.1.0],SizeBytes:17680993,},ContainerImage{Names:[registry.k8s.io/sig-storage/livenessprobe@sha256:406f59599991916d2942d8d02f076d957ed71b541ee19f09fc01723a6e6f5932 registry.k8s.io/sig-storage/livenessprobe:v2.6.0],SizeBytes:17611980,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:529be2c9770add0cdd0c989115222ea9fc1be430c11095eb9f6dafcf98a36e2b k8s.gcr.io/sig-storage/livenessprobe:v2.4.0],SizeBytes:17175488,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:13616070e3f29de4417eee434a8ef472221c9e51b3d037b5a6b46cef08eb7443 k8s.gcr.io/e2e-test-images/nginx:1.14-2],SizeBytes:16032814,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:c318242786b139d18676b1c09a0ad7f15fc17f8f16a5b2e625cd0dc8c9703daf k8s.gcr.io/e2e-test-images/busybox:1.29-2],SizeBytes:1154361,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:1154361,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db registry.k8s.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6 registry.k8s.io/pause:3.6],SizeBytes:682696,},},VolumesInUse:[kubernetes.io/csi/csi-hostpath-provisioning-1997^55e55a3c-8ed1-11ed-b986-eefc817d4a90 kubernetes.io/csi/csi-mock-csi-mock-volumes-175^4 kubernetes.io/csi/ebs.csi.aws.com^vol-0f972a11de1aaaa99],VolumesAttached:[]AttachedVolume{AttachedVolume{Name:kubernetes.io/csi/csi-hostpath-provisioning-1997^55e55a3c-8ed1-11ed-b986-eefc817d4a90,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/csi-mock-csi-mock-volumes-175^4,DevicePath:,},AttachedVolume{Name:kubernetes.io/csi/ebs.csi.aws.com^vol-0f972a11de1aaaa99,DevicePath:,},},Config:nil,},} Jan 7 21:30:20.436: INFO: Logging kubelet events for node ip-172-20-45-194.ec2.internal Jan 7 21:30:20.468: INFO: Logging pods the kubelet thinks is on node ip-172-20-45-194.ec2.internal Jan 7 21:30:20.509: INFO: csi-mockplugin-resizer-0 started at 2023-01-07 21:22:31 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container csi-resizer ready: false, restart count 0 Jan 7 21:30:20.510: INFO: hostexec-ip-172-20-45-194.ec2.internal-s99fb started at 2023-01-07 21:23:13 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container agnhost-container ready: false, restart count 0 Jan 7 21:30:20.510: INFO: netserver-0 started at 2023-01-07 21:24:19 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container webserver ready: false, restart count 0 Jan 7 21:30:20.510: INFO: hostexec-ip-172-20-45-194.ec2.internal-d8ldr started at 2023-01-07 21:23:49 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container agnhost-container ready: false, restart count 0 Jan 7 21:30:20.510: INFO: ebs-csi-node-nxhjh started at 2023-01-07 21:08:34 +0000 UTC (0+3 container statuses recorded) Jan 7 21:30:20.510: INFO: Container ebs-plugin ready: true, restart count 0 Jan 7 21:30:20.510: INFO: Container liveness-probe ready: true, restart count 0 Jan 7 21:30:20.510: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 7 21:30:20.510: INFO: hostpath-symlink-prep-provisioning-7368 started at 2023-01-07 21:22:37 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container init-volume-provisioning-7368 ready: false, restart count 0 Jan 7 21:30:20.510: INFO: test-pod started at 2023-01-07 21:21:18 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container test-container ready: false, restart count 0 Jan 7 21:30:20.510: INFO: netserver-0 started at 2023-01-07 21:24:07 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container webserver ready: false, restart count 0 Jan 7 21:30:20.510: INFO: csi-hostpathplugin-0 started at 2023-01-07 21:24:28 +0000 UTC (0+7 container statuses recorded) Jan 7 21:30:20.510: INFO: Container csi-attacher ready: false, restart count 0 Jan 7 21:30:20.510: INFO: Container csi-provisioner ready: false, restart count 0 Jan 7 21:30:20.510: INFO: Container csi-resizer ready: false, restart count 0 Jan 7 21:30:20.510: INFO: Container csi-snapshotter ready: false, restart count 0 Jan 7 21:30:20.510: INFO: Container hostpath ready: false, restart count 0 Jan 7 21:30:20.510: INFO: Container liveness-probe ready: false, restart count 0 Jan 7 21:30:20.510: INFO: Container node-driver-registrar ready: false, restart count 0 Jan 7 21:30:20.510: INFO: pvc-tester-ld5k2 started at 2023-01-07 21:22:28 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container write-pod ready: false, restart count 0 Jan 7 21:30:20.510: INFO: kube-proxy-ip-172-20-45-194.ec2.internal started at 2023-01-07 21:08:33 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container kube-proxy ready: true, restart count 0 Jan 7 21:30:20.510: INFO: netserver-0 started at 2023-01-07 21:22:55 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container webserver ready: false, restart count 0 Jan 7 21:30:20.510: INFO: netserver-0 started at 2023-01-07 21:23:13 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container webserver ready: false, restart count 0 Jan 7 21:30:20.510: INFO: csi-mockplugin-attacher-0 started at 2023-01-07 21:24:30 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container csi-attacher ready: false, restart count 0 Jan 7 21:30:20.510: INFO: hostexec-ip-172-20-45-194.ec2.internal-9crcb started at 2023-01-07 21:22:34 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container agnhost-container ready: false, restart count 0 Jan 7 21:30:20.510: INFO: pod-projected-configmaps-11cccafa-c260-4582-b722-247f8db041ec started at 2023-01-07 21:22:35 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container agnhost-container ready: false, restart count 0 Jan 7 21:30:20.510: INFO: hostexec-ip-172-20-45-194.ec2.internal-bgsdg started at 2023-01-07 21:22:25 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container agnhost-container ready: true, restart count 0 Jan 7 21:30:20.510: INFO: test-deployment-6d7ffcf7fb-78jb9 started at 2023-01-07 21:22:28 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container test-deployment ready: true, restart count 0 Jan 7 21:30:20.510: INFO: csi-mockplugin-attacher-0 started at 2023-01-07 21:22:31 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container csi-attacher ready: true, restart count 0 Jan 7 21:30:20.510: INFO: exec-volume-test-preprovisionedpv-fngf started at 2023-01-07 21:22:48 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container exec-container-preprovisionedpv-fngf ready: false, restart count 0 Jan 7 21:30:20.510: INFO: test-deployment-5ddd8b47d8-rnwtg started at 2023-01-07 21:22:50 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container test-deployment ready: false, restart count 0 Jan 7 21:30:20.510: INFO: hostpath-injector started at 2023-01-07 21:22:10 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container hostpath-injector ready: true, restart count 0 Jan 7 21:30:20.510: INFO: csi-mockplugin-0 started at 2023-01-07 21:22:31 +0000 UTC (0+3 container statuses recorded) Jan 7 21:30:20.510: INFO: Container csi-provisioner ready: true, restart count 0 Jan 7 21:30:20.510: INFO: Container driver-registrar ready: true, restart count 0 Jan 7 21:30:20.510: INFO: Container mock ready: true, restart count 0 Jan 7 21:30:20.510: INFO: netserver-0 started at 2023-01-07 21:22:44 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container webserver ready: false, restart count 0 Jan 7 21:30:20.510: INFO: pvc-volume-tester-pqj4n started at 2023-01-07 21:22:43 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container volume-tester ready: false, restart count 0 Jan 7 21:30:20.510: INFO: csi-hostpathplugin-0 started at 2023-01-07 21:21:55 +0000 UTC (0+7 container statuses recorded) Jan 7 21:30:20.510: INFO: Container csi-attacher ready: true, restart count 0 Jan 7 21:30:20.510: INFO: Container csi-provisioner ready: true, restart count 0 Jan 7 21:30:20.510: INFO: Container csi-resizer ready: true, restart count 0 Jan 7 21:30:20.510: INFO: Container csi-snapshotter ready: true, restart count 0 Jan 7 21:30:20.510: INFO: Container hostpath ready: true, restart count 0 Jan 7 21:30:20.510: INFO: Container liveness-probe ready: true, restart count 0 Jan 7 21:30:20.510: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 7 21:30:20.510: INFO: csi-mockplugin-0 started at 2023-01-07 21:24:30 +0000 UTC (0+3 container statuses recorded) Jan 7 21:30:20.510: INFO: Container csi-provisioner ready: false, restart count 0 Jan 7 21:30:20.510: INFO: Container driver-registrar ready: false, restart count 0 Jan 7 21:30:20.510: INFO: Container mock ready: false, restart count 0 Jan 7 21:30:20.510: INFO: pod-server-1 started at 2023-01-07 21:25:20 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.510: INFO: Container agnhost-container ready: false, restart count 0 Jan 7 21:30:20.683: INFO: Latency metrics for node ip-172-20-45-194.ec2.internal Jan 7 21:30:20.683: INFO: Logging node info for node ip-172-20-51-5.ec2.internal Jan 7 21:30:20.714: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-51-5.ec2.internal fcb45f81-f242-41e7-ad0c-57cbc656d334 40160 0 2023-01-07 21:08:30 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:us-east-1 failure-domain.beta.kubernetes.io/zone:us-east-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-51-5.ec2.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:us-east-1a topology.hostpath.csi/node:ip-172-20-51-5.ec2.internal topology.kubernetes.io/region:us-east-1 topology.kubernetes.io/zone:us-east-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-0434808a6ba1189a2"} node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kops-controller Update v1 2023-01-07 21:08:30 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}} } {kube-controller-manager Update v1 2023-01-07 21:08:30 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.2.0/24\"":{}}}} } {kubelet Update v1 2023-01-07 21:08:30 +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: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-07 21:29:48 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-07 21:30:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.ebs.csi.aws.com/zone":{},"f:topology.hostpath.csi/node":{}}},"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:capacity":{"f:ephemeral-storage":{}},"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:100.96.2.0/24,DoNotUseExternalID:,ProviderID:aws:///us-east-1a/i-0434808a6ba1189a2,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.2.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49753808896 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4051689472 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44778427933 0} {<nil>} 44778427933 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3946831872 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-07 21:08:36 +0000 UTC,LastTransitionTime:2023-01-07 21:08:36 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-07 21:30:07 +0000 UTC,LastTransitionTime:2023-01-07 21:08:30 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-07 21:30:07 +0000 UTC,LastTransitionTime:2023-01-07 21:08:30 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-07 21:30:07 +0000 UTC,LastTransitionTime:2023-01-07 21:08:30 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-07 21:30:07 +0000 UTC,LastTransitionTime:2023-01-07 21:08:40 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.51.5,},NodeAddress{Type:ExternalIP,Address:34.229.205.72,},NodeAddress{Type:Hostname,Address:ip-172-20-51-5.ec2.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-51-5.ec2.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-34-229-205-72.compute-1.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec2e13eac8190cd0c0bd4be8df5fdf62,SystemUUID:ec2e13ea-c819-0cd0-c0bd-4be8df5fdf62,BootID:41400145-15aa-4241-b685-22af2a127e7f,KernelVersion:5.15.0-1026-aws,OSImage:Ubuntu 20.04.5 LTS,ContainerRuntimeVersion:docker://20.10.17,KubeletVersion:v1.23.15,KubeProxyVersion:v1.23.15,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/e2e-test-images/jessie-dnsutils@sha256:11e6a66017ba4e4b938c1612b7a54a3befcefd354796c04e1dba76873a13518e k8s.gcr.io/e2e-test-images/jessie-dnsutils:1.5],SizeBytes:253371792,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/httpd@sha256:20f25f275d46aa728f7615a1ccc19c78b2ed89435bf943a44b339f70f45508e6 k8s.gcr.io/e2e-test-images/httpd:2.4.39-2],SizeBytes:126894770,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:7e8bdd271312fd25fc5ff5a8f04727be84044eb3d7d8d03611972a6752e2e11e k8s.gcr.io/e2e-test-images/agnhost:2.39],SizeBytes:126872991,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/httpd@sha256:1b9d1b2f36cb2dbee1960e82a9344aeb11bd4c4c03abf5e1853e0559c23855e3 k8s.gcr.io/e2e-test-images/httpd:2.4.38-2],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-proxy-amd64:v1.23.15 registry.k8s.io/kube-proxy-amd64:v1.23.15],SizeBytes:112336036,},ContainerImage{Names:[registry.k8s.io/provider-aws/aws-ebs-csi-driver@sha256:10e231cf07c82dfab5141c1afe548dc734e5fc1f67665ec3982a325d1bd31a9a registry.k8s.io/provider-aws/aws-ebs-csi-driver:v1.14.0],SizeBytes:94471559,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-provisioner@sha256:c8e03f60afa90a28e4bb6ec9a8d0fc36d89de4b7475cf2d613afa793ec969fe0 k8s.gcr.io/sig-storage/csi-provisioner:v2.2.0],SizeBytes:56382329,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-provisioner@sha256:4e74c0492bceddc598de1c90cc5bc14dcda94cb49fa9c5bad9d117c4834b5e08 k8s.gcr.io/sig-storage/csi-provisioner:v2.2.1],SizeBytes:56379269,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-resizer@sha256:36c31f7e1f433c9634d24f876353e8646246d81a03c4e351202c2644daff1620 k8s.gcr.io/sig-storage/csi-resizer:v1.2.0],SizeBytes:53956308,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-snapshotter@sha256:ed98431376c9e944e19a465fe8ea944806714dd95416a0821096c78d66b579bd k8s.gcr.io/sig-storage/csi-snapshotter:v4.1.1],SizeBytes:53531990,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-attacher@sha256:c5be65d6679efabb969d9b019300d187437ae876f992c40911fd2892bbef3b36 k8s.gcr.io/sig-storage/csi-attacher:v3.2.0],SizeBytes:53500826,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-attacher@sha256:60ab9b3e6a030d3038c87c0d6bca2930f58d1d72823e6a4af09767dc83b696a2 k8s.gcr.io/sig-storage/csi-attacher:v3.2.1],SizeBytes:53499570,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:50249337,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-resizer@sha256:7a5ba58a44e0d749e0767e4e37315bcf6a61f33ce3185c1991848af4db0fb70a k8s.gcr.io/sig-storage/csi-resizer:v1.1.0],SizeBytes:49176472,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/regression-issue-74839@sha256:b4f1d8d61bdad84bd50442d161d5460e4019d53e989b64220fdbc62fc87d76bf k8s.gcr.io/e2e-test-images/regression-issue-74839:1.2],SizeBytes:44576952,},ContainerImage{Names:[k8s.gcr.io/sig-storage/hostpathplugin@sha256:232fe80174d60d520d36043103853a1d7ab4b7f3782cf43e45034f04ccda58ce k8s.gcr.io/sig-storage/hostpathplugin:v1.7.1],SizeBytes:29977921,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:19662887,},ContainerImage{Names:[registry.k8s.io/sig-storage/csi-node-driver-registrar@sha256:0103eee7c35e3e0b5cd8cdca9850dc71c793cdeb6669d8be7a89440da2d06ae4 registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.5.1],SizeBytes:19582112,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:2dee3fe5fe861bb66c3a4ac51114f3447a4cd35870e0f2e2b558c7a400d89589 k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.2.0],SizeBytes:18699436,},ContainerImage{Names:[k8s.gcr.io/sig-storage/mock-driver@sha256:a7b517f9e0f42ffade802eef9cefa271372386b85f55b702b493241e58459793 k8s.gcr.io/sig-storage/mock-driver:v4.1.0],SizeBytes:17680993,},ContainerImage{Names:[registry.k8s.io/sig-storage/livenessprobe@sha256:406f59599991916d2942d8d02f076d957ed71b541ee19f09fc01723a6e6f5932 registry.k8s.io/sig-storage/livenessprobe:v2.6.0],SizeBytes:17611980,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:529be2c9770add0cdd0c989115222ea9fc1be430c11095eb9f6dafcf98a36e2b k8s.gcr.io/sig-storage/livenessprobe:v2.4.0],SizeBytes:17175488,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:13616070e3f29de4417eee434a8ef472221c9e51b3d037b5a6b46cef08eb7443 k8s.gcr.io/e2e-test-images/nginx:1.14-2],SizeBytes:16032814,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nonewprivs@sha256:8ac1264691820febacf3aea5d152cbde6d10685731ec14966a9401c6f47a68ac k8s.gcr.io/e2e-test-images/nonewprivs:1.3],SizeBytes:7107254,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:c318242786b139d18676b1c09a0ad7f15fc17f8f16a5b2e625cd0dc8c9703daf k8s.gcr.io/e2e-test-images/busybox:1.29-2],SizeBytes:1154361,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db registry.k8s.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6 registry.k8s.io/pause:3.6],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 7 21:30:20.714: INFO: Logging kubelet events for node ip-172-20-51-5.ec2.internal Jan 7 21:30:20.747: INFO: Logging pods the kubelet thinks is on node ip-172-20-51-5.ec2.internal Jan 7 21:30:20.782: INFO: netserver-1 started at 2023-01-07 21:22:44 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.782: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:20.782: INFO: ebs-csi-node-5djh8 started at 2023-01-07 21:08:31 +0000 UTC (0+3 container statuses recorded) Jan 7 21:30:20.782: INFO: Container ebs-plugin ready: true, restart count 0 Jan 7 21:30:20.782: INFO: Container liveness-probe ready: true, restart count 0 Jan 7 21:30:20.782: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 7 21:30:20.783: INFO: netserver-1 started at 2023-01-07 21:24:07 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.783: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:20.783: INFO: coredns-867df8f45c-hm8mm started at 2023-01-07 21:08:44 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.783: INFO: Container coredns ready: true, restart count 0 Jan 7 21:30:20.783: INFO: execpodmrtcw started at 2023-01-07 21:30:08 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.783: INFO: Container agnhost-container ready: true, restart count 0 Jan 7 21:30:20.783: INFO: netserver-1 started at 2023-01-07 21:22:55 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.783: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:20.783: INFO: netserver-1 started at 2023-01-07 21:23:13 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.783: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:20.783: INFO: externalname-service-lvd45 started at 2023-01-07 21:30:05 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.783: INFO: Container externalname-service ready: true, restart count 0 Jan 7 21:30:20.783: INFO: kube-proxy-ip-172-20-51-5.ec2.internal started at 2023-01-07 21:08:30 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.783: INFO: Container kube-proxy ready: true, restart count 0 Jan 7 21:30:20.783: INFO: netserver-1 started at 2023-01-07 21:24:19 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:20.783: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:20.921: INFO: Latency metrics for node ip-172-20-51-5.ec2.internal Jan 7 21:30:20.921: INFO: Logging node info for node ip-172-20-54-171.ec2.internal Jan 7 21:30:20.952: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-54-171.ec2.internal 1234c811-abf8-44d0-8872-7ad4ed148e42 40266 0 2023-01-07 21:08:31 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:us-east-1 failure-domain.beta.kubernetes.io/zone:us-east-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-54-171.ec2.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:us-east-1a topology.hostpath.csi/node:ip-172-20-54-171.ec2.internal topology.kubernetes.io/region:us-east-1 topology.kubernetes.io/zone:us-east-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-07426332fdbd0ee79"} node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-07 21:08:31 +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: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":{}}} } {kops-controller Update v1 2023-01-07 21:08:32 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}} } {kube-controller-manager Update v1 2023-01-07 21:08:32 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.3.0/24\"":{}}}} } {kube-controller-manager Update v1 2023-01-07 21:29:26 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-07 21:30:08 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.ebs.csi.aws.com/zone":{},"f:topology.hostpath.csi/node":{}}},"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:capacity":{"f:ephemeral-storage":{}},"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:100.96.3.0/24,DoNotUseExternalID:,ProviderID:aws:///us-east-1a/i-07426332fdbd0ee79,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.3.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49753808896 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4051681280 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44778427933 0} {<nil>} 44778427933 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3946823680 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-07 21:08:36 +0000 UTC,LastTransitionTime:2023-01-07 21:08:36 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-07 21:30:08 +0000 UTC,LastTransitionTime:2023-01-07 21:08:31 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-07 21:30:08 +0000 UTC,LastTransitionTime:2023-01-07 21:08:31 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-07 21:30:08 +0000 UTC,LastTransitionTime:2023-01-07 21:08:31 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-07 21:30:08 +0000 UTC,LastTransitionTime:2023-01-07 21:08:42 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.54.171,},NodeAddress{Type:ExternalIP,Address:54.87.25.163,},NodeAddress{Type:Hostname,Address:ip-172-20-54-171.ec2.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-54-171.ec2.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-54-87-25-163.compute-1.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec20487bd0d373c3006264e85a97bdb1,SystemUUID:ec20487b-d0d3-73c3-0062-64e85a97bdb1,BootID:6ee03b7c-9910-4945-a0b0-ddb03deec484,KernelVersion:5.15.0-1026-aws,OSImage:Ubuntu 20.04.5 LTS,ContainerRuntimeVersion:docker://20.10.17,KubeletVersion:v1.23.15,KubeProxyVersion:v1.23.15,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/e2e-test-images/jessie-dnsutils@sha256:11e6a66017ba4e4b938c1612b7a54a3befcefd354796c04e1dba76873a13518e k8s.gcr.io/e2e-test-images/jessie-dnsutils:1.5],SizeBytes:253371792,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/httpd@sha256:20f25f275d46aa728f7615a1ccc19c78b2ed89435bf943a44b339f70f45508e6 k8s.gcr.io/e2e-test-images/httpd:2.4.39-2],SizeBytes:126894770,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:7e8bdd271312fd25fc5ff5a8f04727be84044eb3d7d8d03611972a6752e2e11e k8s.gcr.io/e2e-test-images/agnhost:2.39],SizeBytes:126872991,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nautilus@sha256:99c0d6f1ad24a1aa1905d9c6534d193f268f7b23f9add2ae6bb41f31094bdd5c k8s.gcr.io/e2e-test-images/nautilus:1.5],SizeBytes:124758741,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/httpd@sha256:1b9d1b2f36cb2dbee1960e82a9344aeb11bd4c4c03abf5e1853e0559c23855e3 k8s.gcr.io/e2e-test-images/httpd:2.4.38-2],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-proxy-amd64:v1.23.15 registry.k8s.io/kube-proxy-amd64:v1.23.15],SizeBytes:112336036,},ContainerImage{Names:[registry.k8s.io/provider-aws/aws-ebs-csi-driver@sha256:10e231cf07c82dfab5141c1afe548dc734e5fc1f67665ec3982a325d1bd31a9a registry.k8s.io/provider-aws/aws-ebs-csi-driver:v1.14.0],SizeBytes:94471559,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-provisioner@sha256:c8e03f60afa90a28e4bb6ec9a8d0fc36d89de4b7475cf2d613afa793ec969fe0 k8s.gcr.io/sig-storage/csi-provisioner:v2.2.0],SizeBytes:56382329,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-provisioner@sha256:4e74c0492bceddc598de1c90cc5bc14dcda94cb49fa9c5bad9d117c4834b5e08 k8s.gcr.io/sig-storage/csi-provisioner:v2.2.1],SizeBytes:56379269,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-resizer@sha256:36c31f7e1f433c9634d24f876353e8646246d81a03c4e351202c2644daff1620 k8s.gcr.io/sig-storage/csi-resizer:v1.2.0],SizeBytes:53956308,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-snapshotter@sha256:ed98431376c9e944e19a465fe8ea944806714dd95416a0821096c78d66b579bd k8s.gcr.io/sig-storage/csi-snapshotter:v4.1.1],SizeBytes:53531990,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-attacher@sha256:c5be65d6679efabb969d9b019300d187437ae876f992c40911fd2892bbef3b36 k8s.gcr.io/sig-storage/csi-attacher:v3.2.0],SizeBytes:53500826,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-attacher@sha256:60ab9b3e6a030d3038c87c0d6bca2930f58d1d72823e6a4af09767dc83b696a2 k8s.gcr.io/sig-storage/csi-attacher:v3.2.1],SizeBytes:53499570,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-resizer@sha256:7a5ba58a44e0d749e0767e4e37315bcf6a61f33ce3185c1991848af4db0fb70a k8s.gcr.io/sig-storage/csi-resizer:v1.1.0],SizeBytes:49176472,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nonroot@sha256:b9e2958a3dd879e3cf11142228c6d073d0fc4ea2e857c3be6f4fb0ab5fb2c937 k8s.gcr.io/e2e-test-images/nonroot:1.2],SizeBytes:42321438,},ContainerImage{Names:[k8s.gcr.io/sig-storage/hostpathplugin@sha256:232fe80174d60d520d36043103853a1d7ab4b7f3782cf43e45034f04ccda58ce k8s.gcr.io/sig-storage/hostpathplugin:v1.7.1],SizeBytes:29977921,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:19662887,},ContainerImage{Names:[registry.k8s.io/sig-storage/csi-node-driver-registrar@sha256:0103eee7c35e3e0b5cd8cdca9850dc71c793cdeb6669d8be7a89440da2d06ae4 registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.5.1],SizeBytes:19582112,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:2dee3fe5fe861bb66c3a4ac51114f3447a4cd35870e0f2e2b558c7a400d89589 k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.2.0],SizeBytes:18699436,},ContainerImage{Names:[k8s.gcr.io/sig-storage/mock-driver@sha256:a7b517f9e0f42ffade802eef9cefa271372386b85f55b702b493241e58459793 k8s.gcr.io/sig-storage/mock-driver:v4.1.0],SizeBytes:17680993,},ContainerImage{Names:[registry.k8s.io/sig-storage/livenessprobe@sha256:406f59599991916d2942d8d02f076d957ed71b541ee19f09fc01723a6e6f5932 registry.k8s.io/sig-storage/livenessprobe:v2.6.0],SizeBytes:17611980,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:529be2c9770add0cdd0c989115222ea9fc1be430c11095eb9f6dafcf98a36e2b k8s.gcr.io/sig-storage/livenessprobe:v2.4.0],SizeBytes:17175488,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:13616070e3f29de4417eee434a8ef472221c9e51b3d037b5a6b46cef08eb7443 k8s.gcr.io/e2e-test-images/nginx:1.14-2],SizeBytes:16032814,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:c318242786b139d18676b1c09a0ad7f15fc17f8f16a5b2e625cd0dc8c9703daf k8s.gcr.io/e2e-test-images/busybox:1.29-2],SizeBytes:1154361,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:1154361,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db registry.k8s.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6 registry.k8s.io/pause:3.6],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 7 21:30:20.952: INFO: Logging kubelet events for node ip-172-20-54-171.ec2.internal Jan 7 21:30:20.985: INFO: Logging pods the kubelet thinks is on node ip-172-20-54-171.ec2.internal Jan 7 21:30:21.019: INFO: kube-proxy-ip-172-20-54-171.ec2.internal started at 2023-01-07 21:08:32 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.019: INFO: Container kube-proxy ready: true, restart count 0 Jan 7 21:30:21.019: INFO: ebs-csi-node-lkzp8 started at 2023-01-07 21:08:33 +0000 UTC (0+3 container statuses recorded) Jan 7 21:30:21.020: INFO: Container ebs-plugin ready: true, restart count 0 Jan 7 21:30:21.020: INFO: Container liveness-probe ready: true, restart count 0 Jan 7 21:30:21.020: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 7 21:30:21.020: INFO: netserver-2 started at 2023-01-07 21:24:07 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.020: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:21.020: INFO: netserver-2 started at 2023-01-07 21:22:55 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.020: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:21.020: INFO: netserver-2 started at 2023-01-07 21:24:19 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.020: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:21.020: INFO: netserver-2 started at 2023-01-07 21:22:44 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.020: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:21.020: INFO: netserver-2 started at 2023-01-07 21:23:13 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.020: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:21.181: INFO: Latency metrics for node ip-172-20-54-171.ec2.internal Jan 7 21:30:21.181: INFO: Logging node info for node ip-172-20-57-157.ec2.internal Jan 7 21:30:21.212: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-57-157.ec2.internal 01758eef-c696-4bda-ab17-559a54bc1492 39405 0 2023-01-07 21:06:41 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:c5.large beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:us-east-1 failure-domain.beta.kubernetes.io/zone:us-east-1a kops.k8s.io/kops-controller-pki: kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-57-157.ec2.internal kubernetes.io/os:linux kubernetes.io/role:master node-role.kubernetes.io/control-plane: node-role.kubernetes.io/master: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:c5.large topology.ebs.csi.aws.com/zone:us-east-1a topology.kubernetes.io/region:us-east-1 topology.kubernetes.io/zone:us-east-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-09fb60937e522a8b1"} node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-07 21:06:41 +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: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":{}}} } {protokube Update v1 2023-01-07 21:07:04 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kops.k8s.io/kops-controller-pki":{},"f:node-role.kubernetes.io/control-plane":{},"f:node.kubernetes.io/exclude-from-external-load-balancers":{}}}} } {kube-controller-manager Update v1 2023-01-07 21:07:05 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kube-controller-manager Update v1 2023-01-07 21:07:17 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.0.0/24\"":{}},"f:taints":{}}} } {kops-controller Update v1 2023-01-07 21:07:19 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/master":{}}}} } {kubelet Update v1 2023-01-07 21:07:33 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.ebs.csi.aws.com/zone":{}}},"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:100.96.0.0/24,DoNotUseExternalID:,ProviderID:aws:///us-east-1a/i-09fb60937e522a8b1,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/master,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[100.96.0.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49753808896 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3892301824 0} {<nil>} 3801076Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44778427933 0} {<nil>} 44778427933 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3787444224 0} {<nil>} 3698676Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-07 21:07:26 +0000 UTC,LastTransitionTime:2023-01-07 21:07:26 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-07 21:28:02 +0000 UTC,LastTransitionTime:2023-01-07 21:06:37 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-07 21:28:02 +0000 UTC,LastTransitionTime:2023-01-07 21:06:37 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-07 21:28:02 +0000 UTC,LastTransitionTime:2023-01-07 21:06:37 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-07 21:28:02 +0000 UTC,LastTransitionTime:2023-01-07 21:07:17 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.57.157,},NodeAddress{Type:ExternalIP,Address:54.145.242.88,},NodeAddress{Type:Hostname,Address:ip-172-20-57-157.ec2.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-57-157.ec2.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-54-145-242-88.compute-1.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec2d38878eca4a64d4adbb2d6af3d2df,SystemUUID:ec2d3887-8eca-4a64-d4ad-bb2d6af3d2df,BootID:5bff2f8f-f2ed-472d-b40a-11bacd7139a1,KernelVersion:5.15.0-1026-aws,OSImage:Ubuntu 20.04.5 LTS,ContainerRuntimeVersion:docker://20.10.17,KubeletVersion:v1.23.15,KubeProxyVersion:v1.23.15,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/etcdadm/etcd-manager@sha256:66a453db625abb268f4b3bbefc5a34a171d81e6e8796cecca54cfd71775c77c4 registry.k8s.io/etcdadm/etcd-manager:v3.0.20221209],SizeBytes:662209237,},ContainerImage{Names:[k8s.gcr.io/kube-apiserver-amd64:v1.23.15 registry.k8s.io/kube-apiserver-amd64:v1.23.15],SizeBytes:135240444,},ContainerImage{Names:[k8s.gcr.io/kube-controller-manager-amd64:v1.23.15 registry.k8s.io/kube-controller-manager-amd64:v1.23.15],SizeBytes:125046097,},ContainerImage{Names:[k8s.gcr.io/kube-proxy-amd64:v1.23.15 registry.k8s.io/kube-proxy-amd64:v1.23.15],SizeBytes:112336036,},ContainerImage{Names:[registry.k8s.io/kops/kops-controller:1.26.0-beta.1],SizeBytes:104212800,},ContainerImage{Names:[registry.k8s.io/kops/dns-controller:1.26.0-beta.1],SizeBytes:102566451,},ContainerImage{Names:[registry.k8s.io/provider-aws/aws-ebs-csi-driver@sha256:10e231cf07c82dfab5141c1afe548dc734e5fc1f67665ec3982a325d1bd31a9a registry.k8s.io/provider-aws/aws-ebs-csi-driver:v1.14.0],SizeBytes:94471559,},ContainerImage{Names:[registry.k8s.io/sig-storage/csi-provisioner@sha256:122bfb8c1edabb3c0edd63f06523e6940d958d19b3957dc7b1d6f81e9f1f6119 registry.k8s.io/sig-storage/csi-provisioner:v3.1.0],SizeBytes:57736070,},ContainerImage{Names:[registry.k8s.io/sig-storage/csi-resizer@sha256:9ebbf9f023e7b41ccee3d52afe39a89e3ddacdbb69269d583abfc25847cfd9e4 registry.k8s.io/sig-storage/csi-resizer:v1.4.0],SizeBytes:55464778,},ContainerImage{Names:[registry.k8s.io/sig-storage/csi-attacher@sha256:8b9c313c05f54fb04f8d430896f5f5904b6cb157df261501b29adc04d2b2dc7b registry.k8s.io/sig-storage/csi-attacher:v3.4.0],SizeBytes:54848595,},ContainerImage{Names:[k8s.gcr.io/kube-scheduler-amd64:v1.23.15 registry.k8s.io/kube-scheduler-amd64:v1.23.15],SizeBytes:53521430,},ContainerImage{Names:[registry.k8s.io/sig-storage/csi-node-driver-registrar@sha256:0103eee7c35e3e0b5cd8cdca9850dc71c793cdeb6669d8be7a89440da2d06ae4 registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.5.1],SizeBytes:19582112,},ContainerImage{Names:[registry.k8s.io/sig-storage/livenessprobe@sha256:406f59599991916d2942d8d02f076d957ed71b541ee19f09fc01723a6e6f5932 registry.k8s.io/sig-storage/livenessprobe:v2.6.0],SizeBytes:17611980,},ContainerImage{Names:[registry.k8s.io/kops/kube-apiserver-healthcheck:1.26.0-beta.1],SizeBytes:8787111,},ContainerImage{Names:[registry.k8s.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db registry.k8s.io/pause:3.6],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 7 21:30:21.212: INFO: Logging kubelet events for node ip-172-20-57-157.ec2.internal Jan 7 21:30:21.244: INFO: Logging pods the kubelet thinks is on node ip-172-20-57-157.ec2.internal Jan 7 21:30:21.279: INFO: kube-controller-manager-ip-172-20-57-157.ec2.internal started at 2023-01-07 21:06:03 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.279: INFO: Container kube-controller-manager ready: true, restart count 2 Jan 7 21:30:21.279: INFO: kube-proxy-ip-172-20-57-157.ec2.internal started at 2023-01-07 21:06:03 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.279: INFO: Container kube-proxy ready: true, restart count 0 Jan 7 21:30:21.280: INFO: ebs-csi-node-jmtsb started at 2023-01-07 21:07:18 +0000 UTC (0+3 container statuses recorded) Jan 7 21:30:21.280: INFO: Container ebs-plugin ready: true, restart count 0 Jan 7 21:30:21.280: INFO: Container liveness-probe ready: true, restart count 0 Jan 7 21:30:21.280: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 7 21:30:21.280: INFO: dns-controller-867784b75c-mv95c started at 2023-01-07 21:07:26 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.280: INFO: Container dns-controller ready: true, restart count 0 Jan 7 21:30:21.280: INFO: kube-scheduler-ip-172-20-57-157.ec2.internal started at 2023-01-07 21:06:03 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.280: INFO: Container kube-scheduler ready: true, restart count 0 Jan 7 21:30:21.280: INFO: etcd-manager-events-ip-172-20-57-157.ec2.internal started at 2023-01-07 21:06:03 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.280: INFO: Container etcd-manager ready: true, restart count 0 Jan 7 21:30:21.280: INFO: etcd-manager-main-ip-172-20-57-157.ec2.internal started at 2023-01-07 21:06:03 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.280: INFO: Container etcd-manager ready: true, restart count 0 Jan 7 21:30:21.280: INFO: kube-apiserver-ip-172-20-57-157.ec2.internal started at 2023-01-07 21:06:03 +0000 UTC (0+2 container statuses recorded) Jan 7 21:30:21.280: INFO: Container healthcheck ready: true, restart count 0 Jan 7 21:30:21.280: INFO: Container kube-apiserver ready: true, restart count 1 Jan 7 21:30:21.280: INFO: kops-controller-2mz96 started at 2023-01-07 21:07:18 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.280: INFO: Container kops-controller ready: true, restart count 0 Jan 7 21:30:21.280: INFO: ebs-csi-controller-68cc985d75-h2c78 started at 2023-01-07 21:07:18 +0000 UTC (0+5 container statuses recorded) Jan 7 21:30:21.280: INFO: Container csi-attacher ready: true, restart count 0 Jan 7 21:30:21.280: INFO: Container csi-provisioner ready: true, restart count 0 Jan 7 21:30:21.280: INFO: Container csi-resizer ready: true, restart count 0 Jan 7 21:30:21.280: INFO: Container ebs-plugin ready: true, restart count 0 Jan 7 21:30:21.280: INFO: Container liveness-probe ready: true, restart count 0 Jan 7 21:30:21.401: INFO: Latency metrics for node ip-172-20-57-157.ec2.internal Jan 7 21:30:21.401: INFO: Logging node info for node ip-172-20-60-128.ec2.internal Jan 7 21:30:21.431: INFO: Node Info: &Node{ObjectMeta:{ip-172-20-60-128.ec2.internal 2802a658-85cb-450f-a29e-12879429bb23 38575 0 2023-01-07 21:08:30 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:t3.medium beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:us-east-1 failure-domain.beta.kubernetes.io/zone:us-east-1a kubernetes.io/arch:amd64 kubernetes.io/hostname:ip-172-20-60-128.ec2.internal kubernetes.io/os:linux kubernetes.io/role:node node-role.kubernetes.io/node: node.kubernetes.io/instance-type:t3.medium topology.ebs.csi.aws.com/zone:us-east-1a topology.hostpath.csi/node:ip-172-20-60-128.ec2.internal topology.kubernetes.io/region:us-east-1 topology.kubernetes.io/zone:us-east-1a] map[csi.volume.kubernetes.io/nodeid:{"ebs.csi.aws.com":"i-01cf1b1df8f153175"} node.alpha.kubernetes.io/ttl:0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kops-controller Update v1 2023-01-07 21:08:30 +0000 UTC FieldsV1 {"f:metadata":{"f:labels":{"f:kubernetes.io/role":{},"f:node-role.kubernetes.io/node":{}}}} } {kube-controller-manager Update v1 2023-01-07 21:08:30 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:podCIDR":{},"f:podCIDRs":{".":{},"v:\"100.96.1.0/24\"":{}}}} } {kubelet Update v1 2023-01-07 21:08:30 +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: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-07 21:24:59 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-07 21:25:43 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.ebs.csi.aws.com/zone":{},"f:topology.hostpath.csi/node":{}}},"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:capacity":{"f:ephemeral-storage":{}},"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:100.96.1.0/24,DoNotUseExternalID:,ProviderID:aws:///us-east-1a/i-01cf1b1df8f153175,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[100.96.1.0/24],},Status:NodeStatus{Capacity:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{49753808896 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{4051681280 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{44778427933 0} {<nil>} 44778427933 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{3946823680 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-07 21:08:36 +0000 UTC,LastTransitionTime:2023-01-07 21:08:36 +0000 UTC,Reason:RouteCreated,Message:RouteController created a route,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-07 21:25:43 +0000 UTC,LastTransitionTime:2023-01-07 21:08:30 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-07 21:25:43 +0000 UTC,LastTransitionTime:2023-01-07 21:08:30 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-07 21:25:43 +0000 UTC,LastTransitionTime:2023-01-07 21:08:30 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-07 21:25:43 +0000 UTC,LastTransitionTime:2023-01-07 21:08:40 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:InternalIP,Address:172.20.60.128,},NodeAddress{Type:ExternalIP,Address:3.82.22.118,},NodeAddress{Type:Hostname,Address:ip-172-20-60-128.ec2.internal,},NodeAddress{Type:InternalDNS,Address:ip-172-20-60-128.ec2.internal,},NodeAddress{Type:ExternalDNS,Address:ec2-3-82-22-118.compute-1.amazonaws.com,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:ec226bbe59cb8ef10228c0d22828baa4,SystemUUID:ec226bbe-59cb-8ef1-0228-c0d22828baa4,BootID:19b7a6ce-ff2a-4dfa-b312-52a5813c832a,KernelVersion:5.15.0-1026-aws,OSImage:Ubuntu 20.04.5 LTS,ContainerRuntimeVersion:docker://20.10.17,KubeletVersion:v1.23.15,KubeProxyVersion:v1.23.15,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[k8s.gcr.io/e2e-test-images/jessie-dnsutils@sha256:11e6a66017ba4e4b938c1612b7a54a3befcefd354796c04e1dba76873a13518e k8s.gcr.io/e2e-test-images/jessie-dnsutils:1.5],SizeBytes:253371792,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/httpd@sha256:20f25f275d46aa728f7615a1ccc19c78b2ed89435bf943a44b339f70f45508e6 k8s.gcr.io/e2e-test-images/httpd:2.4.39-2],SizeBytes:126894770,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/agnhost@sha256:7e8bdd271312fd25fc5ff5a8f04727be84044eb3d7d8d03611972a6752e2e11e k8s.gcr.io/e2e-test-images/agnhost:2.39],SizeBytes:126872991,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nautilus@sha256:99c0d6f1ad24a1aa1905d9c6534d193f268f7b23f9add2ae6bb41f31094bdd5c k8s.gcr.io/e2e-test-images/nautilus:1.5],SizeBytes:124758741,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/httpd@sha256:1b9d1b2f36cb2dbee1960e82a9344aeb11bd4c4c03abf5e1853e0559c23855e3 k8s.gcr.io/e2e-test-images/httpd:2.4.38-2],SizeBytes:123781643,},ContainerImage{Names:[k8s.gcr.io/kube-proxy-amd64:v1.23.15 registry.k8s.io/kube-proxy-amd64:v1.23.15],SizeBytes:112336036,},ContainerImage{Names:[registry.k8s.io/provider-aws/aws-ebs-csi-driver@sha256:10e231cf07c82dfab5141c1afe548dc734e5fc1f67665ec3982a325d1bd31a9a registry.k8s.io/provider-aws/aws-ebs-csi-driver:v1.14.0],SizeBytes:94471559,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-provisioner@sha256:c8e03f60afa90a28e4bb6ec9a8d0fc36d89de4b7475cf2d613afa793ec969fe0 k8s.gcr.io/sig-storage/csi-provisioner:v2.2.0],SizeBytes:56382329,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-provisioner@sha256:4e74c0492bceddc598de1c90cc5bc14dcda94cb49fa9c5bad9d117c4834b5e08 k8s.gcr.io/sig-storage/csi-provisioner:v2.2.1],SizeBytes:56379269,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-resizer@sha256:36c31f7e1f433c9634d24f876353e8646246d81a03c4e351202c2644daff1620 k8s.gcr.io/sig-storage/csi-resizer:v1.2.0],SizeBytes:53956308,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-snapshotter@sha256:ed98431376c9e944e19a465fe8ea944806714dd95416a0821096c78d66b579bd k8s.gcr.io/sig-storage/csi-snapshotter:v4.1.1],SizeBytes:53531990,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-attacher@sha256:c5be65d6679efabb969d9b019300d187437ae876f992c40911fd2892bbef3b36 k8s.gcr.io/sig-storage/csi-attacher:v3.2.0],SizeBytes:53500826,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-attacher@sha256:60ab9b3e6a030d3038c87c0d6bca2930f58d1d72823e6a4af09767dc83b696a2 k8s.gcr.io/sig-storage/csi-attacher:v3.2.1],SizeBytes:53499570,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:50249337,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-resizer@sha256:7a5ba58a44e0d749e0767e4e37315bcf6a61f33ce3185c1991848af4db0fb70a k8s.gcr.io/sig-storage/csi-resizer:v1.1.0],SizeBytes:49176472,},ContainerImage{Names:[registry.k8s.io/cpa/cluster-proportional-autoscaler@sha256:68d396900aeaa072c1f27289485fdac29834045a6f3ffe369bf389d830ef572d registry.k8s.io/cpa/cluster-proportional-autoscaler:1.8.6],SizeBytes:47910609,},ContainerImage{Names:[k8s.gcr.io/sig-storage/hostpathplugin@sha256:232fe80174d60d520d36043103853a1d7ab4b7f3782cf43e45034f04ccda58ce k8s.gcr.io/sig-storage/hostpathplugin:v1.7.1],SizeBytes:29977921,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:a61d309da54641db41fb8f35718f744e9f730d4d0384f8c4b186ddc9f06cbd5f k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0],SizeBytes:19662887,},ContainerImage{Names:[registry.k8s.io/sig-storage/csi-node-driver-registrar@sha256:0103eee7c35e3e0b5cd8cdca9850dc71c793cdeb6669d8be7a89440da2d06ae4 registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.5.1],SizeBytes:19582112,},ContainerImage{Names:[k8s.gcr.io/sig-storage/csi-node-driver-registrar@sha256:2dee3fe5fe861bb66c3a4ac51114f3447a4cd35870e0f2e2b558c7a400d89589 k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.2.0],SizeBytes:18699436,},ContainerImage{Names:[k8s.gcr.io/sig-storage/mock-driver@sha256:a7b517f9e0f42ffade802eef9cefa271372386b85f55b702b493241e58459793 k8s.gcr.io/sig-storage/mock-driver:v4.1.0],SizeBytes:17680993,},ContainerImage{Names:[registry.k8s.io/sig-storage/livenessprobe@sha256:406f59599991916d2942d8d02f076d957ed71b541ee19f09fc01723a6e6f5932 registry.k8s.io/sig-storage/livenessprobe:v2.6.0],SizeBytes:17611980,},ContainerImage{Names:[k8s.gcr.io/sig-storage/livenessprobe@sha256:529be2c9770add0cdd0c989115222ea9fc1be430c11095eb9f6dafcf98a36e2b k8s.gcr.io/sig-storage/livenessprobe:v2.4.0],SizeBytes:17175488,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/nginx@sha256:13616070e3f29de4417eee434a8ef472221c9e51b3d037b5a6b46cef08eb7443 k8s.gcr.io/e2e-test-images/nginx:1.14-2],SizeBytes:16032814,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:c318242786b139d18676b1c09a0ad7f15fc17f8f16a5b2e625cd0dc8c9703daf k8s.gcr.io/e2e-test-images/busybox:1.29-2],SizeBytes:1154361,},ContainerImage{Names:[k8s.gcr.io/e2e-test-images/busybox@sha256:39e1e963e5310e9c313bad51523be012ede7b35bb9316517d19089a010356592 k8s.gcr.io/e2e-test-images/busybox:1.29-1],SizeBytes:1154361,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db registry.k8s.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6 registry.k8s.io/pause:3.6],SizeBytes:682696,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 7 21:30:21.432: INFO: Logging kubelet events for node ip-172-20-60-128.ec2.internal Jan 7 21:30:21.464: INFO: Logging pods the kubelet thinks is on node ip-172-20-60-128.ec2.internal Jan 7 21:30:21.499: INFO: netserver-3 started at 2023-01-07 21:24:07 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.499: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:21.499: INFO: netserver-3 started at 2023-01-07 21:24:19 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.499: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:21.499: INFO: netserver-3 started at 2023-01-07 21:22:44 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.499: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:21.499: INFO: coredns-autoscaler-557ccb4c66-s4q7h started at 2023-01-07 21:08:40 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.499: INFO: Container autoscaler ready: true, restart count 0 Jan 7 21:30:21.499: INFO: netserver-3 started at 2023-01-07 21:22:55 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.499: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:21.499: INFO: ebs-csi-node-jv2cp started at 2023-01-07 21:08:31 +0000 UTC (0+3 container statuses recorded) Jan 7 21:30:21.499: INFO: Container ebs-plugin ready: true, restart count 0 Jan 7 21:30:21.499: INFO: Container liveness-probe ready: true, restart count 0 Jan 7 21:30:21.499: INFO: Container node-driver-registrar ready: true, restart count 0 Jan 7 21:30:21.499: INFO: coredns-867df8f45c-ds847 started at 2023-01-07 21:08:40 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.499: INFO: Container coredns ready: true, restart count 0 Jan 7 21:30:21.499: INFO: netserver-3 started at 2023-01-07 21:23:13 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.499: INFO: Container webserver ready: true, restart count 0 Jan 7 21:30:21.499: INFO: externalname-service-wv9b2 started at 2023-01-07 21:30:05 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.499: INFO: Container externalname-service ready: true, restart count 0 Jan 7 21:30:21.499: INFO: kube-proxy-ip-172-20-60-128.ec2.internal started at 2023-01-07 21:08:30 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.499: INFO: Container kube-proxy ready: true, restart count 0 Jan 7 21:30:21.499: INFO: pod-client started at 2023-01-07 21:25:17 +0000 UTC (0+1 container statuses recorded) Jan 7 21:30:21.499: INFO: Container pod-client ready: true, restart count 0 Jan 7 21:30:21.631: INFO: Latency metrics for node ip-172-20-60-128.ec2.internal Jan 7 21:30:21.631: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:30:21.662: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:23.696: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:25.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:27.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:29.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:31.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:33.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:35.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:37.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:39.696: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:41.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:43.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:45.693: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:47.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:49.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:51.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:53.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:55.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:57.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:59.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:01.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:03.696: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:05.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:07.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:09.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:11.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:13.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:15.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:17.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:19.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:21.696: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:23.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:25.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:27.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:29.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:31.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:33.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:35.696: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:37.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:39.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:41.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:43.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:45.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:47.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:49.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:51.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:53.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:55.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:57.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:31:59.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:01.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:03.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:05.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:07.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:09.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:11.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:13.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:15.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:17.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:19.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:21.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:23.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:25.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:27.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:29.696: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:31.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:33.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:35.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:37.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:39.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:41.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:43.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:45.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:47.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:49.696: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:51.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:53.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:55.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:57.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:32:59.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:01.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:03.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:05.696: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:07.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:09.696: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:11.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:13.694: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:15.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:17.696: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:19.696: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:21.695: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:21.726: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:33:21.726: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0xc) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc0007fdba0, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "conntrack-6846" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sDNS\sshould\sprovide\sDNS\sfor\spods\sfor\sSubdomain\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:40:03.044: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_16.xml
[BeforeEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:36:29.995: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename dns �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] should provide DNS for pods for Subdomain [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 �[1mSTEP�[0m: Creating a test headless service �[1mSTEP�[0m: Running these commands on wheezy: for i in `seq 1 600`; do check="$$(dig +notcp +noall +answer +search dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local A)" && test -n "$$check" && echo OK > /results/wheezy_udp@dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local;check="$$(dig +tcp +noall +answer +search dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local;check="$$(dig +notcp +noall +answer +search dns-test-service-2.dns-1061.svc.cluster.local A)" && test -n "$$check" && echo OK > /results/wheezy_udp@dns-test-service-2.dns-1061.svc.cluster.local;check="$$(dig +tcp +noall +answer +search dns-test-service-2.dns-1061.svc.cluster.local A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@dns-test-service-2.dns-1061.svc.cluster.local;sleep 1; done �[1mSTEP�[0m: Running these commands on jessie: for i in `seq 1 600`; do check="$$(dig +notcp +noall +answer +search dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local A)" && test -n "$$check" && echo OK > /results/jessie_udp@dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local;check="$$(dig +tcp +noall +answer +search dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local A)" && test -n "$$check" && echo OK > /results/jessie_tcp@dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local;check="$$(dig +notcp +noall +answer +search dns-test-service-2.dns-1061.svc.cluster.local A)" && test -n "$$check" && echo OK > /results/jessie_udp@dns-test-service-2.dns-1061.svc.cluster.local;check="$$(dig +tcp +noall +answer +search dns-test-service-2.dns-1061.svc.cluster.local A)" && test -n "$$check" && echo OK > /results/jessie_tcp@dns-test-service-2.dns-1061.svc.cluster.local;sleep 1; done �[1mSTEP�[0m: creating a pod to probe DNS �[1mSTEP�[0m: submitting the pod to kubernetes �[1mSTEP�[0m: retrieving the pod �[1mSTEP�[0m: looking for the results for each expected name from probers Jan 7 21:36:32.400: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:32.431: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:32.462: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:32.493: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:32.524: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:32.555: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:32.586: INFO: Unable to read jessie_udp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:32.617: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:32.617: INFO: Lookups using dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local wheezy_udp@dns-test-service-2.dns-1061.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-1061.svc.cluster.local jessie_udp@dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-1061.svc.cluster.local jessie_udp@dns-test-service-2.dns-1061.svc.cluster.local jessie_tcp@dns-test-service-2.dns-1061.svc.cluster.local] Jan 7 21:36:37.711: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:37.743: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:37.836: INFO: Unable to read jessie_udp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:37.869: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:37.869: INFO: Lookups using dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84 failed for: [wheezy_udp@dns-test-service-2.dns-1061.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-1061.svc.cluster.local jessie_udp@dns-test-service-2.dns-1061.svc.cluster.local jessie_tcp@dns-test-service-2.dns-1061.svc.cluster.local] Jan 7 21:36:42.711: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:42.742: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:42.835: INFO: Unable to read jessie_udp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:42.866: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:42.866: INFO: Lookups using dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84 failed for: [wheezy_udp@dns-test-service-2.dns-1061.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-1061.svc.cluster.local jessie_udp@dns-test-service-2.dns-1061.svc.cluster.local jessie_tcp@dns-test-service-2.dns-1061.svc.cluster.local] Jan 7 21:36:47.711: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:47.747: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:47.840: INFO: Unable to read jessie_udp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:47.872: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:47.872: INFO: Lookups using dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84 failed for: [wheezy_udp@dns-test-service-2.dns-1061.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-1061.svc.cluster.local jessie_udp@dns-test-service-2.dns-1061.svc.cluster.local jessie_tcp@dns-test-service-2.dns-1061.svc.cluster.local] Jan 7 21:36:52.711: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:52.742: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:52.835: INFO: Unable to read jessie_udp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:52.866: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:52.866: INFO: Lookups using dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84 failed for: [wheezy_udp@dns-test-service-2.dns-1061.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-1061.svc.cluster.local jessie_udp@dns-test-service-2.dns-1061.svc.cluster.local jessie_tcp@dns-test-service-2.dns-1061.svc.cluster.local] Jan 7 21:36:57.710: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:57.741: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:57.835: INFO: Unable to read jessie_udp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:57.865: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-1061.svc.cluster.local from pod dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84: the server could not find the requested resource (get pods dns-test-925ca604-3a02-4dd9-991f-457690240b84) Jan 7 21:36:57.865: INFO: Lookups using dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84 failed for: [wheezy_udp@dns-test-service-2.dns-1061.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-1061.svc.cluster.local jessie_udp@dns-test-service-2.dns-1061.svc.cluster.local jessie_tcp@dns-test-service-2.dns-1061.svc.cluster.local] Jan 7 21:37:02.867: INFO: DNS probes using dns-1061/dns-test-925ca604-3a02-4dd9-991f-457690240b84 succeeded �[1mSTEP�[0m: deleting the pod �[1mSTEP�[0m: deleting the test headless service [AfterEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:37:02.948: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:37:02.980: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:05.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:07.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:09.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:11.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:13.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:15.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:17.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:19.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:21.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:23.022: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:25.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:27.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:29.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:31.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:33.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:35.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:37.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:39.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:41.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:43.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:45.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:47.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:49.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:51.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:53.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:55.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:57.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:59.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:01.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:03.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:05.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:07.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:09.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:11.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:13.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:15.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:17.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:19.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:21.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:23.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:25.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:27.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:29.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:31.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:33.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:35.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:37.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:39.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:41.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:43.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:45.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:47.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:49.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:51.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:53.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:55.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:57.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:59.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:01.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:03.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:05.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:07.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:09.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:11.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:13.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:15.015: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:17.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:19.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:21.024: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:23.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:25.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:27.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:29.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:31.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:33.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:35.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:37.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:39.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:41.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:43.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:45.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:47.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:49.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:51.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:53.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:55.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:57.011: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:59.013: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:01.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:03.012: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:03.044: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:03.044: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x243a8f9) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc00021e340, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "dns-1061" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sDNS\sshould\ssupport\sconfigurable\spod\sDNS\snameservers\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:40:19.408: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_07.xml
[BeforeEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:37:16.412: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename dns �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [It] should support configurable pod DNS nameservers [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 �[1mSTEP�[0m: Creating a pod with dnsPolicy=None and customized dnsConfig... Jan 7 21:37:16.647: INFO: Created pod &Pod{ObjectMeta:{test-dns-nameservers dns-2082 9a1cbe5b-9096-4fa8-a46c-f34bfc717751 43195 0 2023-01-07 21:37:16 +0000 UTC <nil> <nil> map[] map[] [] [] [{e2e.test Update v1 2023-01-07 21:37:16 +0000 UTC FieldsV1 {"f:spec":{"f:containers":{"k:{\"name\":\"agnhost-container\"}":{".":{},"f:args":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsConfig":{".":{},"f:nameservers":{},"f:searches":{}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}} }]},Spec:PodSpec{Volumes:[]Volume{Volume{Name:kube-api-access-rjrdj,VolumeSource:VolumeSource{HostPath:nil,EmptyDir:nil,GCEPersistentDisk:nil,AWSElasticBlockStore:nil,GitRepo:nil,Secret:nil,NFS:nil,ISCSI:nil,Glusterfs:nil,PersistentVolumeClaim:nil,RBD:nil,FlexVolume:nil,Cinder:nil,CephFS:nil,Flocker:nil,DownwardAPI:nil,FC:nil,AzureFile:nil,ConfigMap:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Projected:&ProjectedVolumeSource{Sources:[]VolumeProjection{VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:nil,ServiceAccountToken:&ServiceAccountTokenProjection{Audience:,ExpirationSeconds:*3607,Path:token,},},VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:&ConfigMapProjection{LocalObjectReference:LocalObjectReference{Name:kube-root-ca.crt,},Items:[]KeyToPath{KeyToPath{Key:ca.crt,Path:ca.crt,Mode:nil,},},Optional:nil,},ServiceAccountToken:nil,},VolumeProjection{Secret:nil,DownwardAPI:&DownwardAPIProjection{Items:[]DownwardAPIVolumeFile{DownwardAPIVolumeFile{Path:namespace,FieldRef:&ObjectFieldSelector{APIVersion:v1,FieldPath:metadata.namespace,},ResourceFieldRef:nil,Mode:nil,},},},ConfigMap:nil,ServiceAccountToken:nil,},},DefaultMode:*420,},StorageOS:nil,CSI:nil,Ephemeral:nil,},},},Containers:[]Container{Container{Name:agnhost-container,Image:k8s.gcr.io/e2e-test-images/agnhost:2.39,Command:[],Args:[pause],WorkingDir:,Ports:[]ContainerPort{},Env:[]EnvVar{},Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},},VolumeMounts:[]VolumeMount{VolumeMount{Name:kube-api-access-rjrdj,ReadOnly:true,MountPath:/var/run/secrets/kubernetes.io/serviceaccount,SubPath:,MountPropagation:nil,SubPathExpr:,},},LivenessProbe:nil,ReadinessProbe:nil,Lifecycle:nil,TerminationMessagePath:/dev/termination-log,ImagePullPolicy:IfNotPresent,SecurityContext:&SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,},Stdin:false,StdinOnce:false,TTY:false,EnvFrom:[]EnvFromSource{},TerminationMessagePolicy:File,VolumeDevices:[]VolumeDevice{},StartupProbe:nil,},},RestartPolicy:Always,TerminationGracePeriodSeconds:*0,ActiveDeadlineSeconds:nil,DNSPolicy:None,NodeSelector:map[string]string{},ServiceAccountName:default,DeprecatedServiceAccount:default,NodeName:,HostNetwork:false,HostPID:false,HostIPC:false,SecurityContext:&PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,},ImagePullSecrets:[]LocalObjectReference{},Hostname:,Subdomain:,Affinity:nil,SchedulerName:default-scheduler,InitContainers:[]Container{},AutomountServiceAccountToken:nil,Tolerations:[]Toleration{Toleration{Key:node.kubernetes.io/not-ready,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},Toleration{Key:node.kubernetes.io/unreachable,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},},HostAliases:[]HostAlias{},PriorityClassName:,Priority:*0,DNSConfig:&PodDNSConfig{Nameservers:[1.1.1.1],Searches:[resolv.conf.local],Options:[]PodDNSConfigOption{},},ShareProcessNamespace:nil,ReadinessGates:[]PodReadinessGate{},RuntimeClassName:nil,EnableServiceLinks:*true,PreemptionPolicy:*PreemptLowerPriority,Overhead:ResourceList{},TopologySpreadConstraints:[]TopologySpreadConstraint{},EphemeralContainers:[]EphemeralContainer{},SetHostnameAsFQDN:nil,OS:nil,},Status:PodStatus{Phase:Pending,Conditions:[]PodCondition{},Message:,Reason:,HostIP:,PodIP:,StartTime:<nil>,ContainerStatuses:[]ContainerStatus{},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{},EphemeralContainerStatuses:[]ContainerStatus{},},} Jan 7 21:37:16.677: INFO: The status of Pod test-dns-nameservers is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:37:18.707: INFO: The status of Pod test-dns-nameservers is Running (Ready = true) �[1mSTEP�[0m: Verifying customized DNS suffix list is configured on pod... Jan 7 21:37:18.707: INFO: ExecWithOptions {Command:[/agnhost dns-suffix] Namespace:dns-2082 PodName:test-dns-nameservers ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:37:18.707: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:37:18.707: INFO: ExecWithOptions: Clientset creation Jan 7 21:37:18.707: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/dns-2082/pods/test-dns-nameservers/exec?command=%2Fagnhost&command=dns-suffix&container=agnhost-container&container=agnhost-container&stderr=true&stdout=true %!s(MISSING)) �[1mSTEP�[0m: Verifying customized DNS server is configured on pod... Jan 7 21:37:19.001: INFO: ExecWithOptions {Command:[/agnhost dns-server-list] Namespace:dns-2082 PodName:test-dns-nameservers ContainerName:agnhost-container Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:37:19.001: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:37:19.002: INFO: ExecWithOptions: Clientset creation Jan 7 21:37:19.002: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/dns-2082/pods/test-dns-nameservers/exec?command=%2Fagnhost&command=dns-server-list&container=agnhost-container&container=agnhost-container&stderr=true&stdout=true %!s(MISSING)) Jan 7 21:37:19.279: INFO: Deleting pod test-dns-nameservers... [AfterEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:37:19.317: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:37:19.347: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:21.380: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:23.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:25.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:27.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:29.381: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:31.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:33.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:35.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:37.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:39.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:41.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:43.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:45.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:47.380: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:49.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:51.380: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:53.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:55.380: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:57.380: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:59.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:01.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:03.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:05.380: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:07.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:09.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:11.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:13.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:15.380: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:17.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:19.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:21.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:23.381: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:25.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:27.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:29.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:31.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:33.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:35.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:37.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:39.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:41.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:43.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:45.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:47.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:49.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:51.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:53.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:55.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:57.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:59.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:01.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:03.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:05.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:07.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:09.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:11.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:13.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:15.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:17.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:19.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:21.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:23.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:25.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:27.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:29.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:31.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:33.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:35.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:37.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:39.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:41.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:43.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:45.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:47.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:49.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:51.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:53.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:55.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:57.385: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:59.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:01.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:03.382: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:05.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:07.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:09.380: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:11.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:13.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:15.379: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:17.378: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:19.377: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:19.407: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:19.408: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x0) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000c7da00, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "dns-2082" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sEndpointSlice\sshould\shave\sEndpoints\sand\sEndpointSlices\spointing\sto\sAPI\sServer\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:39:57.979: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_05.xml
[BeforeEach] [sig-network] EndpointSlice /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:36:57.580: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename endpointslice �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [BeforeEach] [sig-network] EndpointSlice /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/endpointslice.go:49 [It] should have Endpoints and EndpointSlices pointing to API Server [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 Jan 7 21:36:57.883: INFO: Endpoints addresses: [172.20.57.157] , ports: [443] Jan 7 21:36:57.883: INFO: EndpointSlices addresses: [172.20.57.157] , ports: [443] [AfterEach] [sig-network] EndpointSlice /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:36:57.883: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:36:57.914: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:36:59.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:01.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:03.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:05.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:07.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:09.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:11.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:13.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:15.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:17.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:19.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:21.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:23.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:25.948: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:27.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:29.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:31.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:33.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:35.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:37.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:39.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:41.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:43.948: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:45.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:47.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:49.949: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:51.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:53.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:55.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:57.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:37:59.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:01.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:03.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:05.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:07.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:09.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:11.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:13.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:15.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:17.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:19.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:21.950: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:23.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:25.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:27.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:29.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:31.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:33.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:35.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:37.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:39.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:41.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:43.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:45.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:47.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:49.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:51.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:53.948: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:55.949: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:57.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:59.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:01.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:03.956: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:05.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:07.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:09.948: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:11.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:13.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:15.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:17.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:19.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:21.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:23.951: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:25.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:27.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:29.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:31.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:33.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:35.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:37.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:39.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:41.949: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:43.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:45.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:47.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:49.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:51.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:53.946: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:55.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:57.947: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:57.978: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:57.979: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x243a8f9) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000766820, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "endpointslice-8274" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sEndpointSliceMirroring\sshould\smirror\sa\scustom\sEndpoints\sresource\sthrough\screate\supdate\sand\sdelete\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:40:58.502: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_10.xml
[BeforeEach] [sig-network] EndpointSliceMirroring /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:37:57.966: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename endpointslicemirroring �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [BeforeEach] [sig-network] EndpointSliceMirroring /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/endpointslicemirroring.go:39 [It] should mirror a custom Endpoints resource through create update and delete [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 �[1mSTEP�[0m: mirroring a new custom Endpoint �[1mSTEP�[0m: mirroring an update to a custom Endpoint �[1mSTEP�[0m: mirroring deletion of a custom Endpoint [AfterEach] [sig-network] EndpointSliceMirroring /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:37:58.407: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:37:58.438: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:00.474: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:02.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:04.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:06.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:08.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:10.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:12.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:14.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:16.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:18.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:20.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:22.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:24.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:26.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:28.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:30.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:32.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:34.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:36.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:38.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:40.481: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:42.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:44.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:46.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:48.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:50.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:52.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:54.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:56.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:38:58.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:00.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:02.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:04.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:06.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:08.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:10.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:12.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:14.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:16.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:18.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:20.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:22.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:24.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:26.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:28.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:30.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:32.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:34.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:36.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:38.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:40.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:42.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:44.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:46.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:48.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:50.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:52.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:54.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:56.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:39:58.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:00.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:02.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:04.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:06.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:08.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:10.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:12.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:14.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:16.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:18.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:20.473: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:22.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:24.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:26.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:28.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:30.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:32.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:34.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:36.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:38.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:40.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:42.473: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:44.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:46.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:48.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:50.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:52.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:54.472: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:56.471: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:58.470: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:58.502: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:40:58.502: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x243a8f9) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000bda4e0, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "endpointslicemirroring-218" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sHostPort\svalidates\sthat\sthere\sis\sno\sconflict\sbetween\spods\swith\ssame\shostPort\sbut\sdifferent\shostIP\sand\sprotocol\s\[LinuxOnly\]\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:29:05.916: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113from junit_01.xml
[BeforeEach] [sig-network] HostPort /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:25:45.257: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename hostport �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [BeforeEach] [sig-network] HostPort /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/hostport.go:47 [It] validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 �[1mSTEP�[0m: Trying to create a pod(pod1) with hostport 54323 and hostIP 127.0.0.1 and expect scheduled Jan 7 21:25:45.578: INFO: The status of Pod pod1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:47.610: INFO: The status of Pod pod1 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:49.611: INFO: The status of Pod pod1 is Running (Ready = true) �[1mSTEP�[0m: Trying to create another pod(pod2) with hostport 54323 but hostIP 172.20.51.5 on the node which pod1 resides and expect scheduled Jan 7 21:25:49.677: INFO: The status of Pod pod2 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:51.709: INFO: The status of Pod pod2 is Running (Ready = false) Jan 7 21:25:53.711: INFO: The status of Pod pod2 is Running (Ready = true) �[1mSTEP�[0m: Trying to create a third pod(pod3) with hostport 54323, hostIP 172.20.51.5 but use UDP protocol on the node which pod2 resides Jan 7 21:25:53.776: INFO: The status of Pod pod3 is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:55.808: INFO: The status of Pod pod3 is Running (Ready = true) Jan 7 21:25:55.872: INFO: The status of Pod e2e-host-exec is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:57.903: INFO: The status of Pod e2e-host-exec is Pending, waiting for it to be Running (with Ready = true) Jan 7 21:25:59.905: INFO: The status of Pod e2e-host-exec is Running (Ready = true) �[1mSTEP�[0m: checking connectivity from pod e2e-host-exec to serverIP: 127.0.0.1, port: 54323 Jan 7 21:25:59.937: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g --connect-timeout 5 --interface 172.20.51.5 http://127.0.0.1:54323/hostname] Namespace:hostport-7243 PodName:e2e-host-exec ContainerName:e2e-host-exec Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:25:59.937: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:25:59.937: INFO: ExecWithOptions: Clientset creation Jan 7 21:25:59.937: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/hostport-7243/pods/e2e-host-exec/exec?command=%2Fbin%2Fsh&command=-c&command=curl+-g+--connect-timeout+5+--interface+172.20.51.5+http%3A%2F%2F127.0.0.1%3A54323%2Fhostname&container=e2e-host-exec&container=e2e-host-exec&stderr=true&stdout=true %!s(MISSING)) �[1mSTEP�[0m: checking connectivity from pod e2e-host-exec to serverIP: 172.20.51.5, port: 54323 Jan 7 21:26:00.206: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g --connect-timeout 5 http://172.20.51.5:54323/hostname] Namespace:hostport-7243 PodName:e2e-host-exec ContainerName:e2e-host-exec Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:26:00.206: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:26:00.207: INFO: ExecWithOptions: Clientset creation Jan 7 21:26:00.207: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/hostport-7243/pods/e2e-host-exec/exec?command=%2Fbin%2Fsh&command=-c&command=curl+-g+--connect-timeout+5+http%3A%2F%2F172.20.51.5%3A54323%2Fhostname&container=e2e-host-exec&container=e2e-host-exec&stderr=true&stdout=true %!s(MISSING)) �[1mSTEP�[0m: checking connectivity from pod e2e-host-exec to serverIP: 172.20.51.5, port: 54323 UDP Jan 7 21:26:00.483: INFO: ExecWithOptions {Command:[/bin/sh -c nc -vuz -w 5 172.20.51.5 54323] Namespace:hostport-7243 PodName:e2e-host-exec ContainerName:e2e-host-exec Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false} Jan 7 21:26:00.483: INFO: >>> kubeConfig: /root/.kube/config Jan 7 21:26:00.484: INFO: ExecWithOptions: Clientset creation Jan 7 21:26:00.484: INFO: ExecWithOptions: execute(POST https://api.e2e-e2e-kops-grid-kubenet-u2004-k23-ko26-docker.test-cncf-aws.k8s.io/api/v1/namespaces/hostport-7243/pods/e2e-host-exec/exec?command=%2Fbin%2Fsh&command=-c&command=nc+-vuz+-w+5+172.20.51.5+54323&container=e2e-host-exec&container=e2e-host-exec&stderr=true&stdout=true %!s(MISSING)) [AfterEach] [sig-network] HostPort /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:26:05.819: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:26:05.851: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:07.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:09.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:11.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:13.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:15.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:17.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:19.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:21.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:23.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:25.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:27.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:29.886: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:31.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:33.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:35.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:37.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:39.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:41.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:43.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:45.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:47.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:49.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:51.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:53.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:55.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:57.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:26:59.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:01.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:03.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:05.886: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:07.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:09.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:11.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:13.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:15.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:17.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:19.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:21.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:23.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:25.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:27.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:29.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:31.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:33.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:35.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:37.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:39.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:41.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:43.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:45.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:47.893: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:49.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:51.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:53.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:55.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:57.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:27:59.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:01.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:03.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:05.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:07.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:09.886: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:11.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:13.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:15.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:17.886: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:19.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:21.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:23.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:25.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:27.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:29.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:31.887: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:33.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:35.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:37.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:39.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:41.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:43.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:45.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:47.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:49.885: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:51.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:53.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:55.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:57.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:28:59.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:01.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:03.883: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:05.884: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:05.915: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:05.916: FAIL: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" Full Stack Trace k8s.io/kubernetes/test/e2e.RunE2ETests(0x24c66d7) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:133 +0x697 k8s.io/kubernetes/test/e2e.TestE2E(0x243a8f9) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:136 +0x19 testing.tRunner(0xc000103d40, 0x735e880) /usr/local/go/src/testing/testing.go:1259 +0x102 created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1306 +0x35a �[1mSTEP�[0m: Destroying namespace "hostport-7243" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sIngressClass\sAPI\s\sshould\ssupport\screating\sIngressClass\sAPI\soperations\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:32:06.974: All nodes should be ready after test, Not ready nodes: ", ip-172-20-45-194.ec2.internal" /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113
[BeforeEach] [sig-network] IngressClass API /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 �[1mSTEP�[0m: Creating a kubernetes client Jan 7 21:29:06.116: INFO: >>> kubeConfig: /root/.kube/config �[1mSTEP�[0m: Building a namespace api object, basename ingressclass �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace �[1mSTEP�[0m: Waiting for kube-root-ca.crt to be provisioned in namespace [BeforeEach] [sig-network] IngressClass API /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/ingressclass.go:186 [It] should support creating IngressClass API operations [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:633 �[1mSTEP�[0m: getting /apis �[1mSTEP�[0m: getting /apis/networking.k8s.io �[1mSTEP�[0m: getting /apis/networking.k8s.iov1 �[1mSTEP�[0m: creating �[1mSTEP�[0m: getting �[1mSTEP�[0m: listing �[1mSTEP�[0m: watching Jan 7 21:29:06.614: INFO: starting watch �[1mSTEP�[0m: patching �[1mSTEP�[0m: updating Jan 7 21:29:06.710: INFO: waiting for watch events with expected annotations Jan 7 21:29:06.710: INFO: saw patched and updated annotations �[1mSTEP�[0m: deleting �[1mSTEP�[0m: deleting a collection [AfterEach] [sig-network] IngressClass API /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Jan 7 21:29:06.876: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready Jan 7 21:29:06.908: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:08.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:10.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:12.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:14.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:16.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:18.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:20.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:22.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:24.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:26.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:28.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:30.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:32.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:34.942: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:36.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:38.942: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:40.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:42.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:44.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:46.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:48.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:50.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:52.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:54.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:56.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:29:58.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:00.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:02.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:04.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:06.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:08.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:10.944: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:12.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:14.942: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:16.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:18.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:20.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:22.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:24.942: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:26.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:28.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:30.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:32.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:34.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:36.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:38.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:40.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:42.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:44.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:46.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:48.940: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule 2023-01-07 21:25:47 +0000 UTC} {node.kubernetes.io/not-ready NoExecute 2023-01-07 21:25:47 +0000 UTC}]. Failure Jan 7 21:30:50.941: INFO: Condition Ready of node ip-172-20-45-194.ec2.internal is false, but Node is tainted by NodeController with [{node.kubernetes.i