I1113 01:43:14.199520 23 e2e.go:129] Starting e2e run "811d99fc-be43-4d68-a640-0821daf6c1e8" on Ginkgo node 1 {"msg":"Test Suite starting","total":17,"completed":0,"skipped":0,"failed":0} Running Suite: Kubernetes e2e suite =================================== Random Seed: 1636767792 - Will randomize all specs Will run 17 of 5770 specs Nov 13 01:43:14.262: INFO: >>> kubeConfig: /root/.kube/config Nov 13 01:43:14.267: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Nov 13 01:43:14.296: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Nov 13 01:43:14.365: INFO: The status of Pod cmk-init-discover-node1-vkj2s is Succeeded, skipping waiting Nov 13 01:43:14.365: INFO: The status of Pod cmk-init-discover-node2-5f4hp is Succeeded, skipping waiting Nov 13 01:43:14.365: INFO: 40 / 42 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Nov 13 01:43:14.365: INFO: expected 8 pod replicas in namespace 'kube-system', 8 are Running and Ready. Nov 13 01:43:14.365: INFO: Waiting up to 5m0s for all daemonsets in namespace 'kube-system' to start Nov 13 01:43:14.382: INFO: 2 / 2 pods ready in namespace 'kube-system' in daemonset 'cmk' (0 seconds elapsed) Nov 13 01:43:14.382: INFO: 5 / 5 pods ready in namespace 'kube-system' in daemonset 'kube-flannel' (0 seconds elapsed) Nov 13 01:43:14.382: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'kube-flannel-ds-arm' (0 seconds elapsed) Nov 13 01:43:14.382: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'kube-flannel-ds-arm64' (0 seconds elapsed) Nov 13 01:43:14.382: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'kube-flannel-ds-ppc64le' (0 seconds elapsed) Nov 13 01:43:14.382: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'kube-flannel-ds-s390x' (0 seconds elapsed) Nov 13 01:43:14.382: INFO: 5 / 5 pods ready in namespace 'kube-system' in daemonset 'kube-multus-ds-amd64' (0 seconds elapsed) Nov 13 01:43:14.382: INFO: 5 / 5 pods ready in namespace 'kube-system' in daemonset 'kube-proxy' (0 seconds elapsed) Nov 13 01:43:14.382: INFO: 2 / 2 pods ready in namespace 'kube-system' in daemonset 'node-feature-discovery-worker' (0 seconds elapsed) Nov 13 01:43:14.382: INFO: 2 / 2 pods ready in namespace 'kube-system' in daemonset 'sriov-net-dp-kube-sriov-device-plugin-amd64' (0 seconds elapsed) Nov 13 01:43:14.382: INFO: e2e test version: v1.21.5 Nov 13 01:43:14.383: INFO: kube-apiserver version: v1.21.1 Nov 13 01:43:14.384: INFO: >>> kubeConfig: /root/.kube/config Nov 13 01:43:14.390: INFO: Cluster IP family: ipv4 SSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if matching [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:43:14.391: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-pred W1113 01:43:14.424873 23 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+ Nov 13 01:43:14.425: INFO: Found PodSecurityPolicies; testing pod creation to see if PodSecurityPolicy is enabled Nov 13 01:43:14.428: INFO: Error creating dryrun pod; assuming PodSecurityPolicy is disabled: admission webhook "cmk.intel.com" does not support dry run STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:90 Nov 13 01:43:14.430: INFO: Waiting up to 1m0s for all (but 0) nodes to be ready Nov 13 01:43:14.443: INFO: Waiting for terminating namespaces to be deleted... Nov 13 01:43:14.445: INFO: Logging pods the apiserver thinks is on node node1 before test Nov 13 01:43:14.455: INFO: cmk-4tcdw from kube-system started at 2021-11-12 21:21:00 +0000 UTC (2 container statuses recorded) Nov 13 01:43:14.455: INFO: Container nodereport ready: true, restart count 0 Nov 13 01:43:14.456: INFO: Container reconcile ready: true, restart count 0 Nov 13 01:43:14.456: INFO: cmk-init-discover-node1-vkj2s from kube-system started at 2021-11-12 21:20:18 +0000 UTC (3 container statuses recorded) Nov 13 01:43:14.456: INFO: Container discover ready: false, restart count 0 Nov 13 01:43:14.456: INFO: Container init ready: false, restart count 0 Nov 13 01:43:14.456: INFO: Container install ready: false, restart count 0 Nov 13 01:43:14.456: INFO: cmk-webhook-6c9d5f8578-2gp25 from kube-system started at 2021-11-12 21:21:01 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.456: INFO: Container cmk-webhook ready: true, restart count 0 Nov 13 01:43:14.456: INFO: kube-flannel-r7bbp from kube-system started at 2021-11-12 21:08:36 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.456: INFO: Container kube-flannel ready: true, restart count 3 Nov 13 01:43:14.456: INFO: kube-multus-ds-amd64-4wqsv from kube-system started at 2021-11-12 21:08:45 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.456: INFO: Container kube-multus ready: true, restart count 1 Nov 13 01:43:14.456: INFO: kube-proxy-p6kbl from kube-system started at 2021-11-12 21:07:39 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.456: INFO: Container kube-proxy ready: true, restart count 2 Nov 13 01:43:14.456: INFO: nginx-proxy-node1 from kube-system started at 2021-11-12 21:07:36 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.456: INFO: Container nginx-proxy ready: true, restart count 2 Nov 13 01:43:14.456: INFO: node-feature-discovery-worker-zgr4c from kube-system started at 2021-11-12 21:16:36 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.456: INFO: Container nfd-worker ready: true, restart count 0 Nov 13 01:43:14.456: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-m62v8 from kube-system started at 2021-11-12 21:17:59 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.456: INFO: Container kube-sriovdp ready: true, restart count 0 Nov 13 01:43:14.456: INFO: collectd-74xkn from monitoring started at 2021-11-12 21:25:58 +0000 UTC (3 container statuses recorded) Nov 13 01:43:14.456: INFO: Container collectd ready: true, restart count 0 Nov 13 01:43:14.456: INFO: Container collectd-exporter ready: true, restart count 0 Nov 13 01:43:14.456: INFO: Container rbac-proxy ready: true, restart count 0 Nov 13 01:43:14.456: INFO: node-exporter-hqkfs from monitoring started at 2021-11-12 21:22:03 +0000 UTC (2 container statuses recorded) Nov 13 01:43:14.456: INFO: Container kube-rbac-proxy ready: true, restart count 0 Nov 13 01:43:14.456: INFO: Container node-exporter ready: true, restart count 0 Nov 13 01:43:14.456: INFO: prometheus-k8s-0 from monitoring started at 2021-11-12 21:22:14 +0000 UTC (4 container statuses recorded) Nov 13 01:43:14.456: INFO: Container config-reloader ready: true, restart count 0 Nov 13 01:43:14.456: INFO: Container custom-metrics-apiserver ready: true, restart count 0 Nov 13 01:43:14.456: INFO: Container grafana ready: true, restart count 0 Nov 13 01:43:14.456: INFO: Container prometheus ready: true, restart count 1 Nov 13 01:43:14.456: INFO: prometheus-operator-585ccfb458-qcz7s from monitoring started at 2021-11-12 21:21:55 +0000 UTC (2 container statuses recorded) Nov 13 01:43:14.456: INFO: Container kube-rbac-proxy ready: true, restart count 0 Nov 13 01:43:14.456: INFO: Container prometheus-operator ready: true, restart count 0 Nov 13 01:43:14.456: INFO: Logging pods the apiserver thinks is on node node2 before test Nov 13 01:43:14.463: INFO: cmk-init-discover-node2-5f4hp from kube-system started at 2021-11-12 21:20:38 +0000 UTC (3 container statuses recorded) Nov 13 01:43:14.463: INFO: Container discover ready: false, restart count 0 Nov 13 01:43:14.463: INFO: Container init ready: false, restart count 0 Nov 13 01:43:14.463: INFO: Container install ready: false, restart count 0 Nov 13 01:43:14.463: INFO: cmk-qhvr7 from kube-system started at 2021-11-12 21:21:01 +0000 UTC (2 container statuses recorded) Nov 13 01:43:14.463: INFO: Container nodereport ready: true, restart count 0 Nov 13 01:43:14.463: INFO: Container reconcile ready: true, restart count 0 Nov 13 01:43:14.463: INFO: kube-flannel-mg66r from kube-system started at 2021-11-12 21:08:36 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.463: INFO: Container kube-flannel ready: true, restart count 2 Nov 13 01:43:14.463: INFO: kube-multus-ds-amd64-2wqj5 from kube-system started at 2021-11-12 21:08:45 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.463: INFO: Container kube-multus ready: true, restart count 1 Nov 13 01:43:14.463: INFO: kube-proxy-pzhf2 from kube-system started at 2021-11-12 21:07:39 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.463: INFO: Container kube-proxy ready: true, restart count 1 Nov 13 01:43:14.463: INFO: kubernetes-dashboard-785dcbb76d-w2mls from kube-system started at 2021-11-12 21:09:15 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.463: INFO: Container kubernetes-dashboard ready: true, restart count 1 Nov 13 01:43:14.463: INFO: kubernetes-metrics-scraper-5558854cb-jmbpk from kube-system started at 2021-11-12 21:09:15 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.463: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 Nov 13 01:43:14.463: INFO: nginx-proxy-node2 from kube-system started at 2021-11-12 21:07:36 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.463: INFO: Container nginx-proxy ready: true, restart count 2 Nov 13 01:43:14.463: INFO: node-feature-discovery-worker-mm7xs from kube-system started at 2021-11-12 21:16:36 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.463: INFO: Container nfd-worker ready: true, restart count 0 Nov 13 01:43:14.463: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-7brrh from kube-system started at 2021-11-12 21:17:59 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.463: INFO: Container kube-sriovdp ready: true, restart count 0 Nov 13 01:43:14.463: INFO: collectd-mp2z6 from monitoring started at 2021-11-12 21:25:58 +0000 UTC (3 container statuses recorded) Nov 13 01:43:14.463: INFO: Container collectd ready: true, restart count 0 Nov 13 01:43:14.463: INFO: Container collectd-exporter ready: true, restart count 0 Nov 13 01:43:14.463: INFO: Container rbac-proxy ready: true, restart count 0 Nov 13 01:43:14.463: INFO: node-exporter-hstd9 from monitoring started at 2021-11-12 21:22:03 +0000 UTC (2 container statuses recorded) Nov 13 01:43:14.463: INFO: Container kube-rbac-proxy ready: true, restart count 0 Nov 13 01:43:14.463: INFO: Container node-exporter ready: true, restart count 0 Nov 13 01:43:14.463: INFO: tas-telemetry-aware-scheduling-84ff454dfb-q7m54 from monitoring started at 2021-11-12 21:25:09 +0000 UTC (1 container statuses recorded) Nov 13 01:43:14.463: INFO: Container tas-extender ready: true, restart count 0 [It] validates that NodeSelector is respected if matching [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 STEP: Trying to launch a pod without a label to get a node which can launch it. STEP: Explicitly delete pod here to free the resource it takes. STEP: Trying to apply a random label on the found node. STEP: verifying the node has the label kubernetes.io/e2e-3db6469b-c03b-4fb5-8a1c-6e9721a54b8c 42 STEP: Trying to relaunch the pod, now with labels. STEP: removing the label kubernetes.io/e2e-3db6469b-c03b-4fb5-8a1c-6e9721a54b8c off the node node2 STEP: verifying the node doesn't have the label kubernetes.io/e2e-3db6469b-c03b-4fb5-8a1c-6e9721a54b8c [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:43:22.539: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-pred-6606" for this suite. [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:81 • [SLOW TEST:8.156 seconds] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 validates that NodeSelector is respected if matching [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if matching [Conformance]","total":17,"completed":1,"skipped":17,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPredicates [Serial] validates that there exists conflict between pods with same hostPort and protocol but one using 0.0.0.0 hostIP [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:43:22.550: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-pred STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:90 Nov 13 01:43:22.574: INFO: Waiting up to 1m0s for all (but 0) nodes to be ready Nov 13 01:43:22.583: INFO: Waiting for terminating namespaces to be deleted... Nov 13 01:43:22.585: INFO: Logging pods the apiserver thinks is on node node1 before test Nov 13 01:43:22.598: INFO: cmk-4tcdw from kube-system started at 2021-11-12 21:21:00 +0000 UTC (2 container statuses recorded) Nov 13 01:43:22.598: INFO: Container nodereport ready: true, restart count 0 Nov 13 01:43:22.599: INFO: Container reconcile ready: true, restart count 0 Nov 13 01:43:22.599: INFO: cmk-init-discover-node1-vkj2s from kube-system started at 2021-11-12 21:20:18 +0000 UTC (3 container statuses recorded) Nov 13 01:43:22.599: INFO: Container discover ready: false, restart count 0 Nov 13 01:43:22.599: INFO: Container init ready: false, restart count 0 Nov 13 01:43:22.599: INFO: Container install ready: false, restart count 0 Nov 13 01:43:22.599: INFO: cmk-webhook-6c9d5f8578-2gp25 from kube-system started at 2021-11-12 21:21:01 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.599: INFO: Container cmk-webhook ready: true, restart count 0 Nov 13 01:43:22.599: INFO: kube-flannel-r7bbp from kube-system started at 2021-11-12 21:08:36 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.599: INFO: Container kube-flannel ready: true, restart count 3 Nov 13 01:43:22.599: INFO: kube-multus-ds-amd64-4wqsv from kube-system started at 2021-11-12 21:08:45 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.599: INFO: Container kube-multus ready: true, restart count 1 Nov 13 01:43:22.599: INFO: kube-proxy-p6kbl from kube-system started at 2021-11-12 21:07:39 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.599: INFO: Container kube-proxy ready: true, restart count 2 Nov 13 01:43:22.599: INFO: nginx-proxy-node1 from kube-system started at 2021-11-12 21:07:36 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.599: INFO: Container nginx-proxy ready: true, restart count 2 Nov 13 01:43:22.599: INFO: node-feature-discovery-worker-zgr4c from kube-system started at 2021-11-12 21:16:36 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.599: INFO: Container nfd-worker ready: true, restart count 0 Nov 13 01:43:22.599: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-m62v8 from kube-system started at 2021-11-12 21:17:59 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.599: INFO: Container kube-sriovdp ready: true, restart count 0 Nov 13 01:43:22.599: INFO: collectd-74xkn from monitoring started at 2021-11-12 21:25:58 +0000 UTC (3 container statuses recorded) Nov 13 01:43:22.599: INFO: Container collectd ready: true, restart count 0 Nov 13 01:43:22.599: INFO: Container collectd-exporter ready: true, restart count 0 Nov 13 01:43:22.599: INFO: Container rbac-proxy ready: true, restart count 0 Nov 13 01:43:22.599: INFO: node-exporter-hqkfs from monitoring started at 2021-11-12 21:22:03 +0000 UTC (2 container statuses recorded) Nov 13 01:43:22.599: INFO: Container kube-rbac-proxy ready: true, restart count 0 Nov 13 01:43:22.599: INFO: Container node-exporter ready: true, restart count 0 Nov 13 01:43:22.599: INFO: prometheus-k8s-0 from monitoring started at 2021-11-12 21:22:14 +0000 UTC (4 container statuses recorded) Nov 13 01:43:22.599: INFO: Container config-reloader ready: true, restart count 0 Nov 13 01:43:22.599: INFO: Container custom-metrics-apiserver ready: true, restart count 0 Nov 13 01:43:22.599: INFO: Container grafana ready: true, restart count 0 Nov 13 01:43:22.599: INFO: Container prometheus ready: true, restart count 1 Nov 13 01:43:22.599: INFO: prometheus-operator-585ccfb458-qcz7s from monitoring started at 2021-11-12 21:21:55 +0000 UTC (2 container statuses recorded) Nov 13 01:43:22.599: INFO: Container kube-rbac-proxy ready: true, restart count 0 Nov 13 01:43:22.599: INFO: Container prometheus-operator ready: true, restart count 0 Nov 13 01:43:22.599: INFO: Logging pods the apiserver thinks is on node node2 before test Nov 13 01:43:22.617: INFO: cmk-init-discover-node2-5f4hp from kube-system started at 2021-11-12 21:20:38 +0000 UTC (3 container statuses recorded) Nov 13 01:43:22.617: INFO: Container discover ready: false, restart count 0 Nov 13 01:43:22.617: INFO: Container init ready: false, restart count 0 Nov 13 01:43:22.617: INFO: Container install ready: false, restart count 0 Nov 13 01:43:22.617: INFO: cmk-qhvr7 from kube-system started at 2021-11-12 21:21:01 +0000 UTC (2 container statuses recorded) Nov 13 01:43:22.617: INFO: Container nodereport ready: true, restart count 0 Nov 13 01:43:22.617: INFO: Container reconcile ready: true, restart count 0 Nov 13 01:43:22.617: INFO: kube-flannel-mg66r from kube-system started at 2021-11-12 21:08:36 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.617: INFO: Container kube-flannel ready: true, restart count 2 Nov 13 01:43:22.617: INFO: kube-multus-ds-amd64-2wqj5 from kube-system started at 2021-11-12 21:08:45 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.617: INFO: Container kube-multus ready: true, restart count 1 Nov 13 01:43:22.617: INFO: kube-proxy-pzhf2 from kube-system started at 2021-11-12 21:07:39 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.617: INFO: Container kube-proxy ready: true, restart count 1 Nov 13 01:43:22.617: INFO: kubernetes-dashboard-785dcbb76d-w2mls from kube-system started at 2021-11-12 21:09:15 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.617: INFO: Container kubernetes-dashboard ready: true, restart count 1 Nov 13 01:43:22.617: INFO: kubernetes-metrics-scraper-5558854cb-jmbpk from kube-system started at 2021-11-12 21:09:15 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.617: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 Nov 13 01:43:22.617: INFO: nginx-proxy-node2 from kube-system started at 2021-11-12 21:07:36 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.617: INFO: Container nginx-proxy ready: true, restart count 2 Nov 13 01:43:22.617: INFO: node-feature-discovery-worker-mm7xs from kube-system started at 2021-11-12 21:16:36 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.617: INFO: Container nfd-worker ready: true, restart count 0 Nov 13 01:43:22.617: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-7brrh from kube-system started at 2021-11-12 21:17:59 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.617: INFO: Container kube-sriovdp ready: true, restart count 0 Nov 13 01:43:22.617: INFO: collectd-mp2z6 from monitoring started at 2021-11-12 21:25:58 +0000 UTC (3 container statuses recorded) Nov 13 01:43:22.617: INFO: Container collectd ready: true, restart count 0 Nov 13 01:43:22.617: INFO: Container collectd-exporter ready: true, restart count 0 Nov 13 01:43:22.617: INFO: Container rbac-proxy ready: true, restart count 0 Nov 13 01:43:22.617: INFO: node-exporter-hstd9 from monitoring started at 2021-11-12 21:22:03 +0000 UTC (2 container statuses recorded) Nov 13 01:43:22.617: INFO: Container kube-rbac-proxy ready: true, restart count 0 Nov 13 01:43:22.617: INFO: Container node-exporter ready: true, restart count 0 Nov 13 01:43:22.617: INFO: tas-telemetry-aware-scheduling-84ff454dfb-q7m54 from monitoring started at 2021-11-12 21:25:09 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.617: INFO: Container tas-extender ready: true, restart count 0 Nov 13 01:43:22.617: INFO: with-labels from sched-pred-6606 started at 2021-11-13 01:43:18 +0000 UTC (1 container statuses recorded) Nov 13 01:43:22.617: INFO: Container with-labels ready: true, restart count 0 [It] validates that there exists conflict between pods with same hostPort and protocol but one using 0.0.0.0 hostIP [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 STEP: Trying to launch a pod without a label to get a node which can launch it. STEP: Explicitly delete pod here to free the resource it takes. STEP: Trying to apply a random label on the found node. STEP: verifying the node has the label kubernetes.io/e2e-0db3152d-7d93-4983-b732-4f340c331288 95 STEP: Trying to create a pod(pod4) with hostport 54322 and hostIP 0.0.0.0(empty string here) and expect scheduled STEP: Trying to create another pod(pod5) with hostport 54322 but hostIP 10.10.190.208 on the node which pod4 resides and expect not scheduled STEP: removing the label kubernetes.io/e2e-0db3152d-7d93-4983-b732-4f340c331288 off the node node2 STEP: verifying the node doesn't have the label kubernetes.io/e2e-0db3152d-7d93-4983-b732-4f340c331288 [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:48:32.713: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-pred-2790" for this suite. [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:81 • [SLOW TEST:310.171 seconds] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 validates that there exists conflict between pods with same hostPort and protocol but one using 0.0.0.0 hostIP [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPredicates [Serial] validates that there exists conflict between pods with same hostPort and protocol but one using 0.0.0.0 hostIP [Conformance]","total":17,"completed":2,"skipped":246,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-api-machinery] Namespaces [Serial] should patch a Namespace [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:48:32.730: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename namespaces STEP: Waiting for a default service account to be provisioned in namespace [It] should patch a Namespace [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 STEP: creating a Namespace STEP: patching the Namespace STEP: get the Namespace and ensuring it has the label [AfterEach] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:48:32.781: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "namespaces-1627" for this suite. STEP: Destroying namespace "nspatchtest-96243aa3-3a8a-4302-87bb-05b69fa74c9e-7841" for this suite. •{"msg":"PASSED [sig-api-machinery] Namespaces [Serial] should patch a Namespace [Conformance]","total":17,"completed":3,"skipped":838,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPreemption [Serial] validates lower priority pod preemption by critical pod [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:48:32.796: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-preemption STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:90 Nov 13 01:48:32.823: INFO: Waiting up to 1m0s for all nodes to be ready Nov 13 01:49:32.882: INFO: Waiting for terminating namespaces to be deleted... [It] validates lower priority pod preemption by critical pod [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 STEP: Create pods that use 2/3 of node resources. Nov 13 01:49:32.910: INFO: Created pod: pod0-sched-preemption-low-priority Nov 13 01:49:32.930: INFO: Created pod: pod1-sched-preemption-medium-priority STEP: Wait for pods to be scheduled. STEP: Run a critical pod that use same resources as that of a lower priority pod [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:49:52.976: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-preemption-301" for this suite. [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:78 • [SLOW TEST:80.218 seconds] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 validates lower priority pod preemption by critical pod [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPreemption [Serial] validates lower priority pod preemption by critical pod [Conformance]","total":17,"completed":4,"skipped":960,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:49:53.025: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-pred STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:90 Nov 13 01:49:53.050: INFO: Waiting up to 1m0s for all (but 0) nodes to be ready Nov 13 01:49:53.059: INFO: Waiting for terminating namespaces to be deleted... Nov 13 01:49:53.061: INFO: Logging pods the apiserver thinks is on node node1 before test Nov 13 01:49:53.073: INFO: cmk-4tcdw from kube-system started at 2021-11-12 21:21:00 +0000 UTC (2 container statuses recorded) Nov 13 01:49:53.073: INFO: Container nodereport ready: true, restart count 0 Nov 13 01:49:53.073: INFO: Container reconcile ready: true, restart count 0 Nov 13 01:49:53.073: INFO: cmk-init-discover-node1-vkj2s from kube-system started at 2021-11-12 21:20:18 +0000 UTC (3 container statuses recorded) Nov 13 01:49:53.073: INFO: Container discover ready: false, restart count 0 Nov 13 01:49:53.073: INFO: Container init ready: false, restart count 0 Nov 13 01:49:53.073: INFO: Container install ready: false, restart count 0 Nov 13 01:49:53.073: INFO: cmk-webhook-6c9d5f8578-2gp25 from kube-system started at 2021-11-12 21:21:01 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.073: INFO: Container cmk-webhook ready: true, restart count 0 Nov 13 01:49:53.073: INFO: kube-flannel-r7bbp from kube-system started at 2021-11-12 21:08:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.073: INFO: Container kube-flannel ready: true, restart count 3 Nov 13 01:49:53.073: INFO: kube-multus-ds-amd64-4wqsv from kube-system started at 2021-11-12 21:08:45 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.073: INFO: Container kube-multus ready: true, restart count 1 Nov 13 01:49:53.073: INFO: kube-proxy-p6kbl from kube-system started at 2021-11-12 21:07:39 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.073: INFO: Container kube-proxy ready: true, restart count 2 Nov 13 01:49:53.073: INFO: nginx-proxy-node1 from kube-system started at 2021-11-12 21:07:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.073: INFO: Container nginx-proxy ready: true, restart count 2 Nov 13 01:49:53.073: INFO: node-feature-discovery-worker-zgr4c from kube-system started at 2021-11-12 21:16:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.073: INFO: Container nfd-worker ready: true, restart count 0 Nov 13 01:49:53.073: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-m62v8 from kube-system started at 2021-11-12 21:17:59 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.073: INFO: Container kube-sriovdp ready: true, restart count 0 Nov 13 01:49:53.073: INFO: collectd-74xkn from monitoring started at 2021-11-12 21:25:58 +0000 UTC (3 container statuses recorded) Nov 13 01:49:53.073: INFO: Container collectd ready: true, restart count 0 Nov 13 01:49:53.073: INFO: Container collectd-exporter ready: true, restart count 0 Nov 13 01:49:53.073: INFO: Container rbac-proxy ready: true, restart count 0 Nov 13 01:49:53.073: INFO: node-exporter-hqkfs from monitoring started at 2021-11-12 21:22:03 +0000 UTC (2 container statuses recorded) Nov 13 01:49:53.073: INFO: Container kube-rbac-proxy ready: true, restart count 0 Nov 13 01:49:53.073: INFO: Container node-exporter ready: true, restart count 0 Nov 13 01:49:53.073: INFO: prometheus-k8s-0 from monitoring started at 2021-11-12 21:22:14 +0000 UTC (4 container statuses recorded) Nov 13 01:49:53.073: INFO: Container config-reloader ready: true, restart count 0 Nov 13 01:49:53.073: INFO: Container custom-metrics-apiserver ready: true, restart count 0 Nov 13 01:49:53.073: INFO: Container grafana ready: true, restart count 0 Nov 13 01:49:53.073: INFO: Container prometheus ready: true, restart count 1 Nov 13 01:49:53.073: INFO: prometheus-operator-585ccfb458-qcz7s from monitoring started at 2021-11-12 21:21:55 +0000 UTC (2 container statuses recorded) Nov 13 01:49:53.073: INFO: Container kube-rbac-proxy ready: true, restart count 0 Nov 13 01:49:53.073: INFO: Container prometheus-operator ready: true, restart count 0 Nov 13 01:49:53.073: INFO: Logging pods the apiserver thinks is on node node2 before test Nov 13 01:49:53.084: INFO: cmk-init-discover-node2-5f4hp from kube-system started at 2021-11-12 21:20:38 +0000 UTC (3 container statuses recorded) Nov 13 01:49:53.084: INFO: Container discover ready: false, restart count 0 Nov 13 01:49:53.084: INFO: Container init ready: false, restart count 0 Nov 13 01:49:53.084: INFO: Container install ready: false, restart count 0 Nov 13 01:49:53.084: INFO: cmk-qhvr7 from kube-system started at 2021-11-12 21:21:01 +0000 UTC (2 container statuses recorded) Nov 13 01:49:53.084: INFO: Container nodereport ready: true, restart count 0 Nov 13 01:49:53.084: INFO: Container reconcile ready: true, restart count 0 Nov 13 01:49:53.084: INFO: kube-flannel-mg66r from kube-system started at 2021-11-12 21:08:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.084: INFO: Container kube-flannel ready: true, restart count 2 Nov 13 01:49:53.084: INFO: kube-multus-ds-amd64-2wqj5 from kube-system started at 2021-11-12 21:08:45 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.084: INFO: Container kube-multus ready: true, restart count 1 Nov 13 01:49:53.084: INFO: kube-proxy-pzhf2 from kube-system started at 2021-11-12 21:07:39 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.084: INFO: Container kube-proxy ready: true, restart count 1 Nov 13 01:49:53.084: INFO: kubernetes-dashboard-785dcbb76d-w2mls from kube-system started at 2021-11-12 21:09:15 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.084: INFO: Container kubernetes-dashboard ready: true, restart count 1 Nov 13 01:49:53.084: INFO: kubernetes-metrics-scraper-5558854cb-jmbpk from kube-system started at 2021-11-12 21:09:15 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.084: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 Nov 13 01:49:53.084: INFO: nginx-proxy-node2 from kube-system started at 2021-11-12 21:07:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.084: INFO: Container nginx-proxy ready: true, restart count 2 Nov 13 01:49:53.084: INFO: node-feature-discovery-worker-mm7xs from kube-system started at 2021-11-12 21:16:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.084: INFO: Container nfd-worker ready: true, restart count 0 Nov 13 01:49:53.084: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-7brrh from kube-system started at 2021-11-12 21:17:59 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.084: INFO: Container kube-sriovdp ready: true, restart count 0 Nov 13 01:49:53.084: INFO: collectd-mp2z6 from monitoring started at 2021-11-12 21:25:58 +0000 UTC (3 container statuses recorded) Nov 13 01:49:53.084: INFO: Container collectd ready: true, restart count 0 Nov 13 01:49:53.084: INFO: Container collectd-exporter ready: true, restart count 0 Nov 13 01:49:53.084: INFO: Container rbac-proxy ready: true, restart count 0 Nov 13 01:49:53.084: INFO: node-exporter-hstd9 from monitoring started at 2021-11-12 21:22:03 +0000 UTC (2 container statuses recorded) Nov 13 01:49:53.084: INFO: Container kube-rbac-proxy ready: true, restart count 0 Nov 13 01:49:53.084: INFO: Container node-exporter ready: true, restart count 0 Nov 13 01:49:53.084: INFO: tas-telemetry-aware-scheduling-84ff454dfb-q7m54 from monitoring started at 2021-11-12 21:25:09 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.084: INFO: Container tas-extender ready: true, restart count 0 Nov 13 01:49:53.084: INFO: pod1-sched-preemption-medium-priority from sched-preemption-301 started at 2021-11-13 01:49:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:53.084: INFO: Container pod1-sched-preemption-medium-priority ready: true, restart count 0 [It] validates that NodeSelector is respected if not matching [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 STEP: Trying to schedule Pod with nonempty NodeSelector. STEP: Considering event: Type = [Warning], Name = [restricted-pod.16b6f7ffeaacd5a2], Reason = [FailedScheduling], Message = [0/5 nodes are available: 2 node(s) didn't match Pod's node affinity/selector, 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.] [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:49:54.128: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-pred-6718" for this suite. [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:81 •{"msg":"PASSED [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance]","total":17,"completed":5,"skipped":1710,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:49:54.151: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-pred STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:90 Nov 13 01:49:54.177: INFO: Waiting up to 1m0s for all (but 0) nodes to be ready Nov 13 01:49:54.186: INFO: Waiting for terminating namespaces to be deleted... Nov 13 01:49:54.188: INFO: Logging pods the apiserver thinks is on node node1 before test Nov 13 01:49:54.195: INFO: cmk-4tcdw from kube-system started at 2021-11-12 21:21:00 +0000 UTC (2 container statuses recorded) Nov 13 01:49:54.195: INFO: Container nodereport ready: true, restart count 0 Nov 13 01:49:54.195: INFO: Container reconcile ready: true, restart count 0 Nov 13 01:49:54.195: INFO: cmk-init-discover-node1-vkj2s from kube-system started at 2021-11-12 21:20:18 +0000 UTC (3 container statuses recorded) Nov 13 01:49:54.195: INFO: Container discover ready: false, restart count 0 Nov 13 01:49:54.195: INFO: Container init ready: false, restart count 0 Nov 13 01:49:54.195: INFO: Container install ready: false, restart count 0 Nov 13 01:49:54.195: INFO: cmk-webhook-6c9d5f8578-2gp25 from kube-system started at 2021-11-12 21:21:01 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.195: INFO: Container cmk-webhook ready: true, restart count 0 Nov 13 01:49:54.195: INFO: kube-flannel-r7bbp from kube-system started at 2021-11-12 21:08:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.195: INFO: Container kube-flannel ready: true, restart count 3 Nov 13 01:49:54.195: INFO: kube-multus-ds-amd64-4wqsv from kube-system started at 2021-11-12 21:08:45 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.195: INFO: Container kube-multus ready: true, restart count 1 Nov 13 01:49:54.195: INFO: kube-proxy-p6kbl from kube-system started at 2021-11-12 21:07:39 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.195: INFO: Container kube-proxy ready: true, restart count 2 Nov 13 01:49:54.195: INFO: nginx-proxy-node1 from kube-system started at 2021-11-12 21:07:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.195: INFO: Container nginx-proxy ready: true, restart count 2 Nov 13 01:49:54.195: INFO: node-feature-discovery-worker-zgr4c from kube-system started at 2021-11-12 21:16:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.195: INFO: Container nfd-worker ready: true, restart count 0 Nov 13 01:49:54.195: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-m62v8 from kube-system started at 2021-11-12 21:17:59 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.195: INFO: Container kube-sriovdp ready: true, restart count 0 Nov 13 01:49:54.195: INFO: collectd-74xkn from monitoring started at 2021-11-12 21:25:58 +0000 UTC (3 container statuses recorded) Nov 13 01:49:54.195: INFO: Container collectd ready: true, restart count 0 Nov 13 01:49:54.195: INFO: Container collectd-exporter ready: true, restart count 0 Nov 13 01:49:54.195: INFO: Container rbac-proxy ready: true, restart count 0 Nov 13 01:49:54.195: INFO: node-exporter-hqkfs from monitoring started at 2021-11-12 21:22:03 +0000 UTC (2 container statuses recorded) Nov 13 01:49:54.195: INFO: Container kube-rbac-proxy ready: true, restart count 0 Nov 13 01:49:54.195: INFO: Container node-exporter ready: true, restart count 0 Nov 13 01:49:54.195: INFO: prometheus-k8s-0 from monitoring started at 2021-11-12 21:22:14 +0000 UTC (4 container statuses recorded) Nov 13 01:49:54.195: INFO: Container config-reloader ready: true, restart count 0 Nov 13 01:49:54.195: INFO: Container custom-metrics-apiserver ready: true, restart count 0 Nov 13 01:49:54.195: INFO: Container grafana ready: true, restart count 0 Nov 13 01:49:54.195: INFO: Container prometheus ready: true, restart count 1 Nov 13 01:49:54.195: INFO: prometheus-operator-585ccfb458-qcz7s from monitoring started at 2021-11-12 21:21:55 +0000 UTC (2 container statuses recorded) Nov 13 01:49:54.195: INFO: Container kube-rbac-proxy ready: true, restart count 0 Nov 13 01:49:54.195: INFO: Container prometheus-operator ready: true, restart count 0 Nov 13 01:49:54.195: INFO: Logging pods the apiserver thinks is on node node2 before test Nov 13 01:49:54.205: INFO: cmk-init-discover-node2-5f4hp from kube-system started at 2021-11-12 21:20:38 +0000 UTC (3 container statuses recorded) Nov 13 01:49:54.205: INFO: Container discover ready: false, restart count 0 Nov 13 01:49:54.205: INFO: Container init ready: false, restart count 0 Nov 13 01:49:54.205: INFO: Container install ready: false, restart count 0 Nov 13 01:49:54.205: INFO: cmk-qhvr7 from kube-system started at 2021-11-12 21:21:01 +0000 UTC (2 container statuses recorded) Nov 13 01:49:54.205: INFO: Container nodereport ready: true, restart count 0 Nov 13 01:49:54.205: INFO: Container reconcile ready: true, restart count 0 Nov 13 01:49:54.205: INFO: kube-flannel-mg66r from kube-system started at 2021-11-12 21:08:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.205: INFO: Container kube-flannel ready: true, restart count 2 Nov 13 01:49:54.205: INFO: kube-multus-ds-amd64-2wqj5 from kube-system started at 2021-11-12 21:08:45 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.205: INFO: Container kube-multus ready: true, restart count 1 Nov 13 01:49:54.205: INFO: kube-proxy-pzhf2 from kube-system started at 2021-11-12 21:07:39 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.205: INFO: Container kube-proxy ready: true, restart count 1 Nov 13 01:49:54.205: INFO: kubernetes-dashboard-785dcbb76d-w2mls from kube-system started at 2021-11-12 21:09:15 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.205: INFO: Container kubernetes-dashboard ready: true, restart count 1 Nov 13 01:49:54.205: INFO: kubernetes-metrics-scraper-5558854cb-jmbpk from kube-system started at 2021-11-12 21:09:15 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.205: INFO: Container kubernetes-metrics-scraper ready: true, restart count 1 Nov 13 01:49:54.205: INFO: nginx-proxy-node2 from kube-system started at 2021-11-12 21:07:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.205: INFO: Container nginx-proxy ready: true, restart count 2 Nov 13 01:49:54.205: INFO: node-feature-discovery-worker-mm7xs from kube-system started at 2021-11-12 21:16:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.205: INFO: Container nfd-worker ready: true, restart count 0 Nov 13 01:49:54.205: INFO: sriov-net-dp-kube-sriov-device-plugin-amd64-7brrh from kube-system started at 2021-11-12 21:17:59 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.205: INFO: Container kube-sriovdp ready: true, restart count 0 Nov 13 01:49:54.205: INFO: collectd-mp2z6 from monitoring started at 2021-11-12 21:25:58 +0000 UTC (3 container statuses recorded) Nov 13 01:49:54.205: INFO: Container collectd ready: true, restart count 0 Nov 13 01:49:54.205: INFO: Container collectd-exporter ready: true, restart count 0 Nov 13 01:49:54.205: INFO: Container rbac-proxy ready: true, restart count 0 Nov 13 01:49:54.205: INFO: node-exporter-hstd9 from monitoring started at 2021-11-12 21:22:03 +0000 UTC (2 container statuses recorded) Nov 13 01:49:54.205: INFO: Container kube-rbac-proxy ready: true, restart count 0 Nov 13 01:49:54.205: INFO: Container node-exporter ready: true, restart count 0 Nov 13 01:49:54.205: INFO: tas-telemetry-aware-scheduling-84ff454dfb-q7m54 from monitoring started at 2021-11-12 21:25:09 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.205: INFO: Container tas-extender ready: true, restart count 0 Nov 13 01:49:54.205: INFO: pod1-sched-preemption-medium-priority from sched-preemption-301 started at 2021-11-13 01:49:36 +0000 UTC (1 container statuses recorded) Nov 13 01:49:54.205: INFO: Container pod1-sched-preemption-medium-priority ready: true, restart count 0 [It] validates resource limits of pods that are allowed to run [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 STEP: verifying the node has the label node node1 STEP: verifying the node has the label node node2 Nov 13 01:50:00.325: INFO: Pod cmk-4tcdw requesting resource cpu=0m on Node node1 Nov 13 01:50:00.325: INFO: Pod cmk-qhvr7 requesting resource cpu=0m on Node node2 Nov 13 01:50:00.325: INFO: Pod cmk-webhook-6c9d5f8578-2gp25 requesting resource cpu=0m on Node node1 Nov 13 01:50:00.325: INFO: Pod kube-flannel-mg66r requesting resource cpu=150m on Node node2 Nov 13 01:50:00.325: INFO: Pod kube-flannel-r7bbp requesting resource cpu=150m on Node node1 Nov 13 01:50:00.325: INFO: Pod kube-multus-ds-amd64-2wqj5 requesting resource cpu=100m on Node node2 Nov 13 01:50:00.325: INFO: Pod kube-multus-ds-amd64-4wqsv requesting resource cpu=100m on Node node1 Nov 13 01:50:00.325: INFO: Pod kube-proxy-p6kbl requesting resource cpu=0m on Node node1 Nov 13 01:50:00.325: INFO: Pod kube-proxy-pzhf2 requesting resource cpu=0m on Node node2 Nov 13 01:50:00.325: INFO: Pod kubernetes-dashboard-785dcbb76d-w2mls requesting resource cpu=50m on Node node2 Nov 13 01:50:00.325: INFO: Pod kubernetes-metrics-scraper-5558854cb-jmbpk requesting resource cpu=0m on Node node2 Nov 13 01:50:00.325: INFO: Pod nginx-proxy-node1 requesting resource cpu=25m on Node node1 Nov 13 01:50:00.325: INFO: Pod nginx-proxy-node2 requesting resource cpu=25m on Node node2 Nov 13 01:50:00.325: INFO: Pod node-feature-discovery-worker-mm7xs requesting resource cpu=0m on Node node2 Nov 13 01:50:00.325: INFO: Pod node-feature-discovery-worker-zgr4c requesting resource cpu=0m on Node node1 Nov 13 01:50:00.325: INFO: Pod sriov-net-dp-kube-sriov-device-plugin-amd64-7brrh requesting resource cpu=0m on Node node2 Nov 13 01:50:00.325: INFO: Pod sriov-net-dp-kube-sriov-device-plugin-amd64-m62v8 requesting resource cpu=0m on Node node1 Nov 13 01:50:00.325: INFO: Pod collectd-74xkn requesting resource cpu=0m on Node node1 Nov 13 01:50:00.325: INFO: Pod collectd-mp2z6 requesting resource cpu=0m on Node node2 Nov 13 01:50:00.325: INFO: Pod node-exporter-hqkfs requesting resource cpu=112m on Node node1 Nov 13 01:50:00.325: INFO: Pod node-exporter-hstd9 requesting resource cpu=112m on Node node2 Nov 13 01:50:00.325: INFO: Pod prometheus-k8s-0 requesting resource cpu=200m on Node node1 Nov 13 01:50:00.325: INFO: Pod prometheus-operator-585ccfb458-qcz7s requesting resource cpu=100m on Node node1 Nov 13 01:50:00.325: INFO: Pod tas-telemetry-aware-scheduling-84ff454dfb-q7m54 requesting resource cpu=0m on Node node2 STEP: Starting Pods to consume most of the cluster CPU. Nov 13 01:50:00.325: INFO: Creating a pod which consumes cpu=53419m on Node node1 Nov 13 01:50:00.337: INFO: Creating a pod which consumes cpu=53594m on Node node2 STEP: Creating another pod that requires unavailable amount of CPU. STEP: Considering event: Type = [Normal], Name = [filler-pod-f41924ff-4196-4bfe-a5b5-84bd7dbb6822.16b6f80198c9c367], Reason = [Scheduled], Message = [Successfully assigned sched-pred-8547/filler-pod-f41924ff-4196-4bfe-a5b5-84bd7dbb6822 to node1] STEP: Considering event: Type = [Normal], Name = [filler-pod-f41924ff-4196-4bfe-a5b5-84bd7dbb6822.16b6f801f38a75f0], Reason = [Pulling], Message = [Pulling image "k8s.gcr.io/pause:3.4.1"] STEP: Considering event: Type = [Normal], Name = [filler-pod-f41924ff-4196-4bfe-a5b5-84bd7dbb6822.16b6f8020b47080a], Reason = [Pulled], Message = [Successfully pulled image "k8s.gcr.io/pause:3.4.1" in 398.226461ms] STEP: Considering event: Type = [Normal], Name = [filler-pod-f41924ff-4196-4bfe-a5b5-84bd7dbb6822.16b6f80211c05f14], Reason = [Created], Message = [Created container filler-pod-f41924ff-4196-4bfe-a5b5-84bd7dbb6822] STEP: Considering event: Type = [Normal], Name = [filler-pod-f41924ff-4196-4bfe-a5b5-84bd7dbb6822.16b6f802199f8d7f], Reason = [Started], Message = [Started container filler-pod-f41924ff-4196-4bfe-a5b5-84bd7dbb6822] STEP: Considering event: Type = [Normal], Name = [filler-pod-f5f4aa4b-accb-4804-b94f-dc92fef11048.16b6f801994ccc5b], Reason = [Scheduled], Message = [Successfully assigned sched-pred-8547/filler-pod-f5f4aa4b-accb-4804-b94f-dc92fef11048 to node2] STEP: Considering event: Type = [Normal], Name = [filler-pod-f5f4aa4b-accb-4804-b94f-dc92fef11048.16b6f801efc95bdb], Reason = [Pulling], Message = [Pulling image "k8s.gcr.io/pause:3.4.1"] STEP: Considering event: Type = [Normal], Name = [filler-pod-f5f4aa4b-accb-4804-b94f-dc92fef11048.16b6f80204280991], Reason = [Pulled], Message = [Successfully pulled image "k8s.gcr.io/pause:3.4.1" in 341.741693ms] STEP: Considering event: Type = [Normal], Name = [filler-pod-f5f4aa4b-accb-4804-b94f-dc92fef11048.16b6f8020a68b335], Reason = [Created], Message = [Created container filler-pod-f5f4aa4b-accb-4804-b94f-dc92fef11048] STEP: Considering event: Type = [Normal], Name = [filler-pod-f5f4aa4b-accb-4804-b94f-dc92fef11048.16b6f80210eacc44], Reason = [Started], Message = [Started container filler-pod-f5f4aa4b-accb-4804-b94f-dc92fef11048] STEP: Considering event: Type = [Warning], Name = [additional-pod.16b6f802892f860d], Reason = [FailedScheduling], Message = [0/5 nodes are available: 2 Insufficient cpu, 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.] STEP: removing the label node off the node node2 STEP: verifying the node doesn't have the label node STEP: removing the label node off the node node1 STEP: verifying the node doesn't have the label node [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:50:05.404: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-pred-8547" for this suite. [AfterEach] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:81 • [SLOW TEST:11.260 seconds] [sig-scheduling] SchedulerPredicates [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 validates resource limits of pods that are allowed to run [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance]","total":17,"completed":6,"skipped":2592,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath runs ReplicaSets to verify preemption running path [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:50:05.415: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-preemption STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:90 Nov 13 01:50:05.446: INFO: Waiting up to 1m0s for all nodes to be ready Nov 13 01:51:05.502: INFO: Waiting for terminating namespaces to be deleted... [BeforeEach] PreemptionExecutionPath /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:51:05.504: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-preemption-path STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] PreemptionExecutionPath /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:488 STEP: Finding an available node STEP: Trying to launch a pod without a label to get a node which can launch it. STEP: Explicitly delete pod here to free the resource it takes. Nov 13 01:51:09.562: INFO: found a healthy node: node2 [It] runs ReplicaSets to verify preemption running path [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 Nov 13 01:51:21.622: INFO: pods created so far: [1 1 1] Nov 13 01:51:21.622: INFO: length of pods created so far: 3 Nov 13 01:51:31.636: INFO: pods created so far: [2 2 1] [AfterEach] PreemptionExecutionPath /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:51:38.641: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-preemption-path-3872" for this suite. [AfterEach] PreemptionExecutionPath /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:462 [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:51:38.677: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-preemption-3339" for this suite. [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:78 • [SLOW TEST:93.301 seconds] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 PreemptionExecutionPath /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:451 runs ReplicaSets to verify preemption running path [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath runs ReplicaSets to verify preemption running path [Conformance]","total":17,"completed":7,"skipped":2862,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:51:38.720: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename daemonsets STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:135 [It] should rollback without unnecessary restarts [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 Nov 13 01:51:38.767: INFO: Create a RollingUpdate DaemonSet Nov 13 01:51:38.770: INFO: Check that daemon pods launch on every node of the cluster Nov 13 01:51:38.773: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:38.774: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:38.774: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:38.775: INFO: Number of nodes with available pods: 0 Nov 13 01:51:38.775: INFO: Node node1 is running more than one daemon pod Nov 13 01:51:39.781: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:39.781: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:39.781: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:39.784: INFO: Number of nodes with available pods: 0 Nov 13 01:51:39.784: INFO: Node node1 is running more than one daemon pod Nov 13 01:51:40.783: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:40.783: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:40.783: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:40.785: INFO: Number of nodes with available pods: 0 Nov 13 01:51:40.785: INFO: Node node1 is running more than one daemon pod Nov 13 01:51:41.823: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:41.823: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:41.823: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:41.825: INFO: Number of nodes with available pods: 0 Nov 13 01:51:41.825: INFO: Node node1 is running more than one daemon pod Nov 13 01:51:42.782: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:42.782: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:42.782: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:42.785: INFO: Number of nodes with available pods: 2 Nov 13 01:51:42.785: INFO: Number of running nodes: 2, number of available pods: 2 Nov 13 01:51:42.785: INFO: Update the DaemonSet to trigger a rollout Nov 13 01:51:42.794: INFO: Updating DaemonSet daemon-set Nov 13 01:51:46.809: INFO: Roll back the DaemonSet before rollout is complete Nov 13 01:51:46.816: INFO: Updating DaemonSet daemon-set Nov 13 01:51:46.816: INFO: Make sure DaemonSet rollback is complete Nov 13 01:51:46.819: INFO: Wrong image for pod: daemon-set-qrxvm. Expected: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1, got: foo:non-existent. Nov 13 01:51:46.819: INFO: Pod daemon-set-qrxvm is not available Nov 13 01:51:46.823: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:46.823: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:46.823: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:47.835: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:47.835: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:47.835: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:48.834: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:48.835: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:48.835: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:49.833: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:49.834: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:49.834: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:50.832: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:50.832: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:50.832: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:51.870: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:51.870: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:51.870: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:52.833: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:52.833: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:52.834: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:53.832: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:53.832: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:53.832: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:54.833: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:54.833: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:54.833: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:55.833: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:55.833: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:55.833: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:56.833: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:56.833: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:56.833: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:57.832: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:57.832: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:57.832: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:58.834: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:58.834: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:58.834: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:59.832: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:59.832: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:51:59.832: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:52:00.834: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:52:00.834: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:52:00.834: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:52:01.826: INFO: Pod daemon-set-5krgk is not available Nov 13 01:52:01.830: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:52:01.830: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:52:01.830: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:101 STEP: Deleting DaemonSet "daemon-set" STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-6248, will wait for the garbage collector to delete the pods Nov 13 01:52:01.921: INFO: Deleting DaemonSet.extensions daemon-set took: 31.318025ms Nov 13 01:52:02.021: INFO: Terminating DaemonSet.extensions daemon-set pods took: 100.124069ms Nov 13 01:52:11.524: INFO: Number of nodes with available pods: 0 Nov 13 01:52:11.524: INFO: Number of running nodes: 0, number of available pods: 0 Nov 13 01:52:11.530: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"resourceVersion":"105673"},"items":null} Nov 13 01:52:11.533: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"resourceVersion":"105673"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:52:11.543: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "daemonsets-6248" for this suite. • [SLOW TEST:32.833 seconds] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23 should rollback without unnecessary restarts [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]","total":17,"completed":8,"skipped":3031,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:52:11.556: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename daemonsets STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:135 [It] should run and stop complex daemon [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 Nov 13 01:52:11.598: INFO: Creating daemon "daemon-set" with a node selector STEP: Initially, daemon pods should not be running on any nodes. Nov 13 01:52:11.604: INFO: Number of nodes with available pods: 0 Nov 13 01:52:11.604: INFO: Number of running nodes: 0, number of available pods: 0 STEP: Change node label to blue, check that daemon pod is launched. Nov 13 01:52:11.626: INFO: Number of nodes with available pods: 0 Nov 13 01:52:11.626: INFO: Node node1 is running more than one daemon pod Nov 13 01:52:12.631: INFO: Number of nodes with available pods: 0 Nov 13 01:52:12.631: INFO: Node node1 is running more than one daemon pod Nov 13 01:52:13.629: INFO: Number of nodes with available pods: 0 Nov 13 01:52:13.629: INFO: Node node1 is running more than one daemon pod Nov 13 01:52:14.629: INFO: Number of nodes with available pods: 1 Nov 13 01:52:14.629: INFO: Number of running nodes: 1, number of available pods: 1 STEP: Update the node label to green, and wait for daemons to be unscheduled Nov 13 01:52:14.644: INFO: Number of nodes with available pods: 1 Nov 13 01:52:14.644: INFO: Number of running nodes: 0, number of available pods: 1 Nov 13 01:52:15.650: INFO: Number of nodes with available pods: 0 Nov 13 01:52:15.650: INFO: Number of running nodes: 0, number of available pods: 0 STEP: Update DaemonSet node selector to green, and change its update strategy to RollingUpdate Nov 13 01:52:15.658: INFO: Number of nodes with available pods: 0 Nov 13 01:52:15.658: INFO: Node node1 is running more than one daemon pod Nov 13 01:52:16.661: INFO: Number of nodes with available pods: 0 Nov 13 01:52:16.661: INFO: Node node1 is running more than one daemon pod Nov 13 01:52:17.663: INFO: Number of nodes with available pods: 0 Nov 13 01:52:17.663: INFO: Node node1 is running more than one daemon pod Nov 13 01:52:18.662: INFO: Number of nodes with available pods: 0 Nov 13 01:52:18.662: INFO: Node node1 is running more than one daemon pod Nov 13 01:52:19.661: INFO: Number of nodes with available pods: 0 Nov 13 01:52:19.661: INFO: Node node1 is running more than one daemon pod Nov 13 01:52:20.662: INFO: Number of nodes with available pods: 1 Nov 13 01:52:20.662: INFO: Number of running nodes: 1, number of available pods: 1 [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:101 STEP: Deleting DaemonSet "daemon-set" STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-8203, will wait for the garbage collector to delete the pods Nov 13 01:52:20.724: INFO: Deleting DaemonSet.extensions daemon-set took: 4.211492ms Nov 13 01:52:20.825: INFO: Terminating DaemonSet.extensions daemon-set pods took: 100.854584ms Nov 13 01:52:31.429: INFO: Number of nodes with available pods: 0 Nov 13 01:52:31.429: INFO: Number of running nodes: 0, number of available pods: 0 Nov 13 01:52:31.435: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"resourceVersion":"105811"},"items":null} Nov 13 01:52:31.438: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"resourceVersion":"105811"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:52:31.457: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "daemonsets-8203" for this suite. • [SLOW TEST:19.908 seconds] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23 should run and stop complex daemon [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance]","total":17,"completed":9,"skipped":3254,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-storage] EmptyDir wrapper volumes should not cause race condition when used for configmaps [Serial] [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-storage] EmptyDir wrapper volumes /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:52:31.466: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename emptydir-wrapper STEP: Waiting for a default service account to be provisioned in namespace [It] should not cause race condition when used for configmaps [Serial] [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 STEP: Creating 50 configmaps STEP: Creating RC which spawns configmap-volume pods Nov 13 01:52:31.773: INFO: Pod name wrapped-volume-race-c7aab27f-2132-4b2b-b68f-5b3c8f81afdd: Found 3 pods out of 5 Nov 13 01:52:36.787: INFO: Pod name wrapped-volume-race-c7aab27f-2132-4b2b-b68f-5b3c8f81afdd: Found 5 pods out of 5 STEP: Ensuring each pod is running STEP: deleting ReplicationController wrapped-volume-race-c7aab27f-2132-4b2b-b68f-5b3c8f81afdd in namespace emptydir-wrapper-3801, will wait for the garbage collector to delete the pods Nov 13 01:52:50.869: INFO: Deleting ReplicationController wrapped-volume-race-c7aab27f-2132-4b2b-b68f-5b3c8f81afdd took: 4.656352ms Nov 13 01:52:50.969: INFO: Terminating ReplicationController wrapped-volume-race-c7aab27f-2132-4b2b-b68f-5b3c8f81afdd pods took: 100.600518ms STEP: Creating RC which spawns configmap-volume pods Nov 13 01:53:01.589: INFO: Pod name wrapped-volume-race-00488f6e-9740-40e1-b8fd-1e37158e334c: Found 0 pods out of 5 Nov 13 01:53:06.599: INFO: Pod name wrapped-volume-race-00488f6e-9740-40e1-b8fd-1e37158e334c: Found 5 pods out of 5 STEP: Ensuring each pod is running STEP: deleting ReplicationController wrapped-volume-race-00488f6e-9740-40e1-b8fd-1e37158e334c in namespace emptydir-wrapper-3801, will wait for the garbage collector to delete the pods Nov 13 01:53:24.682: INFO: Deleting ReplicationController wrapped-volume-race-00488f6e-9740-40e1-b8fd-1e37158e334c took: 4.605004ms Nov 13 01:53:24.783: INFO: Terminating ReplicationController wrapped-volume-race-00488f6e-9740-40e1-b8fd-1e37158e334c pods took: 100.757404ms STEP: Creating RC which spawns configmap-volume pods Nov 13 01:53:41.400: INFO: Pod name wrapped-volume-race-0126dde6-f062-4074-89e1-ea150756fb23: Found 0 pods out of 5 Nov 13 01:53:46.409: INFO: Pod name wrapped-volume-race-0126dde6-f062-4074-89e1-ea150756fb23: Found 5 pods out of 5 STEP: Ensuring each pod is running STEP: deleting ReplicationController wrapped-volume-race-0126dde6-f062-4074-89e1-ea150756fb23 in namespace emptydir-wrapper-3801, will wait for the garbage collector to delete the pods Nov 13 01:54:00.490: INFO: Deleting ReplicationController wrapped-volume-race-0126dde6-f062-4074-89e1-ea150756fb23 took: 6.329354ms Nov 13 01:54:00.591: INFO: Terminating ReplicationController wrapped-volume-race-0126dde6-f062-4074-89e1-ea150756fb23 pods took: 100.370495ms STEP: Cleaning up the configMaps [AfterEach] [sig-storage] EmptyDir wrapper volumes /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:54:11.665: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "emptydir-wrapper-3801" for this suite. • [SLOW TEST:100.207 seconds] [sig-storage] EmptyDir wrapper volumes /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/utils/framework.go:23 should not cause race condition when used for configmaps [Serial] [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-storage] EmptyDir wrapper volumes should not cause race condition when used for configmaps [Serial] [Conformance]","total":17,"completed":10,"skipped":3391,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:54:11.678: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename daemonsets STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:135 [It] should run and stop simple daemon [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 STEP: Creating simple DaemonSet "daemon-set" STEP: Check that daemon pods launch on every node of the cluster. Nov 13 01:54:11.732: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:11.732: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:11.732: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:11.737: INFO: Number of nodes with available pods: 0 Nov 13 01:54:11.737: INFO: Node node1 is running more than one daemon pod Nov 13 01:54:12.743: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:12.743: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:12.743: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:12.745: INFO: Number of nodes with available pods: 0 Nov 13 01:54:12.745: INFO: Node node1 is running more than one daemon pod Nov 13 01:54:13.743: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:13.743: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:13.743: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:13.746: INFO: Number of nodes with available pods: 0 Nov 13 01:54:13.746: INFO: Node node1 is running more than one daemon pod Nov 13 01:54:14.743: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:14.744: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:14.744: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:14.746: INFO: Number of nodes with available pods: 1 Nov 13 01:54:14.746: INFO: Node node1 is running more than one daemon pod Nov 13 01:54:15.745: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:15.745: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:15.745: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:15.748: INFO: Number of nodes with available pods: 2 Nov 13 01:54:15.748: INFO: Number of running nodes: 2, number of available pods: 2 STEP: Stop a daemon pod, check that the daemon pod is revived. Nov 13 01:54:15.763: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:15.763: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:15.763: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:15.766: INFO: Number of nodes with available pods: 1 Nov 13 01:54:15.766: INFO: Node node2 is running more than one daemon pod Nov 13 01:54:16.773: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:16.773: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:16.773: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:16.776: INFO: Number of nodes with available pods: 1 Nov 13 01:54:16.776: INFO: Node node2 is running more than one daemon pod Nov 13 01:54:17.773: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:17.773: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:17.773: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:17.775: INFO: Number of nodes with available pods: 1 Nov 13 01:54:17.775: INFO: Node node2 is running more than one daemon pod Nov 13 01:54:18.774: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:18.774: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:18.774: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:18.778: INFO: Number of nodes with available pods: 1 Nov 13 01:54:18.778: INFO: Node node2 is running more than one daemon pod Nov 13 01:54:19.773: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:19.773: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:19.773: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:19.776: INFO: Number of nodes with available pods: 1 Nov 13 01:54:19.776: INFO: Node node2 is running more than one daemon pod Nov 13 01:54:20.771: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:20.771: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:20.771: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:20.774: INFO: Number of nodes with available pods: 1 Nov 13 01:54:20.774: INFO: Node node2 is running more than one daemon pod Nov 13 01:54:21.772: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:21.772: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:21.772: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:21.774: INFO: Number of nodes with available pods: 1 Nov 13 01:54:21.774: INFO: Node node2 is running more than one daemon pod Nov 13 01:54:22.774: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:22.774: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:22.774: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:22.777: INFO: Number of nodes with available pods: 1 Nov 13 01:54:22.777: INFO: Node node2 is running more than one daemon pod Nov 13 01:54:23.773: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:23.773: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:23.774: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:23.777: INFO: Number of nodes with available pods: 1 Nov 13 01:54:23.777: INFO: Node node2 is running more than one daemon pod Nov 13 01:54:24.772: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:24.772: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:24.772: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:54:24.775: INFO: Number of nodes with available pods: 2 Nov 13 01:54:24.775: INFO: Number of running nodes: 2, number of available pods: 2 [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:101 STEP: Deleting DaemonSet "daemon-set" STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-754, will wait for the garbage collector to delete the pods Nov 13 01:54:24.836: INFO: Deleting DaemonSet.extensions daemon-set took: 5.473331ms Nov 13 01:54:24.937: INFO: Terminating DaemonSet.extensions daemon-set pods took: 100.210184ms Nov 13 01:54:31.540: INFO: Number of nodes with available pods: 0 Nov 13 01:54:31.540: INFO: Number of running nodes: 0, number of available pods: 0 Nov 13 01:54:31.543: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"resourceVersion":"107056"},"items":null} Nov 13 01:54:31.546: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"resourceVersion":"107056"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:54:31.557: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "daemonsets-754" for this suite. • [SLOW TEST:19.888 seconds] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23 should run and stop simple daemon [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-apps] Daemon set [Serial] should run and stop simple daemon [Conformance]","total":17,"completed":11,"skipped":3727,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPreemption [Serial] PriorityClass endpoints verify PriorityClass endpoints can be operated with different HTTP methods [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:54:31.574: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-preemption STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:90 Nov 13 01:54:31.607: INFO: Waiting up to 1m0s for all nodes to be ready Nov 13 01:55:31.672: INFO: Waiting for terminating namespaces to be deleted... [BeforeEach] PriorityClass endpoints /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:55:31.675: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-preemption-path STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] PriorityClass endpoints /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:679 [It] verify PriorityClass endpoints can be operated with different HTTP methods [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 Nov 13 01:55:31.712: INFO: PriorityClass.scheduling.k8s.io "p1" is invalid: Value: Forbidden: may not be changed in an update. Nov 13 01:55:31.726: INFO: PriorityClass.scheduling.k8s.io "p2" is invalid: Value: Forbidden: may not be changed in an update. [AfterEach] PriorityClass endpoints /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:55:31.738: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-preemption-path-8636" for this suite. [AfterEach] PriorityClass endpoints /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:693 [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:55:31.752: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-preemption-5524" for this suite. [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:78 • [SLOW TEST:60.215 seconds] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 PriorityClass endpoints /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:673 verify PriorityClass endpoints can be operated with different HTTP methods [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPreemption [Serial] PriorityClass endpoints verify PriorityClass endpoints can be operated with different HTTP methods [Conformance]","total":17,"completed":12,"skipped":4236,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-api-machinery] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:55:31.795: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename namespaces STEP: Waiting for a default service account to be provisioned in namespace [It] should ensure that all services are removed when a namespace is deleted [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 STEP: Creating a test namespace STEP: Waiting for a default service account to be provisioned in namespace STEP: Creating a service in the namespace STEP: Deleting the namespace STEP: Waiting for the namespace to be removed. STEP: Recreating the namespace STEP: Verifying there is no service in the namespace [AfterEach] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:55:37.866: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "namespaces-1217" for this suite. STEP: Destroying namespace "nsdeletetest-1371" for this suite. Nov 13 01:55:37.876: INFO: Namespace nsdeletetest-1371 was already deleted STEP: Destroying namespace "nsdeletetest-9830" for this suite. • [SLOW TEST:6.084 seconds] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23 should ensure that all services are removed when a namespace is deleted [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-api-machinery] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted [Conformance]","total":17,"completed":13,"skipped":4603,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-scheduling] SchedulerPreemption [Serial] validates basic preemption works [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:55:37.881: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename sched-preemption STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:90 Nov 13 01:55:37.919: INFO: Waiting up to 1m0s for all nodes to be ready Nov 13 01:56:37.971: INFO: Waiting for terminating namespaces to be deleted... [It] validates basic preemption works [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 STEP: Create pods that use 2/3 of node resources. Nov 13 01:56:37.998: INFO: Created pod: pod0-sched-preemption-low-priority Nov 13 01:56:38.018: INFO: Created pod: pod1-sched-preemption-medium-priority STEP: Wait for pods to be scheduled. STEP: Run a high priority pod that has same requirements as that of lower priority pod [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:57:00.054: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-preemption-5592" for this suite. [AfterEach] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:78 • [SLOW TEST:82.215 seconds] [sig-scheduling] SchedulerPreemption [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:40 validates basic preemption works [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-scheduling] SchedulerPreemption [Serial] validates basic preemption works [Conformance]","total":17,"completed":14,"skipped":4709,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:57:00.103: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename daemonsets STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:135 [It] should update pod when spec was updated and update strategy is RollingUpdate [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 Nov 13 01:57:00.146: INFO: Creating simple daemon set daemon-set STEP: Check that daemon pods launch on every node of the cluster. Nov 13 01:57:00.155: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:00.155: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:00.155: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:00.158: INFO: Number of nodes with available pods: 0 Nov 13 01:57:00.158: INFO: Node node1 is running more than one daemon pod Nov 13 01:57:01.163: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:01.163: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:01.163: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:01.166: INFO: Number of nodes with available pods: 0 Nov 13 01:57:01.166: INFO: Node node1 is running more than one daemon pod Nov 13 01:57:02.166: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:02.166: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:02.166: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:02.170: INFO: Number of nodes with available pods: 0 Nov 13 01:57:02.170: INFO: Node node1 is running more than one daemon pod Nov 13 01:57:03.163: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:03.163: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:03.163: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:03.167: INFO: Number of nodes with available pods: 2 Nov 13 01:57:03.167: INFO: Number of running nodes: 2, number of available pods: 2 STEP: Update daemon pods image. STEP: Check that daemon pods images are updated. Nov 13 01:57:03.189: INFO: Wrong image for pod: daemon-set-hr9cx. Expected: k8s.gcr.io/e2e-test-images/agnhost:2.32, got: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1. Nov 13 01:57:03.189: INFO: Wrong image for pod: daemon-set-x2fzz. Expected: k8s.gcr.io/e2e-test-images/agnhost:2.32, got: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1. Nov 13 01:57:03.193: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:03.193: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:03.193: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:04.196: INFO: Wrong image for pod: daemon-set-x2fzz. Expected: k8s.gcr.io/e2e-test-images/agnhost:2.32, got: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1. Nov 13 01:57:04.200: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:04.200: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:04.200: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:05.197: INFO: Wrong image for pod: daemon-set-x2fzz. Expected: k8s.gcr.io/e2e-test-images/agnhost:2.32, got: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1. Nov 13 01:57:05.200: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:05.200: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:05.200: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:06.200: INFO: Wrong image for pod: daemon-set-x2fzz. Expected: k8s.gcr.io/e2e-test-images/agnhost:2.32, got: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1. Nov 13 01:57:06.203: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:06.203: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:06.204: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:07.197: INFO: Wrong image for pod: daemon-set-x2fzz. Expected: k8s.gcr.io/e2e-test-images/agnhost:2.32, got: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1. Nov 13 01:57:07.201: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:07.201: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:07.201: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:08.197: INFO: Wrong image for pod: daemon-set-x2fzz. Expected: k8s.gcr.io/e2e-test-images/agnhost:2.32, got: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1. Nov 13 01:57:08.203: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:08.203: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:08.203: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:09.198: INFO: Wrong image for pod: daemon-set-x2fzz. Expected: k8s.gcr.io/e2e-test-images/agnhost:2.32, got: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1. Nov 13 01:57:09.201: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:09.201: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:09.201: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:10.199: INFO: Wrong image for pod: daemon-set-x2fzz. Expected: k8s.gcr.io/e2e-test-images/agnhost:2.32, got: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1. Nov 13 01:57:10.203: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:10.203: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:10.203: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:11.200: INFO: Wrong image for pod: daemon-set-x2fzz. Expected: k8s.gcr.io/e2e-test-images/agnhost:2.32, got: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1. Nov 13 01:57:11.205: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:11.205: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:11.205: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:12.201: INFO: Pod daemon-set-gxfcl is not available Nov 13 01:57:12.201: INFO: Wrong image for pod: daemon-set-x2fzz. Expected: k8s.gcr.io/e2e-test-images/agnhost:2.32, got: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1. Nov 13 01:57:12.207: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:12.207: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:12.207: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:13.198: INFO: Pod daemon-set-gxfcl is not available Nov 13 01:57:13.198: INFO: Wrong image for pod: daemon-set-x2fzz. Expected: k8s.gcr.io/e2e-test-images/agnhost:2.32, got: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1. Nov 13 01:57:13.202: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:13.203: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:13.203: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:14.200: INFO: Pod daemon-set-gxfcl is not available Nov 13 01:57:14.200: INFO: Wrong image for pod: daemon-set-x2fzz. Expected: k8s.gcr.io/e2e-test-images/agnhost:2.32, got: k8s.gcr.io/e2e-test-images/httpd:2.4.38-1. Nov 13 01:57:14.205: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:14.205: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:14.205: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:15.204: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:15.204: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:15.205: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:16.203: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:16.204: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:16.204: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:17.203: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:17.203: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:17.203: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:18.202: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:18.202: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:18.202: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:19.204: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:19.204: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:19.205: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:20.203: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:20.204: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:20.204: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:21.203: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:21.203: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:21.203: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:22.197: INFO: Pod daemon-set-9xwn7 is not available Nov 13 01:57:22.201: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:22.201: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:22.201: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node STEP: Check that daemon pods are still running on every node of the cluster. Nov 13 01:57:22.205: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:22.205: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:22.205: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:22.208: INFO: Number of nodes with available pods: 1 Nov 13 01:57:22.208: INFO: Node node2 is running more than one daemon pod Nov 13 01:57:23.212: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:23.213: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:23.213: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:23.216: INFO: Number of nodes with available pods: 1 Nov 13 01:57:23.216: INFO: Node node2 is running more than one daemon pod Nov 13 01:57:24.216: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:24.216: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:24.216: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:24.219: INFO: Number of nodes with available pods: 1 Nov 13 01:57:24.219: INFO: Node node2 is running more than one daemon pod Nov 13 01:57:25.214: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:25.214: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:25.214: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:25.218: INFO: Number of nodes with available pods: 2 Nov 13 01:57:25.218: INFO: Number of running nodes: 2, number of available pods: 2 [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:101 STEP: Deleting DaemonSet "daemon-set" STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-1104, will wait for the garbage collector to delete the pods Nov 13 01:57:25.288: INFO: Deleting DaemonSet.extensions daemon-set took: 4.761331ms Nov 13 01:57:25.388: INFO: Terminating DaemonSet.extensions daemon-set pods took: 100.818178ms Nov 13 01:57:31.492: INFO: Number of nodes with available pods: 0 Nov 13 01:57:31.492: INFO: Number of running nodes: 0, number of available pods: 0 Nov 13 01:57:31.495: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"resourceVersion":"107797"},"items":null} Nov 13 01:57:31.496: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"resourceVersion":"107797"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:57:31.507: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "daemonsets-1104" for this suite. • [SLOW TEST:31.414 seconds] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23 should update pod when spec was updated and update strategy is RollingUpdate [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-apps] Daemon set [Serial] should update pod when spec was updated and update strategy is RollingUpdate [Conformance]","total":17,"completed":15,"skipped":5202,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-apps] Daemon set [Serial] should retry creating failed daemon pods [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:57:31.521: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename daemonsets STEP: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:135 [It] should retry creating failed daemon pods [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 STEP: Creating a simple DaemonSet "daemon-set" STEP: Check that daemon pods launch on every node of the cluster. Nov 13 01:57:31.565: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:31.565: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:31.565: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:31.567: INFO: Number of nodes with available pods: 0 Nov 13 01:57:31.567: INFO: Node node1 is running more than one daemon pod Nov 13 01:57:32.571: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:32.572: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:32.572: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:32.575: INFO: Number of nodes with available pods: 0 Nov 13 01:57:32.575: INFO: Node node1 is running more than one daemon pod Nov 13 01:57:33.572: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:33.572: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:33.573: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:33.576: INFO: Number of nodes with available pods: 0 Nov 13 01:57:33.576: INFO: Node node1 is running more than one daemon pod Nov 13 01:57:34.573: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:34.573: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:34.573: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:34.576: INFO: Number of nodes with available pods: 2 Nov 13 01:57:34.576: INFO: Number of running nodes: 2, number of available pods: 2 STEP: Set a daemon pod's phase to 'Failed', check that the daemon pod is revived. Nov 13 01:57:34.590: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:34.590: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:34.590: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:34.592: INFO: Number of nodes with available pods: 1 Nov 13 01:57:34.592: INFO: Node node1 is running more than one daemon pod Nov 13 01:57:35.598: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:35.598: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:35.598: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:35.601: INFO: Number of nodes with available pods: 1 Nov 13 01:57:35.601: INFO: Node node1 is running more than one daemon pod Nov 13 01:57:36.600: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:36.601: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:36.601: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:36.603: INFO: Number of nodes with available pods: 1 Nov 13 01:57:36.603: INFO: Node node1 is running more than one daemon pod Nov 13 01:57:37.598: INFO: DaemonSet pods can't tolerate node master1 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:37.598: INFO: DaemonSet pods can't tolerate node master2 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:37.598: INFO: DaemonSet pods can't tolerate node master3 with taints [{Key:node-role.kubernetes.io/master Value: Effect:NoSchedule TimeAdded:}], skip checking this node Nov 13 01:57:37.601: INFO: Number of nodes with available pods: 2 Nov 13 01:57:37.601: INFO: Number of running nodes: 2, number of available pods: 2 STEP: Wait for the failed daemon pod to be completely deleted. [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:101 STEP: Deleting DaemonSet "daemon-set" STEP: deleting DaemonSet.extensions daemon-set in namespace daemonsets-1909, will wait for the garbage collector to delete the pods Nov 13 01:57:37.663: INFO: Deleting DaemonSet.extensions daemon-set took: 4.366011ms Nov 13 01:57:37.764: INFO: Terminating DaemonSet.extensions daemon-set pods took: 100.934152ms Nov 13 01:57:41.467: INFO: Number of nodes with available pods: 0 Nov 13 01:57:41.467: INFO: Number of running nodes: 0, number of available pods: 0 Nov 13 01:57:41.469: INFO: daemonset: {"kind":"DaemonSetList","apiVersion":"apps/v1","metadata":{"resourceVersion":"107923"},"items":null} Nov 13 01:57:41.472: INFO: pods: {"kind":"PodList","apiVersion":"v1","metadata":{"resourceVersion":"107923"},"items":null} [AfterEach] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:57:41.483: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "daemonsets-1909" for this suite. • [SLOW TEST:9.972 seconds] [sig-apps] Daemon set [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23 should retry creating failed daemon pods [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-apps] Daemon set [Serial] should retry creating failed daemon pods [Conformance]","total":17,"completed":16,"skipped":5416,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ [sig-api-machinery] Namespaces [Serial] should ensure that all pods are removed when a namespace is deleted [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 [BeforeEach] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185 STEP: Creating a kubernetes client Nov 13 01:57:41.495: INFO: >>> kubeConfig: /root/.kube/config STEP: Building a namespace api object, basename namespaces STEP: Waiting for a default service account to be provisioned in namespace [It] should ensure that all pods are removed when a namespace is deleted [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 STEP: Creating a test namespace STEP: Waiting for a default service account to be provisioned in namespace STEP: Creating a pod in the namespace STEP: Waiting for the pod to have running status STEP: Deleting the namespace STEP: Waiting for the namespace to be removed. STEP: Recreating the namespace STEP: Verifying there are no pods in the namespace [AfterEach] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186 Nov 13 01:58:12.587: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "namespaces-4829" for this suite. STEP: Destroying namespace "nsdeletetest-2880" for this suite. Nov 13 01:58:12.597: INFO: Namespace nsdeletetest-2880 was already deleted STEP: Destroying namespace "nsdeletetest-2557" for this suite. • [SLOW TEST:31.106 seconds] [sig-api-machinery] Namespaces [Serial] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23 should ensure that all pods are removed when a namespace is deleted [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630 ------------------------------ {"msg":"PASSED [sig-api-machinery] Namespaces [Serial] should ensure that all pods are removed when a namespace is deleted [Conformance]","total":17,"completed":17,"skipped":5637,"failed":0} SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSNov 13 01:58:12.603: INFO: Running AfterSuite actions on all nodes Nov 13 01:58:12.603: INFO: Running AfterSuite actions on node 1 Nov 13 01:58:12.603: INFO: Skipping dumping logs from cluster JUnit report was created: /home/opnfv/functest/results/k8s_conformance_serial/junit_01.xml {"msg":"Test Suite completed","total":17,"completed":17,"skipped":5753,"failed":0} Ran 17 of 5770 Specs in 898.345 seconds SUCCESS! -- 17 Passed | 0 Failed | 0 Pending | 5753 Skipped PASS Ginkgo ran 1 suite in 14m59.788576367s Test Suite Passed