This job view page is being replaced by Spyglass soon. Check out the new job view.
Resultfailure
Tests 0 failed / 7 succeeded
Started2022-09-07 00:41
Elapsed1h6m
Revision
uploadercrier

No Test Failures!


Show 7 Passed Tests

Show 20 Skipped Tests

Error lines from build-log.txt

... skipping 900 lines ...
Status: Downloaded newer image for quay.io/jetstack/cert-manager-controller:v1.9.1
quay.io/jetstack/cert-manager-controller:v1.9.1
+ export GINKGO_NODES=3
+ GINKGO_NODES=3
+ export GINKGO_NOCOLOR=true
+ GINKGO_NOCOLOR=true
+ export GINKGO_ARGS=--fail-fast
+ GINKGO_ARGS=--fail-fast
+ export E2E_CONF_FILE=/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/config/docker.yaml
+ E2E_CONF_FILE=/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/config/docker.yaml
+ export ARTIFACTS=/logs/artifacts
+ ARTIFACTS=/logs/artifacts
+ export SKIP_RESOURCE_CLEANUP=false
+ SKIP_RESOURCE_CLEANUP=false
... skipping 79 lines ...
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-kcp-scale-in --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-kcp-scale-in.yaml
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-ipv6 --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-ipv6.yaml
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-topology --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-topology.yaml
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-ignition --load-restrictor LoadRestrictionsNone > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/infrastructure-docker/v1beta1/cluster-template-ignition.yaml
mkdir -p /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/test-extension
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/kustomize-v4.5.2 build /home/prow/go/src/sigs.k8s.io/cluster-api/test/extension/config/default > /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/data/test-extension/deployment.yaml
/home/prow/go/src/sigs.k8s.io/cluster-api/hack/tools/bin/ginkgo-v2.1.4 -v --trace --tags=e2e --focus="\[K8s-Upgrade\]"  --nodes=3 --no-color=true --output-dir="/logs/artifacts" --junit-report="junit.e2e_suite.1.xml" --fail-fast . -- \
    -e2e.artifacts-folder="/logs/artifacts" \
    -e2e.config="/home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/config/docker.yaml" \
    -e2e.skip-resource-cleanup=false -e2e.use-existing-cluster=false
go: downloading github.com/onsi/gomega v1.20.0
go: downloading github.com/blang/semver v3.5.1+incompatible
go: downloading k8s.io/apimachinery v0.24.2
... skipping 229 lines ...
    kubeadmconfig.bootstrap.cluster.x-k8s.io/k8s-upgrade-and-conformance-7r78ik-mp-0-config created
    kubeadmconfig.bootstrap.cluster.x-k8s.io/k8s-upgrade-and-conformance-7r78ik-mp-0-config-cgroupfs created
    cluster.cluster.x-k8s.io/k8s-upgrade-and-conformance-7r78ik created
    machinepool.cluster.x-k8s.io/k8s-upgrade-and-conformance-7r78ik-mp-0 created
    dockermachinepool.infrastructure.cluster.x-k8s.io/k8s-upgrade-and-conformance-7r78ik-dmp-0 created

    Failed to get logs for Machine k8s-upgrade-and-conformance-7r78ik-4tllz-mbf7x, Cluster k8s-upgrade-and-conformance-8u5qlk/k8s-upgrade-and-conformance-7r78ik: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4, Cluster k8s-upgrade-and-conformance-8u5qlk/k8s-upgrade-and-conformance-7r78ik: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-h877k, Cluster k8s-upgrade-and-conformance-8u5qlk/k8s-upgrade-and-conformance-7r78ik: exit status 2
    Failed to get logs for MachinePool k8s-upgrade-and-conformance-7r78ik-mp-0, Cluster k8s-upgrade-and-conformance-8u5qlk/k8s-upgrade-and-conformance-7r78ik: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "k8s-upgrade-and-conformance" test spec 09/07/22 00:50:44.3
    INFO: Creating namespace k8s-upgrade-and-conformance-8u5qlk
    INFO: Creating event watcher for namespace "k8s-upgrade-and-conformance-8u5qlk"
... skipping 41 lines ...
    
    Running in parallel across 4 nodes
    
    Sep  7 01:01:49.039: INFO: >>> kubeConfig: /tmp/kubeconfig
    Sep  7 01:01:49.041: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
    Sep  7 01:01:49.059: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
    Sep  7 01:01:49.099: INFO: The status of Pod coredns-f9fd979d6-kqmrf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:49.099: INFO: The status of Pod coredns-f9fd979d6-vskv2 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:49.099: INFO: The status of Pod kindnet-ffc6b is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:49.099: INFO: The status of Pod kindnet-zsdcf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:49.099: INFO: The status of Pod kube-proxy-qqccj is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:49.099: INFO: The status of Pod kube-proxy-sdzn7 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:49.099: INFO: 14 / 20 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
    Sep  7 01:01:49.099: INFO: expected 2 pod replicas in namespace 'kube-system', 0 are Running and Ready.
    Sep  7 01:01:49.099: INFO: POD                      NODE                                              PHASE    GRACE  CONDITIONS
    Sep  7 01:01:49.099: INFO: coredns-f9fd979d6-kqmrf  k8s-upgrade-and-conformance-7r78ik-worker-oyd2sy  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:08 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:12 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:08 +0000 UTC  }]
    Sep  7 01:01:49.099: INFO: coredns-f9fd979d6-vskv2  k8s-upgrade-and-conformance-7r78ik-worker-s09xwa  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:11 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:14 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:11 +0000 UTC  }]
    Sep  7 01:01:49.099: INFO: kindnet-ffc6b            k8s-upgrade-and-conformance-7r78ik-worker-oyd2sy  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:45 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:53:03 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:41 +0000 UTC  }]
    Sep  7 01:01:49.099: INFO: kindnet-zsdcf            k8s-upgrade-and-conformance-7r78ik-worker-s09xwa  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:43 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:25 +0000 UTC  }]
    Sep  7 01:01:49.099: INFO: kube-proxy-qqccj         k8s-upgrade-and-conformance-7r78ik-worker-s09xwa  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:35 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:38 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:35 +0000 UTC  }]
    Sep  7 01:01:49.099: INFO: kube-proxy-sdzn7         k8s-upgrade-and-conformance-7r78ik-worker-oyd2sy  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:08 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:11 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:08 +0000 UTC  }]
    Sep  7 01:01:49.099: INFO: 
    Sep  7 01:01:51.119: INFO: The status of Pod coredns-f9fd979d6-kqmrf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:51.119: INFO: The status of Pod coredns-f9fd979d6-vskv2 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:51.119: INFO: The status of Pod kindnet-ffc6b is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:51.119: INFO: The status of Pod kindnet-zsdcf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:51.119: INFO: The status of Pod kube-proxy-qqccj is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:51.119: INFO: The status of Pod kube-proxy-sdzn7 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:51.119: INFO: 14 / 20 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
    Sep  7 01:01:51.119: INFO: expected 2 pod replicas in namespace 'kube-system', 0 are Running and Ready.
    Sep  7 01:01:51.119: INFO: POD                      NODE                                              PHASE    GRACE  CONDITIONS
    Sep  7 01:01:51.119: INFO: coredns-f9fd979d6-kqmrf  k8s-upgrade-and-conformance-7r78ik-worker-oyd2sy  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:08 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:12 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:08 +0000 UTC  }]
    Sep  7 01:01:51.119: INFO: coredns-f9fd979d6-vskv2  k8s-upgrade-and-conformance-7r78ik-worker-s09xwa  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:11 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:14 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:11 +0000 UTC  }]
    Sep  7 01:01:51.119: INFO: kindnet-ffc6b            k8s-upgrade-and-conformance-7r78ik-worker-oyd2sy  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:45 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:53:03 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:41 +0000 UTC  }]
    Sep  7 01:01:51.119: INFO: kindnet-zsdcf            k8s-upgrade-and-conformance-7r78ik-worker-s09xwa  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:43 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:25 +0000 UTC  }]
    Sep  7 01:01:51.119: INFO: kube-proxy-qqccj         k8s-upgrade-and-conformance-7r78ik-worker-s09xwa  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:35 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:38 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:35 +0000 UTC  }]
    Sep  7 01:01:51.119: INFO: kube-proxy-sdzn7         k8s-upgrade-and-conformance-7r78ik-worker-oyd2sy  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:08 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:11 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:08 +0000 UTC  }]
    Sep  7 01:01:51.119: INFO: 
    Sep  7 01:01:53.119: INFO: The status of Pod coredns-f9fd979d6-kqmrf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:53.119: INFO: The status of Pod coredns-f9fd979d6-vskv2 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:53.119: INFO: The status of Pod kindnet-ffc6b is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:53.119: INFO: The status of Pod kindnet-zsdcf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:53.119: INFO: The status of Pod kube-proxy-qqccj is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:53.119: INFO: The status of Pod kube-proxy-sdzn7 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:53.119: INFO: 14 / 20 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
    Sep  7 01:01:53.119: INFO: expected 2 pod replicas in namespace 'kube-system', 0 are Running and Ready.
    Sep  7 01:01:53.119: INFO: POD                      NODE                                              PHASE    GRACE  CONDITIONS
    Sep  7 01:01:53.119: INFO: coredns-f9fd979d6-kqmrf  k8s-upgrade-and-conformance-7r78ik-worker-oyd2sy  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:08 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:12 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:08 +0000 UTC  }]
    Sep  7 01:01:53.119: INFO: coredns-f9fd979d6-vskv2  k8s-upgrade-and-conformance-7r78ik-worker-s09xwa  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:11 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:14 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:11 +0000 UTC  }]
    Sep  7 01:01:53.119: INFO: kindnet-ffc6b            k8s-upgrade-and-conformance-7r78ik-worker-oyd2sy  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:45 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:53:03 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:41 +0000 UTC  }]
    Sep  7 01:01:53.119: INFO: kindnet-zsdcf            k8s-upgrade-and-conformance-7r78ik-worker-s09xwa  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:28 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:43 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:52:25 +0000 UTC  }]
    Sep  7 01:01:53.119: INFO: kube-proxy-qqccj         k8s-upgrade-and-conformance-7r78ik-worker-s09xwa  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:35 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:38 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:58:35 +0000 UTC  }]
    Sep  7 01:01:53.119: INFO: kube-proxy-sdzn7         k8s-upgrade-and-conformance-7r78ik-worker-oyd2sy  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:08 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:00:54 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:11 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 00:59:08 +0000 UTC  }]
    Sep  7 01:01:53.119: INFO: 
    Sep  7 01:01:55.132: INFO: The status of Pod coredns-f9fd979d6-7lzbz is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:55.132: INFO: The status of Pod coredns-f9fd979d6-jngwk is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:55.132: INFO: 14 / 16 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
    Sep  7 01:01:55.132: INFO: expected 2 pod replicas in namespace 'kube-system', 0 are Running and Ready.
    Sep  7 01:01:55.132: INFO: POD                      NODE                                              PHASE    GRACE  CONDITIONS
    Sep  7 01:01:55.132: INFO: coredns-f9fd979d6-7lzbz  k8s-upgrade-and-conformance-7r78ik-worker-ynukn0  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  }]
    Sep  7 01:01:55.132: INFO: coredns-f9fd979d6-jngwk  k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  }]
    Sep  7 01:01:55.132: INFO: 
    Sep  7 01:01:57.116: INFO: The status of Pod coredns-f9fd979d6-7lzbz is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:57.116: INFO: The status of Pod coredns-f9fd979d6-jngwk is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:57.116: INFO: 14 / 16 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
    Sep  7 01:01:57.116: INFO: expected 2 pod replicas in namespace 'kube-system', 0 are Running and Ready.
    Sep  7 01:01:57.116: INFO: POD                      NODE                                              PHASE    GRACE  CONDITIONS
    Sep  7 01:01:57.116: INFO: coredns-f9fd979d6-7lzbz  k8s-upgrade-and-conformance-7r78ik-worker-ynukn0  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  }]
    Sep  7 01:01:57.116: INFO: coredns-f9fd979d6-jngwk  k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  }]
    Sep  7 01:01:57.116: INFO: 
    Sep  7 01:01:59.117: INFO: The status of Pod coredns-f9fd979d6-7lzbz is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:59.117: INFO: The status of Pod coredns-f9fd979d6-jngwk is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:01:59.117: INFO: 14 / 16 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
    Sep  7 01:01:59.117: INFO: expected 2 pod replicas in namespace 'kube-system', 0 are Running and Ready.
    Sep  7 01:01:59.117: INFO: POD                      NODE                                              PHASE    GRACE  CONDITIONS
    Sep  7 01:01:59.117: INFO: coredns-f9fd979d6-7lzbz  k8s-upgrade-and-conformance-7r78ik-worker-ynukn0  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  }]
    Sep  7 01:01:59.117: INFO: coredns-f9fd979d6-jngwk  k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  }]
    Sep  7 01:01:59.117: INFO: 
    Sep  7 01:02:01.114: INFO: The status of Pod coredns-f9fd979d6-7lzbz is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:02:01.114: INFO: The status of Pod coredns-f9fd979d6-jngwk is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  7 01:02:01.114: INFO: 14 / 16 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
    Sep  7 01:02:01.114: INFO: expected 2 pod replicas in namespace 'kube-system', 0 are Running and Ready.
    Sep  7 01:02:01.114: INFO: POD                      NODE                                              PHASE    GRACE  CONDITIONS
    Sep  7 01:02:01.114: INFO: coredns-f9fd979d6-7lzbz  k8s-upgrade-and-conformance-7r78ik-worker-ynukn0  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  }]
    Sep  7 01:02:01.114: INFO: coredns-f9fd979d6-jngwk  k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC ContainersNotReady containers with unready status: [coredns]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-07 01:01:54 +0000 UTC  }]
    Sep  7 01:02:01.114: INFO: 
... skipping 41 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:03.290: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-8278" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Events should ensure that an event can be fetched, patched, deleted, and listed [Conformance]","total":-1,"completed":1,"skipped":10,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:07.316: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-823" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Pods should get a host IP [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":26,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Events
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 15 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:07.481: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-6186" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Events should delete a collection of events [Conformance]","total":-1,"completed":2,"skipped":28,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    Sep  7 01:02:03.178: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating secret with name secret-test-814e832d-9397-494a-8308-c5f4794c3668
    STEP: Creating a pod to test consume secrets
    Sep  7 01:02:03.193: INFO: Waiting up to 5m0s for pod "pod-secrets-cbbd5406-d4a4-49d8-a4e4-de9a7590f021" in namespace "secrets-5364" to be "Succeeded or Failed"

    Sep  7 01:02:03.197: INFO: Pod "pod-secrets-cbbd5406-d4a4-49d8-a4e4-de9a7590f021": Phase="Pending", Reason="", readiness=false. Elapsed: 3.366669ms
    Sep  7 01:02:05.208: INFO: Pod "pod-secrets-cbbd5406-d4a4-49d8-a4e4-de9a7590f021": Phase="Pending", Reason="", readiness=false. Elapsed: 2.014727324s
    Sep  7 01:02:07.214: INFO: Pod "pod-secrets-cbbd5406-d4a4-49d8-a4e4-de9a7590f021": Phase="Pending", Reason="", readiness=false. Elapsed: 4.02089282s
    Sep  7 01:02:09.290: INFO: Pod "pod-secrets-cbbd5406-d4a4-49d8-a4e4-de9a7590f021": Phase="Pending", Reason="", readiness=false. Elapsed: 6.096731818s
    Sep  7 01:02:11.302: INFO: Pod "pod-secrets-cbbd5406-d4a4-49d8-a4e4-de9a7590f021": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.108807916s
    STEP: Saw pod success
    Sep  7 01:02:11.302: INFO: Pod "pod-secrets-cbbd5406-d4a4-49d8-a4e4-de9a7590f021" satisfied condition "Succeeded or Failed"

    Sep  7 01:02:11.309: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-secrets-cbbd5406-d4a4-49d8-a4e4-de9a7590f021 container secret-volume-test: <nil>
    STEP: delete the pod
    Sep  7 01:02:11.355: INFO: Waiting for pod pod-secrets-cbbd5406-d4a4-49d8-a4e4-de9a7590f021 to disappear
    Sep  7 01:02:11.363: INFO: Pod pod-secrets-cbbd5406-d4a4-49d8-a4e4-de9a7590f021 no longer exists
    [AfterEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:11.364: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-5364" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Secrets should be consumable from pods in volume [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":0,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:11.545: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-7240" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] ConfigMap should run through a ConfigMap lifecycle [Conformance]","total":-1,"completed":2,"skipped":4,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:11.795: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-789" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Secrets should patch a secret [Conformance]","total":-1,"completed":3,"skipped":41,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Container Runtime
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 13 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:12.670: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-runtime-7682" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Container Runtime blackbox test on terminated container should report termination message [LinuxOnly] from file when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":64,"failed":0}

    
    SSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Kubelet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 10 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:15.955: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubelet-test-8982" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Kubelet when scheduling a busybox command that always fails in a pod should have an terminated reason [NodeConformance] [Conformance]","total":-1,"completed":4,"skipped":50,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:02:16.061: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should fail to create ConfigMap with empty key [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap that has name configmap-test-emptyKey-281fca62-3cc2-4ddb-b970-8d318f8961ec
    [AfterEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:16.155: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-9687" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] ConfigMap should fail to create ConfigMap with empty key [Conformance]","total":-1,"completed":5,"skipped":77,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] InitContainer [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 10 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:17.838: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "init-container-3496" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] InitContainer [NodeConformance] should invoke init containers on a RestartNever pod [Conformance]","total":-1,"completed":3,"skipped":77,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 30 lines ...
    STEP: Destroying namespace "webhook-6218-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]","total":-1,"completed":3,"skipped":67,"failed":0}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Downward API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:02:16.565: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename downward-api
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should provide default limits.cpu/memory from node allocatable [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward api env vars
    Sep  7 01:02:16.650: INFO: Waiting up to 5m0s for pod "downward-api-cc20412e-3c75-4471-929f-d9ce7badec03" in namespace "downward-api-7992" to be "Succeeded or Failed"

    Sep  7 01:02:16.657: INFO: Pod "downward-api-cc20412e-3c75-4471-929f-d9ce7badec03": Phase="Pending", Reason="", readiness=false. Elapsed: 6.329159ms
    Sep  7 01:02:18.662: INFO: Pod "downward-api-cc20412e-3c75-4471-929f-d9ce7badec03": Phase="Running", Reason="", readiness=true. Elapsed: 2.01177294s
    Sep  7 01:02:20.671: INFO: Pod "downward-api-cc20412e-3c75-4471-929f-d9ce7badec03": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.020185345s
    STEP: Saw pod success
    Sep  7 01:02:20.671: INFO: Pod "downward-api-cc20412e-3c75-4471-929f-d9ce7badec03" satisfied condition "Succeeded or Failed"

    Sep  7 01:02:20.679: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod downward-api-cc20412e-3c75-4471-929f-d9ce7badec03 container dapi-container: <nil>
    STEP: delete the pod
    Sep  7 01:02:20.756: INFO: Waiting for pod downward-api-cc20412e-3c75-4471-929f-d9ce7badec03 to disappear
    Sep  7 01:02:20.771: INFO: Pod downward-api-cc20412e-3c75-4471-929f-d9ce7badec03 no longer exists
    [AfterEach] [sig-node] Downward API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:20.771: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-7992" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Downward API should provide default limits.cpu/memory from node allocatable [NodeConformance] [Conformance]","total":-1,"completed":6,"skipped":215,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 17 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:23.460: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "dns-3958" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] DNS should support configurable pod DNS nameservers [Conformance]","total":-1,"completed":7,"skipped":219,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:41
    [It] should provide node allocatable (cpu) as default cpu limit if the limit is not set [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward API volume plugin
    Sep  7 01:02:18.230: INFO: Waiting up to 5m0s for pod "downwardapi-volume-eb0e8dd6-f8f8-4fcb-b3b2-e7a88b0bc078" in namespace "projected-2854" to be "Succeeded or Failed"

    Sep  7 01:02:18.250: INFO: Pod "downwardapi-volume-eb0e8dd6-f8f8-4fcb-b3b2-e7a88b0bc078": Phase="Pending", Reason="", readiness=false. Elapsed: 19.608683ms
    Sep  7 01:02:20.271: INFO: Pod "downwardapi-volume-eb0e8dd6-f8f8-4fcb-b3b2-e7a88b0bc078": Phase="Pending", Reason="", readiness=false. Elapsed: 2.040253084s
    Sep  7 01:02:22.279: INFO: Pod "downwardapi-volume-eb0e8dd6-f8f8-4fcb-b3b2-e7a88b0bc078": Phase="Pending", Reason="", readiness=false. Elapsed: 4.048613404s
    Sep  7 01:02:24.285: INFO: Pod "downwardapi-volume-eb0e8dd6-f8f8-4fcb-b3b2-e7a88b0bc078": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.054542195s
    STEP: Saw pod success
    Sep  7 01:02:24.285: INFO: Pod "downwardapi-volume-eb0e8dd6-f8f8-4fcb-b3b2-e7a88b0bc078" satisfied condition "Succeeded or Failed"

    Sep  7 01:02:24.292: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod downwardapi-volume-eb0e8dd6-f8f8-4fcb-b3b2-e7a88b0bc078 container client-container: <nil>
    STEP: delete the pod
    Sep  7 01:02:24.338: INFO: Waiting for pod downwardapi-volume-eb0e8dd6-f8f8-4fcb-b3b2-e7a88b0bc078 to disappear
    Sep  7 01:02:24.343: INFO: Pod downwardapi-volume-eb0e8dd6-f8f8-4fcb-b3b2-e7a88b0bc078 no longer exists
    [AfterEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:24.344: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-2854" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should provide node allocatable (cpu) as default cpu limit if the limit is not set [NodeConformance] [Conformance]","total":-1,"completed":4,"skipped":103,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] PodTemplates
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 6 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:24.530: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "podtemplate-1066" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] PodTemplates should run the lifecycle of PodTemplates [Conformance]","total":-1,"completed":5,"skipped":112,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:02:23.976: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename projected
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with defaultMode set [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap with name projected-configmap-test-volume-0539ac5f-9f92-4add-9c96-207bd9b1ddbf
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:02:24.076: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-bb606b9a-7e47-41b3-b0dc-71c11c68a40d" in namespace "projected-1899" to be "Succeeded or Failed"

    Sep  7 01:02:24.081: INFO: Pod "pod-projected-configmaps-bb606b9a-7e47-41b3-b0dc-71c11c68a40d": Phase="Pending", Reason="", readiness=false. Elapsed: 5.451811ms
    Sep  7 01:02:26.088: INFO: Pod "pod-projected-configmaps-bb606b9a-7e47-41b3-b0dc-71c11c68a40d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.012445628s
    STEP: Saw pod success
    Sep  7 01:02:26.088: INFO: Pod "pod-projected-configmaps-bb606b9a-7e47-41b3-b0dc-71c11c68a40d" satisfied condition "Succeeded or Failed"

    Sep  7 01:02:26.100: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-projected-configmaps-bb606b9a-7e47-41b3-b0dc-71c11c68a40d container agnhost-container: <nil>
    STEP: delete the pod
    Sep  7 01:02:26.143: INFO: Waiting for pod pod-projected-configmaps-bb606b9a-7e47-41b3-b0dc-71c11c68a40d to disappear
    Sep  7 01:02:26.152: INFO: Pod pod-projected-configmaps-bb606b9a-7e47-41b3-b0dc-71c11c68a40d no longer exists
    [AfterEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:26.152: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-1899" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap should be consumable from pods in volume with defaultMode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":8,"skipped":304,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] Deployment
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 46 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:28.560: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-2127" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment deployment should support rollover [Conformance]","total":-1,"completed":1,"skipped":0,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [k8s.io] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:02:26.369: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename security-context-test
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [k8s.io] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:41
    [It] should run the container as unprivileged when false [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    Sep  7 01:02:26.447: INFO: Waiting up to 5m0s for pod "busybox-privileged-false-71e376d1-1e4a-46a8-8fc9-378d1c318a85" in namespace "security-context-test-7558" to be "Succeeded or Failed"

    Sep  7 01:02:26.459: INFO: Pod "busybox-privileged-false-71e376d1-1e4a-46a8-8fc9-378d1c318a85": Phase="Pending", Reason="", readiness=false. Elapsed: 12.685761ms
    Sep  7 01:02:28.495: INFO: Pod "busybox-privileged-false-71e376d1-1e4a-46a8-8fc9-378d1c318a85": Phase="Pending", Reason="", readiness=false. Elapsed: 2.048174212s
    Sep  7 01:02:30.502: INFO: Pod "busybox-privileged-false-71e376d1-1e4a-46a8-8fc9-378d1c318a85": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.055602123s
    Sep  7 01:02:30.502: INFO: Pod "busybox-privileged-false-71e376d1-1e4a-46a8-8fc9-378d1c318a85" satisfied condition "Succeeded or Failed"

    Sep  7 01:02:30.523: INFO: Got logs for pod "busybox-privileged-false-71e376d1-1e4a-46a8-8fc9-378d1c318a85": "ip: RTNETLINK answers: Operation not permitted\n"
    [AfterEach] [k8s.io] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:30.523: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "security-context-test-7558" for this suite.
    
... skipping 29 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:34.750: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-3388" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD preserving unknown fields in an embedded object [Conformance]","total":-1,"completed":4,"skipped":82,"failed":0}

    
    SSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:02:24.651: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename secrets
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with mappings and Item Mode set [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating secret with name secret-test-map-5e913207-7aaf-43b3-b791-92f19d9ff3b0
    STEP: Creating a pod to test consume secrets
    Sep  7 01:02:24.757: INFO: Waiting up to 5m0s for pod "pod-secrets-ae8d0fe2-71de-471f-85d1-3505579d9023" in namespace "secrets-3246" to be "Succeeded or Failed"

    Sep  7 01:02:24.764: INFO: Pod "pod-secrets-ae8d0fe2-71de-471f-85d1-3505579d9023": Phase="Pending", Reason="", readiness=false. Elapsed: 6.364874ms
    Sep  7 01:02:26.769: INFO: Pod "pod-secrets-ae8d0fe2-71de-471f-85d1-3505579d9023": Phase="Pending", Reason="", readiness=false. Elapsed: 2.01215285s
    Sep  7 01:02:28.778: INFO: Pod "pod-secrets-ae8d0fe2-71de-471f-85d1-3505579d9023": Phase="Pending", Reason="", readiness=false. Elapsed: 4.020321083s
    Sep  7 01:02:30.787: INFO: Pod "pod-secrets-ae8d0fe2-71de-471f-85d1-3505579d9023": Phase="Pending", Reason="", readiness=false. Elapsed: 6.029286365s
    Sep  7 01:02:32.792: INFO: Pod "pod-secrets-ae8d0fe2-71de-471f-85d1-3505579d9023": Phase="Running", Reason="", readiness=true. Elapsed: 8.034364687s
    Sep  7 01:02:34.797: INFO: Pod "pod-secrets-ae8d0fe2-71de-471f-85d1-3505579d9023": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.039999362s
    STEP: Saw pod success
    Sep  7 01:02:34.797: INFO: Pod "pod-secrets-ae8d0fe2-71de-471f-85d1-3505579d9023" satisfied condition "Succeeded or Failed"

    Sep  7 01:02:34.804: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1 pod pod-secrets-ae8d0fe2-71de-471f-85d1-3505579d9023 container secret-volume-test: <nil>
    STEP: delete the pod
    Sep  7 01:02:34.856: INFO: Waiting for pod pod-secrets-ae8d0fe2-71de-471f-85d1-3505579d9023 to disappear
    Sep  7 01:02:34.863: INFO: Pod pod-secrets-ae8d0fe2-71de-471f-85d1-3505579d9023 no longer exists
    [AfterEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:34.863: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-3246" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Secrets should be consumable from pods in volume with mappings and Item Mode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":6,"skipped":143,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Downward API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:02:34.804: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename downward-api
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should provide container's limits.cpu/memory and requests.cpu/memory as env vars [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward api env vars
    Sep  7 01:02:34.889: INFO: Waiting up to 5m0s for pod "downward-api-b8145cd2-3366-413d-8dd1-77986da0c2e5" in namespace "downward-api-3520" to be "Succeeded or Failed"

    Sep  7 01:02:34.894: INFO: Pod "downward-api-b8145cd2-3366-413d-8dd1-77986da0c2e5": Phase="Pending", Reason="", readiness=false. Elapsed: 4.876375ms
    Sep  7 01:02:36.901: INFO: Pod "downward-api-b8145cd2-3366-413d-8dd1-77986da0c2e5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.011408746s
    STEP: Saw pod success
    Sep  7 01:02:36.901: INFO: Pod "downward-api-b8145cd2-3366-413d-8dd1-77986da0c2e5" satisfied condition "Succeeded or Failed"

    Sep  7 01:02:36.906: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod downward-api-b8145cd2-3366-413d-8dd1-77986da0c2e5 container dapi-container: <nil>
    STEP: delete the pod
    Sep  7 01:02:36.930: INFO: Waiting for pod downward-api-b8145cd2-3366-413d-8dd1-77986da0c2e5 to disappear
    Sep  7 01:02:36.935: INFO: Pod downward-api-b8145cd2-3366-413d-8dd1-77986da0c2e5 no longer exists
    [AfterEach] [sig-node] Downward API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:36.935: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-3520" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Downward API should provide container's limits.cpu/memory and requests.cpu/memory as env vars [NodeConformance] [Conformance]","total":-1,"completed":5,"skipped":94,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    {"msg":"PASSED [k8s.io] Security Context When creating a pod with privileged should run the container as unprivileged when false [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":9,"skipped":341,"failed":0}

    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:02:30.546: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename downward-api
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 7 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:37.279: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-5976" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should update annotations on modification [NodeConformance] [Conformance]","total":-1,"completed":10,"skipped":341,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 7 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:38.130: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "custom-resource-definition-2828" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition creating/deleting custom resource definition objects works  [Conformance]","total":-1,"completed":6,"skipped":129,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 20 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:38.521: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-1870" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl run pod should create a pod from an image when restart is Never  [Conformance]","total":-1,"completed":2,"skipped":4,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:02:34.969: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename secrets
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable via the environment [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: creating secret secrets-3693/secret-test-cdd8a385-06fe-435d-817f-fe903acbe7b1
    STEP: Creating a pod to test consume secrets
    Sep  7 01:02:35.041: INFO: Waiting up to 5m0s for pod "pod-configmaps-195cf881-ea5f-4c54-b522-3a0307ece5da" in namespace "secrets-3693" to be "Succeeded or Failed"

    Sep  7 01:02:35.047: INFO: Pod "pod-configmaps-195cf881-ea5f-4c54-b522-3a0307ece5da": Phase="Pending", Reason="", readiness=false. Elapsed: 5.311539ms
    Sep  7 01:02:37.052: INFO: Pod "pod-configmaps-195cf881-ea5f-4c54-b522-3a0307ece5da": Phase="Running", Reason="", readiness=true. Elapsed: 2.010785837s
    Sep  7 01:02:39.058: INFO: Pod "pod-configmaps-195cf881-ea5f-4c54-b522-3a0307ece5da": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.016497749s
    STEP: Saw pod success
    Sep  7 01:02:39.058: INFO: Pod "pod-configmaps-195cf881-ea5f-4c54-b522-3a0307ece5da" satisfied condition "Succeeded or Failed"

    Sep  7 01:02:39.067: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod pod-configmaps-195cf881-ea5f-4c54-b522-3a0307ece5da container env-test: <nil>
    STEP: delete the pod
    Sep  7 01:02:39.103: INFO: Waiting for pod pod-configmaps-195cf881-ea5f-4c54-b522-3a0307ece5da to disappear
    Sep  7 01:02:39.111: INFO: Pod pod-configmaps-195cf881-ea5f-4c54-b522-3a0307ece5da no longer exists
    [AfterEach] [sig-api-machinery] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:39.111: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-3693" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Secrets should be consumable via the environment [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":180,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:02:39.229: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should support (non-root,0644,default) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test emptydir 0644 on node default medium
    Sep  7 01:02:39.306: INFO: Waiting up to 5m0s for pod "pod-717c4026-d141-499a-898a-a5438e1bf05e" in namespace "emptydir-3279" to be "Succeeded or Failed"

    Sep  7 01:02:39.314: INFO: Pod "pod-717c4026-d141-499a-898a-a5438e1bf05e": Phase="Pending", Reason="", readiness=false. Elapsed: 8.19318ms
    Sep  7 01:02:41.343: INFO: Pod "pod-717c4026-d141-499a-898a-a5438e1bf05e": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.036897424s
    STEP: Saw pod success
    Sep  7 01:02:41.343: INFO: Pod "pod-717c4026-d141-499a-898a-a5438e1bf05e" satisfied condition "Succeeded or Failed"

    Sep  7 01:02:41.351: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1 pod pod-717c4026-d141-499a-898a-a5438e1bf05e container test-container: <nil>
    STEP: delete the pod
    Sep  7 01:02:41.392: INFO: Waiting for pod pod-717c4026-d141-499a-898a-a5438e1bf05e to disappear
    Sep  7 01:02:41.396: INFO: Pod pod-717c4026-d141-499a-898a-a5438e1bf05e no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:41.396: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-3279" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0644,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":8,"skipped":215,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:02:41.431: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume as non-root [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap with name configmap-test-volume-7ae816f1-55f8-46c7-886b-c6060327d013
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:02:41.522: INFO: Waiting up to 5m0s for pod "pod-configmaps-52766d24-22b3-4c9f-b20f-57f7825cbcef" in namespace "configmap-1319" to be "Succeeded or Failed"

    Sep  7 01:02:41.544: INFO: Pod "pod-configmaps-52766d24-22b3-4c9f-b20f-57f7825cbcef": Phase="Pending", Reason="", readiness=false. Elapsed: 22.057595ms
    Sep  7 01:02:43.549: INFO: Pod "pod-configmaps-52766d24-22b3-4c9f-b20f-57f7825cbcef": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.027063375s
    STEP: Saw pod success
    Sep  7 01:02:43.549: INFO: Pod "pod-configmaps-52766d24-22b3-4c9f-b20f-57f7825cbcef" satisfied condition "Succeeded or Failed"

    Sep  7 01:02:43.563: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-h877k pod pod-configmaps-52766d24-22b3-4c9f-b20f-57f7825cbcef container agnhost-container: <nil>
    STEP: delete the pod
    Sep  7 01:02:43.590: INFO: Waiting for pod pod-configmaps-52766d24-22b3-4c9f-b20f-57f7825cbcef to disappear
    Sep  7 01:02:43.597: INFO: Pod pod-configmaps-52766d24-22b3-4c9f-b20f-57f7825cbcef no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:02:43.597: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-1319" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume as non-root [NodeConformance] [Conformance]","total":-1,"completed":9,"skipped":221,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 64 lines ...
    STEP: Destroying namespace "services-2751" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:749
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to switch session affinity for service with type clusterIP [LinuxOnly] [Conformance]","total":-1,"completed":10,"skipped":229,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected secret
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:03:08.011: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename projected
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with mappings and Item Mode set [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating projection with secret that has name projected-secret-test-map-a0f0626c-5fa0-452d-ba25-8af5d0908112
    STEP: Creating a pod to test consume secrets
    Sep  7 01:03:08.166: INFO: Waiting up to 5m0s for pod "pod-projected-secrets-5d8231f2-8ce9-4850-9dce-87e363c1e7d5" in namespace "projected-7344" to be "Succeeded or Failed"

    Sep  7 01:03:08.173: INFO: Pod "pod-projected-secrets-5d8231f2-8ce9-4850-9dce-87e363c1e7d5": Phase="Pending", Reason="", readiness=false. Elapsed: 6.798634ms
    Sep  7 01:03:10.181: INFO: Pod "pod-projected-secrets-5d8231f2-8ce9-4850-9dce-87e363c1e7d5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.014815954s
    STEP: Saw pod success
    Sep  7 01:03:10.181: INFO: Pod "pod-projected-secrets-5d8231f2-8ce9-4850-9dce-87e363c1e7d5" satisfied condition "Succeeded or Failed"

    Sep  7 01:03:10.186: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-h877k pod pod-projected-secrets-5d8231f2-8ce9-4850-9dce-87e363c1e7d5 container projected-secret-volume-test: <nil>
    STEP: delete the pod
    Sep  7 01:03:10.211: INFO: Waiting for pod pod-projected-secrets-5d8231f2-8ce9-4850-9dce-87e363c1e7d5 to disappear
    Sep  7 01:03:10.215: INFO: Pod pod-projected-secrets-5d8231f2-8ce9-4850-9dce-87e363c1e7d5 no longer exists
    [AfterEach] [sig-storage] Projected secret
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:03:10.215: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-7344" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected secret should be consumable from pods in volume with mappings and Item Mode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":11,"skipped":251,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [k8s.io] Kubelet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 10 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:03:10.330: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubelet-test-4982" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Kubelet when scheduling a busybox command that always fails in a pod should be possible to delete [NodeConformance] [Conformance]","total":-1,"completed":12,"skipped":252,"failed":0}

    
    SSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:03:10.384: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename secrets
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume as non-root with defaultMode and fsGroup set [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating secret with name secret-test-298efe06-255a-4e4e-ac33-96e2c8239fea
    STEP: Creating a pod to test consume secrets
    Sep  7 01:03:10.457: INFO: Waiting up to 5m0s for pod "pod-secrets-a536920c-5f59-4e86-9468-e065e4baca9c" in namespace "secrets-663" to be "Succeeded or Failed"

    Sep  7 01:03:10.462: INFO: Pod "pod-secrets-a536920c-5f59-4e86-9468-e065e4baca9c": Phase="Pending", Reason="", readiness=false. Elapsed: 5.462759ms
    Sep  7 01:03:12.468: INFO: Pod "pod-secrets-a536920c-5f59-4e86-9468-e065e4baca9c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.011390733s
    STEP: Saw pod success
    Sep  7 01:03:12.469: INFO: Pod "pod-secrets-a536920c-5f59-4e86-9468-e065e4baca9c" satisfied condition "Succeeded or Failed"

    Sep  7 01:03:12.474: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-h877k pod pod-secrets-a536920c-5f59-4e86-9468-e065e4baca9c container secret-volume-test: <nil>
    STEP: delete the pod
    Sep  7 01:03:12.503: INFO: Waiting for pod pod-secrets-a536920c-5f59-4e86-9468-e065e4baca9c to disappear
    Sep  7 01:03:12.508: INFO: Pod pod-secrets-a536920c-5f59-4e86-9468-e065e4baca9c no longer exists
    [AfterEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:03:12.508: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-663" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Secrets should be consumable from pods in volume as non-root with defaultMode and fsGroup set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":13,"skipped":265,"failed":0}

    
    SSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Lease
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 6 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:03:12.680: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "lease-test-9323" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Lease lease API should be available [Conformance]","total":-1,"completed":14,"skipped":277,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [k8s.io] Probing container
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 14 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:03:32.649: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-probe-3898" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Probing container should be restarted with a exec \"cat /tmp/health\" liveness probe [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":196,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 4 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/subpath.go:38
    STEP: Setting up data
    [It] should support subpaths with downward pod [LinuxOnly] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating pod pod-subpath-test-downwardapi-c5v9
    STEP: Creating a pod to test atomic-volume-subpath
    Sep  7 01:03:32.829: INFO: Waiting up to 5m0s for pod "pod-subpath-test-downwardapi-c5v9" in namespace "subpath-973" to be "Succeeded or Failed"

    Sep  7 01:03:32.833: INFO: Pod "pod-subpath-test-downwardapi-c5v9": Phase="Pending", Reason="", readiness=false. Elapsed: 3.564752ms
    Sep  7 01:03:34.839: INFO: Pod "pod-subpath-test-downwardapi-c5v9": Phase="Running", Reason="", readiness=true. Elapsed: 2.009503919s
    Sep  7 01:03:36.848: INFO: Pod "pod-subpath-test-downwardapi-c5v9": Phase="Running", Reason="", readiness=true. Elapsed: 4.019160123s
    Sep  7 01:03:38.855: INFO: Pod "pod-subpath-test-downwardapi-c5v9": Phase="Running", Reason="", readiness=true. Elapsed: 6.025878728s
    Sep  7 01:03:40.862: INFO: Pod "pod-subpath-test-downwardapi-c5v9": Phase="Running", Reason="", readiness=true. Elapsed: 8.032853746s
    Sep  7 01:03:42.868: INFO: Pod "pod-subpath-test-downwardapi-c5v9": Phase="Running", Reason="", readiness=true. Elapsed: 10.038899677s
    Sep  7 01:03:44.877: INFO: Pod "pod-subpath-test-downwardapi-c5v9": Phase="Running", Reason="", readiness=true. Elapsed: 12.04726621s
    Sep  7 01:03:46.882: INFO: Pod "pod-subpath-test-downwardapi-c5v9": Phase="Running", Reason="", readiness=true. Elapsed: 14.052973395s
    Sep  7 01:03:48.889: INFO: Pod "pod-subpath-test-downwardapi-c5v9": Phase="Running", Reason="", readiness=true. Elapsed: 16.060120476s
    Sep  7 01:03:50.897: INFO: Pod "pod-subpath-test-downwardapi-c5v9": Phase="Running", Reason="", readiness=true. Elapsed: 18.067664114s
    Sep  7 01:03:52.904: INFO: Pod "pod-subpath-test-downwardapi-c5v9": Phase="Running", Reason="", readiness=true. Elapsed: 20.07452867s
    Sep  7 01:03:54.911: INFO: Pod "pod-subpath-test-downwardapi-c5v9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.081666665s
    STEP: Saw pod success
    Sep  7 01:03:54.911: INFO: Pod "pod-subpath-test-downwardapi-c5v9" satisfied condition "Succeeded or Failed"

    Sep  7 01:03:54.914: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-subpath-test-downwardapi-c5v9 container test-container-subpath-downwardapi-c5v9: <nil>
    STEP: delete the pod
    Sep  7 01:03:54.941: INFO: Waiting for pod pod-subpath-test-downwardapi-c5v9 to disappear
    Sep  7 01:03:54.947: INFO: Pod pod-subpath-test-downwardapi-c5v9 no longer exists
    STEP: Deleting pod pod-subpath-test-downwardapi-c5v9
    Sep  7 01:03:54.947: INFO: Deleting pod "pod-subpath-test-downwardapi-c5v9" in namespace "subpath-973"
    [AfterEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:03:54.952: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "subpath-973" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Subpath Atomic writer volumes should support subpaths with downward pod [LinuxOnly] [Conformance]","total":-1,"completed":8,"skipped":235,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] IngressClass API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 22 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:03:55.246: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "ingressclass-1121" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] IngressClass API  should support creating IngressClass API operations [Conformance]","total":-1,"completed":9,"skipped":256,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 8 lines ...
    STEP: submitting the pod to kubernetes
    STEP: verifying the pod is in kubernetes
    STEP: updating the pod
    Sep  7 01:04:03.937: INFO: Successfully updated pod "pod-update-activedeadlineseconds-0caf44b0-db2a-431c-a21e-2e6f42eb6a20"
    Sep  7 01:04:03.937: INFO: Waiting up to 5m0s for pod "pod-update-activedeadlineseconds-0caf44b0-db2a-431c-a21e-2e6f42eb6a20" in namespace "pods-1953" to be "terminated due to deadline exceeded"
    Sep  7 01:04:03.943: INFO: Pod "pod-update-activedeadlineseconds-0caf44b0-db2a-431c-a21e-2e6f42eb6a20": Phase="Running", Reason="", readiness=true. Elapsed: 5.787743ms
    Sep  7 01:04:05.948: INFO: Pod "pod-update-activedeadlineseconds-0caf44b0-db2a-431c-a21e-2e6f42eb6a20": Phase="Failed", Reason="DeadlineExceeded", readiness=false. Elapsed: 2.01147685s

    Sep  7 01:04:05.948: INFO: Pod "pod-update-activedeadlineseconds-0caf44b0-db2a-431c-a21e-2e6f42eb6a20" satisfied condition "terminated due to deadline exceeded"
    [AfterEach] [k8s.io] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:04:05.948: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-1953" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Pods should allow activeDeadlineSeconds to be updated [NodeConformance] [Conformance]","total":-1,"completed":10,"skipped":282,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [k8s.io] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 16 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:04:17.466: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-9769" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Pods should be submitted and removed [NodeConformance] [Conformance]","total":-1,"completed":11,"skipped":286,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 25 lines ...
    STEP: Destroying namespace "services-4578" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:749
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to change the type from ClusterIP to ExternalName [Conformance]","total":-1,"completed":12,"skipped":449,"failed":0}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] StatefulSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 72 lines ...
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
      [k8s.io] Basic StatefulSet functionality [StatefulSetBasic]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
        should perform rolling updates and roll backs of template modifications [Conformance]
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance]","total":-1,"completed":11,"skipped":363,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:05:19.475: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename secrets
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should fail to create secret due to empty secret key [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating projection with secret that has name secret-emptykey-test-2f3174db-7fc3-4b2c-8746-983094eab9e7
    [AfterEach] [sig-api-machinery] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:05:19.528: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-7060" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Secrets should fail to create secret due to empty secret key [Conformance]","total":-1,"completed":12,"skipped":438,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:05:19.551: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should support (non-root,0777,default) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test emptydir 0777 on node default medium
    Sep  7 01:05:19.625: INFO: Waiting up to 5m0s for pod "pod-b7b91184-3f7a-482e-9548-f067dc4db4a4" in namespace "emptydir-5342" to be "Succeeded or Failed"

    Sep  7 01:05:19.630: INFO: Pod "pod-b7b91184-3f7a-482e-9548-f067dc4db4a4": Phase="Pending", Reason="", readiness=false. Elapsed: 5.140962ms
    Sep  7 01:05:21.636: INFO: Pod "pod-b7b91184-3f7a-482e-9548-f067dc4db4a4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.011837599s
    STEP: Saw pod success
    Sep  7 01:05:21.637: INFO: Pod "pod-b7b91184-3f7a-482e-9548-f067dc4db4a4" satisfied condition "Succeeded or Failed"

    Sep  7 01:05:21.642: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-b7b91184-3f7a-482e-9548-f067dc4db4a4 container test-container: <nil>
    STEP: delete the pod
    Sep  7 01:05:21.672: INFO: Waiting for pod pod-b7b91184-3f7a-482e-9548-f067dc4db4a4 to disappear
    Sep  7 01:05:21.677: INFO: Pod pod-b7b91184-3f7a-482e-9548-f067dc4db4a4 no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:05:21.677: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-5342" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0777,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":13,"skipped":439,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 3 lines ...
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:745
    [It] should serve multiport endpoints from pods  [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: creating service multi-endpoint-test in namespace services-2441
    STEP: waiting up to 3m0s for service multi-endpoint-test in namespace services-2441 to expose endpoints map[]
    Sep  7 01:05:21.780: INFO: Failed go get Endpoints object: endpoints "multi-endpoint-test" not found

    Sep  7 01:05:22.792: INFO: successfully validated that service multi-endpoint-test in namespace services-2441 exposes endpoints map[]
    STEP: Creating pod pod1 in namespace services-2441
    STEP: waiting up to 3m0s for service multi-endpoint-test in namespace services-2441 to expose endpoints map[pod1:[100]]
    Sep  7 01:05:24.851: INFO: successfully validated that service multi-endpoint-test in namespace services-2441 exposes endpoints map[pod1:[100]]
    STEP: Creating pod pod2 in namespace services-2441
    STEP: waiting up to 3m0s for service multi-endpoint-test in namespace services-2441 to expose endpoints map[pod1:[100] pod2:[101]]
... skipping 10 lines ...
    STEP: Destroying namespace "services-2441" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:749
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should serve multiport endpoints from pods  [Conformance]","total":-1,"completed":14,"skipped":445,"failed":0}

    [BeforeEach] [sig-api-machinery] Discovery
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:05:26.237: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename discovery
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 86 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:05:26.931: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "discovery-905" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Discovery should validate PreferredVersion for each APIGroup [Conformance]","total":-1,"completed":15,"skipped":445,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Servers with support for Table transformation
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 8 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:05:27.015: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "tables-7306" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Servers with support for Table transformation should return a 406 for a backend which does not implement metadata [Conformance]","total":-1,"completed":16,"skipped":449,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 7 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:05:27.684: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "custom-resource-definition-9727" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition getting/updating/patching custom resource definition status sub-resource works  [Conformance]","total":-1,"completed":17,"skipped":460,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] ReplicationController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 27 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:05:31.042: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-9416" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should test the lifecycle of a ReplicationController [Conformance]","total":-1,"completed":18,"skipped":494,"failed":0}

    
    SSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Container Runtime
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 21 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:05:54.462: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-runtime-5699" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Container Runtime blackbox test when starting a container that exits should run with the expected status [NodeConformance] [Conformance]","total":-1,"completed":19,"skipped":512,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:05:54.835: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-2548" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl cluster-info should check if Kubernetes control plane services is included in cluster-info  [Conformance]","total":-1,"completed":20,"skipped":543,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 27 lines ...
    STEP: Destroying namespace "services-1130" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:749
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to create a functioning NodePort service [Conformance]","total":-1,"completed":21,"skipped":564,"failed":0}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Watchers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 14 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:06:02.541: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "watch-3110" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Watchers should be able to start watching from a specific resource version [Conformance]","total":-1,"completed":22,"skipped":579,"failed":0}

    
    SSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] StatefulSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 40 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:07:33.051: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-4703" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] should perform canary updates and phased rolling updates of template modifications [Conformance]","total":-1,"completed":23,"skipped":591,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] KubeletManagedEtcHosts
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 43 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:07:43.117: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "e2e-kubelet-etc-hosts-2072" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] KubeletManagedEtcHosts should test kubelet managed /etc/hosts file [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":24,"skipped":597,"failed":0}

    
    SSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:07:43.163: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should support (non-root,0666,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test emptydir 0666 on tmpfs
    Sep  7 01:07:43.228: INFO: Waiting up to 5m0s for pod "pod-618c52df-8d1c-42d5-8c0b-730e95202713" in namespace "emptydir-3886" to be "Succeeded or Failed"

    Sep  7 01:07:43.236: INFO: Pod "pod-618c52df-8d1c-42d5-8c0b-730e95202713": Phase="Pending", Reason="", readiness=false. Elapsed: 7.625415ms
    Sep  7 01:07:45.253: INFO: Pod "pod-618c52df-8d1c-42d5-8c0b-730e95202713": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.02426153s
    STEP: Saw pod success
    Sep  7 01:07:45.253: INFO: Pod "pod-618c52df-8d1c-42d5-8c0b-730e95202713" satisfied condition "Succeeded or Failed"

    Sep  7 01:07:45.258: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1 pod pod-618c52df-8d1c-42d5-8c0b-730e95202713 container test-container: <nil>
    STEP: delete the pod
    Sep  7 01:07:45.298: INFO: Waiting for pod pod-618c52df-8d1c-42d5-8c0b-730e95202713 to disappear
    Sep  7 01:07:45.306: INFO: Pod pod-618c52df-8d1c-42d5-8c0b-730e95202713 no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:07:45.306: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-3886" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0666,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":25,"skipped":609,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 16 lines ...
    STEP: Registering slow webhook via the AdmissionRegistration API
    Sep  7 01:07:59.653: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:08:09.776: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:08:19.877: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:08:29.966: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:08:39.982: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:08:39.983: FAIL: waiting for webhook configuration to be ready

    Unexpected error:

        <*errors.errorString | 0xc00027c200>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 23 lines ...
    [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      should honor timeout [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
      Sep  7 01:08:39.983: waiting for webhook configuration to be ready
      Unexpected error:

          <*errors.errorString | 0xc00027c200>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:2187
    ------------------------------
    {"msg":"FAILED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]","total":-1,"completed":25,"skipped":611,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]"]}

    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:08:40.102: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename webhook
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 10 lines ...
    Sep  7 01:08:45.870: INFO: Waiting for amount of service:e2e-test-webhook endpoints to be 1
    [It] should honor timeout [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Setting timeout (1s) shorter than webhook latency (5s)
    STEP: Registering slow webhook via the AdmissionRegistration API
    STEP: Request fails when timeout (1s) is shorter than slow webhook latency (5s)
    STEP: Having no error when timeout is shorter than webhook latency and failure policy is ignore

    STEP: Registering slow webhook via the AdmissionRegistration API
    STEP: Having no error when timeout is longer than webhook latency

    STEP: Registering slow webhook via the AdmissionRegistration API
    STEP: Having no error when timeout is empty (defaulted to 10s in v1)

    STEP: Registering slow webhook via the AdmissionRegistration API
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:08:58.031: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "webhook-7867" for this suite.
    STEP: Destroying namespace "webhook-7867-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]","total":-1,"completed":26,"skipped":611,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]"]}

    
    S
    ------------------------------
    [BeforeEach] [sig-apps] Job
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 13 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:09:33.905: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "job-8986" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Job should delete a job [Conformance]","total":-1,"completed":27,"skipped":612,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]"]}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:41
    [It] should set DefaultMode on files [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward API volume plugin
    Sep  7 01:09:34.002: INFO: Waiting up to 5m0s for pod "downwardapi-volume-b194d501-0736-4c2e-9812-0d6c4e5aa22e" in namespace "projected-2214" to be "Succeeded or Failed"

    Sep  7 01:09:34.012: INFO: Pod "downwardapi-volume-b194d501-0736-4c2e-9812-0d6c4e5aa22e": Phase="Pending", Reason="", readiness=false. Elapsed: 9.188656ms
    Sep  7 01:09:36.016: INFO: Pod "downwardapi-volume-b194d501-0736-4c2e-9812-0d6c4e5aa22e": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.013378267s
    STEP: Saw pod success
    Sep  7 01:09:36.016: INFO: Pod "downwardapi-volume-b194d501-0736-4c2e-9812-0d6c4e5aa22e" satisfied condition "Succeeded or Failed"

    Sep  7 01:09:36.019: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod downwardapi-volume-b194d501-0736-4c2e-9812-0d6c4e5aa22e container client-container: <nil>
    STEP: delete the pod
    Sep  7 01:09:36.050: INFO: Waiting for pod downwardapi-volume-b194d501-0736-4c2e-9812-0d6c4e5aa22e to disappear
    Sep  7 01:09:36.053: INFO: Pod downwardapi-volume-b194d501-0736-4c2e-9812-0d6c4e5aa22e no longer exists
    [AfterEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:09:36.053: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-2214" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should set DefaultMode on files [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":28,"skipped":617,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] ReplicationController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 15 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:09:46.192: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-3690" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","total":-1,"completed":29,"skipped":666,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-instrumentation] Events API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 21 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:09:46.333: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-456" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-instrumentation] Events API should ensure that an event can be fetched, patched, deleted, and listed [Conformance]","total":-1,"completed":30,"skipped":696,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]"]}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] ReplicationController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:09:49.413: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-3654" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should adopt matching pods on creation [Conformance]","total":-1,"completed":31,"skipped":713,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:09:49.472: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename var-expansion
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should fail substituting values in a volume subpath with absolute path [sig-storage][Slow] [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    Sep  7 01:09:51.528: INFO: Deleting pod "var-expansion-8c858734-403c-4408-a599-7a24fb74f424" in namespace "var-expansion-8207"
    Sep  7 01:09:51.533: INFO: Wait up to 5m0s for pod "var-expansion-8c858734-403c-4408-a599-7a24fb74f424" to be fully deleted
    [AfterEach] [k8s.io] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:09:55.539: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-8207" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Variable Expansion should fail substituting values in a volume subpath with absolute path [sig-storage][Slow] [Conformance]","total":-1,"completed":32,"skipped":747,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 25 lines ...
    Sep  7 01:02:47.217: INFO: stderr: ""
    Sep  7 01:02:47.217: INFO: stdout: "true"
    Sep  7 01:02:47.217: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-3656 get pods update-demo-nautilus-mpwxk -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
    Sep  7 01:02:47.448: INFO: stderr: ""
    Sep  7 01:02:47.448: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
    Sep  7 01:02:47.448: INFO: validating pod update-demo-nautilus-mpwxk
    Sep  7 01:06:20.481: INFO: update-demo-nautilus-mpwxk is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-mpwxk)

    Sep  7 01:06:25.484: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-3656 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
    Sep  7 01:06:25.672: INFO: stderr: ""
    Sep  7 01:06:25.672: INFO: stdout: "update-demo-nautilus-mpwxk update-demo-nautilus-txhmw "
    Sep  7 01:06:25.672: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-3656 get pods update-demo-nautilus-mpwxk -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
    Sep  7 01:06:25.851: INFO: stderr: ""
    Sep  7 01:06:25.851: INFO: stdout: "true"
    Sep  7 01:06:25.851: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-3656 get pods update-demo-nautilus-mpwxk -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
    Sep  7 01:06:26.032: INFO: stderr: ""
    Sep  7 01:06:26.032: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0"
    Sep  7 01:06:26.032: INFO: validating pod update-demo-nautilus-mpwxk
    Sep  7 01:09:59.617: INFO: update-demo-nautilus-mpwxk is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-mpwxk)

    Sep  7 01:10:04.618: FAIL: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state

    
    Full Stack Trace
    k8s.io/kubernetes/test/e2e/kubectl.glob..func1.6.2()
    	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:317 +0x29b
    k8s.io/kubernetes/test/e2e.RunE2ETests(0xc003762300)
    	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c
... skipping 28 lines ...
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
        Sep  7 01:10:04.618: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state
    
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:317
    ------------------------------
    {"msg":"FAILED [sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","total":-1,"completed":2,"skipped":44,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:10:05.016: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename kubectl
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 58 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:10:11.483: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-9340" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","total":-1,"completed":3,"skipped":44,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:10:11.513: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename projected
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with mappings as non-root [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap with name projected-configmap-test-volume-map-9a91398a-4c67-4151-a0aa-e3381917671b
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:10:11.568: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-b09654e9-da77-4adf-8e97-bf2d06113ecc" in namespace "projected-1060" to be "Succeeded or Failed"

    Sep  7 01:10:11.577: INFO: Pod "pod-projected-configmaps-b09654e9-da77-4adf-8e97-bf2d06113ecc": Phase="Pending", Reason="", readiness=false. Elapsed: 9.39221ms
    Sep  7 01:10:13.581: INFO: Pod "pod-projected-configmaps-b09654e9-da77-4adf-8e97-bf2d06113ecc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.013113522s
    STEP: Saw pod success
    Sep  7 01:10:13.581: INFO: Pod "pod-projected-configmaps-b09654e9-da77-4adf-8e97-bf2d06113ecc" satisfied condition "Succeeded or Failed"

    Sep  7 01:10:13.584: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-projected-configmaps-b09654e9-da77-4adf-8e97-bf2d06113ecc container agnhost-container: <nil>
    STEP: delete the pod
    Sep  7 01:10:13.598: INFO: Waiting for pod pod-projected-configmaps-b09654e9-da77-4adf-8e97-bf2d06113ecc to disappear
    Sep  7 01:10:13.601: INFO: Pod pod-projected-configmaps-b09654e9-da77-4adf-8e97-bf2d06113ecc no longer exists
    [AfterEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:10:13.601: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-1060" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap should be consumable from pods in volume with mappings as non-root [NodeConformance] [Conformance]","total":-1,"completed":4,"skipped":58,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 11 lines ...
    STEP: Destroying namespace "services-1573" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:749
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should find a service from listing all namespaces [Conformance]","total":-1,"completed":5,"skipped":68,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Garbage collector
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 5 lines ...
    STEP: create the rc
    STEP: delete the rc
    STEP: wait for the rc to be deleted
    STEP: wait for 30 seconds to see if the garbage collector mistakenly deletes the pods
    STEP: Gathering metrics
    W0907 01:05:18.046271      16 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled.
    Sep  7 01:10:18.050: INFO: MetricsGrabber failed grab metrics. Skipping metrics gathering.

    Sep  7 01:10:18.052: INFO: Deleting pod "simpletest.rc-2qdfb" in namespace "gc-126"
    Sep  7 01:10:18.063: INFO: Deleting pod "simpletest.rc-7v2qk" in namespace "gc-126"
    Sep  7 01:10:18.079: INFO: Deleting pod "simpletest.rc-bkbpb" in namespace "gc-126"
    Sep  7 01:10:18.093: INFO: Deleting pod "simpletest.rc-gxdw5" in namespace "gc-126"
    Sep  7 01:10:18.102: INFO: Deleting pod "simpletest.rc-hhb4b" in namespace "gc-126"
    Sep  7 01:10:18.121: INFO: Deleting pod "simpletest.rc-mrrc6" in namespace "gc-126"
... skipping 10 lines ...
    • [SLOW TEST:340.562 seconds]
    [sig-api-machinery] Garbage collector
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      should orphan pods created by rc if delete options say so [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Garbage collector should orphan pods created by rc if delete options say so [Conformance]","total":-1,"completed":13,"skipped":456,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:41
    [It] should provide node allocatable (cpu) as default cpu limit if the limit is not set [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward API volume plugin
    Sep  7 01:10:18.538: INFO: Waiting up to 5m0s for pod "downwardapi-volume-793c7077-df2d-41ed-b734-62eb91f9a735" in namespace "downward-api-7661" to be "Succeeded or Failed"

    Sep  7 01:10:18.544: INFO: Pod "downwardapi-volume-793c7077-df2d-41ed-b734-62eb91f9a735": Phase="Pending", Reason="", readiness=false. Elapsed: 5.986663ms
    Sep  7 01:10:20.547: INFO: Pod "downwardapi-volume-793c7077-df2d-41ed-b734-62eb91f9a735": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.009225109s
    STEP: Saw pod success
    Sep  7 01:10:20.547: INFO: Pod "downwardapi-volume-793c7077-df2d-41ed-b734-62eb91f9a735" satisfied condition "Succeeded or Failed"

    Sep  7 01:10:20.550: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod downwardapi-volume-793c7077-df2d-41ed-b734-62eb91f9a735 container client-container: <nil>
    STEP: delete the pod
    Sep  7 01:10:20.576: INFO: Waiting for pod downwardapi-volume-793c7077-df2d-41ed-b734-62eb91f9a735 to disappear
    Sep  7 01:10:20.579: INFO: Pod downwardapi-volume-793c7077-df2d-41ed-b734-62eb91f9a735 no longer exists
    [AfterEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:10:20.579: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-7661" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should provide node allocatable (cpu) as default cpu limit if the limit is not set [NodeConformance] [Conformance]","total":-1,"completed":14,"skipped":480,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 13 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:10:31.678: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-4573" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a replication controller. [Conformance]","total":-1,"completed":15,"skipped":489,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 4 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/subpath.go:38
    STEP: Setting up data
    [It] should support subpaths with configmap pod with mountPath of existing file [LinuxOnly] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating pod pod-subpath-test-configmap-fdnn
    STEP: Creating a pod to test atomic-volume-subpath
    Sep  7 01:10:13.718: INFO: Waiting up to 5m0s for pod "pod-subpath-test-configmap-fdnn" in namespace "subpath-5384" to be "Succeeded or Failed"

    Sep  7 01:10:13.723: INFO: Pod "pod-subpath-test-configmap-fdnn": Phase="Pending", Reason="", readiness=false. Elapsed: 4.945895ms
    Sep  7 01:10:15.727: INFO: Pod "pod-subpath-test-configmap-fdnn": Phase="Running", Reason="", readiness=true. Elapsed: 2.009184802s
    Sep  7 01:10:17.731: INFO: Pod "pod-subpath-test-configmap-fdnn": Phase="Running", Reason="", readiness=true. Elapsed: 4.013232794s
    Sep  7 01:10:19.735: INFO: Pod "pod-subpath-test-configmap-fdnn": Phase="Running", Reason="", readiness=true. Elapsed: 6.016667647s
    Sep  7 01:10:21.738: INFO: Pod "pod-subpath-test-configmap-fdnn": Phase="Running", Reason="", readiness=true. Elapsed: 8.019961343s
    Sep  7 01:10:23.742: INFO: Pod "pod-subpath-test-configmap-fdnn": Phase="Running", Reason="", readiness=true. Elapsed: 10.023462035s
    Sep  7 01:10:25.745: INFO: Pod "pod-subpath-test-configmap-fdnn": Phase="Running", Reason="", readiness=true. Elapsed: 12.026725333s
    Sep  7 01:10:27.749: INFO: Pod "pod-subpath-test-configmap-fdnn": Phase="Running", Reason="", readiness=true. Elapsed: 14.030490359s
    Sep  7 01:10:29.752: INFO: Pod "pod-subpath-test-configmap-fdnn": Phase="Running", Reason="", readiness=true. Elapsed: 16.034065364s
    Sep  7 01:10:31.760: INFO: Pod "pod-subpath-test-configmap-fdnn": Phase="Running", Reason="", readiness=true. Elapsed: 18.041994873s
    Sep  7 01:10:33.764: INFO: Pod "pod-subpath-test-configmap-fdnn": Phase="Running", Reason="", readiness=true. Elapsed: 20.045574199s
    Sep  7 01:10:35.768: INFO: Pod "pod-subpath-test-configmap-fdnn": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.049495606s
    STEP: Saw pod success
    Sep  7 01:10:35.768: INFO: Pod "pod-subpath-test-configmap-fdnn" satisfied condition "Succeeded or Failed"

    Sep  7 01:10:35.773: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-subpath-test-configmap-fdnn container test-container-subpath-configmap-fdnn: <nil>
    STEP: delete the pod
    Sep  7 01:10:35.791: INFO: Waiting for pod pod-subpath-test-configmap-fdnn to disappear
    Sep  7 01:10:35.793: INFO: Pod pod-subpath-test-configmap-fdnn no longer exists
    STEP: Deleting pod pod-subpath-test-configmap-fdnn
    Sep  7 01:10:35.793: INFO: Deleting pod "pod-subpath-test-configmap-fdnn" in namespace "subpath-5384"
    [AfterEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:10:35.796: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "subpath-5384" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Subpath Atomic writer volumes should support subpaths with configmap pod with mountPath of existing file [LinuxOnly] [Conformance]","total":-1,"completed":6,"skipped":75,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSS
    ------------------------------
    [BeforeEach] [k8s.io] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:10:35.812: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename var-expansion
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should fail substituting values in a volume subpath with backticks [sig-storage][Slow] [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    Sep  7 01:10:37.857: INFO: Deleting pod "var-expansion-7d6d455b-4bb1-4d10-9d2e-d18beab2c9b3" in namespace "var-expansion-6048"
    Sep  7 01:10:37.862: INFO: Wait up to 5m0s for pod "var-expansion-7d6d455b-4bb1-4d10-9d2e-d18beab2c9b3" to be fully deleted
    [AfterEach] [k8s.io] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:10:41.870: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-6048" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Variable Expansion should fail substituting values in a volume subpath with backticks [sig-storage][Slow] [Conformance]","total":-1,"completed":7,"skipped":79,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Networking
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 47 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:10:54.226: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pod-network-test-8091" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: udp [NodeConformance] [Conformance]","total":-1,"completed":16,"skipped":498,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:10:54.246: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with defaultMode set [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap with name configmap-test-volume-205b8879-a9da-4c3e-8a95-7eb6e754be77
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:10:54.281: INFO: Waiting up to 5m0s for pod "pod-configmaps-a82de4d4-9716-40e8-a330-e7ce3a9cb228" in namespace "configmap-4665" to be "Succeeded or Failed"

    Sep  7 01:10:54.285: INFO: Pod "pod-configmaps-a82de4d4-9716-40e8-a330-e7ce3a9cb228": Phase="Pending", Reason="", readiness=false. Elapsed: 3.39912ms
    Sep  7 01:10:56.288: INFO: Pod "pod-configmaps-a82de4d4-9716-40e8-a330-e7ce3a9cb228": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006952303s
    STEP: Saw pod success
    Sep  7 01:10:56.288: INFO: Pod "pod-configmaps-a82de4d4-9716-40e8-a330-e7ce3a9cb228" satisfied condition "Succeeded or Failed"

    Sep  7 01:10:56.292: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod pod-configmaps-a82de4d4-9716-40e8-a330-e7ce3a9cb228 container agnhost-container: <nil>
    STEP: delete the pod
    Sep  7 01:10:56.313: INFO: Waiting for pod pod-configmaps-a82de4d4-9716-40e8-a330-e7ce3a9cb228 to disappear
    Sep  7 01:10:56.316: INFO: Pod pod-configmaps-a82de4d4-9716-40e8-a330-e7ce3a9cb228 no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:10:56.316: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-4665" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with defaultMode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":17,"skipped":508,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:10:56.477: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-3110" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Proxy server should support --unix-socket=/path  [Conformance]","total":-1,"completed":18,"skipped":531,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-auth] ServiceAccounts
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:10:56.501: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename svcaccounts
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should mount projected service account token [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test service account token: 
    Sep  7 01:10:56.536: INFO: Waiting up to 5m0s for pod "test-pod-e09812dc-4dde-4c35-b9ab-a797e8a4e304" in namespace "svcaccounts-1198" to be "Succeeded or Failed"

    Sep  7 01:10:56.539: INFO: Pod "test-pod-e09812dc-4dde-4c35-b9ab-a797e8a4e304": Phase="Pending", Reason="", readiness=false. Elapsed: 2.383535ms
    Sep  7 01:10:58.543: INFO: Pod "test-pod-e09812dc-4dde-4c35-b9ab-a797e8a4e304": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006104293s
    STEP: Saw pod success
    Sep  7 01:10:58.543: INFO: Pod "test-pod-e09812dc-4dde-4c35-b9ab-a797e8a4e304" satisfied condition "Succeeded or Failed"

    Sep  7 01:10:58.545: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod test-pod-e09812dc-4dde-4c35-b9ab-a797e8a4e304 container agnhost-container: <nil>
    STEP: delete the pod
    Sep  7 01:10:58.565: INFO: Waiting for pod test-pod-e09812dc-4dde-4c35-b9ab-a797e8a4e304 to disappear
    Sep  7 01:10:58.569: INFO: Pod test-pod-e09812dc-4dde-4c35-b9ab-a797e8a4e304 no longer exists
    [AfterEach] [sig-auth] ServiceAccounts
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:10:58.569: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "svcaccounts-1198" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-auth] ServiceAccounts should mount projected service account token [Conformance]","total":-1,"completed":19,"skipped":541,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:11:13.599: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-2409" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] removes definition from spec when one version gets changed to not be served [Conformance]","total":-1,"completed":20,"skipped":568,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:11:13.681: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-1144" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should be able to update and delete ResourceQuota. [Conformance]","total":-1,"completed":21,"skipped":576,"failed":0}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 13 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:11:17.836: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-7597" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap optional updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":22,"skipped":583,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 20 lines ...
    STEP: Destroying namespace "services-2072" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:749
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should test the lifecycle of an Endpoint [Conformance]","total":-1,"completed":23,"skipped":592,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 28 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:11:19.185: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-5900" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Pods should run through the lifecycle of Pods and PodStatus [Conformance]","total":-1,"completed":24,"skipped":629,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 9 lines ...
    
    STEP: creating a pod to probe DNS
    STEP: submitting the pod to kubernetes
    STEP: retrieving the pod
    STEP: looking for the results for each expected name from probers
    Sep  7 01:10:49.968: INFO: File jessie_udp@dns-test-service-3.dns-3758.svc.cluster.local from pod  dns-3758/dns-test-638bae87-6171-4ece-8e6f-b9d14c8f40ae contains '' instead of 'foo.example.com.'
    Sep  7 01:10:49.968: INFO: Lookups using dns-3758/dns-test-638bae87-6171-4ece-8e6f-b9d14c8f40ae failed for: [jessie_udp@dns-test-service-3.dns-3758.svc.cluster.local]

    
    Sep  7 01:10:54.976: INFO: DNS probes using dns-test-638bae87-6171-4ece-8e6f-b9d14c8f40ae succeeded
    
    STEP: deleting the pod
    STEP: changing the externalName to bar.example.com
    STEP: Running these commands on wheezy: for i in `seq 1 30`; do dig +short dns-test-service-3.dns-3758.svc.cluster.local CNAME > /results/wheezy_udp@dns-test-service-3.dns-3758.svc.cluster.local; sleep 1; done
... skipping 5 lines ...
    STEP: retrieving the pod
    STEP: looking for the results for each expected name from probers
    Sep  7 01:10:57.070: INFO: File wheezy_udp@dns-test-service-3.dns-3758.svc.cluster.local from pod  dns-3758/dns-test-2001060c-dc1d-4664-8fd0-c8708d2ceb53 contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Sep  7 01:10:57.075: INFO: File jessie_udp@dns-test-service-3.dns-3758.svc.cluster.local from pod  dns-3758/dns-test-2001060c-dc1d-4664-8fd0-c8708d2ceb53 contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Sep  7 01:10:57.075: INFO: Lookups using dns-3758/dns-test-2001060c-dc1d-4664-8fd0-c8708d2ceb53 failed for: [wheezy_udp@dns-test-service-3.dns-3758.svc.cluster.local jessie_udp@dns-test-service-3.dns-3758.svc.cluster.local]

    
    Sep  7 01:11:02.080: INFO: File wheezy_udp@dns-test-service-3.dns-3758.svc.cluster.local from pod  dns-3758/dns-test-2001060c-dc1d-4664-8fd0-c8708d2ceb53 contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Sep  7 01:11:02.083: INFO: File jessie_udp@dns-test-service-3.dns-3758.svc.cluster.local from pod  dns-3758/dns-test-2001060c-dc1d-4664-8fd0-c8708d2ceb53 contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Sep  7 01:11:02.083: INFO: Lookups using dns-3758/dns-test-2001060c-dc1d-4664-8fd0-c8708d2ceb53 failed for: [wheezy_udp@dns-test-service-3.dns-3758.svc.cluster.local jessie_udp@dns-test-service-3.dns-3758.svc.cluster.local]

    
    Sep  7 01:11:07.080: INFO: File wheezy_udp@dns-test-service-3.dns-3758.svc.cluster.local from pod  dns-3758/dns-test-2001060c-dc1d-4664-8fd0-c8708d2ceb53 contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Sep  7 01:11:07.083: INFO: File jessie_udp@dns-test-service-3.dns-3758.svc.cluster.local from pod  dns-3758/dns-test-2001060c-dc1d-4664-8fd0-c8708d2ceb53 contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Sep  7 01:11:07.083: INFO: Lookups using dns-3758/dns-test-2001060c-dc1d-4664-8fd0-c8708d2ceb53 failed for: [wheezy_udp@dns-test-service-3.dns-3758.svc.cluster.local jessie_udp@dns-test-service-3.dns-3758.svc.cluster.local]

    
    Sep  7 01:11:12.079: INFO: File wheezy_udp@dns-test-service-3.dns-3758.svc.cluster.local from pod  dns-3758/dns-test-2001060c-dc1d-4664-8fd0-c8708d2ceb53 contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Sep  7 01:11:12.083: INFO: File jessie_udp@dns-test-service-3.dns-3758.svc.cluster.local from pod  dns-3758/dns-test-2001060c-dc1d-4664-8fd0-c8708d2ceb53 contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Sep  7 01:11:12.083: INFO: Lookups using dns-3758/dns-test-2001060c-dc1d-4664-8fd0-c8708d2ceb53 failed for: [wheezy_udp@dns-test-service-3.dns-3758.svc.cluster.local jessie_udp@dns-test-service-3.dns-3758.svc.cluster.local]

    
    Sep  7 01:11:17.082: INFO: DNS probes using dns-test-2001060c-dc1d-4664-8fd0-c8708d2ceb53 succeeded
    
    STEP: deleting the pod
    STEP: changing the service to type=ClusterIP
    STEP: Running these commands on wheezy: for i in `seq 1 30`; do dig +short dns-test-service-3.dns-3758.svc.cluster.local A > /results/wheezy_udp@dns-test-service-3.dns-3758.svc.cluster.local; sleep 1; done
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:11:19.242: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "dns-3758" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] DNS should provide DNS for ExternalName services [Conformance]","total":-1,"completed":8,"skipped":94,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:11:19.489: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-5490" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Proxy server should support proxy with --port 0  [Conformance]","total":-1,"completed":9,"skipped":113,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-node] RuntimeClass
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 19 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:11:19.497: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "runtimeclass-5101" for this suite.
    
    •S
    ------------------------------
    {"msg":"PASSED [sig-node] RuntimeClass  should support RuntimeClasses API operations [Conformance]","total":-1,"completed":25,"skipped":663,"failed":0}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 10 lines ...
    STEP: creating a pod to probe DNS
    STEP: submitting the pod to kubernetes
    STEP: retrieving the pod
    STEP: looking for the results for each expected name from probers
    Sep  7 01:03:22.853: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:03:22.882: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:03:22.882: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:03:27.909: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:03:27.934: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:03:27.934: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:03:32.910: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:03:32.930: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:03:37.930: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:03:37.957: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:03:42.913: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:03:42.936: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:03:47.910: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:03:47.937: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:03:52.907: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:03:52.933: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:03:57.907: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:03:57.931: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:04:02.905: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:04:02.929: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:04:07.909: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:04:07.936: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:04:12.910: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:04:12.937: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:04:17.920: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:04:17.960: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:04:22.905: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:04:22.943: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:04:27.910: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:04:27.934: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:04:32.925: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:04:32.963: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:04:37.956: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:04:38.015: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:04:42.934: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:04:42.973: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:04:47.911: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:04:47.936: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:04:52.906: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:04:52.932: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:04:57.908: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:04:57.932: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:05:02.905: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:05:02.927: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:05:07.907: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:05:07.951: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:05:12.914: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:05:12.936: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:05:17.906: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:05:17.932: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:05:22.909: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:05:22.937: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:05:27.911: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:05:27.945: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:05:32.918: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:05:32.944: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:05:37.921: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:05:37.974: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:05:42.904: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:05:42.934: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:05:47.903: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:05:47.926: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:05:52.906: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:05:52.936: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:05:57.906: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:05:57.926: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:06:02.905: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:06:02.930: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:06:07.918: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:06:07.968: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:06:12.903: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:06:12.926: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:06:17.904: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:06:17.927: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:06:22.916: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:06:22.940: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:06:27.903: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:06:27.924: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:06:32.938: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:06:32.977: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:06:37.909: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:06:37.932: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:06:42.905: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:06:42.933: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:06:47.904: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:06:47.925: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:06:52.914: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:06:52.939: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:06:57.908: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:06:57.931: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:07:02.903: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:07:02.925: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:07:07.905: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:07:07.928: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:07:12.911: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:07:12.931: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:07:17.911: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:07:17.935: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:07:22.908: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:07:22.935: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:07:27.902: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:07:27.922: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:07:32.910: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:07:32.935: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:07:37.905: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:07:37.927: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:07:42.906: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:07:42.933: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:07:47.904: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:07:47.924: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:07:52.903: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:07:52.925: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:07:57.906: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:07:57.928: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:08:02.904: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:08:02.932: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:08:07.906: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:08:07.929: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:08:12.902: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:08:12.922: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:08:17.905: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:08:17.930: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:08:22.902: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:08:22.921: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:08:27.909: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:08:27.933: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:08:32.906: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:08:32.931: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:08:37.903: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:08:37.929: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:08:42.907: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:08:42.928: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:08:47.904: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:08:47.924: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:08:52.906: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:08:52.926: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:08:57.904: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:08:57.928: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:09:02.905: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:09:02.931: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:09:07.905: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:09:07.932: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:09:12.902: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:09:12.926: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:09:17.906: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:09:17.928: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:09:22.904: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:09:22.924: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:09:27.908: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:09:27.929: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:09:32.909: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:09:32.929: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:09:37.898: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:09:37.912: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:09:42.898: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:09:42.916: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:09:47.895: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:09:47.908: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:09:52.897: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:09:52.910: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:09:57.896: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:09:57.909: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:10:02.897: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:10:02.914: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:10:07.899: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:10:07.920: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:10:12.901: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:10:12.917: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:10:17.896: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:10:17.911: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:10:22.897: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:10:22.910: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:10:27.898: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:10:27.911: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:10:32.896: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:10:32.908: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:10:37.896: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:10:37.908: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:10:42.896: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:10:42.909: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:10:47.900: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:10:47.914: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:10:52.897: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:10:52.909: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:10:57.895: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:10:57.906: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:11:02.903: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:11:02.915: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:11:07.897: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:11:07.911: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:11:12.898: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:11:12.914: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:11:17.902: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81: the server could not find the requested resource (get pods dns-test-af3c175a-15da-4480-81bd-a2606895ba81)
    Sep  7 01:11:17.917: INFO: Lookups using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:11:22.911: INFO: DNS probes using dns-9600/dns-test-af3c175a-15da-4480-81bd-a2606895ba81 succeeded
    
    STEP: deleting the pod
    STEP: deleting the test headless service
    [AfterEach] [sig-network] DNS
... skipping 5 lines ...
    • [SLOW TEST:490.243 seconds]
    [sig-network] DNS
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
      should provide DNS for pods for Hostname [LinuxOnly] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    ------------------------------
    {"msg":"PASSED [sig-network] DNS should provide DNS for pods for Hostname [LinuxOnly] [Conformance]","total":-1,"completed":15,"skipped":281,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 13 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:11:23.668: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-7027" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap optional updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":10,"skipped":125,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 20 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:11:39.874: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-3712" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should verify ResourceQuota with best effort scope. [Conformance]","total":-1,"completed":11,"skipped":146,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 26 lines ...
    STEP: Destroying namespace "webhook-4652-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a validating webhook should work [Conformance]","total":-1,"completed":12,"skipped":171,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 4 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/subpath.go:38
    STEP: Setting up data
    [It] should support subpaths with secret pod [LinuxOnly] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating pod pod-subpath-test-secret-7qb7
    STEP: Creating a pod to test atomic-volume-subpath
    Sep  7 01:11:46.082: INFO: Waiting up to 5m0s for pod "pod-subpath-test-secret-7qb7" in namespace "subpath-9988" to be "Succeeded or Failed"

    Sep  7 01:11:46.087: INFO: Pod "pod-subpath-test-secret-7qb7": Phase="Pending", Reason="", readiness=false. Elapsed: 3.920359ms
    Sep  7 01:11:48.091: INFO: Pod "pod-subpath-test-secret-7qb7": Phase="Running", Reason="", readiness=true. Elapsed: 2.007619028s
    Sep  7 01:11:50.095: INFO: Pod "pod-subpath-test-secret-7qb7": Phase="Running", Reason="", readiness=true. Elapsed: 4.011844125s
    Sep  7 01:11:52.099: INFO: Pod "pod-subpath-test-secret-7qb7": Phase="Running", Reason="", readiness=true. Elapsed: 6.015853783s
    Sep  7 01:11:54.103: INFO: Pod "pod-subpath-test-secret-7qb7": Phase="Running", Reason="", readiness=true. Elapsed: 8.019616314s
    Sep  7 01:11:56.107: INFO: Pod "pod-subpath-test-secret-7qb7": Phase="Running", Reason="", readiness=true. Elapsed: 10.023839526s
    Sep  7 01:11:58.111: INFO: Pod "pod-subpath-test-secret-7qb7": Phase="Running", Reason="", readiness=true. Elapsed: 12.02845593s
    Sep  7 01:12:00.115: INFO: Pod "pod-subpath-test-secret-7qb7": Phase="Running", Reason="", readiness=true. Elapsed: 14.032431433s
    Sep  7 01:12:02.119: INFO: Pod "pod-subpath-test-secret-7qb7": Phase="Running", Reason="", readiness=true. Elapsed: 16.036489209s
    Sep  7 01:12:04.123: INFO: Pod "pod-subpath-test-secret-7qb7": Phase="Running", Reason="", readiness=true. Elapsed: 18.040505012s
    Sep  7 01:12:06.127: INFO: Pod "pod-subpath-test-secret-7qb7": Phase="Running", Reason="", readiness=true. Elapsed: 20.044601206s
    Sep  7 01:12:08.131: INFO: Pod "pod-subpath-test-secret-7qb7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.048111284s
    STEP: Saw pod success
    Sep  7 01:12:08.131: INFO: Pod "pod-subpath-test-secret-7qb7" satisfied condition "Succeeded or Failed"

    Sep  7 01:12:08.134: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-subpath-test-secret-7qb7 container test-container-subpath-secret-7qb7: <nil>
    STEP: delete the pod
    Sep  7 01:12:08.148: INFO: Waiting for pod pod-subpath-test-secret-7qb7 to disappear
    Sep  7 01:12:08.151: INFO: Pod pod-subpath-test-secret-7qb7 no longer exists
    STEP: Deleting pod pod-subpath-test-secret-7qb7
    Sep  7 01:12:08.151: INFO: Deleting pod "pod-subpath-test-secret-7qb7" in namespace "subpath-9988"
    [AfterEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:08.153: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "subpath-9988" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Subpath Atomic writer volumes should support subpaths with secret pod [LinuxOnly] [Conformance]","total":-1,"completed":13,"skipped":186,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:12:08.208: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename secrets
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be able to mount in a volume regardless of a different secret existing with same name in different namespace [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating secret with name secret-test-e32bb10c-dd02-44cd-aa4e-eae44aee28de
    STEP: Creating a pod to test consume secrets
    Sep  7 01:12:08.274: INFO: Waiting up to 5m0s for pod "pod-secrets-9d1f98b1-0a79-46aa-99a5-109ac0375f62" in namespace "secrets-7945" to be "Succeeded or Failed"

    Sep  7 01:12:08.277: INFO: Pod "pod-secrets-9d1f98b1-0a79-46aa-99a5-109ac0375f62": Phase="Pending", Reason="", readiness=false. Elapsed: 2.624096ms
    Sep  7 01:12:10.281: INFO: Pod "pod-secrets-9d1f98b1-0a79-46aa-99a5-109ac0375f62": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006511692s
    STEP: Saw pod success
    Sep  7 01:12:10.281: INFO: Pod "pod-secrets-9d1f98b1-0a79-46aa-99a5-109ac0375f62" satisfied condition "Succeeded or Failed"

    Sep  7 01:12:10.285: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-secrets-9d1f98b1-0a79-46aa-99a5-109ac0375f62 container secret-volume-test: <nil>
    STEP: delete the pod
    Sep  7 01:12:10.304: INFO: Waiting for pod pod-secrets-9d1f98b1-0a79-46aa-99a5-109ac0375f62 to disappear
    Sep  7 01:12:10.308: INFO: Pod pod-secrets-9d1f98b1-0a79-46aa-99a5-109ac0375f62 no longer exists
    [AfterEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:10.308: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-7945" for this suite.
    STEP: Destroying namespace "secret-namespace-548" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Secrets should be able to mount in a volume regardless of a different secret existing with same name in different namespace [NodeConformance] [Conformance]","total":-1,"completed":14,"skipped":218,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:12:10.433: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should support (root,0777,default) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test emptydir 0777 on node default medium
    Sep  7 01:12:10.475: INFO: Waiting up to 5m0s for pod "pod-21f23040-9206-4f44-a85b-a195c5b66d3f" in namespace "emptydir-2063" to be "Succeeded or Failed"

    Sep  7 01:12:10.477: INFO: Pod "pod-21f23040-9206-4f44-a85b-a195c5b66d3f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.799491ms
    Sep  7 01:12:12.481: INFO: Pod "pod-21f23040-9206-4f44-a85b-a195c5b66d3f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006624566s
    STEP: Saw pod success
    Sep  7 01:12:12.481: INFO: Pod "pod-21f23040-9206-4f44-a85b-a195c5b66d3f" satisfied condition "Succeeded or Failed"

    Sep  7 01:12:12.484: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-21f23040-9206-4f44-a85b-a195c5b66d3f container test-container: <nil>
    STEP: delete the pod
    Sep  7 01:12:12.500: INFO: Waiting for pod pod-21f23040-9206-4f44-a85b-a195c5b66d3f to disappear
    Sep  7 01:12:12.503: INFO: Pod pod-21f23040-9206-4f44-a85b-a195c5b66d3f no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:12.503: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-2063" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0777,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":15,"skipped":297,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Watchers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 9 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:17.979: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "watch-811" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Watchers should receive events on concurrent watches in same order [Conformance]","total":-1,"completed":16,"skipped":300,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Watchers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 27 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:19.614: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "watch-4017" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Watchers should observe add, update, and delete watch notifications on configmaps [Conformance]","total":-1,"completed":26,"skipped":672,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:41
    [It] should provide podname only [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward API volume plugin
    Sep  7 01:12:18.150: INFO: Waiting up to 5m0s for pod "downwardapi-volume-f9bf8059-8272-48d5-9ba5-a409bbd2e559" in namespace "projected-9946" to be "Succeeded or Failed"

    Sep  7 01:12:18.155: INFO: Pod "downwardapi-volume-f9bf8059-8272-48d5-9ba5-a409bbd2e559": Phase="Pending", Reason="", readiness=false. Elapsed: 4.711188ms
    Sep  7 01:12:20.159: INFO: Pod "downwardapi-volume-f9bf8059-8272-48d5-9ba5-a409bbd2e559": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.008727922s
    STEP: Saw pod success
    Sep  7 01:12:20.159: INFO: Pod "downwardapi-volume-f9bf8059-8272-48d5-9ba5-a409bbd2e559" satisfied condition "Succeeded or Failed"

    Sep  7 01:12:20.162: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod downwardapi-volume-f9bf8059-8272-48d5-9ba5-a409bbd2e559 container client-container: <nil>
    STEP: delete the pod
    Sep  7 01:12:20.180: INFO: Waiting for pod downwardapi-volume-f9bf8059-8272-48d5-9ba5-a409bbd2e559 to disappear
    Sep  7 01:12:20.183: INFO: Pod downwardapi-volume-f9bf8059-8272-48d5-9ba5-a409bbd2e559 no longer exists
    [AfterEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:20.183: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-9946" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should provide podname only [NodeConformance] [Conformance]","total":-1,"completed":17,"skipped":326,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Ingress API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 26 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:20.361: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "ingress-3095" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Ingress API should support creating Ingress API operations [Conformance]","total":-1,"completed":18,"skipped":342,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] Deployment
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 26 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:22.557: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-587" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment RecreateDeployment should delete old pods and create new ones [Conformance]","total":-1,"completed":19,"skipped":361,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Watchers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 18 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:22.662: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "watch-6896" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Watchers should be able to restart watching from the last resource version observed by the previous watch [Conformance]","total":-1,"completed":20,"skipped":382,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:12:22.674: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with mappings [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap with name configmap-test-volume-map-120d7ed4-380f-44b0-967d-6e5338b0386a
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:12:22.724: INFO: Waiting up to 5m0s for pod "pod-configmaps-305bee0c-0311-43df-9684-80d10727663a" in namespace "configmap-1411" to be "Succeeded or Failed"

    Sep  7 01:12:22.728: INFO: Pod "pod-configmaps-305bee0c-0311-43df-9684-80d10727663a": Phase="Pending", Reason="", readiness=false. Elapsed: 4.2967ms
    Sep  7 01:12:24.732: INFO: Pod "pod-configmaps-305bee0c-0311-43df-9684-80d10727663a": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.008151643s
    STEP: Saw pod success
    Sep  7 01:12:24.732: INFO: Pod "pod-configmaps-305bee0c-0311-43df-9684-80d10727663a" satisfied condition "Succeeded or Failed"

    Sep  7 01:12:24.735: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-configmaps-305bee0c-0311-43df-9684-80d10727663a container agnhost-container: <nil>
    STEP: delete the pod
    Sep  7 01:12:24.760: INFO: Waiting for pod pod-configmaps-305bee0c-0311-43df-9684-80d10727663a to disappear
    Sep  7 01:12:24.766: INFO: Pod pod-configmaps-305bee0c-0311-43df-9684-80d10727663a no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:24.767: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-1411" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with mappings [NodeConformance] [Conformance]","total":-1,"completed":21,"skipped":382,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] Deployment
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 28 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:31.918: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-4078" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment RollingUpdateDeployment should delete old pods and create new ones [Conformance]","total":-1,"completed":22,"skipped":396,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Container Runtime
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 13 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:34.013: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-runtime-2996" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Container Runtime blackbox test on terminated container should report termination message [LinuxOnly] if TerminationMessagePath is set as non-root user and at a non-default path [NodeConformance] [Conformance]","total":-1,"completed":23,"skipped":409,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:12:34.041: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should support (root,0777,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test emptydir 0777 on tmpfs
    Sep  7 01:12:34.079: INFO: Waiting up to 5m0s for pod "pod-1d74d8a2-b527-4237-9338-c90f065041f0" in namespace "emptydir-3819" to be "Succeeded or Failed"

    Sep  7 01:12:34.082: INFO: Pod "pod-1d74d8a2-b527-4237-9338-c90f065041f0": Phase="Pending", Reason="", readiness=false. Elapsed: 2.546247ms
    Sep  7 01:12:36.086: INFO: Pod "pod-1d74d8a2-b527-4237-9338-c90f065041f0": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006849571s
    STEP: Saw pod success
    Sep  7 01:12:36.086: INFO: Pod "pod-1d74d8a2-b527-4237-9338-c90f065041f0" satisfied condition "Succeeded or Failed"

    Sep  7 01:12:36.089: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-1d74d8a2-b527-4237-9338-c90f065041f0 container test-container: <nil>
    STEP: delete the pod
    Sep  7 01:12:36.104: INFO: Waiting for pod pod-1d74d8a2-b527-4237-9338-c90f065041f0 to disappear
    Sep  7 01:12:36.106: INFO: Pod pod-1d74d8a2-b527-4237-9338-c90f065041f0 no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:36.106: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-3819" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0777,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":24,"skipped":423,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Container Lifecycle Hook
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 28 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:37.726: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-lifecycle-hook-5106" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop http hook properly [NodeConformance] [Conformance]","total":-1,"completed":27,"skipped":682,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] server version
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:37.794: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "server-version-5161" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] server version should find the server version [Conformance]","total":-1,"completed":28,"skipped":692,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:12:36.179: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename projected
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap with name projected-configmap-test-volume-3ae0a187-ce7f-476c-b241-6105a03b236d
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:12:36.221: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-7d7fc443-f754-4e31-8b11-2c46e154dd81" in namespace "projected-4903" to be "Succeeded or Failed"

    Sep  7 01:12:36.225: INFO: Pod "pod-projected-configmaps-7d7fc443-f754-4e31-8b11-2c46e154dd81": Phase="Pending", Reason="", readiness=false. Elapsed: 3.487707ms
    Sep  7 01:12:38.229: INFO: Pod "pod-projected-configmaps-7d7fc443-f754-4e31-8b11-2c46e154dd81": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.008058802s
    STEP: Saw pod success
    Sep  7 01:12:38.230: INFO: Pod "pod-projected-configmaps-7d7fc443-f754-4e31-8b11-2c46e154dd81" satisfied condition "Succeeded or Failed"

    Sep  7 01:12:38.233: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-projected-configmaps-7d7fc443-f754-4e31-8b11-2c46e154dd81 container agnhost-container: <nil>
    STEP: delete the pod
    Sep  7 01:12:38.252: INFO: Waiting for pod pod-projected-configmaps-7d7fc443-f754-4e31-8b11-2c46e154dd81 to disappear
    Sep  7 01:12:38.255: INFO: Pod pod-projected-configmaps-7d7fc443-f754-4e31-8b11-2c46e154dd81 no longer exists
    [AfterEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:38.256: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-4903" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap should be consumable from pods in volume [NodeConformance] [Conformance]","total":-1,"completed":25,"skipped":469,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    S
    ------------------------------
    [BeforeEach] [sig-instrumentation] Events API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 13 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:38.332: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-1396" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-instrumentation] Events API should delete a collection of events [Conformance]","total":-1,"completed":26,"skipped":470,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 48 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:41.780: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-1036" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl label should update the label on a resource  [Conformance]","total":-1,"completed":27,"skipped":509,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:12:41.812: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename secrets
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in env vars [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating secret with name secret-test-c11f4d37-740e-4ad3-abb6-df1ce6e51a82
    STEP: Creating a pod to test consume secrets
    Sep  7 01:12:41.846: INFO: Waiting up to 5m0s for pod "pod-secrets-97ff3cb3-2114-451c-b8df-9215643bb8e6" in namespace "secrets-8792" to be "Succeeded or Failed"

    Sep  7 01:12:41.849: INFO: Pod "pod-secrets-97ff3cb3-2114-451c-b8df-9215643bb8e6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.821013ms
    Sep  7 01:12:43.853: INFO: Pod "pod-secrets-97ff3cb3-2114-451c-b8df-9215643bb8e6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.0065564s
    STEP: Saw pod success
    Sep  7 01:12:43.853: INFO: Pod "pod-secrets-97ff3cb3-2114-451c-b8df-9215643bb8e6" satisfied condition "Succeeded or Failed"

    Sep  7 01:12:43.856: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-secrets-97ff3cb3-2114-451c-b8df-9215643bb8e6 container secret-env-test: <nil>
    STEP: delete the pod
    Sep  7 01:12:43.872: INFO: Waiting for pod pod-secrets-97ff3cb3-2114-451c-b8df-9215643bb8e6 to disappear
    Sep  7 01:12:43.874: INFO: Pod pod-secrets-97ff3cb3-2114-451c-b8df-9215643bb8e6 no longer exists
    [AfterEach] [sig-api-machinery] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:43.874: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-8792" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Secrets should be consumable from pods in env vars [NodeConformance] [Conformance]","total":-1,"completed":28,"skipped":525,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 122 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:53.096: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-8060" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Update Demo should scale a replication controller  [Conformance]","total":-1,"completed":29,"skipped":738,"failed":0}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 25 lines ...
    STEP: Destroying namespace "services-2190" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:749
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to change the type from NodePort to ExternalName [Conformance]","total":-1,"completed":29,"skipped":528,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:41
    [It] should provide container's memory request [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward API volume plugin
    Sep  7 01:12:57.947: INFO: Waiting up to 5m0s for pod "downwardapi-volume-3a9bebb2-32e1-48ea-8aa9-05eb74cc0b35" in namespace "projected-4275" to be "Succeeded or Failed"

    Sep  7 01:12:57.954: INFO: Pod "downwardapi-volume-3a9bebb2-32e1-48ea-8aa9-05eb74cc0b35": Phase="Pending", Reason="", readiness=false. Elapsed: 6.547724ms
    Sep  7 01:12:59.958: INFO: Pod "downwardapi-volume-3a9bebb2-32e1-48ea-8aa9-05eb74cc0b35": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.010324636s
    STEP: Saw pod success
    Sep  7 01:12:59.958: INFO: Pod "downwardapi-volume-3a9bebb2-32e1-48ea-8aa9-05eb74cc0b35" satisfied condition "Succeeded or Failed"

    Sep  7 01:12:59.961: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod downwardapi-volume-3a9bebb2-32e1-48ea-8aa9-05eb74cc0b35 container client-container: <nil>
    STEP: delete the pod
    Sep  7 01:12:59.986: INFO: Waiting for pod downwardapi-volume-3a9bebb2-32e1-48ea-8aa9-05eb74cc0b35 to disappear
    Sep  7 01:12:59.988: INFO: Pod downwardapi-volume-3a9bebb2-32e1-48ea-8aa9-05eb74cc0b35 no longer exists
    [AfterEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:12:59.988: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-4275" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should provide container's memory request [NodeConformance] [Conformance]","total":-1,"completed":30,"skipped":552,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 13 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:13:04.185: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-8673" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a replica set. [Conformance]","total":-1,"completed":30,"skipped":752,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected combined
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should project all components that make up the projection API [Projection][NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap with name configmap-projected-all-test-volume-8e9b423c-e84f-490f-8003-0d47ccb30b21
    STEP: Creating secret with name secret-projected-all-test-volume-9dc54514-b43f-4109-8964-47696f626697
    STEP: Creating a pod to test Check all projections for projected volume plugin
    Sep  7 01:13:04.326: INFO: Waiting up to 5m0s for pod "projected-volume-62e4d36b-455d-442a-a376-34ef06bc04b8" in namespace "projected-549" to be "Succeeded or Failed"

    Sep  7 01:13:04.328: INFO: Pod "projected-volume-62e4d36b-455d-442a-a376-34ef06bc04b8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.118832ms
    Sep  7 01:13:06.332: INFO: Pod "projected-volume-62e4d36b-455d-442a-a376-34ef06bc04b8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.005419977s
    STEP: Saw pod success
    Sep  7 01:13:06.332: INFO: Pod "projected-volume-62e4d36b-455d-442a-a376-34ef06bc04b8" satisfied condition "Succeeded or Failed"

    Sep  7 01:13:06.334: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod projected-volume-62e4d36b-455d-442a-a376-34ef06bc04b8 container projected-all-volume-test: <nil>
    STEP: delete the pod
    Sep  7 01:13:06.349: INFO: Waiting for pod projected-volume-62e4d36b-455d-442a-a376-34ef06bc04b8 to disappear
    Sep  7 01:13:06.352: INFO: Pod projected-volume-62e4d36b-455d-442a-a376-34ef06bc04b8 no longer exists
    [AfterEach] [sig-storage] Projected combined
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:13:06.352: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-549" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected combined should project all components that make up the projection API [Projection][NodeConformance] [Conformance]","total":-1,"completed":31,"skipped":824,"failed":0}

    
    SSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Networking
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 42 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:13:28.906: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pod-network-test-7745" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Networking Granular Checks: Pods should function for node-pod communication: http [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":32,"skipped":837,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] Job
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 21 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:13:34.041: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "job-3175" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Job should adopt matching orphans and release non-matching pods [Conformance]","total":-1,"completed":33,"skipped":846,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:13:34.215: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename secrets
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with mappings [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating secret with name secret-test-map-7ad5640e-bc23-44d0-a48d-f01a90d0c993
    STEP: Creating a pod to test consume secrets
    Sep  7 01:13:34.320: INFO: Waiting up to 5m0s for pod "pod-secrets-f9e3fa34-5e1b-4a61-b805-2d8c09446a86" in namespace "secrets-7419" to be "Succeeded or Failed"

    Sep  7 01:13:34.329: INFO: Pod "pod-secrets-f9e3fa34-5e1b-4a61-b805-2d8c09446a86": Phase="Pending", Reason="", readiness=false. Elapsed: 8.772708ms
    Sep  7 01:13:36.333: INFO: Pod "pod-secrets-f9e3fa34-5e1b-4a61-b805-2d8c09446a86": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.012763648s
    STEP: Saw pod success
    Sep  7 01:13:36.333: INFO: Pod "pod-secrets-f9e3fa34-5e1b-4a61-b805-2d8c09446a86" satisfied condition "Succeeded or Failed"

    Sep  7 01:13:36.336: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-secrets-f9e3fa34-5e1b-4a61-b805-2d8c09446a86 container secret-volume-test: <nil>
    STEP: delete the pod
    Sep  7 01:13:36.352: INFO: Waiting for pod pod-secrets-f9e3fa34-5e1b-4a61-b805-2d8c09446a86 to disappear
    Sep  7 01:13:36.354: INFO: Pod pod-secrets-f9e3fa34-5e1b-4a61-b805-2d8c09446a86 no longer exists
    [AfterEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:13:36.355: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-7419" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Secrets should be consumable from pods in volume with mappings [NodeConformance] [Conformance]","total":-1,"completed":34,"skipped":899,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:13:36.413: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename security-context-test
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [k8s.io] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:41
    [It] should not allow privilege escalation when false [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    Sep  7 01:13:36.452: INFO: Waiting up to 5m0s for pod "alpine-nnp-false-bd34f147-bae4-4876-80e8-d76612c81aa0" in namespace "security-context-test-913" to be "Succeeded or Failed"

    Sep  7 01:13:36.458: INFO: Pod "alpine-nnp-false-bd34f147-bae4-4876-80e8-d76612c81aa0": Phase="Pending", Reason="", readiness=false. Elapsed: 5.563263ms
    Sep  7 01:13:38.462: INFO: Pod "alpine-nnp-false-bd34f147-bae4-4876-80e8-d76612c81aa0": Phase="Pending", Reason="", readiness=false. Elapsed: 2.009796055s
    Sep  7 01:13:40.466: INFO: Pod "alpine-nnp-false-bd34f147-bae4-4876-80e8-d76612c81aa0": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.013605646s
    Sep  7 01:13:40.466: INFO: Pod "alpine-nnp-false-bd34f147-bae4-4876-80e8-d76612c81aa0" satisfied condition "Succeeded or Failed"

    [AfterEach] [k8s.io] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:13:40.472: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "security-context-test-913" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Security Context when creating containers with AllowPrivilegeEscalation should not allow privilege escalation when false [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":35,"skipped":925,"failed":0}

    
    SSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 15 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:13:43.080: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-7204" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Pods should be updated [NodeConformance] [Conformance]","total":-1,"completed":36,"skipped":938,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:14:05.533: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-6988" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of same group but different versions [Conformance]","total":-1,"completed":37,"skipped":949,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 10 lines ...
    STEP: Destroying namespace "services-4441" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:749
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should provide secure master service  [Conformance]","total":-1,"completed":38,"skipped":957,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:14:05.628: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should support (non-root,0777,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test emptydir 0777 on tmpfs
    Sep  7 01:14:05.662: INFO: Waiting up to 5m0s for pod "pod-f4fdd3ab-7f09-484c-a3a0-8f58d22f7e21" in namespace "emptydir-4716" to be "Succeeded or Failed"

    Sep  7 01:14:05.665: INFO: Pod "pod-f4fdd3ab-7f09-484c-a3a0-8f58d22f7e21": Phase="Pending", Reason="", readiness=false. Elapsed: 2.710142ms
    Sep  7 01:14:07.669: INFO: Pod "pod-f4fdd3ab-7f09-484c-a3a0-8f58d22f7e21": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006829464s
    STEP: Saw pod success
    Sep  7 01:14:07.669: INFO: Pod "pod-f4fdd3ab-7f09-484c-a3a0-8f58d22f7e21" satisfied condition "Succeeded or Failed"

    Sep  7 01:14:07.672: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod pod-f4fdd3ab-7f09-484c-a3a0-8f58d22f7e21 container test-container: <nil>
    STEP: delete the pod
    Sep  7 01:14:07.687: INFO: Waiting for pod pod-f4fdd3ab-7f09-484c-a3a0-8f58d22f7e21 to disappear
    Sep  7 01:14:07.690: INFO: Pod pod-f4fdd3ab-7f09-484c-a3a0-8f58d22f7e21 no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:14:07.690: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-4716" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0777,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":39,"skipped":981,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [k8s.io] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 20 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:14:44.443: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-3592" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Variable Expansion should succeed in writing subpaths in container [sig-storage][Slow] [Conformance]","total":-1,"completed":40,"skipped":984,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:14:46.592: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-440" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Pods should support retrieving logs from the container over websockets [NodeConformance] [Conformance]","total":-1,"completed":41,"skipped":1018,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 3 lines ...
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:745
    [It] should serve a basic endpoint from pods  [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: creating service endpoint-test2 in namespace services-6142
    STEP: waiting up to 3m0s for service endpoint-test2 in namespace services-6142 to expose endpoints map[]
    Sep  7 01:14:46.690: INFO: Failed go get Endpoints object: endpoints "endpoint-test2" not found

    Sep  7 01:14:47.697: INFO: successfully validated that service endpoint-test2 in namespace services-6142 exposes endpoints map[]
    STEP: Creating pod pod1 in namespace services-6142
    STEP: waiting up to 3m0s for service endpoint-test2 in namespace services-6142 to expose endpoints map[pod1:[80]]
    Sep  7 01:14:49.721: INFO: successfully validated that service endpoint-test2 in namespace services-6142 exposes endpoints map[pod1:[80]]
    STEP: Creating pod pod2 in namespace services-6142
    STEP: waiting up to 3m0s for service endpoint-test2 in namespace services-6142 to expose endpoints map[pod1:[80] pod2:[80]]
... skipping 10 lines ...
    STEP: Destroying namespace "services-6142" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:749
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should serve a basic endpoint from pods  [Conformance]","total":-1,"completed":42,"skipped":1048,"failed":0}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:14:54.000: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-9562" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Pods should support remote command execution over websockets [NodeConformance] [Conformance]","total":-1,"completed":43,"skipped":1055,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 22 lines ...
    STEP: Destroying namespace "webhook-7648-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with pruning [Conformance]","total":-1,"completed":44,"skipped":1072,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] [sig-node] Events
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 17 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:15:04.931: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-4666" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] [sig-node] Events should be sent by kubelets and the scheduler about pods scheduling and running  [Conformance]","total":-1,"completed":45,"skipped":1098,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-auth] ServiceAccounts
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 25 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:15:05.582: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "svcaccounts-1307" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-auth] ServiceAccounts should allow opting out of API token automount  [Conformance]","total":-1,"completed":46,"skipped":1104,"failed":0}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Garbage collector
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 12 lines ...
    Sep  7 01:11:33.096: INFO: 
    Sep  7 01:11:38.095: INFO: 10 pods remaining
    Sep  7 01:11:38.095: INFO: 10 pods has nil DeletionTimestamp
    Sep  7 01:11:38.095: INFO: 
    STEP: Gathering metrics
    W0907 01:11:43.100285      18 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled.
    Sep  7 01:16:43.104: INFO: MetricsGrabber failed grab metrics. Skipping metrics gathering.

    Sep  7 01:16:43.104: INFO: Deleting pod "simpletest-rc-to-be-deleted-2qqzq" in namespace "gc-9172"
    Sep  7 01:16:43.115: INFO: Deleting pod "simpletest-rc-to-be-deleted-69mqt" in namespace "gc-9172"
    Sep  7 01:16:43.128: INFO: Deleting pod "simpletest-rc-to-be-deleted-8wc45" in namespace "gc-9172"
    Sep  7 01:16:43.144: INFO: Deleting pod "simpletest-rc-to-be-deleted-9z99p" in namespace "gc-9172"
    Sep  7 01:16:43.158: INFO: Deleting pod "simpletest-rc-to-be-deleted-dl257" in namespace "gc-9172"
    [AfterEach] [sig-api-machinery] Garbage collector
... skipping 5 lines ...
    • [SLOW TEST:320.184 seconds]
    [sig-api-machinery] Garbage collector
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      should not delete dependents that have both valid owner and owner that's waiting for dependents to be deleted [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Garbage collector should not delete dependents that have both valid owner and owner that's waiting for dependents to be deleted [Conformance]","total":-1,"completed":16,"skipped":308,"failed":0}

    
    SSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:16:43.213: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename projected
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with mappings and Item mode set [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap with name projected-configmap-test-volume-map-f67c9e7d-00fb-43e7-96a1-9733b51407ea
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:16:43.270: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-b602c398-e76a-4cef-b614-e1d4f12d52f7" in namespace "projected-4610" to be "Succeeded or Failed"

    Sep  7 01:16:43.281: INFO: Pod "pod-projected-configmaps-b602c398-e76a-4cef-b614-e1d4f12d52f7": Phase="Pending", Reason="", readiness=false. Elapsed: 10.384386ms
    Sep  7 01:16:45.285: INFO: Pod "pod-projected-configmaps-b602c398-e76a-4cef-b614-e1d4f12d52f7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.01477486s
    STEP: Saw pod success
    Sep  7 01:16:45.285: INFO: Pod "pod-projected-configmaps-b602c398-e76a-4cef-b614-e1d4f12d52f7" satisfied condition "Succeeded or Failed"

    Sep  7 01:16:45.288: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1 pod pod-projected-configmaps-b602c398-e76a-4cef-b614-e1d4f12d52f7 container agnhost-container: <nil>
    STEP: delete the pod
    Sep  7 01:16:45.320: INFO: Waiting for pod pod-projected-configmaps-b602c398-e76a-4cef-b614-e1d4f12d52f7 to disappear
    Sep  7 01:16:45.326: INFO: Pod pod-projected-configmaps-b602c398-e76a-4cef-b614-e1d4f12d52f7 no longer exists
    [AfterEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:16:45.326: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-4610" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap should be consumable from pods in volume with mappings and Item mode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":17,"skipped":320,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:16:45.351: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable in multiple volumes in the same pod [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap with name configmap-test-volume-559a57b9-c055-489c-9f82-8759e1b6b991
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:16:45.403: INFO: Waiting up to 5m0s for pod "pod-configmaps-52ca2366-2992-406c-9ba9-d6997ba05f89" in namespace "configmap-5541" to be "Succeeded or Failed"

    Sep  7 01:16:45.406: INFO: Pod "pod-configmaps-52ca2366-2992-406c-9ba9-d6997ba05f89": Phase="Pending", Reason="", readiness=false. Elapsed: 3.211716ms
    Sep  7 01:16:47.410: INFO: Pod "pod-configmaps-52ca2366-2992-406c-9ba9-d6997ba05f89": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007841343s
    STEP: Saw pod success
    Sep  7 01:16:47.411: INFO: Pod "pod-configmaps-52ca2366-2992-406c-9ba9-d6997ba05f89" satisfied condition "Succeeded or Failed"

    Sep  7 01:16:47.414: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1 pod pod-configmaps-52ca2366-2992-406c-9ba9-d6997ba05f89 container configmap-volume-test: <nil>
    STEP: delete the pod
    Sep  7 01:16:47.436: INFO: Waiting for pod pod-configmaps-52ca2366-2992-406c-9ba9-d6997ba05f89 to disappear
    Sep  7 01:16:47.439: INFO: Pod pod-configmaps-52ca2366-2992-406c-9ba9-d6997ba05f89 no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:16:47.439: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-5541" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable in multiple volumes in the same pod [NodeConformance] [Conformance]","total":-1,"completed":18,"skipped":330,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:16:47.468: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should support (root,0644,default) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test emptydir 0644 on node default medium
    Sep  7 01:16:47.510: INFO: Waiting up to 5m0s for pod "pod-050b5dc0-a47c-468b-a4ce-482242ebfeb8" in namespace "emptydir-3916" to be "Succeeded or Failed"

    Sep  7 01:16:47.513: INFO: Pod "pod-050b5dc0-a47c-468b-a4ce-482242ebfeb8": Phase="Pending", Reason="", readiness=false. Elapsed: 3.781411ms
    Sep  7 01:16:49.518: INFO: Pod "pod-050b5dc0-a47c-468b-a4ce-482242ebfeb8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.008529687s
    Sep  7 01:16:51.522: INFO: Pod "pod-050b5dc0-a47c-468b-a4ce-482242ebfeb8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.012492735s
    STEP: Saw pod success
    Sep  7 01:16:51.522: INFO: Pod "pod-050b5dc0-a47c-468b-a4ce-482242ebfeb8" satisfied condition "Succeeded or Failed"

    Sep  7 01:16:51.525: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod pod-050b5dc0-a47c-468b-a4ce-482242ebfeb8 container test-container: <nil>
    STEP: delete the pod
    Sep  7 01:16:51.550: INFO: Waiting for pod pod-050b5dc0-a47c-468b-a4ce-482242ebfeb8 to disappear
    Sep  7 01:16:51.553: INFO: Pod pod-050b5dc0-a47c-468b-a4ce-482242ebfeb8 no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:16:51.553: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-3916" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0644,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":19,"skipped":338,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:16:51.639: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with mappings as non-root [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap with name configmap-test-volume-map-3189a73c-61ab-4397-a5d7-58cc8e4f0d62
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:16:51.679: INFO: Waiting up to 5m0s for pod "pod-configmaps-d421927d-037b-463f-bc87-b2fdd7b58d5c" in namespace "configmap-6772" to be "Succeeded or Failed"

    Sep  7 01:16:51.682: INFO: Pod "pod-configmaps-d421927d-037b-463f-bc87-b2fdd7b58d5c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.706942ms
    Sep  7 01:16:53.686: INFO: Pod "pod-configmaps-d421927d-037b-463f-bc87-b2fdd7b58d5c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006911067s
    STEP: Saw pod success
    Sep  7 01:16:53.686: INFO: Pod "pod-configmaps-d421927d-037b-463f-bc87-b2fdd7b58d5c" satisfied condition "Succeeded or Failed"

    Sep  7 01:16:53.689: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod pod-configmaps-d421927d-037b-463f-bc87-b2fdd7b58d5c container agnhost-container: <nil>
    STEP: delete the pod
    Sep  7 01:16:53.705: INFO: Waiting for pod pod-configmaps-d421927d-037b-463f-bc87-b2fdd7b58d5c to disappear
    Sep  7 01:16:53.710: INFO: Pod pod-configmaps-d421927d-037b-463f-bc87-b2fdd7b58d5c no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:16:53.710: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-6772" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with mappings as non-root [NodeConformance] [Conformance]","total":-1,"completed":20,"skipped":396,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected secret
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:16:53.726: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename projected
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with mappings [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating projection with secret that has name projected-secret-test-map-7cc4659d-038e-4732-870b-08e0e1753383
    STEP: Creating a pod to test consume secrets
    Sep  7 01:16:53.775: INFO: Waiting up to 5m0s for pod "pod-projected-secrets-f1ff0ff7-6e80-4aa0-bbfa-af90730a1f95" in namespace "projected-4636" to be "Succeeded or Failed"

    Sep  7 01:16:53.778: INFO: Pod "pod-projected-secrets-f1ff0ff7-6e80-4aa0-bbfa-af90730a1f95": Phase="Pending", Reason="", readiness=false. Elapsed: 3.351618ms
    Sep  7 01:16:55.783: INFO: Pod "pod-projected-secrets-f1ff0ff7-6e80-4aa0-bbfa-af90730a1f95": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.008103375s
    STEP: Saw pod success
    Sep  7 01:16:55.783: INFO: Pod "pod-projected-secrets-f1ff0ff7-6e80-4aa0-bbfa-af90730a1f95" satisfied condition "Succeeded or Failed"

    Sep  7 01:16:55.787: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1 pod pod-projected-secrets-f1ff0ff7-6e80-4aa0-bbfa-af90730a1f95 container projected-secret-volume-test: <nil>
    STEP: delete the pod
    Sep  7 01:16:55.805: INFO: Waiting for pod pod-projected-secrets-f1ff0ff7-6e80-4aa0-bbfa-af90730a1f95 to disappear
    Sep  7 01:16:55.807: INFO: Pod pod-projected-secrets-f1ff0ff7-6e80-4aa0-bbfa-af90730a1f95 no longer exists
    [AfterEach] [sig-storage] Projected secret
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:16:55.807: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-4636" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected secret should be consumable from pods in volume with mappings [NodeConformance] [Conformance]","total":-1,"completed":21,"skipped":399,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [k8s.io] Probing container
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 18 lines ...
    • [SLOW TEST:244.583 seconds]
    [k8s.io] Probing container
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:624
      should *not* be restarted with a tcp:8080 liveness probe [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    ------------------------------
    {"msg":"PASSED [k8s.io] Probing container should *not* be restarted with a tcp:8080 liveness probe [NodeConformance] [Conformance]","total":-1,"completed":31,"skipped":614,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Aggregator
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 16 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:17:05.119: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "aggregator-5267" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Aggregator Should be able to support the 1.17 Sample API Server using the current Aggregator [Conformance]","total":-1,"completed":22,"skipped":400,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:41
    [It] should provide node allocatable (memory) as default memory limit if the limit is not set [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward API volume plugin
    Sep  7 01:17:05.736: INFO: Waiting up to 5m0s for pod "downwardapi-volume-c9a98905-42f7-4524-8c06-3f610d57d9cf" in namespace "downward-api-933" to be "Succeeded or Failed"

    Sep  7 01:17:05.827: INFO: Pod "downwardapi-volume-c9a98905-42f7-4524-8c06-3f610d57d9cf": Phase="Pending", Reason="", readiness=false. Elapsed: 90.89305ms
    Sep  7 01:17:07.831: INFO: Pod "downwardapi-volume-c9a98905-42f7-4524-8c06-3f610d57d9cf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.094766311s
    STEP: Saw pod success
    Sep  7 01:17:07.831: INFO: Pod "downwardapi-volume-c9a98905-42f7-4524-8c06-3f610d57d9cf" satisfied condition "Succeeded or Failed"

    Sep  7 01:17:07.834: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1 pod downwardapi-volume-c9a98905-42f7-4524-8c06-3f610d57d9cf container client-container: <nil>
    STEP: delete the pod
    Sep  7 01:17:07.851: INFO: Waiting for pod downwardapi-volume-c9a98905-42f7-4524-8c06-3f610d57d9cf to disappear
    Sep  7 01:17:07.854: INFO: Pod downwardapi-volume-c9a98905-42f7-4524-8c06-3f610d57d9cf no longer exists
    [AfterEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:17:07.854: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-933" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should provide node allocatable (memory) as default memory limit if the limit is not set [NodeConformance] [Conformance]","total":-1,"completed":32,"skipped":666,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Downward API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:17:05.477: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename downward-api
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should provide pod UID as env vars [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward api env vars
    Sep  7 01:17:05.919: INFO: Waiting up to 5m0s for pod "downward-api-c54a115b-6541-419a-8980-940c3c16cd8d" in namespace "downward-api-2412" to be "Succeeded or Failed"

    Sep  7 01:17:05.921: INFO: Pod "downward-api-c54a115b-6541-419a-8980-940c3c16cd8d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.629962ms
    Sep  7 01:17:07.925: INFO: Pod "downward-api-c54a115b-6541-419a-8980-940c3c16cd8d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006704633s
    STEP: Saw pod success
    Sep  7 01:17:07.925: INFO: Pod "downward-api-c54a115b-6541-419a-8980-940c3c16cd8d" satisfied condition "Succeeded or Failed"

    Sep  7 01:17:07.934: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod downward-api-c54a115b-6541-419a-8980-940c3c16cd8d container dapi-container: <nil>
    STEP: delete the pod
    Sep  7 01:17:07.961: INFO: Waiting for pod downward-api-c54a115b-6541-419a-8980-940c3c16cd8d to disappear
    Sep  7 01:17:07.964: INFO: Pod downward-api-c54a115b-6541-419a-8980-940c3c16cd8d no longer exists
    [AfterEach] [sig-node] Downward API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:17:07.964: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-2412" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Downward API should provide pod UID as env vars [NodeConformance] [Conformance]","total":-1,"completed":23,"skipped":410,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] ReplicationController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 14 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:17:11.098: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-5443" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should surface a failure condition on a common issue like exceeded quota [Conformance]","total":-1,"completed":24,"skipped":456,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-scheduling] LimitRange
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 32 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:17:18.234: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "limitrange-4941" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-scheduling] LimitRange should create a LimitRange with defaults and ensure pod has those defaults applied. [Conformance]","total":-1,"completed":25,"skipped":459,"failed":0}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:17:18.277: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] volume on tmpfs should have the correct mode [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test emptydir volume type on tmpfs
    Sep  7 01:17:18.317: INFO: Waiting up to 5m0s for pod "pod-4d04e980-4600-4966-9ff9-17852a3fd571" in namespace "emptydir-8212" to be "Succeeded or Failed"

    Sep  7 01:17:18.320: INFO: Pod "pod-4d04e980-4600-4966-9ff9-17852a3fd571": Phase="Pending", Reason="", readiness=false. Elapsed: 2.706422ms
    Sep  7 01:17:20.323: INFO: Pod "pod-4d04e980-4600-4966-9ff9-17852a3fd571": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006610187s
    STEP: Saw pod success
    Sep  7 01:17:20.324: INFO: Pod "pod-4d04e980-4600-4966-9ff9-17852a3fd571" satisfied condition "Succeeded or Failed"

    Sep  7 01:17:20.326: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod pod-4d04e980-4600-4966-9ff9-17852a3fd571 container test-container: <nil>
    STEP: delete the pod
    Sep  7 01:17:20.343: INFO: Waiting for pod pod-4d04e980-4600-4966-9ff9-17852a3fd571 to disappear
    Sep  7 01:17:20.348: INFO: Pod pod-4d04e980-4600-4966-9ff9-17852a3fd571 no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:17:20.348: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-8212" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes volume on tmpfs should have the correct mode [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":26,"skipped":474,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Probing container
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 14 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:17:27.983: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-probe-2725" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Probing container should be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]","total":-1,"completed":33,"skipped":680,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Service endpoints latency
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 418 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:17:31.209: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "svc-latency-5810" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Service endpoints latency should not be very high  [Conformance]","total":-1,"completed":27,"skipped":531,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [k8s.io] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:17:31.229: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename var-expansion
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should allow substituting values in a volume subpath [sig-storage] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test substitution in volume subpath
    Sep  7 01:17:31.270: INFO: Waiting up to 5m0s for pod "var-expansion-541ce5f4-105d-4ffd-b987-a9c495d866c8" in namespace "var-expansion-4653" to be "Succeeded or Failed"

    Sep  7 01:17:31.274: INFO: Pod "var-expansion-541ce5f4-105d-4ffd-b987-a9c495d866c8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.912592ms
    Sep  7 01:17:33.278: INFO: Pod "var-expansion-541ce5f4-105d-4ffd-b987-a9c495d866c8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007055053s
    STEP: Saw pod success
    Sep  7 01:17:33.278: INFO: Pod "var-expansion-541ce5f4-105d-4ffd-b987-a9c495d866c8" satisfied condition "Succeeded or Failed"

    Sep  7 01:17:33.281: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-64hd4 pod var-expansion-541ce5f4-105d-4ffd-b987-a9c495d866c8 container dapi-container: <nil>
    STEP: delete the pod
    Sep  7 01:17:33.301: INFO: Waiting for pod var-expansion-541ce5f4-105d-4ffd-b987-a9c495d866c8 to disappear
    Sep  7 01:17:33.304: INFO: Pod var-expansion-541ce5f4-105d-4ffd-b987-a9c495d866c8 no longer exists
    [AfterEach] [k8s.io] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:17:33.304: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-4653" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Variable Expansion should allow substituting values in a volume subpath [sig-storage] [Conformance]","total":-1,"completed":28,"skipped":533,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 13 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:17:56.107: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-6424" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a configMap. [Conformance]","total":-1,"completed":34,"skipped":695,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 15 lines ...
    STEP: Registering the mutating configmap webhook via the AdmissionRegistration API
    Sep  7 01:18:09.438: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:18:19.549: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:18:29.651: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:18:39.750: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:18:49.761: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:18:49.761: FAIL: waiting for webhook configuration to be ready

    Unexpected error:

        <*errors.errorString | 0xc0001fa200>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 23 lines ...
    [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      should mutate configmap [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
      Sep  7 01:18:49.761: waiting for webhook configuration to be ready
      Unexpected error:

          <*errors.errorString | 0xc0001fa200>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:987
    ------------------------------
    {"msg":"FAILED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","total":-1,"completed":34,"skipped":699,"failed":2,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]"]}

    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:18:49.864: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename webhook
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 12 lines ...
    STEP: Registering the mutating configmap webhook via the AdmissionRegistration API
    Sep  7 01:19:03.381: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:19:13.490: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:19:23.593: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:19:33.692: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:19:43.702: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:19:43.703: FAIL: waiting for webhook configuration to be ready

    Unexpected error:

        <*errors.errorString | 0xc0001fa200>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 23 lines ...
    [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      should mutate configmap [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
      Sep  7 01:19:43.703: waiting for webhook configuration to be ready
      Unexpected error:

          <*errors.errorString | 0xc0001fa200>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:987
    ------------------------------
    {"msg":"FAILED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","total":-1,"completed":34,"skipped":699,"failed":3,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]"]}

    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:19:43.780: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename webhook
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 18 lines ...
    STEP: Destroying namespace "webhook-8111-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","total":-1,"completed":35,"skipped":699,"failed":3,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]"]}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:19:47.636: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable via environment variable [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap configmap-2389/configmap-test-adb03cbb-f4a7-49b3-924b-a6401782ea4a
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:19:47.685: INFO: Waiting up to 5m0s for pod "pod-configmaps-22ba5e7b-aa82-4ea0-bf82-427f3f65a3de" in namespace "configmap-2389" to be "Succeeded or Failed"

    Sep  7 01:19:47.689: INFO: Pod "pod-configmaps-22ba5e7b-aa82-4ea0-bf82-427f3f65a3de": Phase="Pending", Reason="", readiness=false. Elapsed: 3.47976ms
    Sep  7 01:19:49.692: INFO: Pod "pod-configmaps-22ba5e7b-aa82-4ea0-bf82-427f3f65a3de": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006467868s
    STEP: Saw pod success
    Sep  7 01:19:49.692: INFO: Pod "pod-configmaps-22ba5e7b-aa82-4ea0-bf82-427f3f65a3de" satisfied condition "Succeeded or Failed"

    Sep  7 01:19:49.694: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod pod-configmaps-22ba5e7b-aa82-4ea0-bf82-427f3f65a3de container env-test: <nil>
    STEP: delete the pod
    Sep  7 01:19:49.721: INFO: Waiting for pod pod-configmaps-22ba5e7b-aa82-4ea0-bf82-427f3f65a3de to disappear
    Sep  7 01:19:49.728: INFO: Pod pod-configmaps-22ba5e7b-aa82-4ea0-bf82-427f3f65a3de no longer exists
    [AfterEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:19:49.728: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-2389" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] ConfigMap should be consumable via environment variable [NodeConformance] [Conformance]","total":-1,"completed":36,"skipped":709,"failed":3,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]"]}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 13 lines ...
    Sep  7 01:09:59.656: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:09:59.660: INFO: Unable to read wheezy_udp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:09:59.663: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:09:59.668: INFO: Unable to read jessie_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:09:59.672: INFO: Unable to read jessie_udp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:09:59.676: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:09:59.676: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@kubernetes.default.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:10:04.684: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:04.688: INFO: Unable to read wheezy_udp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:04.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:04.702: INFO: Unable to read jessie_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:04.708: INFO: Unable to read jessie_udp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:04.712: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:04.712: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@kubernetes.default.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:10:09.684: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:09.688: INFO: Unable to read wheezy_udp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:09.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:09.703: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:09.703: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:10:14.685: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:14.689: INFO: Unable to read wheezy_udp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:14.693: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:14.710: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:14.710: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:10:19.684: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:19.688: INFO: Unable to read wheezy_udp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:19.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:19.703: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:19.703: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:10:24.685: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:24.689: INFO: Unable to read wheezy_udp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:24.694: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:24.713: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:24.713: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:10:29.683: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:29.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:29.705: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:29.705: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:10:34.683: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:34.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:34.703: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:34.703: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:10:39.684: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:39.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:39.704: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:39.704: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:10:44.687: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:44.697: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:44.715: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:44.715: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:10:49.684: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:49.689: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:49.703: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:49.703: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:10:54.686: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:54.693: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:54.712: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:54.712: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:10:59.685: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:59.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:59.722: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:10:59.722: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:11:04.684: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:04.693: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:04.716: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:04.716: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:11:09.685: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:09.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:09.707: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep  7 01:11:14.686: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:14.694: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:14.713: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep  7 01:11:19.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:19.704: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:11:24.702: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:24.722: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:11:29.689: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:29.701: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:11:34.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:34.707: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:11:39.693: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:39.707: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:11:44.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:44.708: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:11:49.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:49.706: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:11:54.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:54.709: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:11:59.696: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:11:59.710: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:12:04.693: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:12:04.707: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:12:09.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:12:09.710: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:12:14.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:12:14.705: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:12:19.694: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:12:19.710: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:12:24.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:12:24.709: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:12:29.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:12:29.703: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:12:34.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:12:34.705: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:12:39.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:12:39.705: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:12:44.697: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:12:44.722: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:12:49.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:12:49.704: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:12:54.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:12:54.707: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:12:59.689: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:12:59.702: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:13:04.694: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:13:04.711: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:13:09.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:13:09.700: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:13:14.694: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:13:14.710: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:13:19.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:13:19.706: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:13:24.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:13:24.705: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:13:29.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:13:29.701: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:13:34.698: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:13:34.715: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:13:39.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:13:39.706: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:13:44.694: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:13:44.710: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:13:49.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:13:49.706: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:13:54.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:13:54.709: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:13:59.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:13:59.703: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:14:04.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:14:04.708: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:14:09.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:14:09.702: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:14:14.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:14:14.702: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:14:19.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:14:19.705: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:14:24.693: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:14:24.708: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:14:29.689: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:14:29.702: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:14:34.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:14:34.701: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:14:39.689: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:14:39.701: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:14:44.693: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:14:44.712: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:14:49.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:14:49.704: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:14:54.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:14:54.707: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:14:59.689: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:14:59.701: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:15:04.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:15:04.708: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:15:09.689: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:15:09.699: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:15:14.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:15:14.703: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:15:19.693: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:15:19.704: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:15:24.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:15:24.704: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:15:29.688: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:15:29.698: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:15:34.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:15:34.705: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:15:39.689: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:15:39.701: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:15:44.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:15:44.721: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:15:49.694: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:15:49.712: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:15:54.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:15:54.704: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:15:59.694: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:15:59.710: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:16:04.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:16:04.703: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:16:09.695: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:16:09.710: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:16:14.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:16:14.703: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:16:19.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:16:19.707: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:16:24.693: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:16:24.713: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:16:29.694: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:16:29.707: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:16:34.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:16:34.707: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:16:39.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:16:39.704: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:16:44.699: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:16:44.711: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:16:49.689: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:16:49.701: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:16:54.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:16:54.705: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:16:59.693: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:16:59.709: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:17:04.698: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:17:04.720: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:17:09.696: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:17:09.710: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:17:14.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:17:14.710: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:17:19.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:17:19.706: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:17:24.706: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:17:24.750: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:17:29.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:17:29.714: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:17:34.704: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:17:34.727: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:17:39.693: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:17:39.710: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:17:44.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:17:44.704: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:17:49.695: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:17:49.707: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:17:54.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:17:54.708: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:17:59.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:17:59.705: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:18:04.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:18:04.708: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:18:09.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:18:09.705: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:18:14.689: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:18:14.708: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:18:19.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:18:19.708: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:18:24.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:18:24.707: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:18:29.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:18:29.703: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:18:34.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:18:34.705: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:18:39.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:18:39.705: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:18:44.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:18:44.704: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:18:49.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:18:49.707: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:18:54.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:18:54.710: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:18:59.698: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:18:59.732: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:04.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:19:04.706: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:09.689: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:19:09.700: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:14.694: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:19:14.709: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:19.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:19:19.704: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:24.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:19:24.704: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:29.688: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:19:29.699: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:34.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:19:34.703: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:39.689: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:19:39.700: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:44.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:19:44.705: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:49.691: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:19:49.713: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:54.692: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:19:54.712: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:59.690: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:19:59.702: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:59.713: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975: the server could not find the requested resource (get pods dns-test-f50f7524-deba-47c2-b629-ba312da69975)
    Sep  7 01:19:59.725: INFO: Lookups using dns-6605/dns-test-f50f7524-deba-47c2-b629-ba312da69975 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:19:59.725: FAIL: Unexpected error:

        <*errors.errorString | 0xc00027c200>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 24 lines ...
    • Failure [604.147 seconds]
    [sig-network] DNS
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
      should provide DNS for the cluster  [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
      Sep  7 01:19:59.725: Unexpected error:

          <*errors.errorString | 0xc00027c200>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
... skipping 12 lines ...
    STEP: delete the deployment
    STEP: wait for all rs to be garbage collected
    STEP: expected 0 rs, got 1 rs
    STEP: expected 0 pods, got 2 pods
    STEP: Gathering metrics
    W0907 01:15:06.767890      16 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled.
    Sep  7 01:20:06.772: INFO: MetricsGrabber failed grab metrics. Skipping metrics gathering.

    [AfterEach] [sig-api-machinery] Garbage collector
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:20:06.772: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "gc-7451" for this suite.
    
    
    • [SLOW TEST:301.136 seconds]
    [sig-api-machinery] Garbage collector
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      should delete RS created by deployment when not orphaning [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Garbage collector should delete RS created by deployment when not orphaning [Conformance]","total":-1,"completed":47,"skipped":1119,"failed":0}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 29 lines ...
    STEP: Destroying namespace "services-747" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:749
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]","total":-1,"completed":48,"skipped":1134,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected secret
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:20:13.720: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename projected
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume as non-root with defaultMode and fsGroup set [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating projection with secret that has name projected-secret-test-dc79ae9f-e50e-4e37-9c64-47c1ac64c0d0
    STEP: Creating a pod to test consume secrets
    Sep  7 01:20:13.762: INFO: Waiting up to 5m0s for pod "pod-projected-secrets-b121ef96-730b-4d62-b0e9-11463be398b7" in namespace "projected-7284" to be "Succeeded or Failed"

    Sep  7 01:20:13.766: INFO: Pod "pod-projected-secrets-b121ef96-730b-4d62-b0e9-11463be398b7": Phase="Pending", Reason="", readiness=false. Elapsed: 3.468646ms
    Sep  7 01:20:15.770: INFO: Pod "pod-projected-secrets-b121ef96-730b-4d62-b0e9-11463be398b7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007446802s
    STEP: Saw pod success
    Sep  7 01:20:15.770: INFO: Pod "pod-projected-secrets-b121ef96-730b-4d62-b0e9-11463be398b7" satisfied condition "Succeeded or Failed"

    Sep  7 01:20:15.773: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1 pod pod-projected-secrets-b121ef96-730b-4d62-b0e9-11463be398b7 container projected-secret-volume-test: <nil>
    STEP: delete the pod
    Sep  7 01:20:15.796: INFO: Waiting for pod pod-projected-secrets-b121ef96-730b-4d62-b0e9-11463be398b7 to disappear
    Sep  7 01:20:15.799: INFO: Pod pod-projected-secrets-b121ef96-730b-4d62-b0e9-11463be398b7 no longer exists
    [AfterEach] [sig-storage] Projected secret
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:20:15.800: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-7284" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected secret should be consumable from pods in volume as non-root with defaultMode and fsGroup set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":49,"skipped":1155,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] Deployment
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 23 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:20:20.938: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-8501" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment deployment should delete old replica sets [Conformance]","total":-1,"completed":50,"skipped":1186,"failed":0}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 18 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:20:22.637: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-8579" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl diff should check if kubectl diff finds a difference for Deployments [Conformance]","total":-1,"completed":51,"skipped":1193,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 15 lines ...
    STEP: Creating a mutating webhook configuration
    Sep  7 01:20:03.236: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:20:13.347: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:20:23.455: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:20:33.550: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:20:43.560: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:20:43.560: FAIL: waiting for webhook configuration to be ready

    Unexpected error:

        <*errors.errorString | 0xc0001fa200>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 21 lines ...
    [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      patching/updating a mutating webhook should work [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
      Sep  7 01:20:43.560: waiting for webhook configuration to be ready
      Unexpected error:

          <*errors.errorString | 0xc0001fa200>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:526
    ------------------------------
    {"msg":"FAILED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","total":-1,"completed":36,"skipped":714,"failed":4,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]"]}

    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:20:43.636: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename webhook
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 12 lines ...
    STEP: Creating a mutating webhook configuration
    Sep  7 01:20:57.313: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:21:07.423: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:21:17.527: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:21:27.622: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:21:37.633: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:21:37.634: FAIL: waiting for webhook configuration to be ready

    Unexpected error:

        <*errors.errorString | 0xc0001fa200>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 21 lines ...
    [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      patching/updating a mutating webhook should work [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
      Sep  7 01:21:37.634: waiting for webhook configuration to be ready
      Unexpected error:

          <*errors.errorString | 0xc0001fa200>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:526
    ------------------------------
    {"msg":"FAILED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","total":-1,"completed":36,"skipped":714,"failed":5,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]"]}

    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:21:37.705: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename webhook
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 21 lines ...
    STEP: Destroying namespace "webhook-1894-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","total":-1,"completed":37,"skipped":714,"failed":5,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]"]}

    
    SSS
    ------------------------------
    [BeforeEach] [k8s.io] InitContainer [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:21:41.219: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename init-container
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [k8s.io] InitContainer [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/init_container.go:162
    [It] should not start app containers and fail the pod if init containers fail on a RestartNever pod [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: creating the pod
    Sep  7 01:21:41.306: INFO: PodSpec: initContainers in spec.initContainers
    [AfterEach] [k8s.io] InitContainer [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:21:44.214: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "init-container-1146" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] InitContainer [NodeConformance] should not start app containers and fail the pod if init containers fail on a RestartNever pod [Conformance]","total":-1,"completed":38,"skipped":717,"failed":5,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 20 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:22:00.368: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-8175" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should verify ResourceQuota with terminating scopes. [Conformance]","total":-1,"completed":39,"skipped":749,"failed":5,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]"]}

    
    SSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Watchers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 23 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:22:10.471: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "watch-6728" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Watchers should observe an object deletion if it stops meeting the requirements of the selector [Conformance]","total":-1,"completed":40,"skipped":762,"failed":5,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]"]}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 24 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:22:16.637: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-1396" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD without validation schema [Conformance]","total":-1,"completed":41,"skipped":772,"failed":5,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:22:16.718: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable via the environment [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap configmap-8186/configmap-test-0737ba8b-6208-435d-af71-6c38926c4468
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:22:16.760: INFO: Waiting up to 5m0s for pod "pod-configmaps-d3b31fea-c69a-4693-8eed-8452aa60a05e" in namespace "configmap-8186" to be "Succeeded or Failed"

    Sep  7 01:22:16.764: INFO: Pod "pod-configmaps-d3b31fea-c69a-4693-8eed-8452aa60a05e": Phase="Pending", Reason="", readiness=false. Elapsed: 3.499202ms
    Sep  7 01:22:18.767: INFO: Pod "pod-configmaps-d3b31fea-c69a-4693-8eed-8452aa60a05e": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007052392s
    STEP: Saw pod success
    Sep  7 01:22:18.767: INFO: Pod "pod-configmaps-d3b31fea-c69a-4693-8eed-8452aa60a05e" satisfied condition "Succeeded or Failed"

    Sep  7 01:22:18.770: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1 pod pod-configmaps-d3b31fea-c69a-4693-8eed-8452aa60a05e container env-test: <nil>
    STEP: delete the pod
    Sep  7 01:22:18.795: INFO: Waiting for pod pod-configmaps-d3b31fea-c69a-4693-8eed-8452aa60a05e to disappear
    Sep  7 01:22:18.798: INFO: Pod pod-configmaps-d3b31fea-c69a-4693-8eed-8452aa60a05e no longer exists
    [AfterEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:22:18.798: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-8186" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] ConfigMap should be consumable via the environment [NodeConformance] [Conformance]","total":-1,"completed":42,"skipped":829,"failed":5,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]"]}

    
    SS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:22:18.812: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should support (root,0644,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test emptydir 0644 on tmpfs
    Sep  7 01:22:18.846: INFO: Waiting up to 5m0s for pod "pod-e0f5dced-7271-4ba3-b2dc-e53d65dd77b9" in namespace "emptydir-9240" to be "Succeeded or Failed"

    Sep  7 01:22:18.849: INFO: Pod "pod-e0f5dced-7271-4ba3-b2dc-e53d65dd77b9": Phase="Pending", Reason="", readiness=false. Elapsed: 2.957792ms
    Sep  7 01:22:20.852: INFO: Pod "pod-e0f5dced-7271-4ba3-b2dc-e53d65dd77b9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.00671585s
    STEP: Saw pod success
    Sep  7 01:22:20.852: INFO: Pod "pod-e0f5dced-7271-4ba3-b2dc-e53d65dd77b9" satisfied condition "Succeeded or Failed"

    Sep  7 01:22:20.855: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1 pod pod-e0f5dced-7271-4ba3-b2dc-e53d65dd77b9 container test-container: <nil>
    STEP: delete the pod
    Sep  7 01:22:20.873: INFO: Waiting for pod pod-e0f5dced-7271-4ba3-b2dc-e53d65dd77b9 to disappear
    Sep  7 01:22:20.875: INFO: Pod pod-e0f5dced-7271-4ba3-b2dc-e53d65dd77b9 no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:22:20.875: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-9240" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0644,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":43,"skipped":831,"failed":5,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]"]}

    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:22:20.884: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename webhook
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 20 lines ...
    STEP: Destroying namespace "webhook-2580-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should deny crd creation [Conformance]","total":-1,"completed":44,"skipped":831,"failed":5,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]"]}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 7 lines ...
    STEP: Deploying the webhook pod
    STEP: Wait for the deployment to be ready
    Sep  7 01:22:27.113: INFO: deployment "sample-webhook-deployment" doesn't have the required revision set
    STEP: Deploying the webhook service
    STEP: Verifying the service has paired with the endpoint
    Sep  7 01:22:30.132: INFO: Waiting for amount of service:e2e-test-webhook endpoints to be 1
    [It] should unconditionally reject operations on fail closed webhook [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Registering a webhook that server cannot talk to, with fail closed policy, via the AdmissionRegistration API

    Sep  7 01:22:40.150: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:22:50.260: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:23:00.363: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:23:10.461: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:23:20.470: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:23:20.471: FAIL: waiting for webhook configuration to be ready

    Unexpected error:

        <*errors.errorString | 0xc0001fa200>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 19 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
    
    
    • Failure [54.246 seconds]
    [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      should unconditionally reject operations on fail closed webhook [Conformance] [It]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
      Sep  7 01:23:20.471: waiting for webhook configuration to be ready
      Unexpected error:

          <*errors.errorString | 0xc0001fa200>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:1274
    ------------------------------
    {"msg":"FAILED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","total":-1,"completed":44,"skipped":837,"failed":6,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]"]}

    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:23:20.536: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename webhook
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 4 lines ...
    STEP: Deploying the webhook pod
    STEP: Wait for the deployment to be ready
    Sep  7 01:23:21.933: INFO: new replicaset for deployment "sample-webhook-deployment" is yet to be created
    STEP: Deploying the webhook service
    STEP: Verifying the service has paired with the endpoint
    Sep  7 01:23:24.956: INFO: Waiting for amount of service:e2e-test-webhook endpoints to be 1
    [It] should unconditionally reject operations on fail closed webhook [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Registering a webhook that server cannot talk to, with fail closed policy, via the AdmissionRegistration API

    STEP: create a namespace for the webhook
    STEP: create a configmap should be unconditionally rejected by the webhook
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:23:25.030: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "webhook-2955" for this suite.
    STEP: Destroying namespace "webhook-2955-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","total":-1,"completed":45,"skipped":837,"failed":6,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]"]}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 10 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:23:31.765: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-509" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should update labels on modification [NodeConformance] [Conformance]","total":-1,"completed":46,"skipped":853,"failed":6,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 37 lines ...
    Sep  7 01:23:36.917: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=crd-publish-openapi-5619 explain e2e-test-crd-publish-openapi-2053-crds.spec'
    Sep  7 01:23:37.147: INFO: stderr: ""
    Sep  7 01:23:37.147: INFO: stdout: "KIND:     E2e-test-crd-publish-openapi-2053-crd\nVERSION:  crd-publish-openapi-test-foo.example.com/v1\n\nRESOURCE: spec <Object>\n\nDESCRIPTION:\n     Specification of Foo\n\nFIELDS:\n   bars\t<[]Object>\n     List of Bars and their specs.\n\n"
    Sep  7 01:23:37.147: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=crd-publish-openapi-5619 explain e2e-test-crd-publish-openapi-2053-crds.spec.bars'
    Sep  7 01:23:37.375: INFO: stderr: ""
    Sep  7 01:23:37.375: INFO: stdout: "KIND:     E2e-test-crd-publish-openapi-2053-crd\nVERSION:  crd-publish-openapi-test-foo.example.com/v1\n\nRESOURCE: bars <[]Object>\n\nDESCRIPTION:\n     List of Bars and their specs.\n\nFIELDS:\n   age\t<string>\n     Age of Bar.\n\n   bazs\t<[]string>\n     List of Bazs.\n\n   name\t<string> -required-\n     Name of Bar.\n\n"
    STEP: kubectl explain works to return error when explain is called on property that doesn't exist

    Sep  7 01:23:37.376: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=crd-publish-openapi-5619 explain e2e-test-crd-publish-openapi-2053-crds.spec.bars2'
    Sep  7 01:23:37.603: INFO: rc: 1
    [AfterEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:23:39.821: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-5619" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD with validation schema [Conformance]","total":-1,"completed":47,"skipped":876,"failed":6,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 57 lines ...
    STEP: Destroying namespace "services-8656" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:749
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should have session affinity timeout work for service with type clusterIP [LinuxOnly] [Conformance]","total":-1,"completed":48,"skipped":902,"failed":6,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]"]}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-apps] StatefulSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 10 lines ...
    STEP: Looking for a node to schedule stateful set and pod
    STEP: Creating pod with conflicting port in namespace statefulset-6102
    STEP: Creating statefulset with conflicting port in namespace statefulset-6102
    STEP: Waiting until pod test-pod will start running in namespace statefulset-6102
    STEP: Waiting until stateful pod ss-0 will be recreated and deleted at least once in namespace statefulset-6102
    Sep  7 01:24:23.698: INFO: Observed stateful pod in namespace: statefulset-6102, name: ss-0, uid: db8d65d3-c981-426f-8a8e-e5bc865245eb, status phase: Pending. Waiting for statefulset controller to delete.
    Sep  7 01:24:23.954: INFO: Observed stateful pod in namespace: statefulset-6102, name: ss-0, uid: db8d65d3-c981-426f-8a8e-e5bc865245eb, status phase: Failed. Waiting for statefulset controller to delete.

    Sep  7 01:24:23.961: INFO: Observed stateful pod in namespace: statefulset-6102, name: ss-0, uid: db8d65d3-c981-426f-8a8e-e5bc865245eb, status phase: Failed. Waiting for statefulset controller to delete.

    Sep  7 01:24:23.966: INFO: Observed delete event for stateful pod ss-0 in namespace statefulset-6102
    STEP: Removing pod with conflicting port in namespace statefulset-6102
    STEP: Waiting when stateful pod ss-0 will be recreated in namespace statefulset-6102 and will be in running state
    [AfterEach] [k8s.io] Basic StatefulSet functionality [StatefulSetBasic]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/statefulset.go:114
    Sep  7 01:24:25.988: INFO: Deleting all statefulset in ns statefulset-6102
... skipping 4 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:24:36.017: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-6102" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] Should recreate evicted statefulset [Conformance]","total":-1,"completed":49,"skipped":905,"failed":6,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Garbage collector
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 4 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: create the rc
    STEP: delete the rc
    STEP: wait for the rc to be deleted
    STEP: Gathering metrics
    W0907 01:20:28.723028      16 metrics_grabber.go:105] Did not receive an external client interface. Grabbing metrics from ClusterAutoscaler is disabled.
    Sep  7 01:25:28.727: INFO: MetricsGrabber failed grab metrics. Skipping metrics gathering.

    [AfterEach] [sig-api-machinery] Garbage collector
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:25:28.727: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "gc-995" for this suite.
    
    
    • [SLOW TEST:306.083 seconds]
    [sig-api-machinery] Garbage collector
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      should keep the rc around until all its pods are deleted if the deleteOptions says so [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Garbage collector should keep the rc around until all its pods are deleted if the deleteOptions says so [Conformance]","total":-1,"completed":52,"skipped":1194,"failed":0}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 14 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:25:45.821: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-5948" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a secret. [Conformance]","total":-1,"completed":53,"skipped":1210,"failed":0}

    
    SSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourceDefinition Watch [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 19 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:26:47.008: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-watch-9261" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceDefinition Watch [Privileged:ClusterAdmin] CustomResourceDefinition Watch watch on custom resource definition objects [Conformance]","total":-1,"completed":54,"skipped":1228,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 23 lines ...
    STEP: Destroying namespace "webhook-1951-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing mutating webhooks should work [Conformance]","total":-1,"completed":55,"skipped":1231,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 10 lines ...
    I0907 01:24:36.137199      14 runners.go:190] Created replication controller with name: affinity-clusterip, namespace: services-7115, replica count: 3
    I0907 01:24:39.187679      14 runners.go:190] affinity-clusterip Pods: 3 out of 3 created, 2 running, 1 pending, 0 waiting, 0 inactive, 0 terminating, 0 unknown, 0 runningButNotReady 
    I0907 01:24:42.188035      14 runners.go:190] affinity-clusterip Pods: 3 out of 3 created, 3 running, 0 pending, 0 waiting, 0 inactive, 0 terminating, 0 unknown, 0 runningButNotReady 
    Sep  7 01:24:42.194: INFO: Creating new exec pod
    Sep  7 01:24:45.206: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:24:47.407: INFO: rc: 1
    Sep  7 01:24:47.407: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:24:48.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:24:50.590: INFO: rc: 1
    Sep  7 01:24:50.591: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:24:51.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:24:53.571: INFO: rc: 1
    Sep  7 01:24:53.571: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:24:54.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:24:56.595: INFO: rc: 1
    Sep  7 01:24:56.595: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:24:57.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:24:59.564: INFO: rc: 1
    Sep  7 01:24:59.564: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:00.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:02.590: INFO: rc: 1
    Sep  7 01:25:02.590: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:03.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:05.576: INFO: rc: 1
    Sep  7 01:25:05.576: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:06.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:08.587: INFO: rc: 1
    Sep  7 01:25:08.587: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:09.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:11.580: INFO: rc: 1
    Sep  7 01:25:11.580: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:12.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:14.568: INFO: rc: 1
    Sep  7 01:25:14.568: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:15.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:17.578: INFO: rc: 1
    Sep  7 01:25:17.578: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:18.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:20.582: INFO: rc: 1
    Sep  7 01:25:20.582: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:21.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:23.584: INFO: rc: 1
    Sep  7 01:25:23.584: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:24.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:26.581: INFO: rc: 1
    Sep  7 01:25:26.581: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:27.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:29.574: INFO: rc: 1
    Sep  7 01:25:29.574: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:30.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:32.570: INFO: rc: 1
    Sep  7 01:25:32.571: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:33.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:35.579: INFO: rc: 1
    Sep  7 01:25:35.579: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:36.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:38.585: INFO: rc: 1
    Sep  7 01:25:38.585: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:39.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:41.586: INFO: rc: 1
    Sep  7 01:25:41.586: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:42.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:44.589: INFO: rc: 1
    Sep  7 01:25:44.589: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:45.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:47.589: INFO: rc: 1
    Sep  7 01:25:47.589: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:48.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:50.586: INFO: rc: 1
    Sep  7 01:25:50.586: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:51.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:53.593: INFO: rc: 1
    Sep  7 01:25:53.593: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:54.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:56.588: INFO: rc: 1
    Sep  7 01:25:56.588: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:25:57.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:25:59.596: INFO: rc: 1
    Sep  7 01:25:59.596: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:00.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:02.590: INFO: rc: 1
    Sep  7 01:26:02.590: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:03.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:05.589: INFO: rc: 1
    Sep  7 01:26:05.589: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:06.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:08.571: INFO: rc: 1
    Sep  7 01:26:08.571: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:09.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:11.571: INFO: rc: 1
    Sep  7 01:26:11.571: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:12.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:14.579: INFO: rc: 1
    Sep  7 01:26:14.579: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:15.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:17.591: INFO: rc: 1
    Sep  7 01:26:17.591: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:18.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:20.582: INFO: rc: 1
    Sep  7 01:26:20.582: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:21.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:23.585: INFO: rc: 1
    Sep  7 01:26:23.585: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:24.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:26.586: INFO: rc: 1
    Sep  7 01:26:26.586: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:27.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:29.579: INFO: rc: 1
    Sep  7 01:26:29.579: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:30.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:32.578: INFO: rc: 1
    Sep  7 01:26:32.578: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:33.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:35.571: INFO: rc: 1
    Sep  7 01:26:35.571: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:36.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:38.575: INFO: rc: 1
    Sep  7 01:26:38.575: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:39.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:41.586: INFO: rc: 1
    Sep  7 01:26:41.586: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:42.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:44.590: INFO: rc: 1
    Sep  7 01:26:44.590: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:45.408: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:47.582: INFO: rc: 1
    Sep  7 01:26:47.582: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:47.582: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80'
    Sep  7 01:26:49.757: INFO: rc: 1
    Sep  7 01:26:49.758: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7115 exec execpod-affinityxfh4l -- /bin/sh -x -c nc -zv -t -w 2 affinity-clusterip 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-clusterip 80
    nc: connect to affinity-clusterip port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:26:49.758: FAIL: Unexpected error:

        <*errors.errorString | 0xc0029fe990>: {
            s: "service is not reachable within 2m0s timeout on endpoint affinity-clusterip:80 over TCP protocol",
        }
        service is not reachable within 2m0s timeout on endpoint affinity-clusterip:80 over TCP protocol
    occurred
    
... skipping 27 lines ...
    • Failure [142.486 seconds]
    [sig-network] Services
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
      should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
      Sep  7 01:26:49.758: Unexpected error:

          <*errors.errorString | 0xc0029fe990>: {
              s: "service is not reachable within 2m0s timeout on endpoint affinity-clusterip:80 over TCP protocol",
          }
          service is not reachable within 2m0s timeout on endpoint affinity-clusterip:80 over TCP protocol
      occurred
    
... skipping 23 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:26:59.345: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-lifecycle-hook-54" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart http hook properly [NodeConformance] [Conformance]","total":-1,"completed":56,"skipped":1235,"failed":0}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:26:59.365: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should support (root,0666,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test emptydir 0666 on tmpfs
    Sep  7 01:26:59.412: INFO: Waiting up to 5m0s for pod "pod-cd689e36-ea6c-4469-b9db-411c660a5473" in namespace "emptydir-2295" to be "Succeeded or Failed"

    Sep  7 01:26:59.415: INFO: Pod "pod-cd689e36-ea6c-4469-b9db-411c660a5473": Phase="Pending", Reason="", readiness=false. Elapsed: 2.894335ms
    Sep  7 01:27:01.419: INFO: Pod "pod-cd689e36-ea6c-4469-b9db-411c660a5473": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006504601s
    STEP: Saw pod success
    Sep  7 01:27:01.419: INFO: Pod "pod-cd689e36-ea6c-4469-b9db-411c660a5473" satisfied condition "Succeeded or Failed"

    Sep  7 01:27:01.421: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod pod-cd689e36-ea6c-4469-b9db-411c660a5473 container test-container: <nil>
    STEP: delete the pod
    Sep  7 01:27:01.448: INFO: Waiting for pod pod-cd689e36-ea6c-4469-b9db-411c660a5473 to disappear
    Sep  7 01:27:01.451: INFO: Pod pod-cd689e36-ea6c-4469-b9db-411c660a5473 no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:27:01.451: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-2295" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0666,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":57,"skipped":1240,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:27:03.594: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-3252" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes pod should support shared volumes between containers [Conformance]","total":-1,"completed":58,"skipped":1250,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    {"msg":"FAILED [sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]","total":-1,"completed":49,"skipped":955,"failed":7,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]"]}

    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:26:58.584: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename services
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 42 lines ...
    STEP: Destroying namespace "services-772" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:749
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]","total":-1,"completed":50,"skipped":955,"failed":7,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]"]}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:27:17.866: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename var-expansion
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should allow composing env vars into new env vars [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test env composition
    Sep  7 01:27:17.924: INFO: Waiting up to 5m0s for pod "var-expansion-d2f3e626-f739-4187-a83b-51ab80fc2993" in namespace "var-expansion-7902" to be "Succeeded or Failed"

    Sep  7 01:27:17.928: INFO: Pod "var-expansion-d2f3e626-f739-4187-a83b-51ab80fc2993": Phase="Pending", Reason="", readiness=false. Elapsed: 4.149925ms
    Sep  7 01:27:19.931: INFO: Pod "var-expansion-d2f3e626-f739-4187-a83b-51ab80fc2993": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007419671s
    STEP: Saw pod success
    Sep  7 01:27:19.931: INFO: Pod "var-expansion-d2f3e626-f739-4187-a83b-51ab80fc2993" satisfied condition "Succeeded or Failed"

    Sep  7 01:27:19.934: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod var-expansion-d2f3e626-f739-4187-a83b-51ab80fc2993 container dapi-container: <nil>
    STEP: delete the pod
    Sep  7 01:27:19.953: INFO: Waiting for pod var-expansion-d2f3e626-f739-4187-a83b-51ab80fc2993 to disappear
    Sep  7 01:27:19.956: INFO: Pod var-expansion-d2f3e626-f739-4187-a83b-51ab80fc2993 no longer exists
    [AfterEach] [k8s.io] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:27:19.956: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-7902" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Variable Expansion should allow composing env vars into new env vars [NodeConformance] [Conformance]","total":-1,"completed":51,"skipped":962,"failed":7,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Container Runtime
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:27:20.038: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename container-runtime
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should report termination message [LinuxOnly] from log output if TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: create the container
    STEP: wait for the container to reach Failed

    STEP: get the container status
    STEP: the container should be terminated
    STEP: the termination message should be set
    Sep  7 01:27:22.096: INFO: Expected: &{DONE} to match Container's Termination Message: DONE --
    STEP: delete the container
    [AfterEach] [k8s.io] Container Runtime
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:27:22.106: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-runtime-3661" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Container Runtime blackbox test on terminated container should report termination message [LinuxOnly] from log output if TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]","total":-1,"completed":52,"skipped":1013,"failed":7,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]"]}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:41
    [It] should provide container's cpu request [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward API volume plugin
    Sep  7 01:27:22.161: INFO: Waiting up to 5m0s for pod "downwardapi-volume-80b68e02-8950-4d2b-9747-91fd0a43a1a7" in namespace "projected-8527" to be "Succeeded or Failed"

    Sep  7 01:27:22.164: INFO: Pod "downwardapi-volume-80b68e02-8950-4d2b-9747-91fd0a43a1a7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.758166ms
    Sep  7 01:27:24.168: INFO: Pod "downwardapi-volume-80b68e02-8950-4d2b-9747-91fd0a43a1a7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.00687675s
    STEP: Saw pod success
    Sep  7 01:27:24.168: INFO: Pod "downwardapi-volume-80b68e02-8950-4d2b-9747-91fd0a43a1a7" satisfied condition "Succeeded or Failed"

    Sep  7 01:27:24.171: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod downwardapi-volume-80b68e02-8950-4d2b-9747-91fd0a43a1a7 container client-container: <nil>
    STEP: delete the pod
    Sep  7 01:27:24.188: INFO: Waiting for pod downwardapi-volume-80b68e02-8950-4d2b-9747-91fd0a43a1a7 to disappear
    Sep  7 01:27:24.190: INFO: Pod downwardapi-volume-80b68e02-8950-4d2b-9747-91fd0a43a1a7 no longer exists
    [AfterEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:27:24.190: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-8527" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should provide container's cpu request [NodeConformance] [Conformance]","total":-1,"completed":53,"skipped":1018,"failed":7,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 4 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/subpath.go:38
    STEP: Setting up data
    [It] should support subpaths with configmap pod [LinuxOnly] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating pod pod-subpath-test-configmap-wvlh
    STEP: Creating a pod to test atomic-volume-subpath
    Sep  7 01:27:03.666: INFO: Waiting up to 5m0s for pod "pod-subpath-test-configmap-wvlh" in namespace "subpath-7255" to be "Succeeded or Failed"

    Sep  7 01:27:03.668: INFO: Pod "pod-subpath-test-configmap-wvlh": Phase="Pending", Reason="", readiness=false. Elapsed: 2.340543ms
    Sep  7 01:27:05.672: INFO: Pod "pod-subpath-test-configmap-wvlh": Phase="Running", Reason="", readiness=true. Elapsed: 2.006172707s
    Sep  7 01:27:07.676: INFO: Pod "pod-subpath-test-configmap-wvlh": Phase="Running", Reason="", readiness=true. Elapsed: 4.009866406s
    Sep  7 01:27:09.680: INFO: Pod "pod-subpath-test-configmap-wvlh": Phase="Running", Reason="", readiness=true. Elapsed: 6.014069547s
    Sep  7 01:27:11.684: INFO: Pod "pod-subpath-test-configmap-wvlh": Phase="Running", Reason="", readiness=true. Elapsed: 8.017878574s
    Sep  7 01:27:13.688: INFO: Pod "pod-subpath-test-configmap-wvlh": Phase="Running", Reason="", readiness=true. Elapsed: 10.021842677s
    Sep  7 01:27:15.692: INFO: Pod "pod-subpath-test-configmap-wvlh": Phase="Running", Reason="", readiness=true. Elapsed: 12.025673867s
    Sep  7 01:27:17.695: INFO: Pod "pod-subpath-test-configmap-wvlh": Phase="Running", Reason="", readiness=true. Elapsed: 14.029566922s
    Sep  7 01:27:19.699: INFO: Pod "pod-subpath-test-configmap-wvlh": Phase="Running", Reason="", readiness=true. Elapsed: 16.033471787s
    Sep  7 01:27:21.703: INFO: Pod "pod-subpath-test-configmap-wvlh": Phase="Running", Reason="", readiness=true. Elapsed: 18.037081118s
    Sep  7 01:27:23.707: INFO: Pod "pod-subpath-test-configmap-wvlh": Phase="Running", Reason="", readiness=true. Elapsed: 20.041122344s
    Sep  7 01:27:25.712: INFO: Pod "pod-subpath-test-configmap-wvlh": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.045920065s
    STEP: Saw pod success
    Sep  7 01:27:25.712: INFO: Pod "pod-subpath-test-configmap-wvlh" satisfied condition "Succeeded or Failed"

    Sep  7 01:27:25.716: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1 pod pod-subpath-test-configmap-wvlh container test-container-subpath-configmap-wvlh: <nil>
    STEP: delete the pod
    Sep  7 01:27:25.738: INFO: Waiting for pod pod-subpath-test-configmap-wvlh to disappear
    Sep  7 01:27:25.741: INFO: Pod pod-subpath-test-configmap-wvlh no longer exists
    STEP: Deleting pod pod-subpath-test-configmap-wvlh
    Sep  7 01:27:25.741: INFO: Deleting pod "pod-subpath-test-configmap-wvlh" in namespace "subpath-7255"
    [AfterEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:27:25.743: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "subpath-7255" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Subpath Atomic writer volumes should support subpaths with configmap pod [LinuxOnly] [Conformance]","total":-1,"completed":59,"skipped":1267,"failed":0}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:27:24.239: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] volume on default medium should have the correct mode [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test emptydir volume type on node default medium
    Sep  7 01:27:24.281: INFO: Waiting up to 5m0s for pod "pod-2fbdcd6e-0811-4764-986a-f5f500a6e136" in namespace "emptydir-5747" to be "Succeeded or Failed"

    Sep  7 01:27:24.284: INFO: Pod "pod-2fbdcd6e-0811-4764-986a-f5f500a6e136": Phase="Pending", Reason="", readiness=false. Elapsed: 2.424523ms
    Sep  7 01:27:26.288: INFO: Pod "pod-2fbdcd6e-0811-4764-986a-f5f500a6e136": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006519602s
    STEP: Saw pod success
    Sep  7 01:27:26.288: INFO: Pod "pod-2fbdcd6e-0811-4764-986a-f5f500a6e136" satisfied condition "Succeeded or Failed"

    Sep  7 01:27:26.291: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod pod-2fbdcd6e-0811-4764-986a-f5f500a6e136 container test-container: <nil>
    STEP: delete the pod
    Sep  7 01:27:26.308: INFO: Waiting for pod pod-2fbdcd6e-0811-4764-986a-f5f500a6e136 to disappear
    Sep  7 01:27:26.312: INFO: Pod pod-2fbdcd6e-0811-4764-986a-f5f500a6e136 no longer exists
    [AfterEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:27:26.312: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-5747" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes volume on default medium should have the correct mode [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":54,"skipped":1048,"failed":7,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]"]}

    
    SSS
    ------------------------------
    [BeforeEach] [k8s.io] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:27:25.775: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename security-context-test
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [k8s.io] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/security_context.go:41
    [It] should run the container with writable rootfs when readOnlyRootFilesystem=false [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    Sep  7 01:27:25.811: INFO: Waiting up to 5m0s for pod "busybox-readonly-false-38b57a00-0c07-4698-9063-28599a5b221a" in namespace "security-context-test-9879" to be "Succeeded or Failed"

    Sep  7 01:27:25.814: INFO: Pod "busybox-readonly-false-38b57a00-0c07-4698-9063-28599a5b221a": Phase="Pending", Reason="", readiness=false. Elapsed: 2.893788ms
    Sep  7 01:27:27.819: INFO: Pod "busybox-readonly-false-38b57a00-0c07-4698-9063-28599a5b221a": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.008009051s
    Sep  7 01:27:27.819: INFO: Pod "busybox-readonly-false-38b57a00-0c07-4698-9063-28599a5b221a" satisfied condition "Succeeded or Failed"

    [AfterEach] [k8s.io] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:27:27.819: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "security-context-test-9879" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Security Context When creating a pod with readOnlyRootFilesystem should run the container with writable rootfs when readOnlyRootFilesystem=false [NodeConformance] [Conformance]","total":-1,"completed":60,"skipped":1283,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 36 lines ...
    Sep  7 01:17:35.515: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:35.518: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:35.521: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:35.526: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:35.530: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:35.535: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:35.535: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000 wheezy_tcp@dns-test-service.dns-5000 wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_udp@dns-test-service.dns-5000.svc jessie_tcp@dns-test-service.dns-5000.svc jessie_udp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_udp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:17:40.542: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:40.549: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:40.555: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:40.560: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:40.564: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 17 lines ...
    Sep  7 01:17:40.655: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:40.662: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:40.667: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:40.672: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:40.676: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:40.681: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:40.681: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000 wheezy_tcp@dns-test-service.dns-5000 wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_udp@dns-test-service.dns-5000.svc jessie_tcp@dns-test-service.dns-5000.svc jessie_udp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_udp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:17:45.541: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:45.545: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:45.549: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:45.553: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:45.556: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 17 lines ...
    Sep  7 01:17:45.628: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:45.631: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:45.634: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:45.637: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:45.640: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:45.644: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:45.644: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000 wheezy_tcp@dns-test-service.dns-5000 wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_udp@dns-test-service.dns-5000.svc jessie_tcp@dns-test-service.dns-5000.svc jessie_udp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_udp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:17:50.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:50.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:50.546: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:50.550: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:50.553: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 17 lines ...
    Sep  7 01:17:50.618: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:50.623: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:50.627: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:50.632: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:50.636: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:50.640: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:50.640: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000 wheezy_tcp@dns-test-service.dns-5000 wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_udp@dns-test-service.dns-5000.svc jessie_tcp@dns-test-service.dns-5000.svc jessie_udp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_udp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:17:55.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:55.543: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:55.547: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:55.552: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:55.556: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 17 lines ...
    Sep  7 01:17:55.625: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:55.631: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:55.640: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:55.646: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:55.651: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:55.655: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:17:55.655: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000 wheezy_tcp@dns-test-service.dns-5000 wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_udp@dns-test-service.dns-5000.svc jessie_tcp@dns-test-service.dns-5000.svc jessie_udp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_udp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:18:00.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:00.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:00.545: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:00.548: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:00.551: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 17 lines ...
    Sep  7 01:18:00.609: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:00.612: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:00.616: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:00.618: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:00.621: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:00.624: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:00.624: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000 wheezy_tcp@dns-test-service.dns-5000 wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_udp@dns-test-service.dns-5000.svc jessie_tcp@dns-test-service.dns-5000.svc jessie_udp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_udp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:18:05.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:05.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:05.551: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:05.554: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:05.557: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 14 lines ...
    Sep  7 01:18:05.603: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:05.605: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:05.608: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:05.611: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:05.614: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:05.617: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:05.617: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_udp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_udp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:18:10.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:10.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:10.552: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:10.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:10.558: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 14 lines ...
    Sep  7 01:18:10.613: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:10.616: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:10.619: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:10.623: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:10.626: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:10.630: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:10.630: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_udp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_udp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:18:15.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:15.543: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:15.554: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:15.557: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:15.560: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 13 lines ...
    Sep  7 01:18:15.617: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:15.621: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:15.625: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:15.628: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:15.631: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:15.635: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:15.635: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_udp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:18:20.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:20.543: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:20.555: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:20.559: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:20.563: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 13 lines ...
    Sep  7 01:18:20.619: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:20.623: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:20.626: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:20.631: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:20.634: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:20.638: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:20.638: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_udp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:18:25.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:25.543: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:25.554: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:25.557: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:25.562: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 13 lines ...
    Sep  7 01:18:25.625: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:25.630: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:25.635: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:25.639: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:25.643: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:25.647: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:25.647: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_udp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:18:30.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:30.543: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:30.554: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:30.557: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:30.560: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 13 lines ...
    Sep  7 01:18:30.610: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:30.613: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:30.616: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:30.620: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:30.624: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:30.628: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:30.628: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_udp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:18:35.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:35.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:35.551: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:35.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:35.561: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 11 lines ...
    Sep  7 01:18:35.600: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:35.605: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:35.608: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:35.612: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:35.615: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:35.617: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:35.617: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:18:40.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:40.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:40.554: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:40.558: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:40.567: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 11 lines ...
    Sep  7 01:18:40.615: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:40.623: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:40.626: INFO: Unable to read jessie_udp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:40.629: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:40.633: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:40.637: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:40.637: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.dns-test-service.dns-5000.svc wheezy_udp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:18:45.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:45.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:45.558: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:45.561: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:45.575: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 8 lines ...
    Sep  7 01:18:45.606: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:45.612: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:45.618: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:45.624: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:45.627: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:45.630: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:45.630: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:18:50.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:50.543: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:50.555: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:50.560: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:50.576: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 8 lines ...
    Sep  7 01:18:50.606: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:50.614: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:50.625: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:50.633: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:50.637: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:50.641: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:50.641: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:18:55.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:55.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:55.554: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:55.557: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:55.571: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 8 lines ...
    Sep  7 01:18:55.603: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:55.609: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:55.617: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:55.625: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:55.629: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:55.633: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:18:55.633: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:19:00.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:00.541: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:00.552: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:00.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:00.567: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 8 lines ...
    Sep  7 01:19:00.594: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:00.599: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:00.605: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:00.612: INFO: Unable to read jessie_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:00.615: INFO: Unable to read 10.139.69.185_udp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:00.618: INFO: Unable to read 10.139.69.185_tcp@PTR from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:00.618: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc jessie_tcp@PodARecord 10.139.69.185_udp@PTR 10.139.69.185_tcp@PTR]

    
    Sep  7 01:19:05.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:05.543: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:05.554: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:05.558: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:05.572: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 3 lines ...
    Sep  7 01:19:05.592: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:05.595: INFO: Unable to read jessie_udp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:05.599: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:05.605: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:05.611: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:05.618: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:05.636: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:19:10.538: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:10.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:10.552: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:10.554: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:10.566: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
... skipping 2 lines ...
    Sep  7 01:19:10.585: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:10.589: INFO: Unable to read jessie_udp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:10.591: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:10.597: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:10.602: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:10.608: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:10.621: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:19:15.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:15.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:15.553: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:15.556: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:15.568: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:15.573: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:15.585: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:15.588: INFO: Unable to read jessie_udp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:15.590: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:15.595: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:15.600: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:15.606: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:15.617: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:19:20.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:20.543: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:20.552: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:20.556: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:20.571: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:20.577: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:20.589: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:20.594: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:20.599: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:20.606: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:20.613: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:20.623: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:19:25.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:25.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:25.552: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:25.554: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:25.566: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:25.572: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:25.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:25.589: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:25.594: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:25.599: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:25.605: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:25.615: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:19:30.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:30.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:30.552: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:30.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:30.568: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:30.576: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:30.587: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:30.594: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:30.599: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:30.605: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:30.613: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:30.625: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:19:35.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:35.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:35.551: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:35.554: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:35.566: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:35.572: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:35.584: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:35.589: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:35.596: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:35.602: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:35.607: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:35.619: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:19:40.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:40.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:40.551: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:40.554: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:40.566: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:40.572: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:40.584: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:40.590: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:40.596: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:40.601: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:40.608: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:40.618: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:19:45.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:45.543: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:45.554: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:45.558: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:45.571: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:45.577: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:45.589: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:45.594: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:45.600: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:45.607: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:45.613: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:45.626: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:19:50.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:50.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:50.551: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:50.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:50.568: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:50.574: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:50.588: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:50.596: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:50.603: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:50.609: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:50.615: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:50.627: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:19:55.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:55.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:55.556: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:55.560: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:55.575: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:55.581: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:55.593: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:55.599: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:55.606: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:55.612: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:55.618: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:19:55.632: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:20:00.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:00.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:00.555: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:00.558: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:00.572: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:00.577: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:00.590: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:00.596: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:00.602: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:00.611: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:00.619: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:00.634: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:20:05.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:05.543: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:05.554: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:05.558: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:05.573: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:05.579: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:05.592: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:05.598: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:05.605: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:05.612: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:05.619: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:05.634: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:20:10.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:10.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:10.552: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:10.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:10.570: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:10.577: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:10.589: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:10.594: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:10.602: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:10.608: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:10.614: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:10.626: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:20:15.539: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:15.543: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:15.556: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:15.560: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:15.575: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:15.581: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:15.593: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:15.598: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:15.603: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:15.609: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:15.614: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:15.625: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:20:20.542: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:20.551: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:20.553: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:20.564: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:20.570: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:20.582: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:20.587: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:20.592: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:20.598: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:20.604: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:20.616: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:20:25.543: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:25.554: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:25.558: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:25.573: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:25.579: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:25.593: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:25.600: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:25.608: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:25.617: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:25.626: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:25.641: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:20:30.551: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:30.554: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:30.565: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:30.570: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:30.581: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:30.586: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:30.592: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:30.597: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:30.603: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:30.613: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:20:35.553: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:35.557: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:35.570: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:35.576: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:35.587: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:35.601: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:35.611: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:35.618: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:35.626: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:35.640: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:20:40.549: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:40.552: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:40.563: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:40.568: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:40.577: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:40.582: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:40.587: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:40.592: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:40.597: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:40.608: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:20:45.556: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:45.559: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:45.573: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:45.579: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:45.590: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:45.596: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:45.602: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:45.607: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:45.613: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:45.623: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:20:50.552: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:50.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:50.566: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:50.572: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:50.584: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:50.589: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:50.595: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:50.601: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:50.607: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:50.620: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:20:55.551: INFO: Unable to read wheezy_udp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:55.554: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:55.567: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:55.573: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:55.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:55.588: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:55.593: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:55.597: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:55.602: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:20:55.613: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_udp@dns-test-service.dns-5000.svc wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:21:00.553: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:00.565: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:00.570: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:00.581: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:00.586: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:00.592: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:00.598: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:00.603: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:00.615: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:21:05.553: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:05.565: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:05.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:05.584: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:05.589: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:05.594: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:05.600: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:05.606: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:05.617: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:21:10.556: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:10.569: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:10.575: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:10.586: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:10.591: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:10.597: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:10.605: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:10.612: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:10.623: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:21:15.557: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:15.572: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:15.581: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:15.593: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:15.599: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:15.604: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:15.611: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:15.617: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:15.628: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:21:20.557: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:20.568: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:20.573: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:20.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:20.589: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:20.594: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:20.600: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:20.605: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:20.616: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:21:25.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:25.567: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:25.572: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:25.582: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:25.587: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:25.593: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:25.599: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:25.603: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:25.613: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:21:30.553: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:30.563: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:30.569: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:30.580: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:30.584: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:30.589: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:30.594: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:30.599: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:30.609: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:21:35.553: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:35.567: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:35.572: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:35.582: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:35.587: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:35.592: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:35.599: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:35.606: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:35.617: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:21:40.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:40.567: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:40.572: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:40.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:40.588: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:40.593: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:40.598: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:40.603: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:40.614: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:21:45.553: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:45.565: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:45.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:45.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:45.589: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:45.594: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:45.601: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:45.607: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:45.619: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@_http._tcp.test-service-2.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:21:50.556: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:50.574: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:50.584: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:50.590: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:50.595: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:50.601: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:50.607: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:50.618: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:21:55.554: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:55.570: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:55.580: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:55.586: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:55.591: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:55.596: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:55.601: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:21:55.611: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:22:00.556: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:00.573: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:00.584: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:00.589: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:00.594: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:00.599: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:00.604: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:00.614: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:22:05.556: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:05.578: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:05.591: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:05.598: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:05.603: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:05.608: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:05.614: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:05.625: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:22:10.557: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:10.579: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:10.590: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:10.595: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:10.601: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:10.606: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:10.613: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:10.625: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:22:15.557: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:15.577: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:15.593: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:15.599: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:15.608: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:15.615: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:15.621: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:15.634: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:22:20.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:20.574: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:20.585: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:20.590: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:20.595: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:20.601: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:20.606: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:20.616: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:22:25.556: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:25.575: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:25.591: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:25.598: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:25.605: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:25.611: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:25.617: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:25.633: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:22:30.554: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:30.573: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:30.584: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:30.589: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:30.595: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:30.600: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:30.605: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:30.617: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:22:35.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:35.572: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:35.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:35.588: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:35.593: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:35.599: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:35.604: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:35.615: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:22:40.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:40.573: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:40.586: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:40.592: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:40.598: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:40.604: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:40.609: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:40.619: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:22:45.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:45.575: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:45.587: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:45.593: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:45.598: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:45.604: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:45.609: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:45.619: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:22:50.553: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:50.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:50.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:50.589: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:50.595: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:50.601: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:50.606: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:50.618: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:22:55.555: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:55.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:55.581: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:55.586: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:55.591: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:55.596: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:55.601: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:22:55.611: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:23:00.553: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:00.569: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:00.581: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:00.587: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:00.593: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:00.598: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:00.604: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:00.614: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:23:05.554: INFO: Unable to read wheezy_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:05.570: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:05.581: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:05.586: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:05.592: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:05.597: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:05.602: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:05.612: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@dns-test-service.dns-5000.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:23:10.574: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:10.587: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:10.593: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:10.600: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:10.606: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:10.613: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:10.625: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:23:15.576: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:15.586: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:15.591: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:15.597: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:15.603: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:15.608: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:15.618: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:23:20.613: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:20.625: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:20.631: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:20.637: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:20.643: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:20.649: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:20.660: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:23:25.586: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:25.602: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:25.609: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:25.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:25.623: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:25.630: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:25.650: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:23:30.574: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:30.585: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:30.592: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:30.598: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:30.603: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:30.608: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:30.618: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:23:35.573: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:35.584: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:35.590: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:35.595: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:35.601: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:35.608: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:35.620: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:23:40.577: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:40.588: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:40.593: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:40.599: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:40.604: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:40.611: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:40.622: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:23:45.574: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:45.589: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:45.596: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:45.603: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:45.609: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:45.615: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:45.627: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:23:50.570: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:50.584: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:50.590: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:50.596: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:50.601: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:50.607: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:50.619: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:23:55.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:55.582: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:55.586: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:55.591: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:55.597: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:55.601: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:23:55.612: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:24:00.567: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:00.578: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:00.583: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:00.588: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:00.593: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:00.599: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:00.609: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:24:05.568: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:05.578: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:05.584: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:05.589: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:05.598: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:05.605: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:05.617: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:24:10.577: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:10.589: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:10.595: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:10.602: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:10.609: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:10.616: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:10.630: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:24:15.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:15.582: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:15.587: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:15.593: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:15.598: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:15.604: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:15.614: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:24:20.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:20.582: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:20.588: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:20.593: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:20.598: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:20.604: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:20.614: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:24:25.582: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:25.596: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:25.609: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:25.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:25.623: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:25.629: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:25.641: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:24:30.576: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:30.588: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:30.594: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:30.606: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:30.612: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:30.624: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:24:35.572: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:35.585: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:35.591: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:35.604: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:35.612: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:35.625: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:24:40.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:40.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:40.589: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:40.599: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:40.605: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:40.621: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:24:45.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:45.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:45.588: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:45.599: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:45.604: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:45.616: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:24:50.570: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:50.581: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:50.588: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:50.598: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:50.603: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:50.615: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:24:55.572: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:55.582: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:55.587: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:55.598: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:55.604: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:24:55.616: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:25:00.577: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:00.589: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:00.593: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:00.603: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:00.608: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:00.620: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:25:05.570: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:05.582: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:05.588: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:05.599: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:05.605: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:05.625: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:25:10.579: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:10.592: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:10.600: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:10.617: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:10.624: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:10.638: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:25:15.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:15.581: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:15.587: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:15.597: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:15.602: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:15.613: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:25:20.579: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:20.592: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:20.597: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:20.609: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:20.614: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:20.627: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:25:25.573: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:25.585: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:25.591: INFO: Unable to read jessie_tcp@dns-test-service.dns-5000 from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:25.607: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:25.613: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:25.625: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-5000 jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:25:30.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:30.584: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:30.604: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:30.609: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:30.622: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:25:35.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:35.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:35.600: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:35.605: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:35.616: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:25:40.570: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:40.584: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:40.608: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:40.614: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:40.629: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:25:45.579: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:45.592: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:45.611: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:45.617: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:45.630: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:25:50.568: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:50.580: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:50.596: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:50.602: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:50.613: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:25:55.577: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:55.591: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:55.609: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:55.614: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:25:55.628: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:26:00.577: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:00.589: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:00.609: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:00.615: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:00.627: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:26:05.577: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:05.590: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:05.606: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:05.612: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:05.624: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:26:10.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:10.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:10.598: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:10.603: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:10.614: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:26:15.572: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:15.585: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:15.601: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:15.607: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:15.618: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:26:20.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:20.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:20.604: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:20.614: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:20.626: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:26:25.576: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:25.588: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:25.607: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:25.614: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:25.626: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:26:30.575: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:30.587: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:30.603: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:30.608: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:30.618: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:26:35.567: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:35.577: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:35.591: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:35.596: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:35.605: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:26:40.576: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:40.590: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:40.606: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:40.613: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:40.625: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:26:45.569: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:45.579: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:45.595: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:45.600: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:45.610: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:26:50.572: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:50.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:50.598: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:50.603: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:50.615: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:26:55.579: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:55.590: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:55.606: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:55.611: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:26:55.622: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:27:00.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:00.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:00.607: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:00.613: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:00.625: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:27:05.570: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:05.581: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:05.597: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:05.604: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:05.614: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:27:10.574: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:10.585: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:10.601: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:10.606: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:10.617: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:27:15.569: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:15.582: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:15.596: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:15.601: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:15.612: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:27:20.573: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:20.594: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:20.613: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:20.620: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:20.637: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:27:25.578: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:25.591: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:25.611: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:25.617: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:25.631: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:27:30.573: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:30.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:30.600: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:30.606: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:30.618: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:27:35.572: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:35.583: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:35.612: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:35.618: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:35.630: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:27:35.666: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:35.678: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:35.696: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:35.701: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-5000.svc from pod dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf: the server could not find the requested resource (get pods dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf)
    Sep  7 01:27:35.839: INFO: Lookups using dns-5000/dns-test-67d6d6c3-ba3a-4e2b-b338-0d68d663feaf failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@_http._tcp.dns-test-service.dns-5000.svc jessie_tcp@_http._tcp.test-service-2.dns-5000.svc]

    
    Sep  7 01:27:35.840: FAIL: Unexpected error:

        <*errors.errorString | 0xc00026e1f0>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 26 lines ...
    • Failure [602.746 seconds]
    [sig-network] DNS
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
      should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
      Sep  7 01:27:35.840: Unexpected error:

          <*errors.errorString | 0xc00026e1f0>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
... skipping 348 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:27:47.838: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "proxy-2249" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Proxy version v1 should proxy through a service and a pod  [Conformance]","total":-1,"completed":61,"skipped":1293,"failed":0}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 29 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:27:56.359: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-8700" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl replace should update a single-container pod's image  [Conformance]","total":-1,"completed":62,"skipped":1298,"failed":0}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected_downwardapi.go:41
    [It] should set mode on item file [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward API volume plugin
    Sep  7 01:27:56.412: INFO: Waiting up to 5m0s for pod "downwardapi-volume-957e2568-a645-4d1a-8a86-ab133130f79d" in namespace "projected-4207" to be "Succeeded or Failed"

    Sep  7 01:27:56.416: INFO: Pod "downwardapi-volume-957e2568-a645-4d1a-8a86-ab133130f79d": Phase="Pending", Reason="", readiness=false. Elapsed: 3.751493ms
    Sep  7 01:27:58.419: INFO: Pod "downwardapi-volume-957e2568-a645-4d1a-8a86-ab133130f79d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007258202s
    STEP: Saw pod success
    Sep  7 01:27:58.419: INFO: Pod "downwardapi-volume-957e2568-a645-4d1a-8a86-ab133130f79d" satisfied condition "Succeeded or Failed"

    Sep  7 01:27:58.422: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod downwardapi-volume-957e2568-a645-4d1a-8a86-ab133130f79d container client-container: <nil>
    STEP: delete the pod
    Sep  7 01:27:58.435: INFO: Waiting for pod downwardapi-volume-957e2568-a645-4d1a-8a86-ab133130f79d to disappear
    Sep  7 01:27:58.438: INFO: Pod downwardapi-volume-957e2568-a645-4d1a-8a86-ab133130f79d no longer exists
    [AfterEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:27:58.438: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-4207" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should set mode on item file [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":63,"skipped":1305,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:27:58.475: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with mappings and Item mode set [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap with name configmap-test-volume-map-efb7bf24-1d8d-424d-8645-16e86e50b2d9
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:27:58.520: INFO: Waiting up to 5m0s for pod "pod-configmaps-dcf0bc41-b446-40f6-807c-6939900c7bdf" in namespace "configmap-3107" to be "Succeeded or Failed"

    Sep  7 01:27:58.523: INFO: Pod "pod-configmaps-dcf0bc41-b446-40f6-807c-6939900c7bdf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.634915ms
    Sep  7 01:28:00.527: INFO: Pod "pod-configmaps-dcf0bc41-b446-40f6-807c-6939900c7bdf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006883076s
    STEP: Saw pod success
    Sep  7 01:28:00.527: INFO: Pod "pod-configmaps-dcf0bc41-b446-40f6-807c-6939900c7bdf" satisfied condition "Succeeded or Failed"

    Sep  7 01:28:00.530: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod pod-configmaps-dcf0bc41-b446-40f6-807c-6939900c7bdf container agnhost-container: <nil>
    STEP: delete the pod
    Sep  7 01:28:00.545: INFO: Waiting for pod pod-configmaps-dcf0bc41-b446-40f6-807c-6939900c7bdf to disappear
    Sep  7 01:28:00.548: INFO: Pod pod-configmaps-dcf0bc41-b446-40f6-807c-6939900c7bdf no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:28:00.548: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-3107" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with mappings and Item mode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":64,"skipped":1326,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 10 lines ...
    STEP: Deploying the webhook service
    STEP: Verifying the service has paired with the endpoint
    Sep  7 01:27:29.835: INFO: Waiting for amount of service:e2e-test-crd-conversion-webhook endpoints to be 1
    [It] should be able to convert from CR v1 to CR v2 [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    Sep  7 01:27:29.839: INFO: >>> kubeConfig: /tmp/kubeconfig
    Sep  7 01:27:40.410: INFO: error waiting for conversion to succeed during setup: conversion webhook for stable.example.com/v2, Kind=E2e-test-crd-webhook-969-crd failed: Post "https://e2e-test-crd-conversion-webhook.crd-webhook-3279.svc:9443/crdconvert?timeout=30s": net/http: TLS handshake timeout

    Sep  7 01:27:50.521: INFO: error waiting for conversion to succeed during setup: conversion webhook for stable.example.com/v2, Kind=E2e-test-crd-webhook-969-crd failed: Post "https://e2e-test-crd-conversion-webhook.crd-webhook-3279.svc:9443/crdconvert?timeout=30s": net/http: TLS handshake timeout

    Sep  7 01:28:00.614: INFO: error waiting for conversion to succeed during setup: conversion webhook for stable.example.com/v2, Kind=E2e-test-crd-webhook-969-crd failed: Post "https://e2e-test-crd-conversion-webhook.crd-webhook-3279.svc:9443/crdconvert?timeout=30s": net/http: TLS handshake timeout

    Sep  7 01:28:10.718: INFO: error waiting for conversion to succeed during setup: conversion webhook for stable.example.com/v2, Kind=E2e-test-crd-webhook-969-crd failed: Post "https://e2e-test-crd-conversion-webhook.crd-webhook-3279.svc:9443/crdconvert?timeout=30s": net/http: TLS handshake timeout

    Sep  7 01:28:20.725: INFO: error waiting for conversion to succeed during setup: conversion webhook for stable.example.com/v2, Kind=E2e-test-crd-webhook-969-crd failed: Post "https://e2e-test-crd-conversion-webhook.crd-webhook-3279.svc:9443/crdconvert?timeout=30s": net/http: TLS handshake timeout

    Sep  7 01:28:20.725: FAIL: Unexpected error:

        <*errors.errorString | 0xc0001fa200>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 21 lines ...
    • Failure [55.031 seconds]
    [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      should be able to convert from CR v1 to CR v2 [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
      Sep  7 01:28:20.725: Unexpected error:

          <*errors.errorString | 0xc0001fa200>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
... skipping 15 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:29:08.852: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-8634" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":65,"skipped":1328,"failed":0}

    
    SSSS
    ------------------------------
    {"msg":"FAILED [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]","total":-1,"completed":54,"skipped":1051,"failed":8,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]","[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]"]}

    [BeforeEach] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:28:21.364: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename crd-webhook
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 7 lines ...
    STEP: Deploying the webhook service
    STEP: Verifying the service has paired with the endpoint
    Sep  7 01:28:24.927: INFO: Waiting for amount of service:e2e-test-crd-conversion-webhook endpoints to be 1
    [It] should be able to convert from CR v1 to CR v2 [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    Sep  7 01:28:24.931: INFO: >>> kubeConfig: /tmp/kubeconfig
    Sep  7 01:28:35.495: INFO: error waiting for conversion to succeed during setup: conversion webhook for stable.example.com/v2, Kind=E2e-test-crd-webhook-4240-crd failed: Post "https://e2e-test-crd-conversion-webhook.crd-webhook-5050.svc:9443/crdconvert?timeout=30s": net/http: TLS handshake timeout

    Sep  7 01:28:45.600: INFO: error waiting for conversion to succeed during setup: conversion webhook for stable.example.com/v2, Kind=E2e-test-crd-webhook-4240-crd failed: Post "https://e2e-test-crd-conversion-webhook.crd-webhook-5050.svc:9443/crdconvert?timeout=30s": net/http: TLS handshake timeout

    Sep  7 01:28:55.700: INFO: error waiting for conversion to succeed during setup: conversion webhook for stable.example.com/v2, Kind=E2e-test-crd-webhook-4240-crd failed: Post "https://e2e-test-crd-conversion-webhook.crd-webhook-5050.svc:9443/crdconvert?timeout=30s": net/http: TLS handshake timeout

    Sep  7 01:29:05.802: INFO: error waiting for conversion to succeed during setup: conversion webhook for stable.example.com/v2, Kind=E2e-test-crd-webhook-4240-crd failed: Post "https://e2e-test-crd-conversion-webhook.crd-webhook-5050.svc:9443/crdconvert?timeout=30s": net/http: TLS handshake timeout

    Sep  7 01:29:15.806: INFO: error waiting for conversion to succeed during setup: conversion webhook for stable.example.com/v2, Kind=E2e-test-crd-webhook-4240-crd failed: Post "https://e2e-test-crd-conversion-webhook.crd-webhook-5050.svc:9443/crdconvert?timeout=30s": net/http: TLS handshake timeout

    Sep  7 01:29:15.806: FAIL: Unexpected error:

        <*errors.errorString | 0xc0001fa200>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 21 lines ...
    • Failure [55.017 seconds]
    [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      should be able to convert from CR v1 to CR v2 [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
      Sep  7 01:29:15.806: Unexpected error:

          <*errors.errorString | 0xc0001fa200>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/crd_conversion_webhook.go:499
    ------------------------------
    {"msg":"FAILED [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]","total":-1,"completed":54,"skipped":1051,"failed":9,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]","[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]","[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]"]}

    [BeforeEach] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:29:16.382: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename crd-webhook
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 18 lines ...
    STEP: Destroying namespace "crd-webhook-4255" for this suite.
    [AfterEach] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/crd_conversion_webhook.go:137
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]","total":-1,"completed":55,"skipped":1051,"failed":9,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]","[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]","[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:41
    [It] should provide container's cpu request [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward API volume plugin
    Sep  7 01:29:20.990: INFO: Waiting up to 5m0s for pod "downwardapi-volume-8eaf825f-8756-4ead-85d8-25402b10ae47" in namespace "downward-api-2087" to be "Succeeded or Failed"

    Sep  7 01:29:21.004: INFO: Pod "downwardapi-volume-8eaf825f-8756-4ead-85d8-25402b10ae47": Phase="Pending", Reason="", readiness=false. Elapsed: 13.804396ms
    Sep  7 01:29:23.009: INFO: Pod "downwardapi-volume-8eaf825f-8756-4ead-85d8-25402b10ae47": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.018341713s
    STEP: Saw pod success
    Sep  7 01:29:23.009: INFO: Pod "downwardapi-volume-8eaf825f-8756-4ead-85d8-25402b10ae47" satisfied condition "Succeeded or Failed"

    Sep  7 01:29:23.012: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod downwardapi-volume-8eaf825f-8756-4ead-85d8-25402b10ae47 container client-container: <nil>
    STEP: delete the pod
    Sep  7 01:29:23.026: INFO: Waiting for pod downwardapi-volume-8eaf825f-8756-4ead-85d8-25402b10ae47 to disappear
    Sep  7 01:29:23.029: INFO: Pod downwardapi-volume-8eaf825f-8756-4ead-85d8-25402b10ae47 no longer exists
    [AfterEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:29:23.029: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-2087" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should provide container's cpu request [NodeConformance] [Conformance]","total":-1,"completed":56,"skipped":1080,"failed":9,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]","[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]","[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]"]}

    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:29:23.041: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename downward-api
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:41
    [It] should provide podname only [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward API volume plugin
    Sep  7 01:29:23.078: INFO: Waiting up to 5m0s for pod "downwardapi-volume-602e596e-d541-4a86-a465-05c83273ded7" in namespace "downward-api-4264" to be "Succeeded or Failed"

    Sep  7 01:29:23.081: INFO: Pod "downwardapi-volume-602e596e-d541-4a86-a465-05c83273ded7": Phase="Pending", Reason="", readiness=false. Elapsed: 2.366689ms
    Sep  7 01:29:25.085: INFO: Pod "downwardapi-volume-602e596e-d541-4a86-a465-05c83273ded7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006249234s
    STEP: Saw pod success
    Sep  7 01:29:25.085: INFO: Pod "downwardapi-volume-602e596e-d541-4a86-a465-05c83273ded7" satisfied condition "Succeeded or Failed"

    Sep  7 01:29:25.087: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod downwardapi-volume-602e596e-d541-4a86-a465-05c83273ded7 container client-container: <nil>
    STEP: delete the pod
    Sep  7 01:29:25.102: INFO: Waiting for pod downwardapi-volume-602e596e-d541-4a86-a465-05c83273ded7 to disappear
    Sep  7 01:29:25.105: INFO: Pod downwardapi-volume-602e596e-d541-4a86-a465-05c83273ded7 no longer exists
    [AfterEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:29:25.105: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-4264" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should provide podname only [NodeConformance] [Conformance]","total":-1,"completed":57,"skipped":1080,"failed":9,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]","[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]","[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]"]}

    [BeforeEach] [k8s.io] Kubelet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:29:25.116: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename kubelet-test
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 5 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:29:27.167: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubelet-test-7530" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Kubelet when scheduling a busybox command in a pod should print the output to logs [NodeConformance] [Conformance]","total":-1,"completed":58,"skipped":1080,"failed":9,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]","[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]","[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]"]}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 2 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/downwardapi_volume.go:41
    [It] should set DefaultMode on files [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test downward API volume plugin
    Sep  7 01:29:27.225: INFO: Waiting up to 5m0s for pod "downwardapi-volume-596e9be4-3f34-4076-b8ed-05bdef28eb7b" in namespace "downward-api-8142" to be "Succeeded or Failed"

    Sep  7 01:29:27.228: INFO: Pod "downwardapi-volume-596e9be4-3f34-4076-b8ed-05bdef28eb7b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.688471ms
    Sep  7 01:29:29.232: INFO: Pod "downwardapi-volume-596e9be4-3f34-4076-b8ed-05bdef28eb7b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006546337s
    STEP: Saw pod success
    Sep  7 01:29:29.232: INFO: Pod "downwardapi-volume-596e9be4-3f34-4076-b8ed-05bdef28eb7b" satisfied condition "Succeeded or Failed"

    Sep  7 01:29:29.234: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-md-0-rvq9k-6dfcc85f89-h877k pod downwardapi-volume-596e9be4-3f34-4076-b8ed-05bdef28eb7b container client-container: <nil>
    STEP: delete the pod
    Sep  7 01:29:29.261: INFO: Waiting for pod downwardapi-volume-596e9be4-3f34-4076-b8ed-05bdef28eb7b to disappear
    Sep  7 01:29:29.264: INFO: Pod downwardapi-volume-596e9be4-3f34-4076-b8ed-05bdef28eb7b no longer exists
    [AfterEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:29:29.264: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-8142" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should set DefaultMode on files [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":59,"skipped":1094,"failed":9,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should unconditionally reject operations on fail closed webhook [Conformance]","[sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]","[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]","[sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin] should be able to convert from CR v1 to CR v2 [Conformance]"]}

    
    S
    ------------------------------
    {"msg":"FAILED [sig-network] DNS should provide DNS for the cluster  [Conformance]","total":-1,"completed":32,"skipped":787,"failed":2,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]","[sig-network] DNS should provide DNS for the cluster  [Conformance]"]}

    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:19:59.754: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename dns
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 10 lines ...
    Sep  7 01:20:01.819: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:01.822: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:01.825: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:01.834: INFO: Unable to read jessie_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:01.838: INFO: Unable to read jessie_udp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:01.841: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:01.841: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@kubernetes.default.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:20:06.852: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:06.858: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:06.868: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:06.885: INFO: Unable to read jessie_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:06.911: INFO: Unable to read jessie_udp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:06.923: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:06.923: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@kubernetes.default.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:20:11.848: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:11.851: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:11.853: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:11.865: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:11.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:20:16.849: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:16.852: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:16.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:16.867: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:16.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:20:21.853: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:21.858: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:21.861: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:21.873: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:21.873: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:20:26.849: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:26.852: INFO: Unable to read wheezy_udp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:26.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:26.867: INFO: Unable to read jessie_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:26.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  7 01:20:31.848: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:31.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:31.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep  7 01:20:36.851: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:36.858: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:36.871: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep  7 01:20:41.848: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:41.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:41.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep  7 01:20:46.848: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:46.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:46.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep  7 01:20:51.849: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:51.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:51.869: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep  7 01:20:56.849: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:56.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:20:56.870: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep  7 01:21:01.849: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:01.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:01.869: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep  7 01:21:06.849: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:06.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:06.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep  7 01:21:11.848: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:11.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:11.870: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep  7 01:21:16.848: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:16.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:16.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord]

    
    Sep  7 01:21:21.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:21.864: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:21:26.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:26.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:21:31.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:31.868: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:21:36.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:36.868: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:21:41.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:41.864: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:21:46.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:46.868: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:21:51.858: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:51.869: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:21:56.853: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:21:56.863: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:22:01.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:22:01.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:22:06.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:22:06.868: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:22:11.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:22:11.872: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:22:16.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:22:16.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:22:21.861: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:22:21.878: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:22:26.857: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:22:26.872: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:22:31.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:22:31.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:22:36.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:22:36.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:22:41.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:22:41.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:22:46.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:22:46.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:22:51.853: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:22:51.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:22:56.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:22:56.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:23:01.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:23:01.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:23:06.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:23:06.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:23:11.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:23:11.864: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:23:16.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:23:16.871: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:23:21.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:23:21.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:23:26.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:23:26.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:23:31.859: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:23:31.869: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:23:36.853: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:23:36.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:23:41.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:23:41.868: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:23:46.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:23:46.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:23:51.860: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:23:51.872: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:23:56.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:23:56.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:24:01.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:24:01.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:24:06.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:24:06.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:24:11.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:24:11.873: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:24:16.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:24:16.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:24:21.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:24:21.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:24:26.853: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:24:26.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:24:31.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:24:31.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:24:36.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:24:36.868: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:24:41.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:24:41.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:24:46.860: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:24:46.870: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:24:51.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:24:51.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:24:56.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:24:56.869: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:25:01.853: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:25:01.863: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:25:06.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:25:06.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:25:11.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:25:11.868: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:25:16.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:25:16.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:25:21.860: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:25:21.871: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:25:26.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:25:26.869: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:25:31.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:25:31.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:25:36.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:25:36.870: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:25:41.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:25:41.869: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:25:46.862: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:25:46.880: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:25:51.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:25:51.869: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:25:56.858: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:25:56.870: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:26:01.857: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:26:01.869: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:26:06.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:26:06.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:26:11.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:26:11.872: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:26:16.857: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:26:16.869: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:26:21.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:26:21.870: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:26:26.857: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:26:26.870: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:26:31.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:26:31.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:26:36.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:26:36.870: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:26:41.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:26:41.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:26:46.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:26:46.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:26:51.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:26:51.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:26:56.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:26:56.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:27:01.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:27:01.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:27:06.857: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:27:06.869: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:27:11.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:27:11.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:27:16.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:27:16.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:27:21.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:27:21.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:27:26.858: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:27:26.870: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:27:31.857: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:27:31.871: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:27:36.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:27:36.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:27:41.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:27:41.868: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:27:46.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:27:46.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:27:51.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:27:51.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:27:56.859: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:27:56.873: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:28:01.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:28:01.868: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:28:06.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:28:06.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:28:11.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:28:11.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:28:16.853: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:28:16.863: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:28:21.860: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:28:21.878: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:28:26.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:28:26.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:28:31.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:28:31.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:28:36.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:28:36.868: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:28:41.853: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:28:41.863: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:28:46.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:28:46.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:28:51.853: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:28:51.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:28:56.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:28:56.868: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:29:01.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:29:01.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:29:06.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:29:06.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:29:11.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:29:11.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:29:16.862: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:29:16.879: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:29:21.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:29:21.865: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:29:26.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:29:26.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:29:31.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:29:31.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:29:36.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:29:36.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:29:41.855: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:29:41.868: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:29:46.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:29:46.866: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:29:51.854: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:29:51.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:29:56.856: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:29:56.867: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:30:01.857: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:30:01.870: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:30:01.882: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3: the server could not find the requested resource (get pods dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3)
    Sep  7 01:30:01.897: INFO: Lookups using dns-7080/dns-test-f7d8f7b3-fe89-4bd5-84bb-ea75c62b3bf3 failed for: [wheezy_tcp@PodARecord]

    
    Sep  7 01:30:01.897: FAIL: Unexpected error:

        <*errors.errorString | 0xc00027c200>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 24 lines ...
    • Failure [602.173 seconds]
    [sig-network] DNS
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:23
      should provide DNS for the cluster  [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
      Sep  7 01:30:01.897: Unexpected error:

          <*errors.errorString | 0xc00027c200>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
... skipping 21 lines ...
    STEP: Registering the mutating pod webhook via the AdmissionRegistration API
    Sep  7 01:29:24.659: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:29:34.770: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:29:44.872: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:29:54.969: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:30:04.979: INFO: Waiting for webhook configuration to be ready...
    Sep  7 01:30:04.979: FAIL: waiting for webhook configuration to be ready

    Unexpected error:

        <*errors.errorString | 0xc0001f61f0>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 23 lines ...
    [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/framework.go:23
      should mutate pod and apply defaults after mutation [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    
      Sep  7 01:30:04.979: waiting for webhook configuration to be ready
      Unexpected error:

          <*errors.errorString | 0xc0001f61f0>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:1054
    ------------------------------
    {"msg":"FAILED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]","total":-1,"completed":65,"skipped":1332,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]"]}

    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:30:05.049: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename webhook
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 18 lines ...
    STEP: Destroying namespace "webhook-6707-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]","total":-1,"completed":66,"skipped":1332,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]"]}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 28 lines ...
    STEP: Destroying namespace "webhook-5693-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny pod and configmap creation [Conformance]","total":-1,"completed":67,"skipped":1338,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 24 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:30:29.962: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-1877" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD preserving unknown fields at the schema root [Conformance]","total":-1,"completed":68,"skipped":1360,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]"]}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 25 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:30:31.768: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-2595" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl patch should add annotations for pods in rc  [Conformance]","total":-1,"completed":69,"skipped":1364,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]"]}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 16 lines ...
    Sep  7 01:30:39.871: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:39.875: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:39.897: INFO: Unable to read jessie_udp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:39.900: INFO: Unable to read jessie_tcp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:39.903: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:39.905: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:39.922: INFO: Lookups using dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd failed for: [wheezy_udp@dns-test-service.dns-829.svc.cluster.local wheezy_tcp@dns-test-service.dns-829.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local jessie_udp@dns-test-service.dns-829.svc.cluster.local jessie_tcp@dns-test-service.dns-829.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local]

    
    Sep  7 01:30:44.926: INFO: Unable to read wheezy_udp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:44.929: INFO: Unable to read wheezy_tcp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:44.933: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:44.936: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:44.954: INFO: Unable to read jessie_udp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:44.957: INFO: Unable to read jessie_tcp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:44.959: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:44.962: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:44.980: INFO: Lookups using dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd failed for: [wheezy_udp@dns-test-service.dns-829.svc.cluster.local wheezy_tcp@dns-test-service.dns-829.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local jessie_udp@dns-test-service.dns-829.svc.cluster.local jessie_tcp@dns-test-service.dns-829.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local]

    
    Sep  7 01:30:49.927: INFO: Unable to read wheezy_udp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:49.930: INFO: Unable to read wheezy_tcp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:49.933: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:49.936: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:49.954: INFO: Unable to read jessie_udp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:49.957: INFO: Unable to read jessie_tcp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:49.960: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:49.963: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:49.985: INFO: Lookups using dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd failed for: [wheezy_udp@dns-test-service.dns-829.svc.cluster.local wheezy_tcp@dns-test-service.dns-829.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local jessie_udp@dns-test-service.dns-829.svc.cluster.local jessie_tcp@dns-test-service.dns-829.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local]

    
    Sep  7 01:30:54.927: INFO: Unable to read wheezy_udp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:54.930: INFO: Unable to read wheezy_tcp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:54.934: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:54.937: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:54.959: INFO: Unable to read jessie_udp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:54.962: INFO: Unable to read jessie_tcp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:54.966: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:54.969: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:54.986: INFO: Lookups using dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd failed for: [wheezy_udp@dns-test-service.dns-829.svc.cluster.local wheezy_tcp@dns-test-service.dns-829.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local jessie_udp@dns-test-service.dns-829.svc.cluster.local jessie_tcp@dns-test-service.dns-829.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local]

    
    Sep  7 01:30:59.926: INFO: Unable to read wheezy_udp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:59.929: INFO: Unable to read wheezy_tcp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:59.932: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:59.935: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:59.956: INFO: Unable to read jessie_udp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:59.958: INFO: Unable to read jessie_tcp@dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:59.961: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:59.965: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local from pod dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd: the server could not find the requested resource (get pods dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd)
    Sep  7 01:30:59.983: INFO: Lookups using dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd failed for: [wheezy_udp@dns-test-service.dns-829.svc.cluster.local wheezy_tcp@dns-test-service.dns-829.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local jessie_udp@dns-test-service.dns-829.svc.cluster.local jessie_tcp@dns-test-service.dns-829.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-829.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-829.svc.cluster.local]

    
    Sep  7 01:31:04.987: INFO: DNS probes using dns-829/dns-test-3dc57aa3-2eaa-4176-8347-24412b3b38fd succeeded
    
    STEP: deleting the pod
    STEP: deleting the test service
    STEP: deleting the test headless service
    [AfterEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:31:05.094: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "dns-829" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] DNS should provide DNS for services  [Conformance]","total":-1,"completed":70,"skipped":1368,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]"]}

    
    SSS
    ------------------------------
    [BeforeEach] [k8s.io] Docker Containers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:31:05.113: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename containers
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be able to override the image's default arguments (docker cmd) [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating a pod to test override arguments
    Sep  7 01:31:05.160: INFO: Waiting up to 5m0s for pod "client-containers-a389ac05-36e5-4092-8f29-8886ef098fee" in namespace "containers-6718" to be "Succeeded or Failed"

    Sep  7 01:31:05.163: INFO: Pod "client-containers-a389ac05-36e5-4092-8f29-8886ef098fee": Phase="Pending", Reason="", readiness=false. Elapsed: 3.14866ms
    Sep  7 01:31:07.167: INFO: Pod "client-containers-a389ac05-36e5-4092-8f29-8886ef098fee": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006972485s
    STEP: Saw pod success
    Sep  7 01:31:07.167: INFO: Pod "client-containers-a389ac05-36e5-4092-8f29-8886ef098fee" satisfied condition "Succeeded or Failed"

    Sep  7 01:31:07.169: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-tbg5y1 pod client-containers-a389ac05-36e5-4092-8f29-8886ef098fee container agnhost-container: <nil>
    STEP: delete the pod
    Sep  7 01:31:07.193: INFO: Waiting for pod client-containers-a389ac05-36e5-4092-8f29-8886ef098fee to disappear
    Sep  7 01:31:07.196: INFO: Pod client-containers-a389ac05-36e5-4092-8f29-8886ef098fee no longer exists
    [AfterEach] [k8s.io] Docker Containers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:31:07.196: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "containers-6718" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Docker Containers should be able to override the image's default arguments (docker cmd) [NodeConformance] [Conformance]","total":-1,"completed":71,"skipped":1371,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]"]}

    
    SS
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:31:07.212: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename projected
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume as non-root [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap with name projected-configmap-test-volume-9c74039b-189b-425d-bc45-b929b528c5bb
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:31:07.254: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-5978e504-83be-4cd5-a9ad-7f1d2a2cd60f" in namespace "projected-5738" to be "Succeeded or Failed"

    Sep  7 01:31:07.256: INFO: Pod "pod-projected-configmaps-5978e504-83be-4cd5-a9ad-7f1d2a2cd60f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.438438ms
    Sep  7 01:31:09.260: INFO: Pod "pod-projected-configmaps-5978e504-83be-4cd5-a9ad-7f1d2a2cd60f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006531838s
    STEP: Saw pod success
    Sep  7 01:31:09.260: INFO: Pod "pod-projected-configmaps-5978e504-83be-4cd5-a9ad-7f1d2a2cd60f" satisfied condition "Succeeded or Failed"

    Sep  7 01:31:09.263: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod pod-projected-configmaps-5978e504-83be-4cd5-a9ad-7f1d2a2cd60f container agnhost-container: <nil>
    STEP: delete the pod
    Sep  7 01:31:09.288: INFO: Waiting for pod pod-projected-configmaps-5978e504-83be-4cd5-a9ad-7f1d2a2cd60f to disappear
    Sep  7 01:31:09.290: INFO: Pod pod-projected-configmaps-5978e504-83be-4cd5-a9ad-7f1d2a2cd60f no longer exists
    [AfterEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:31:09.290: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-5738" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap should be consumable from pods in volume as non-root [NodeConformance] [Conformance]","total":-1,"completed":72,"skipped":1373,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]"]}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [k8s.io] Container Lifecycle Hook
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 24 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:31:23.394: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-lifecycle-hook-3464" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [k8s.io] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart exec hook properly [NodeConformance] [Conformance]","total":-1,"completed":73,"skipped":1389,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]"]}

    
    SS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 9 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:31:30.453: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-3435" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and ensure its status is promptly calculated. [Conformance]","total":-1,"completed":74,"skipped":1391,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]"]}

    
    SSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] Deployment
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 98 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:31:32.939: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-3434" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment should run the lifecycle of a Deployment [Conformance]","total":-1,"completed":75,"skipped":1404,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]"]}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 25 lines ...
    STEP: Destroying namespace "webhook-669-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with different stored version [Conformance]","total":-1,"completed":76,"skipped":1408,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]"]}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
    Sep  7 01:31:39.675: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629
    STEP: Creating configMap with name configmap-test-volume-f7b426e8-e59b-4c54-a9a3-bf2d2a8c2792
    STEP: Creating a pod to test consume configMaps
    Sep  7 01:31:39.750: INFO: Waiting up to 5m0s for pod "pod-configmaps-d99befda-1ea0-4959-ba85-aa3ea408546e" in namespace "configmap-1532" to be "Succeeded or Failed"

    Sep  7 01:31:39.755: INFO: Pod "pod-configmaps-d99befda-1ea0-4959-ba85-aa3ea408546e": Phase="Pending", Reason="", readiness=false. Elapsed: 4.869366ms
    Sep  7 01:31:41.758: INFO: Pod "pod-configmaps-d99befda-1ea0-4959-ba85-aa3ea408546e": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.008483918s
    STEP: Saw pod success
    Sep  7 01:31:41.758: INFO: Pod "pod-configmaps-d99befda-1ea0-4959-ba85-aa3ea408546e" satisfied condition "Succeeded or Failed"

    Sep  7 01:31:41.761: INFO: Trying to get logs from node k8s-upgrade-and-conformance-7r78ik-worker-ynukn0 pod pod-configmaps-d99befda-1ea0-4959-ba85-aa3ea408546e container agnhost-container: <nil>
    STEP: delete the pod
    Sep  7 01:31:41.778: INFO: Waiting for pod pod-configmaps-d99befda-1ea0-4959-ba85-aa3ea408546e to disappear
    Sep  7 01:31:41.781: INFO: Pod pod-configmaps-d99befda-1ea0-4959-ba85-aa3ea408546e no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175
    Sep  7 01:31:41.781: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-1532" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume [NodeConformance] [Conformance]","total":-1,"completed":77,"skipped":1414,"failed":1,"failures":["[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate pod and apply defaults after mutation [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174
    STEP: Creating a kubernetes client
... skipping 15 lines ...
    STEP: creating replication controller affinity-nodeport-timeout in namespace services-7879
    I0907 01:29:31.553576      14 runners.go:190] Created replication controller with name: affinity-nodeport-timeout, namespace: services-7879, replica count: 3
    I0907 01:29:34.603951      14 runners.go:190] affinity-nodeport-timeout Pods: 3 out of 3 created, 3 running, 0 pending, 0 waiting, 0 inactive, 0 terminating, 0 unknown, 0 runningButNotReady 
    Sep  7 01:29:34.614: INFO: Creating new exec pod
    Sep  7 01:29:37.630: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:29:39.892: INFO: rc: 1
    Sep  7 01:29:39.892: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:29:40.894: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:29:43.094: INFO: rc: 1
    Sep  7 01:29:43.094: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:29:43.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:29:46.080: INFO: rc: 1
    Sep  7 01:29:46.081: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:29:46.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:29:49.048: INFO: rc: 1
    Sep  7 01:29:49.048: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:29:49.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:29:52.066: INFO: rc: 1
    Sep  7 01:29:52.066: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:29:52.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:29:55.073: INFO: rc: 1
    Sep  7 01:29:55.073: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:29:55.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:29:58.067: INFO: rc: 1
    Sep  7 01:29:58.067: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:29:58.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:01.094: INFO: rc: 1
    Sep  7 01:30:01.094: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:01.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:04.102: INFO: rc: 1
    Sep  7 01:30:04.102: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:04.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:07.090: INFO: rc: 1
    Sep  7 01:30:07.090: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:07.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:10.078: INFO: rc: 1
    Sep  7 01:30:10.078: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:10.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:13.089: INFO: rc: 1
    Sep  7 01:30:13.089: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:13.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:16.074: INFO: rc: 1
    Sep  7 01:30:16.074: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:16.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:19.060: INFO: rc: 1
    Sep  7 01:30:19.060: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:19.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:22.074: INFO: rc: 1
    Sep  7 01:30:22.074: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:22.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:25.082: INFO: rc: 1
    Sep  7 01:30:25.082: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:25.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:28.090: INFO: rc: 1
    Sep  7 01:30:28.090: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:28.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:31.088: INFO: rc: 1
    Sep  7 01:30:31.088: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:31.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:34.121: INFO: rc: 1
    Sep  7 01:30:34.121: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:34.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:37.099: INFO: rc: 1
    Sep  7 01:30:37.099: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:37.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:40.074: INFO: rc: 1
    Sep  7 01:30:40.074: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:40.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:43.091: INFO: rc: 1
    Sep  7 01:30:43.091: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:43.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:46.064: INFO: rc: 1
    Sep  7 01:30:46.064: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:46.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:49.066: INFO: rc: 1
    Sep  7 01:30:49.066: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:49.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:52.071: INFO: rc: 1
    Sep  7 01:30:52.071: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:52.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:55.060: INFO: rc: 1
    Sep  7 01:30:55.060: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:55.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:30:58.081: INFO: rc: 1
    Sep  7 01:30:58.081: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:30:58.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:31:01.073: INFO: rc: 1
    Sep  7 01:31:01.073: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:31:01.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:31:04.056: INFO: rc: 1
    Sep  7 01:31:04.056: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:31:04.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:31:07.145: INFO: rc: 1
    Sep  7 01:31:07.145: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:31:07.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:31:10.082: INFO: rc: 1
    Sep  7 01:31:10.082: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:31:10.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:31:13.083: INFO: rc: 1
    Sep  7 01:31:13.083: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:31:13.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:31:16.066: INFO: rc: 1
    Sep  7 01:31:16.066: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:31:16.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:31:19.064: INFO: rc: 1
    Sep  7 01:31:19.064: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:31:19.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:31:22.067: INFO: rc: 1
    Sep  7 01:31:22.067: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:31:22.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:31:25.087: INFO: rc: 1
    Sep  7 01:31:25.087: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:31:25.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:31:28.063: INFO: rc: 1
    Sep  7 01:31:28.063: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:31:28.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:31:31.064: INFO: rc: 1
    Sep  7 01:31:31.064: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:31:31.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:31:34.126: INFO: rc: 1
    Sep  7 01:31:34.126: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:31:34.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80'
    Sep  7 01:31:37.068: INFO: rc: 1
    Sep  7 01:31:37.068: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh -x -c nc -zv -t -w 2 affinity-nodeport-timeout 80:

    Command stdout:
    
    stderr:
    + nc -zv -t -w 2 affinity-nodeport-timeout 80
    nc: connect to affinity-nodeport-timeout port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  7 01:31:37.893: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7879 exec execpod-affinityggjvd -- /bin/sh