I0411 17:15:19.308148 17 e2e.go:126] Starting e2e run "00769458-9f89-470f-ad8c-a36ba20c99ad" on Ginkgo node 1 Apr 11 17:15:19.319: INFO: Enabling in-tree volume drivers Running Suite: Kubernetes e2e suite - /usr/local/bin ==================================================== Random Seed: 1712855719 - will randomize all specs Will run 6 of 7069 specs ------------------------------ [SynchronizedBeforeSuite] test/e2e/e2e.go:77 [SynchronizedBeforeSuite] TOP-LEVEL test/e2e/e2e.go:77 Apr 11 17:15:19.484: INFO: >>> kubeConfig: /home/xtesting/.kube/config Apr 11 17:15:19.487: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Apr 11 17:15:19.513: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Apr 11 17:15:19.544: INFO: 15 / 15 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Apr 11 17:15:19.544: INFO: expected 2 pod replicas in namespace 'kube-system', 2 are Running and Ready. Apr 11 17:15:19.544: INFO: Waiting up to 5m0s for all daemonsets in namespace 'kube-system' to start Apr 11 17:15:19.550: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'create-loop-devs' (0 seconds elapsed) Apr 11 17:15:19.550: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'kindnet' (0 seconds elapsed) Apr 11 17:15:19.550: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'kube-proxy' (0 seconds elapsed) Apr 11 17:15:19.550: INFO: e2e test version: v1.26.13 Apr 11 17:15:19.552: INFO: kube-apiserver version: v1.26.6 [SynchronizedBeforeSuite] TOP-LEVEL test/e2e/e2e.go:77 Apr 11 17:15:19.552: INFO: >>> kubeConfig: /home/xtesting/.kube/config Apr 11 17:15:19.558: INFO: Cluster IP family: ipv4 ------------------------------ [SynchronizedBeforeSuite] PASSED [0.073 seconds] [SynchronizedBeforeSuite] test/e2e/e2e.go:77 Begin Captured GinkgoWriter Output >> [SynchronizedBeforeSuite] TOP-LEVEL test/e2e/e2e.go:77 Apr 11 17:15:19.484: INFO: >>> kubeConfig: /home/xtesting/.kube/config Apr 11 17:15:19.487: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Apr 11 17:15:19.513: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Apr 11 17:15:19.544: INFO: 15 / 15 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Apr 11 17:15:19.544: INFO: expected 2 pod replicas in namespace 'kube-system', 2 are Running and Ready. Apr 11 17:15:19.544: INFO: Waiting up to 5m0s for all daemonsets in namespace 'kube-system' to start Apr 11 17:15:19.550: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'create-loop-devs' (0 seconds elapsed) Apr 11 17:15:19.550: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'kindnet' (0 seconds elapsed) Apr 11 17:15:19.550: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'kube-proxy' (0 seconds elapsed) Apr 11 17:15:19.550: INFO: e2e test version: v1.26.13 Apr 11 17:15:19.552: INFO: kube-apiserver version: v1.26.6 [SynchronizedBeforeSuite] TOP-LEVEL test/e2e/e2e.go:77 Apr 11 17:15:19.552: INFO: >>> kubeConfig: /home/xtesting/.kube/config Apr 11 17:15:19.558: INFO: Cluster IP family: ipv4 << End Captured GinkgoWriter Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] DisruptionController evictions: maxUnavailable deny evictions, integer => should not allow an eviction [Serial] test/e2e/apps/disruption.go:290 [BeforeEach] [sig-apps] DisruptionController set up framework | framework.go:178 STEP: Creating a kubernetes client 04/11/24 17:15:19.65 Apr 11 17:15:19.650: INFO: >>> kubeConfig: /home/xtesting/.kube/config STEP: Building a namespace api object, basename disruption 04/11/24 17:15:19.652 STEP: Waiting for a default service account to be provisioned in namespace 04/11/24 17:15:19.664 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 04/11/24 17:15:19.668 [BeforeEach] [sig-apps] DisruptionController test/e2e/framework/metrics/init/init.go:31 [BeforeEach] [sig-apps] DisruptionController test/e2e/apps/disruption.go:72 [It] evictions: maxUnavailable deny evictions, integer => should not allow an eviction [Serial] test/e2e/apps/disruption.go:290 STEP: Waiting for the pdb to be processed 04/11/24 17:15:19.682 STEP: locating a running pod 04/11/24 17:15:21.689 [AfterEach] [sig-apps] DisruptionController test/e2e/framework/node/init/init.go:32 Apr 11 17:15:21.701: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready [DeferCleanup (Each)] [sig-apps] DisruptionController test/e2e/framework/metrics/init/init.go:33 [DeferCleanup (Each)] [sig-apps] DisruptionController dump namespaces | framework.go:196 [DeferCleanup (Each)] [sig-apps] DisruptionController tear down framework | framework.go:193 STEP: Destroying namespace "disruption-9449" for this suite. 04/11/24 17:15:21.705 ------------------------------ • [2.061 seconds] [sig-apps] DisruptionController test/e2e/apps/framework.go:23 evictions: maxUnavailable deny evictions, integer => should not allow an eviction [Serial] test/e2e/apps/disruption.go:290 Begin Captured GinkgoWriter Output >> [BeforeEach] [sig-apps] DisruptionController set up framework | framework.go:178 STEP: Creating a kubernetes client 04/11/24 17:15:19.65 Apr 11 17:15:19.650: INFO: >>> kubeConfig: /home/xtesting/.kube/config STEP: Building a namespace api object, basename disruption 04/11/24 17:15:19.652 STEP: Waiting for a default service account to be provisioned in namespace 04/11/24 17:15:19.664 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 04/11/24 17:15:19.668 [BeforeEach] [sig-apps] DisruptionController test/e2e/framework/metrics/init/init.go:31 [BeforeEach] [sig-apps] DisruptionController test/e2e/apps/disruption.go:72 [It] evictions: maxUnavailable deny evictions, integer => should not allow an eviction [Serial] test/e2e/apps/disruption.go:290 STEP: Waiting for the pdb to be processed 04/11/24 17:15:19.682 STEP: locating a running pod 04/11/24 17:15:21.689 [AfterEach] [sig-apps] DisruptionController test/e2e/framework/node/init/init.go:32 Apr 11 17:15:21.701: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready [DeferCleanup (Each)] [sig-apps] DisruptionController test/e2e/framework/metrics/init/init.go:33 [DeferCleanup (Each)] [sig-apps] DisruptionController dump namespaces | framework.go:196 [DeferCleanup (Each)] [sig-apps] DisruptionController tear down framework | framework.go:193 STEP: Destroying namespace "disruption-9449" for this suite. 04/11/24 17:15:21.705 << End Captured GinkgoWriter Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Daemon set [Serial] should not update pod when spec was updated and update strategy is OnDelete test/e2e/apps/daemon_set.go:335 [BeforeEach] [sig-apps] Daemon set [Serial] set up framework | framework.go:178 STEP: Creating a kubernetes client 04/11/24 17:15:21.74 Apr 11 17:15:21.740: INFO: >>> kubeConfig: /home/xtesting/.kube/config STEP: Building a namespace api object, basename daemonsets 04/11/24 17:15:21.742 STEP: Waiting for a default service account to be provisioned in namespace 04/11/24 17:15:21.753 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 04/11/24 17:15:21.757 [BeforeEach] [sig-apps] Daemon set [Serial] test/e2e/framework/metrics/init/init.go:31 [BeforeEach] [sig-apps] Daemon set [Serial] test/e2e/apps/daemon_set.go:157 [It] should not update pod when spec was updated and update strategy is OnDelete test/e2e/apps/daemon_set.go:335 Apr 11 17:15:21.774: INFO: Creating simple daemon set daemon-set STEP: Check that daemon pods launch on every node of the cluster. 04/11/24 17:15:21.779 Apr 11 17:15:21.784: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:15:21.787: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:15:21.787: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:15:22.791: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:15:22.796: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:15:22.796: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:15:23.793: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:15:23.797: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 2 Apr 11 17:15:23.797: INFO: Number of running nodes: 2, number of available pods: 2 in daemonset daemon-set STEP: Update daemon pods image. 04/11/24 17:15:23.814 STEP: Check that daemon pods images aren't updated. 04/11/24 17:15:23.822 Apr 11 17:15:23.829: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node STEP: Check that daemon pods are still running on every node of the cluster. 04/11/24 17:15:23.829 Apr 11 17:15:23.835: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:15:23.838: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 2 Apr 11 17:15:23.839: INFO: Number of running nodes: 2, number of available pods: 2 in daemonset daemon-set [AfterEach] [sig-apps] Daemon set [Serial] test/e2e/apps/daemon_set.go:122 STEP: Deleting DaemonSet "daemon-set" 04/11/24 17:15:23.856 STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-8574, will wait for the garbage collector to delete the pods 04/11/24 17:15:23.856 Apr 11 17:15:23.915: INFO: Deleting DaemonSet.extensions daemon-set took: 4.987759ms Apr 11 17:15:24.016: INFO: Terminating DaemonSet.extensions daemon-set pods took: 101.028035ms Apr 11 17:15:26.619: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:15:26.619: INFO: Number of running nodes: 0, number of available pods: 0 in daemonset daemon-set Apr 11 17:15:26.622: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"resourceVersion":"7522353"},"items":null} Apr 11 17:15:26.626: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"resourceVersion":"7522353"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] test/e2e/framework/node/init/init.go:32 Apr 11 17:15:26.633: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] test/e2e/framework/metrics/init/init.go:33 [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] dump namespaces | framework.go:196 [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] tear down framework | framework.go:193 STEP: Destroying namespace "daemonsets-8574" for this suite. 04/11/24 17:15:26.638 ------------------------------ • [4.905 seconds] [sig-apps] Daemon set [Serial] test/e2e/apps/framework.go:23 should not update pod when spec was updated and update strategy is OnDelete test/e2e/apps/daemon_set.go:335 Begin Captured GinkgoWriter Output >> [BeforeEach] [sig-apps] Daemon set [Serial] set up framework | framework.go:178 STEP: Creating a kubernetes client 04/11/24 17:15:21.74 Apr 11 17:15:21.740: INFO: >>> kubeConfig: /home/xtesting/.kube/config STEP: Building a namespace api object, basename daemonsets 04/11/24 17:15:21.742 STEP: Waiting for a default service account to be provisioned in namespace 04/11/24 17:15:21.753 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 04/11/24 17:15:21.757 [BeforeEach] [sig-apps] Daemon set [Serial] test/e2e/framework/metrics/init/init.go:31 [BeforeEach] [sig-apps] Daemon set [Serial] test/e2e/apps/daemon_set.go:157 [It] should not update pod when spec was updated and update strategy is OnDelete test/e2e/apps/daemon_set.go:335 Apr 11 17:15:21.774: INFO: Creating simple daemon set daemon-set STEP: Check that daemon pods launch on every node of the cluster. 04/11/24 17:15:21.779 Apr 11 17:15:21.784: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:15:21.787: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:15:21.787: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:15:22.791: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:15:22.796: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:15:22.796: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:15:23.793: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:15:23.797: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 2 Apr 11 17:15:23.797: INFO: Number of running nodes: 2, number of available pods: 2 in daemonset daemon-set STEP: Update daemon pods image. 04/11/24 17:15:23.814 STEP: Check that daemon pods images aren't updated. 04/11/24 17:15:23.822 Apr 11 17:15:23.829: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node STEP: Check that daemon pods are still running on every node of the cluster. 04/11/24 17:15:23.829 Apr 11 17:15:23.835: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:15:23.838: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 2 Apr 11 17:15:23.839: INFO: Number of running nodes: 2, number of available pods: 2 in daemonset daemon-set [AfterEach] [sig-apps] Daemon set [Serial] test/e2e/apps/daemon_set.go:122 STEP: Deleting DaemonSet "daemon-set" 04/11/24 17:15:23.856 STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-8574, will wait for the garbage collector to delete the pods 04/11/24 17:15:23.856 Apr 11 17:15:23.915: INFO: Deleting DaemonSet.extensions daemon-set took: 4.987759ms Apr 11 17:15:24.016: INFO: Terminating DaemonSet.extensions daemon-set pods took: 101.028035ms Apr 11 17:15:26.619: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:15:26.619: INFO: Number of running nodes: 0, number of available pods: 0 in daemonset daemon-set Apr 11 17:15:26.622: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"resourceVersion":"7522353"},"items":null} Apr 11 17:15:26.626: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"resourceVersion":"7522353"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] test/e2e/framework/node/init/init.go:32 Apr 11 17:15:26.633: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] test/e2e/framework/metrics/init/init.go:33 [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] dump namespaces | framework.go:196 [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] tear down framework | framework.go:193 STEP: Destroying namespace "daemonsets-8574" for this suite. 04/11/24 17:15:26.638 << End Captured GinkgoWriter Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Job should run a job to completion with CPU requests [Serial] test/e2e/apps/job.go:581 [BeforeEach] [sig-apps] Job set up framework | framework.go:178 STEP: Creating a kubernetes client 04/11/24 17:15:26.783 Apr 11 17:15:26.783: INFO: >>> kubeConfig: /home/xtesting/.kube/config STEP: Building a namespace api object, basename job 04/11/24 17:15:26.784 STEP: Waiting for a default service account to be provisioned in namespace 04/11/24 17:15:26.795 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 04/11/24 17:15:26.799 [BeforeEach] [sig-apps] Job test/e2e/framework/metrics/init/init.go:31 [It] should run a job to completion with CPU requests [Serial] test/e2e/apps/job.go:581 STEP: Creating a job that with CPU requests 04/11/24 17:15:26.804 STEP: Trying to launch a pod without a label to get a node which can launch it. 04/11/24 17:15:26.804 Apr 11 17:15:26.812: INFO: Waiting up to 1m0s for pod "without-label" in namespace "job-3319" to be "running" Apr 11 17:15:26.816: INFO: Pod "without-label": Phase="Pending", Reason="", readiness=false. Elapsed: 3.454517ms Apr 11 17:15:28.820: INFO: Pod "without-label": Phase="Running", Reason="", readiness=true. Elapsed: 2.00787623s Apr 11 17:15:28.820: INFO: Pod "without-label" satisfied condition "running" STEP: Explicitly delete pod here to free the resource it takes. 04/11/24 17:15:28.823 STEP: Creating a job 04/11/24 17:15:28.837 Apr 11 17:15:28.837: INFO: Creating job "all-succeed" with a node hostname selector "v126-worker2" with cpu request "17" STEP: Ensuring job reaches completions 04/11/24 17:15:28.843 STEP: Ensuring pods for job exist 04/11/24 17:18:18.847 [AfterEach] [sig-apps] Job test/e2e/framework/node/init/init.go:32 Apr 11 17:18:18.871: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready [DeferCleanup (Each)] [sig-apps] Job test/e2e/framework/metrics/init/init.go:33 [DeferCleanup (Each)] [sig-apps] Job dump namespaces | framework.go:196 [DeferCleanup (Each)] [sig-apps] Job tear down framework | framework.go:193 STEP: Destroying namespace "job-3319" for this suite. 04/11/24 17:18:18.876 ------------------------------ • [SLOW TEST] [172.099 seconds] [sig-apps] Job test/e2e/apps/framework.go:23 should run a job to completion with CPU requests [Serial] test/e2e/apps/job.go:581 Begin Captured GinkgoWriter Output >> [BeforeEach] [sig-apps] Job set up framework | framework.go:178 STEP: Creating a kubernetes client 04/11/24 17:15:26.783 Apr 11 17:15:26.783: INFO: >>> kubeConfig: /home/xtesting/.kube/config STEP: Building a namespace api object, basename job 04/11/24 17:15:26.784 STEP: Waiting for a default service account to be provisioned in namespace 04/11/24 17:15:26.795 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 04/11/24 17:15:26.799 [BeforeEach] [sig-apps] Job test/e2e/framework/metrics/init/init.go:31 [It] should run a job to completion with CPU requests [Serial] test/e2e/apps/job.go:581 STEP: Creating a job that with CPU requests 04/11/24 17:15:26.804 STEP: Trying to launch a pod without a label to get a node which can launch it. 04/11/24 17:15:26.804 Apr 11 17:15:26.812: INFO: Waiting up to 1m0s for pod "without-label" in namespace "job-3319" to be "running" Apr 11 17:15:26.816: INFO: Pod "without-label": Phase="Pending", Reason="", readiness=false. Elapsed: 3.454517ms Apr 11 17:15:28.820: INFO: Pod "without-label": Phase="Running", Reason="", readiness=true. Elapsed: 2.00787623s Apr 11 17:15:28.820: INFO: Pod "without-label" satisfied condition "running" STEP: Explicitly delete pod here to free the resource it takes. 04/11/24 17:15:28.823 STEP: Creating a job 04/11/24 17:15:28.837 Apr 11 17:15:28.837: INFO: Creating job "all-succeed" with a node hostname selector "v126-worker2" with cpu request "17" STEP: Ensuring job reaches completions 04/11/24 17:15:28.843 STEP: Ensuring pods for job exist 04/11/24 17:18:18.847 [AfterEach] [sig-apps] Job test/e2e/framework/node/init/init.go:32 Apr 11 17:18:18.871: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready [DeferCleanup (Each)] [sig-apps] Job test/e2e/framework/metrics/init/init.go:33 [DeferCleanup (Each)] [sig-apps] Job dump namespaces | framework.go:196 [DeferCleanup (Each)] [sig-apps] Job tear down framework | framework.go:193 STEP: Destroying namespace "job-3319" for this suite. 04/11/24 17:18:18.876 << End Captured GinkgoWriter Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] DisruptionController evictions: too few pods, replicaSet, percentage => should not allow an eviction [Serial] test/e2e/apps/disruption.go:290 [BeforeEach] [sig-apps] DisruptionController set up framework | framework.go:178 STEP: Creating a kubernetes client 04/11/24 17:18:18.951 Apr 11 17:18:18.951: INFO: >>> kubeConfig: /home/xtesting/.kube/config STEP: Building a namespace api object, basename disruption 04/11/24 17:18:18.953 STEP: Waiting for a default service account to be provisioned in namespace 04/11/24 17:18:18.964 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 04/11/24 17:18:18.968 [BeforeEach] [sig-apps] DisruptionController test/e2e/framework/metrics/init/init.go:31 [BeforeEach] [sig-apps] DisruptionController test/e2e/apps/disruption.go:72 [It] evictions: too few pods, replicaSet, percentage => should not allow an eviction [Serial] test/e2e/apps/disruption.go:290 STEP: Waiting for the pdb to be processed 04/11/24 17:18:18.983 STEP: locating a running pod 04/11/24 17:18:20.99 [AfterEach] [sig-apps] DisruptionController test/e2e/framework/node/init/init.go:32 Apr 11 17:18:21.001: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready [DeferCleanup (Each)] [sig-apps] DisruptionController test/e2e/framework/metrics/init/init.go:33 [DeferCleanup (Each)] [sig-apps] DisruptionController dump namespaces | framework.go:196 [DeferCleanup (Each)] [sig-apps] DisruptionController tear down framework | framework.go:193 STEP: Destroying namespace "disruption-2070" for this suite. 04/11/24 17:18:21.006 ------------------------------ • [2.060 seconds] [sig-apps] DisruptionController test/e2e/apps/framework.go:23 evictions: too few pods, replicaSet, percentage => should not allow an eviction [Serial] test/e2e/apps/disruption.go:290 Begin Captured GinkgoWriter Output >> [BeforeEach] [sig-apps] DisruptionController set up framework | framework.go:178 STEP: Creating a kubernetes client 04/11/24 17:18:18.951 Apr 11 17:18:18.951: INFO: >>> kubeConfig: /home/xtesting/.kube/config STEP: Building a namespace api object, basename disruption 04/11/24 17:18:18.953 STEP: Waiting for a default service account to be provisioned in namespace 04/11/24 17:18:18.964 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 04/11/24 17:18:18.968 [BeforeEach] [sig-apps] DisruptionController test/e2e/framework/metrics/init/init.go:31 [BeforeEach] [sig-apps] DisruptionController test/e2e/apps/disruption.go:72 [It] evictions: too few pods, replicaSet, percentage => should not allow an eviction [Serial] test/e2e/apps/disruption.go:290 STEP: Waiting for the pdb to be processed 04/11/24 17:18:18.983 STEP: locating a running pod 04/11/24 17:18:20.99 [AfterEach] [sig-apps] DisruptionController test/e2e/framework/node/init/init.go:32 Apr 11 17:18:21.001: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready [DeferCleanup (Each)] [sig-apps] DisruptionController test/e2e/framework/metrics/init/init.go:33 [DeferCleanup (Each)] [sig-apps] DisruptionController dump namespaces | framework.go:196 [DeferCleanup (Each)] [sig-apps] DisruptionController tear down framework | framework.go:193 STEP: Destroying namespace "disruption-2070" for this suite. 04/11/24 17:18:21.006 << End Captured GinkgoWriter Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Daemon set [Serial] should run and stop complex daemon with node affinity test/e2e/apps/daemon_set.go:252 [BeforeEach] [sig-apps] Daemon set [Serial] set up framework | framework.go:178 STEP: Creating a kubernetes client 04/11/24 17:18:21.101 Apr 11 17:18:21.101: INFO: >>> kubeConfig: /home/xtesting/.kube/config STEP: Building a namespace api object, basename daemonsets 04/11/24 17:18:21.103 STEP: Waiting for a default service account to be provisioned in namespace 04/11/24 17:18:21.113 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 04/11/24 17:18:21.117 [BeforeEach] [sig-apps] Daemon set [Serial] test/e2e/framework/metrics/init/init.go:31 [BeforeEach] [sig-apps] Daemon set [Serial] test/e2e/apps/daemon_set.go:157 [It] should run and stop complex daemon with node affinity test/e2e/apps/daemon_set.go:252 Apr 11 17:18:21.134: INFO: Creating daemon "daemon-set" with a node affinity STEP: Initially, daemon pods should not be running on any nodes. 04/11/24 17:18:21.14 Apr 11 17:18:21.143: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:21.143: INFO: Number of running nodes: 0, number of available pods: 0 in daemonset daemon-set STEP: Change node label to blue, check that daemon pod is launched. 04/11/24 17:18:21.143 Apr 11 17:18:21.164: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:21.164: INFO: Node v126-worker2 is running 0 daemon pod, expected 1 Apr 11 17:18:22.168: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:22.168: INFO: Node v126-worker2 is running 0 daemon pod, expected 1 Apr 11 17:18:23.168: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 1 Apr 11 17:18:23.168: INFO: Number of running nodes: 1, number of available pods: 1 in daemonset daemon-set STEP: Remove the node label and wait for daemons to be unscheduled 04/11/24 17:18:23.172 Apr 11 17:18:23.191: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 1 Apr 11 17:18:23.191: INFO: Number of running nodes: 0, number of available pods: 1 in daemonset daemon-set Apr 11 17:18:24.196: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:24.196: INFO: Number of running nodes: 0, number of available pods: 0 in daemonset daemon-set [AfterEach] [sig-apps] Daemon set [Serial] test/e2e/apps/daemon_set.go:122 STEP: Deleting DaemonSet "daemon-set" 04/11/24 17:18:24.199 STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-5353, will wait for the garbage collector to delete the pods 04/11/24 17:18:24.2 Apr 11 17:18:24.258: INFO: Deleting DaemonSet.extensions daemon-set took: 4.971689ms Apr 11 17:18:24.258: INFO: Terminating DaemonSet.extensions daemon-set pods took: 32.448µs Apr 11 17:18:25.962: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:25.962: INFO: Number of running nodes: 0, number of available pods: 0 in daemonset daemon-set Apr 11 17:18:25.966: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"resourceVersion":"7525270"},"items":null} Apr 11 17:18:25.969: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"resourceVersion":"7525272"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] test/e2e/framework/node/init/init.go:32 Apr 11 17:18:25.976: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] test/e2e/framework/metrics/init/init.go:33 [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] dump namespaces | framework.go:196 [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] tear down framework | framework.go:193 STEP: Destroying namespace "daemonsets-5353" for this suite. 04/11/24 17:18:25.98 ------------------------------ • [4.883 seconds] [sig-apps] Daemon set [Serial] test/e2e/apps/framework.go:23 should run and stop complex daemon with node affinity test/e2e/apps/daemon_set.go:252 Begin Captured GinkgoWriter Output >> [BeforeEach] [sig-apps] Daemon set [Serial] set up framework | framework.go:178 STEP: Creating a kubernetes client 04/11/24 17:18:21.101 Apr 11 17:18:21.101: INFO: >>> kubeConfig: /home/xtesting/.kube/config STEP: Building a namespace api object, basename daemonsets 04/11/24 17:18:21.103 STEP: Waiting for a default service account to be provisioned in namespace 04/11/24 17:18:21.113 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 04/11/24 17:18:21.117 [BeforeEach] [sig-apps] Daemon set [Serial] test/e2e/framework/metrics/init/init.go:31 [BeforeEach] [sig-apps] Daemon set [Serial] test/e2e/apps/daemon_set.go:157 [It] should run and stop complex daemon with node affinity test/e2e/apps/daemon_set.go:252 Apr 11 17:18:21.134: INFO: Creating daemon "daemon-set" with a node affinity STEP: Initially, daemon pods should not be running on any nodes. 04/11/24 17:18:21.14 Apr 11 17:18:21.143: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:21.143: INFO: Number of running nodes: 0, number of available pods: 0 in daemonset daemon-set STEP: Change node label to blue, check that daemon pod is launched. 04/11/24 17:18:21.143 Apr 11 17:18:21.164: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:21.164: INFO: Node v126-worker2 is running 0 daemon pod, expected 1 Apr 11 17:18:22.168: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:22.168: INFO: Node v126-worker2 is running 0 daemon pod, expected 1 Apr 11 17:18:23.168: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 1 Apr 11 17:18:23.168: INFO: Number of running nodes: 1, number of available pods: 1 in daemonset daemon-set STEP: Remove the node label and wait for daemons to be unscheduled 04/11/24 17:18:23.172 Apr 11 17:18:23.191: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 1 Apr 11 17:18:23.191: INFO: Number of running nodes: 0, number of available pods: 1 in daemonset daemon-set Apr 11 17:18:24.196: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:24.196: INFO: Number of running nodes: 0, number of available pods: 0 in daemonset daemon-set [AfterEach] [sig-apps] Daemon set [Serial] test/e2e/apps/daemon_set.go:122 STEP: Deleting DaemonSet "daemon-set" 04/11/24 17:18:24.199 STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-5353, will wait for the garbage collector to delete the pods 04/11/24 17:18:24.2 Apr 11 17:18:24.258: INFO: Deleting DaemonSet.extensions daemon-set took: 4.971689ms Apr 11 17:18:24.258: INFO: Terminating DaemonSet.extensions daemon-set pods took: 32.448µs Apr 11 17:18:25.962: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:25.962: INFO: Number of running nodes: 0, number of available pods: 0 in daemonset daemon-set Apr 11 17:18:25.966: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"resourceVersion":"7525270"},"items":null} Apr 11 17:18:25.969: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"resourceVersion":"7525272"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] test/e2e/framework/node/init/init.go:32 Apr 11 17:18:25.976: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] test/e2e/framework/metrics/init/init.go:33 [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] dump namespaces | framework.go:196 [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] tear down framework | framework.go:193 STEP: Destroying namespace "daemonsets-5353" for this suite. 04/11/24 17:18:25.98 << End Captured GinkgoWriter Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Daemon set [Serial] should surge pods onto nodes when spec was updated and update strategy is RollingUpdate test/e2e/apps/daemon_set.go:515 [BeforeEach] [sig-apps] Daemon set [Serial] set up framework | framework.go:178 STEP: Creating a kubernetes client 04/11/24 17:18:26.04 Apr 11 17:18:26.040: INFO: >>> kubeConfig: /home/xtesting/.kube/config STEP: Building a namespace api object, basename daemonsets 04/11/24 17:18:26.042 STEP: Waiting for a default service account to be provisioned in namespace 04/11/24 17:18:26.052 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 04/11/24 17:18:26.056 [BeforeEach] [sig-apps] Daemon set [Serial] test/e2e/framework/metrics/init/init.go:31 [BeforeEach] [sig-apps] Daemon set [Serial] test/e2e/apps/daemon_set.go:157 [It] should surge pods onto nodes when spec was updated and update strategy is RollingUpdate test/e2e/apps/daemon_set.go:515 Apr 11 17:18:26.076: INFO: Creating surge daemon set daemon-set STEP: Check that daemon pods launch on every node of the cluster. 04/11/24 17:18:26.081 Apr 11 17:18:26.086: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:26.089: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:26.089: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:27.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:27.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:27.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:28.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:28.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:28.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:29.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:29.099: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:29.099: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:30.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:30.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:30.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:31.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:31.097: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:31.097: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:32.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:32.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:32.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:33.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:33.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:33.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:34.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:34.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:34.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:35.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:35.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:35.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:36.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:36.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:36.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:37.095: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:37.099: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:37.099: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:38.098: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:38.103: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:38.103: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:39.095: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:39.099: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:39.099: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:40.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:40.099: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:40.099: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:41.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:41.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:41.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:42.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:42.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:42.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:43.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:43.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:43.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:44.095: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:44.099: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:44.099: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:45.095: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:45.099: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 2 Apr 11 17:18:45.099: INFO: Number of running nodes: 2, number of available pods: 2 in daemonset daemon-set STEP: Update daemon pods environment var 04/11/24 17:18:45.114 STEP: Check that daemon pods surge and invariants are preserved during that rollout 04/11/24 17:18:45.127 Apr 11 17:18:45.131: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:45.131: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:45.131: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:45.135: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:46.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:46.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:46.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:46.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:46.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:47.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:47.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:47.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:47.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:47.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:48.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:48.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:48.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:48.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:48.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:49.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:49.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:49.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:49.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:49.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:50.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:50.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:50.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:50.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:50.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:51.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:51.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:51.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:51.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:51.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:52.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:52.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:52.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:52.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:52.144: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:53.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:53.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:53.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:53.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:53.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:54.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:54.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:54.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:54.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:54.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:55.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:55.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:55.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:55.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:55.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:56.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:56.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:56.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:56.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:56.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:57.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:57.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:57.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:57.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:57.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:58.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:58.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:58.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:58.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:58.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:59.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:59.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:59.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:59.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:59.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:00.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:00.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:19:00.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:19:00.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:19:00.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:01.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:01.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:19:01.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:19:01.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:19:01.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:02.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:02.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:19:02.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:19:02.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:19:02.144: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:03.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:03.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:19:03.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:19:03.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:19:03.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:04.139: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:04.139: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:19:04.139: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:04.139: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:19:04.143: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:04.143: INFO: Running '/usr/local/bin/kubectl --server=https://172.30.13.90:35339 --kubeconfig=/home/xtesting/.kube/config --namespace=daemonsets-5028 exec -c app daemon-set-nvzlv -- /bin/sh -ec echo 0 > /var/tmp/ready' Apr 11 17:19:04.396: INFO: stderr: "" Apr 11 17:19:04.396: INFO: stdout: "" Apr 11 17:19:04.396: INFO: Marked old pod daemon-set-nvzlv as unready Apr 11 17:19:05.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:05.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:19:05.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:05.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:19:05.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:06.139: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:06.139: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:06.139: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:06.139: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:06.139: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:06.143: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:07.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:07.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:07.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:07.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:07.140: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:07.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:08.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:08.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:08.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:08.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:08.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:08.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:09.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:09.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:09.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:09.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:09.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:09.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:10.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:10.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:10.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:10.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:10.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:10.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:11.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:11.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:11.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:11.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:11.140: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:11.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:12.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:12.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:12.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:12.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:12.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:12.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:13.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:13.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:13.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:13.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:13.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:13.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:14.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:14.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:14.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:14.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:14.140: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:14.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:15.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:15.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:15.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:15.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:15.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:15.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:16.142: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:16.142: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:16.142: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:16.142: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:16.142: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:16.148: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:17.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:17.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:17.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:17.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:17.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:17.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:18.142: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:18.142: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:18.142: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:18.142: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:18.142: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:18.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:19.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:19.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:19.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:19.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:19.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:19.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:20.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:20.142: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:20.142: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:20.142: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:20.142: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:20.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:21.142: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:21.142: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:21.142: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:21.142: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:21.142: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:21.147: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:22.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:22.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:22.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:22.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:22.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:23.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:23.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:23.140: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:23.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:24.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:24.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:24.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false true Apr 11 17:19:24.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node STEP: Check that daemon pods are still running on every node of the cluster. 04/11/24 17:19:24.146 Apr 11 17:19:24.151: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:24.155: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 2 Apr 11 17:19:24.155: INFO: Number of running nodes: 2, number of available pods: 2 in daemonset daemon-set [AfterEach] [sig-apps] Daemon set [Serial] test/e2e/apps/daemon_set.go:122 STEP: Deleting DaemonSet "daemon-set" 04/11/24 17:19:24.172 STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-5028, will wait for the garbage collector to delete the pods 04/11/24 17:19:24.172 Apr 11 17:19:24.231: INFO: Deleting DaemonSet.extensions daemon-set took: 4.9185ms Apr 11 17:19:24.332: INFO: Terminating DaemonSet.extensions daemon-set pods took: 100.356958ms Apr 11 17:19:40.635: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:19:40.635: INFO: Number of running nodes: 0, number of available pods: 0 in daemonset daemon-set Apr 11 17:19:40.638: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"resourceVersion":"7525678"},"items":null} Apr 11 17:19:40.641: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"resourceVersion":"7525678"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] test/e2e/framework/node/init/init.go:32 Apr 11 17:19:40.649: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] test/e2e/framework/metrics/init/init.go:33 [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] dump namespaces | framework.go:196 [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] tear down framework | framework.go:193 STEP: Destroying namespace "daemonsets-5028" for this suite. 04/11/24 17:19:40.654 ------------------------------ • [SLOW TEST] [74.618 seconds] [sig-apps] Daemon set [Serial] test/e2e/apps/framework.go:23 should surge pods onto nodes when spec was updated and update strategy is RollingUpdate test/e2e/apps/daemon_set.go:515 Begin Captured GinkgoWriter Output >> [BeforeEach] [sig-apps] Daemon set [Serial] set up framework | framework.go:178 STEP: Creating a kubernetes client 04/11/24 17:18:26.04 Apr 11 17:18:26.040: INFO: >>> kubeConfig: /home/xtesting/.kube/config STEP: Building a namespace api object, basename daemonsets 04/11/24 17:18:26.042 STEP: Waiting for a default service account to be provisioned in namespace 04/11/24 17:18:26.052 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 04/11/24 17:18:26.056 [BeforeEach] [sig-apps] Daemon set [Serial] test/e2e/framework/metrics/init/init.go:31 [BeforeEach] [sig-apps] Daemon set [Serial] test/e2e/apps/daemon_set.go:157 [It] should surge pods onto nodes when spec was updated and update strategy is RollingUpdate test/e2e/apps/daemon_set.go:515 Apr 11 17:18:26.076: INFO: Creating surge daemon set daemon-set STEP: Check that daemon pods launch on every node of the cluster. 04/11/24 17:18:26.081 Apr 11 17:18:26.086: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:26.089: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:26.089: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:27.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:27.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:27.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:28.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:28.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:28.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:29.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:29.099: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:29.099: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:30.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:30.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:30.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:31.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:31.097: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:31.097: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:32.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:32.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:32.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:33.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:33.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:33.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:34.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:34.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:34.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:35.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:35.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:35.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:36.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:36.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:36.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:37.095: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:37.099: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:37.099: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:38.098: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:38.103: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:38.103: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:39.095: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:39.099: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:39.099: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:40.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:40.099: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:40.099: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:41.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:41.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:41.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:42.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:42.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:42.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:43.094: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:43.098: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:43.098: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:44.095: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:44.099: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:18:44.099: INFO: Node v126-worker is running 0 daemon pod, expected 1 Apr 11 17:18:45.095: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:45.099: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 2 Apr 11 17:18:45.099: INFO: Number of running nodes: 2, number of available pods: 2 in daemonset daemon-set STEP: Update daemon pods environment var 04/11/24 17:18:45.114 STEP: Check that daemon pods surge and invariants are preserved during that rollout 04/11/24 17:18:45.127 Apr 11 17:18:45.131: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:45.131: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:45.131: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:45.135: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:46.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:46.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:46.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:46.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:46.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:47.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:47.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:47.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:47.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:47.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:48.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:48.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:48.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:48.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:48.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:49.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:49.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:49.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:49.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:49.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:50.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:50.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:50.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:50.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:50.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:51.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:51.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:51.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:51.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:51.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:52.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:52.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:52.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:52.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:52.144: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:53.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:53.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:53.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:53.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:53.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:54.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:54.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:54.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:54.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:54.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:55.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:55.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:55.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:55.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:55.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:56.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:56.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:56.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:56.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:56.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:57.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:57.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:57.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:57.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:57.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:58.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:58.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:58.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:58.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:58.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:18:59.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:18:59.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:18:59.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:18:59.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:18:59.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:00.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:00.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:19:00.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:19:00.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:19:00.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:01.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:01.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:19:01.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:19:01.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:19:01.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:02.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:02.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:19:02.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:19:02.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:19:02.144: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:03.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:03.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:19:03.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false false Apr 11 17:19:03.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:19:03.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:04.139: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:04.139: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:19:04.139: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:04.139: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:19:04.143: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:04.143: INFO: Running '/usr/local/bin/kubectl --server=https://172.30.13.90:35339 --kubeconfig=/home/xtesting/.kube/config --namespace=daemonsets-5028 exec -c app daemon-set-nvzlv -- /bin/sh -ec echo 0 > /var/tmp/ready' Apr 11 17:19:04.396: INFO: stderr: "" Apr 11 17:19:04.396: INFO: stdout: "" Apr 11 17:19:04.396: INFO: Marked old pod daemon-set-nvzlv as unready Apr 11 17:19:05.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:05.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 false true Apr 11 17:19:05.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:05.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b false true Apr 11 17:19:05.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:06.139: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:06.139: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:06.139: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:06.139: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:06.139: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:06.143: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:07.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:07.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:07.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:07.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:07.140: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:07.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:08.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:08.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:08.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:08.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:08.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:08.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:09.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:09.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:09.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:09.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:09.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:09.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:10.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:10.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:10.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:10.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:10.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:10.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:11.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:11.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:11.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:11.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:11.140: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:11.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:12.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:12.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:12.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:12.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:12.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:12.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:13.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:13.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:13.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:13.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:13.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:13.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:14.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:14.140: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:14.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:14.140: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:14.140: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:14.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:15.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:15.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:15.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:15.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:15.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:15.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:16.142: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:16.142: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:16.142: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:16.142: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:16.142: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:16.148: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:17.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:17.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:17.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:17.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:17.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:17.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:18.142: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:18.142: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:18.142: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:18.142: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:18.142: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:18.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:19.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:19.141: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:19.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:19.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:19.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:19.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:20.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:20.142: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:20.142: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:20.142: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:20.142: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:20.146: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:21.142: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:21.142: INFO: v126-worker 1 daemon-set-6zb67 ad2e992c-b07c-4437-9d63-fbdaf90e26b4 true true Apr 11 17:19:21.142: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:21.142: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:21.142: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:21.147: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:22.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:22.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:22.141: INFO: v126-worker2 1 daemon-set-nvzlv 0521fb1d-2ad2-49ab-834a-94d4b100de9b true false Apr 11 17:19:22.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:22.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:23.140: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:23.140: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:23.140: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false false Apr 11 17:19:23.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:24.141: INFO: Node Version Name UID Deleted Ready Apr 11 17:19:24.141: INFO: v126-worker 2 daemon-set-rs4kv 67a574eb-f776-41ac-a9b3-13ddaa09c1a8 false true Apr 11 17:19:24.141: INFO: v126-worker2 2 daemon-set-p5mfs 1c7fc317-f8f6-41be-a65e-b161768f8e32 false true Apr 11 17:19:24.145: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node STEP: Check that daemon pods are still running on every node of the cluster. 04/11/24 17:19:24.146 Apr 11 17:19:24.151: INFO: DaemonSet pods can't tolerate node v126-control-plane with taints [{Key:node-role.kubernetes.io/control-plane Value: Effect:NoSchedule TimeAdded:}], skip checking this node Apr 11 17:19:24.155: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 2 Apr 11 17:19:24.155: INFO: Number of running nodes: 2, number of available pods: 2 in daemonset daemon-set [AfterEach] [sig-apps] Daemon set [Serial] test/e2e/apps/daemon_set.go:122 STEP: Deleting DaemonSet "daemon-set" 04/11/24 17:19:24.172 STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-5028, will wait for the garbage collector to delete the pods 04/11/24 17:19:24.172 Apr 11 17:19:24.231: INFO: Deleting DaemonSet.extensions daemon-set took: 4.9185ms Apr 11 17:19:24.332: INFO: Terminating DaemonSet.extensions daemon-set pods took: 100.356958ms Apr 11 17:19:40.635: INFO: Number of nodes with available pods controlled by daemonset daemon-set: 0 Apr 11 17:19:40.635: INFO: Number of running nodes: 0, number of available pods: 0 in daemonset daemon-set Apr 11 17:19:40.638: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"resourceVersion":"7525678"},"items":null} Apr 11 17:19:40.641: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"resourceVersion":"7525678"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] test/e2e/framework/node/init/init.go:32 Apr 11 17:19:40.649: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] test/e2e/framework/metrics/init/init.go:33 [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] dump namespaces | framework.go:196 [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] tear down framework | framework.go:193 STEP: Destroying namespace "daemonsets-5028" for this suite. 04/11/24 17:19:40.654 << End Captured GinkgoWriter Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [SynchronizedAfterSuite] test/e2e/e2e.go:88 [SynchronizedAfterSuite] TOP-LEVEL test/e2e/e2e.go:88 [SynchronizedAfterSuite] TOP-LEVEL test/e2e/e2e.go:88 Apr 11 17:19:40.686: INFO: Running AfterSuite actions on node 1 Apr 11 17:19:40.687: INFO: Skipping dumping logs from cluster ------------------------------ [SynchronizedAfterSuite] PASSED [0.000 seconds] [SynchronizedAfterSuite] test/e2e/e2e.go:88 Begin Captured GinkgoWriter Output >> [SynchronizedAfterSuite] TOP-LEVEL test/e2e/e2e.go:88 [SynchronizedAfterSuite] TOP-LEVEL test/e2e/e2e.go:88 Apr 11 17:19:40.686: INFO: Running AfterSuite actions on node 1 Apr 11 17:19:40.687: INFO: Skipping dumping logs from cluster << End Captured GinkgoWriter Output ------------------------------ [ReportAfterSuite] Kubernetes e2e suite report test/e2e/e2e_test.go:153 [ReportAfterSuite] TOP-LEVEL test/e2e/e2e_test.go:153 ------------------------------ [ReportAfterSuite] PASSED [0.000 seconds] [ReportAfterSuite] Kubernetes e2e suite report test/e2e/e2e_test.go:153 Begin Captured GinkgoWriter Output >> [ReportAfterSuite] TOP-LEVEL test/e2e/e2e_test.go:153 << End Captured GinkgoWriter Output ------------------------------ [ReportAfterSuite] Kubernetes e2e JUnit report test/e2e/framework/test_context.go:529 [ReportAfterSuite] TOP-LEVEL test/e2e/framework/test_context.go:529 ------------------------------ [ReportAfterSuite] PASSED [0.220 seconds] [ReportAfterSuite] Kubernetes e2e JUnit report test/e2e/framework/test_context.go:529 Begin Captured GinkgoWriter Output >> [ReportAfterSuite] TOP-LEVEL test/e2e/framework/test_context.go:529 << End Captured GinkgoWriter Output ------------------------------ Ran 6 of 7069 Specs in 261.203 seconds SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 7063 Skipped PASS Ginkgo ran 1 suite in 4m21.729759443s Test Suite Passed