This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 7 succeeded
Started2022-08-29 20:22
Elapsed1h15m
Revisionmain

No Test Failures!


Show 7 Passed Tests

Show 20 Skipped Tests

Error lines from build-log.txt

... skipping 762 lines ...
+ retVal=0
++ docker images -q kindest/node:v1.21.14
+ [[ '' == '' ]]
+ echo '+ Pulling kindest/node:v1.21.14'
+ Pulling kindest/node:v1.21.14
+ docker pull kindest/node:v1.21.14
Error response from daemon: manifest for kindest/node:v1.21.14 not found: manifest unknown: manifest unknown
+ retVal=1
+ [[ 1 != 0 ]]
+ echo '+ image for Kuberentes v1.21.14 is not available in docker hub, trying local build'
+ image for Kuberentes v1.21.14 is not available in docker hub, trying local build
+ kind::buildNodeImage v1.21.14
+ local version=v1.21.14
... skipping 198 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/blang/semver v3.5.1+incompatible
go: downloading k8s.io/apimachinery v0.24.2
go: downloading github.com/onsi/gomega v1.20.0
... skipping 227 lines ...
    kubeadmconfig.bootstrap.cluster.x-k8s.io/k8s-upgrade-and-conformance-a00ni7-mp-0-config created
    kubeadmconfig.bootstrap.cluster.x-k8s.io/k8s-upgrade-and-conformance-a00ni7-mp-0-config-cgroupfs created
    cluster.cluster.x-k8s.io/k8s-upgrade-and-conformance-a00ni7 created
    machinepool.cluster.x-k8s.io/k8s-upgrade-and-conformance-a00ni7-mp-0 created
    dockermachinepool.infrastructure.cluster.x-k8s.io/k8s-upgrade-and-conformance-a00ni7-dmp-0 created

    Failed to get logs for Machine k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k, Cluster k8s-upgrade-and-conformance-51nzmu/k8s-upgrade-and-conformance-a00ni7: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2, Cluster k8s-upgrade-and-conformance-51nzmu/k8s-upgrade-and-conformance-a00ni7: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc, Cluster k8s-upgrade-and-conformance-51nzmu/k8s-upgrade-and-conformance-a00ni7: exit status 2
    Failed to get logs for MachinePool k8s-upgrade-and-conformance-a00ni7-mp-0, Cluster k8s-upgrade-and-conformance-51nzmu/k8s-upgrade-and-conformance-a00ni7: 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 08/29/22 20:40:34.02
    INFO: Creating namespace k8s-upgrade-and-conformance-51nzmu
    INFO: Creating event watcher for namespace "k8s-upgrade-and-conformance-51nzmu"
... skipping 41 lines ...
    
    Running in parallel across 4 nodes
    
    Aug 29 20:49:05.066: INFO: >>> kubeConfig: /tmp/kubeconfig
    Aug 29 20:49:05.070: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
    Aug 29 20:49:05.092: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
    Aug 29 20:49:05.172: INFO: The status of Pod kube-proxy-f8cvk is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Aug 29 20:49:05.172: INFO: 15 / 16 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
    Aug 29 20:49:05.172: INFO: expected 2 pod replicas in namespace 'kube-system', 2 are Running and Ready.
    Aug 29 20:49:05.172: INFO: POD               NODE                                            PHASE    GRACE  CONDITIONS
    Aug 29 20:49:05.172: INFO: kube-proxy-f8cvk  k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-08-29 20:49:03 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-08-29 20:49:03 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-08-29 20:49:03 +0000 UTC ContainersNotReady containers with unready status: [kube-proxy]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-08-29 20:49:03 +0000 UTC  }]
    Aug 29 20:49:05.172: INFO: 
    Aug 29 20:49:07.203: INFO: 16 / 16 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
... skipping 52 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:49:07.603: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "ingressclass-8845" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] IngressClass API  should support creating IngressClass API operations [Conformance]","total":-1,"completed":1,"skipped":37,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:49:12.295: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-5855" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should be updated [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":61,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 4 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/storage/downwardapi_volume.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:630
    STEP: Creating a pod to test downward API volume plugin
    Aug 29 20:49:07.496: INFO: Waiting up to 5m0s for pod "downwardapi-volume-756168b4-bfd0-4eea-bf0b-75b2cd4c71bf" in namespace "downward-api-2096" to be "Succeeded or Failed"

    Aug 29 20:49:07.512: INFO: Pod "downwardapi-volume-756168b4-bfd0-4eea-bf0b-75b2cd4c71bf": Phase="Pending", Reason="", readiness=false. Elapsed: 16.016101ms
    Aug 29 20:49:09.519: INFO: Pod "downwardapi-volume-756168b4-bfd0-4eea-bf0b-75b2cd4c71bf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.023386032s
    Aug 29 20:49:11.527: INFO: Pod "downwardapi-volume-756168b4-bfd0-4eea-bf0b-75b2cd4c71bf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.031295936s
    Aug 29 20:49:13.781: INFO: Pod "downwardapi-volume-756168b4-bfd0-4eea-bf0b-75b2cd4c71bf": Phase="Running", Reason="", readiness=true. Elapsed: 6.285240128s
    Aug 29 20:49:15.796: INFO: Pod "downwardapi-volume-756168b4-bfd0-4eea-bf0b-75b2cd4c71bf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 8.300280161s
    STEP: Saw pod success
    Aug 29 20:49:15.796: INFO: Pod "downwardapi-volume-756168b4-bfd0-4eea-bf0b-75b2cd4c71bf" satisfied condition "Succeeded or Failed"

    Aug 29 20:49:15.802: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod downwardapi-volume-756168b4-bfd0-4eea-bf0b-75b2cd4c71bf container client-container: <nil>
    STEP: delete the pod
    Aug 29 20:49:15.843: INFO: Waiting for pod downwardapi-volume-756168b4-bfd0-4eea-bf0b-75b2cd4c71bf to disappear
    Aug 29 20:49:15.854: INFO: Pod downwardapi-volume-756168b4-bfd0-4eea-bf0b-75b2cd4c71bf 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:186
    Aug 29 20:49:15.854: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-2096" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should provide container's memory request [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":21,"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:185
    STEP: Creating a kubernetes client
    Aug 29 20:49:15.909: 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:630
    STEP: Creating a pod to test emptydir 0777 on node default medium
    Aug 29 20:49:15.983: INFO: Waiting up to 5m0s for pod "pod-a7b11ac1-55a6-42c5-8698-578c4996251d" in namespace "emptydir-2577" to be "Succeeded or Failed"

    Aug 29 20:49:15.993: INFO: Pod "pod-a7b11ac1-55a6-42c5-8698-578c4996251d": Phase="Pending", Reason="", readiness=false. Elapsed: 9.658627ms
    Aug 29 20:49:18.007: INFO: Pod "pod-a7b11ac1-55a6-42c5-8698-578c4996251d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.02393181s
    STEP: Saw pod success
    Aug 29 20:49:18.008: INFO: Pod "pod-a7b11ac1-55a6-42c5-8698-578c4996251d" satisfied condition "Succeeded or Failed"

    Aug 29 20:49:18.014: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-a7b11ac1-55a6-42c5-8698-578c4996251d container test-container: <nil>
    STEP: delete the pod
    Aug 29 20:49:18.043: INFO: Waiting for pod pod-a7b11ac1-55a6-42c5-8698-578c4996251d to disappear
    Aug 29 20:49:18.050: INFO: Pod pod-a7b11ac1-55a6-42c5-8698-578c4996251d 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:186
    Aug 29 20:49:18.050: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-2577" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0777,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":36,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:49:18.100: 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:630
    STEP: Creating a pod to test emptydir 0644 on node default medium
    Aug 29 20:49:18.171: INFO: Waiting up to 5m0s for pod "pod-a398cdae-94a1-481e-a2f8-97fcca55545d" in namespace "emptydir-3708" to be "Succeeded or Failed"

    Aug 29 20:49:18.176: INFO: Pod "pod-a398cdae-94a1-481e-a2f8-97fcca55545d": Phase="Pending", Reason="", readiness=false. Elapsed: 5.289424ms
    Aug 29 20:49:20.183: INFO: Pod "pod-a398cdae-94a1-481e-a2f8-97fcca55545d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.011954388s
    STEP: Saw pod success
    Aug 29 20:49:20.183: INFO: Pod "pod-a398cdae-94a1-481e-a2f8-97fcca55545d" satisfied condition "Succeeded or Failed"

    Aug 29 20:49:20.187: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-a398cdae-94a1-481e-a2f8-97fcca55545d container test-container: <nil>
    STEP: delete the pod
    Aug 29 20:49:20.210: INFO: Waiting for pod pod-a398cdae-94a1-481e-a2f8-97fcca55545d to disappear
    Aug 29 20:49:20.218: INFO: Pod pod-a398cdae-94a1-481e-a2f8-97fcca55545d 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:186
    Aug 29 20:49:20.218: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-3708" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0644,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":3,"skipped":47,"failed":0}

    
    SSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:49:24.621: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-1192" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl patch should add annotations for pods in rc  [Conformance]","total":-1,"completed":4,"skipped":66,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] InitContainer [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:49:33.072: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "init-container-2500" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] InitContainer [NodeConformance] should invoke init containers on a RestartAlways pod [Conformance]","total":-1,"completed":5,"skipped":104,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Kubelet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:49:33.221: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubelet-test-5721" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Kubelet when scheduling a busybox command that always fails in a pod should be possible to delete [NodeConformance] [Conformance]","total":-1,"completed":6,"skipped":121,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:49:38.797: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-7180" 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":3,"skipped":69,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:49:33.256: 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:630
    STEP: Creating configMap with name configmap-test-volume-cf37a615-1f2a-49f9-923d-874de1966eb5
    STEP: Creating a pod to test consume configMaps
    Aug 29 20:49:33.334: INFO: Waiting up to 5m0s for pod "pod-configmaps-a94de13f-6575-431e-9bfc-884c6bb913bb" in namespace "configmap-4558" to be "Succeeded or Failed"

    Aug 29 20:49:33.343: INFO: Pod "pod-configmaps-a94de13f-6575-431e-9bfc-884c6bb913bb": Phase="Pending", Reason="", readiness=false. Elapsed: 8.736723ms
    Aug 29 20:49:35.349: INFO: Pod "pod-configmaps-a94de13f-6575-431e-9bfc-884c6bb913bb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.015199152s
    Aug 29 20:49:37.356: INFO: Pod "pod-configmaps-a94de13f-6575-431e-9bfc-884c6bb913bb": Phase="Pending", Reason="", readiness=false. Elapsed: 4.022266782s
    Aug 29 20:49:39.364: INFO: Pod "pod-configmaps-a94de13f-6575-431e-9bfc-884c6bb913bb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.029482061s
    STEP: Saw pod success
    Aug 29 20:49:39.364: INFO: Pod "pod-configmaps-a94de13f-6575-431e-9bfc-884c6bb913bb" satisfied condition "Succeeded or Failed"

    Aug 29 20:49:39.368: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-exv40f pod pod-configmaps-a94de13f-6575-431e-9bfc-884c6bb913bb container agnhost-container: <nil>
    STEP: delete the pod
    Aug 29 20:49:39.406: INFO: Waiting for pod pod-configmaps-a94de13f-6575-431e-9bfc-884c6bb913bb to disappear
    Aug 29 20:49:39.412: INFO: Pod pod-configmaps-a94de13f-6575-431e-9bfc-884c6bb913bb no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:49:39.412: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-4558" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":125,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] Job
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:49:39.458: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename job
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should run a job to completion when tasks sometimes fail and are locally restarted [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a job
    STEP: Ensuring job reaches completions
    [AfterEach] [sig-apps] Job
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:49:47.521: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "job-8160" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Job should run a job to completion when tasks sometimes fail and are locally restarted [Conformance]","total":-1,"completed":8,"skipped":136,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:49:50.180: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-2861" 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":4,"skipped":120,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 24 lines ...
    STEP: Destroying namespace "webhook-7672-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:102
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] listing validating webhooks should work [Conformance]","total":-1,"completed":9,"skipped":153,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:49:54.249: 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:630
    STEP: Creating secret with name secret-test-2633b141-dc44-44e4-90d3-ab51d7c8d206
    STEP: Creating a pod to test consume secrets
    Aug 29 20:49:54.371: INFO: Waiting up to 5m0s for pod "pod-secrets-2ad33b8b-8810-45c2-897d-efd3299e4b36" in namespace "secrets-215" to be "Succeeded or Failed"

    Aug 29 20:49:54.392: INFO: Pod "pod-secrets-2ad33b8b-8810-45c2-897d-efd3299e4b36": Phase="Pending", Reason="", readiness=false. Elapsed: 20.754563ms
    Aug 29 20:49:56.398: INFO: Pod "pod-secrets-2ad33b8b-8810-45c2-897d-efd3299e4b36": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.02672291s
    STEP: Saw pod success
    Aug 29 20:49:56.398: INFO: Pod "pod-secrets-2ad33b8b-8810-45c2-897d-efd3299e4b36" satisfied condition "Succeeded or Failed"

    Aug 29 20:49:56.402: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-secrets-2ad33b8b-8810-45c2-897d-efd3299e4b36 container secret-volume-test: <nil>
    STEP: delete the pod
    Aug 29 20:49:56.425: INFO: Waiting for pod pod-secrets-2ad33b8b-8810-45c2-897d-efd3299e4b36 to disappear
    Aug 29 20:49:56.429: INFO: Pod pod-secrets-2ad33b8b-8810-45c2-897d-efd3299e4b36 no longer exists
    [AfterEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:49:56.429: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-215" for this suite.
    STEP: Destroying namespace "secret-namespace-9358" 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":10,"skipped":193,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-auth] ServiceAccounts
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:49:57.178: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "svcaccounts-5981" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-auth] ServiceAccounts should allow opting out of API token automount  [Conformance]","total":-1,"completed":11,"skipped":194,"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:185
    STEP: Creating a kubernetes client
... skipping 29 lines ...
    STEP: Destroying namespace "webhook-4178-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:102
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny custom resource creation, update and deletion [Conformance]","total":-1,"completed":5,"skipped":147,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Events
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:50:05.603: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-8243" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Events should be sent by kubelets and the scheduler about pods scheduling and running  [Conformance]","total":-1,"completed":6,"skipped":169,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected secret
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:50:05.669: 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:630
    STEP: Creating projection with secret that has name projected-secret-test-079f4e27-e8ce-48b7-9e64-1c84103af147
    STEP: Creating a pod to test consume secrets
    Aug 29 20:50:05.728: INFO: Waiting up to 5m0s for pod "pod-projected-secrets-8dde2736-09bf-4344-b8e9-ca8038dba9c3" in namespace "projected-5711" to be "Succeeded or Failed"

    Aug 29 20:50:05.736: INFO: Pod "pod-projected-secrets-8dde2736-09bf-4344-b8e9-ca8038dba9c3": Phase="Pending", Reason="", readiness=false. Elapsed: 7.27402ms
    Aug 29 20:50:07.742: INFO: Pod "pod-projected-secrets-8dde2736-09bf-4344-b8e9-ca8038dba9c3": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.013964791s
    STEP: Saw pod success
    Aug 29 20:50:07.743: INFO: Pod "pod-projected-secrets-8dde2736-09bf-4344-b8e9-ca8038dba9c3" satisfied condition "Succeeded or Failed"

    Aug 29 20:50:07.748: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-projected-secrets-8dde2736-09bf-4344-b8e9-ca8038dba9c3 container projected-secret-volume-test: <nil>
    STEP: delete the pod
    Aug 29 20:50:07.776: INFO: Waiting for pod pod-projected-secrets-8dde2736-09bf-4344-b8e9-ca8038dba9c3 to disappear
    Aug 29 20:50:07.781: INFO: Pod pod-projected-secrets-8dde2736-09bf-4344-b8e9-ca8038dba9c3 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:186
    Aug 29 20:50:07.781: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-5711" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected secret should be consumable from pods in volume with defaultMode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":192,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourceDefinition Watch [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:50:10.721: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-watch-1507" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceDefinition Watch [Privileged:ClusterAdmin] CustomResourceDefinition Watch watch on custom resource definition objects [Conformance]","total":-1,"completed":1,"skipped":3,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 29 lines ...
    STEP: Destroying namespace "services-6706" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:750
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should serve a basic endpoint from pods  [Conformance]","total":-1,"completed":8,"skipped":220,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-instrumentation] Events API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:50:12.458: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-6782" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-instrumentation] Events API should delete a collection of events [Conformance]","total":-1,"completed":9,"skipped":222,"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:185
    STEP: Creating a kubernetes client
    Aug 29 20:50:12.507: 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:630
    STEP: Creating a pod to test emptydir 0666 on tmpfs
    Aug 29 20:50:12.583: INFO: Waiting up to 5m0s for pod "pod-619c5104-c2ca-4e47-abc1-03cf2eed136d" in namespace "emptydir-3282" to be "Succeeded or Failed"

    Aug 29 20:50:12.589: INFO: Pod "pod-619c5104-c2ca-4e47-abc1-03cf2eed136d": Phase="Pending", Reason="", readiness=false. Elapsed: 5.331742ms
    Aug 29 20:50:14.596: INFO: Pod "pod-619c5104-c2ca-4e47-abc1-03cf2eed136d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.01253129s
    STEP: Saw pod success
    Aug 29 20:50:14.596: INFO: Pod "pod-619c5104-c2ca-4e47-abc1-03cf2eed136d" satisfied condition "Succeeded or Failed"

    Aug 29 20:50:14.600: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-619c5104-c2ca-4e47-abc1-03cf2eed136d container test-container: <nil>
    STEP: delete the pod
    Aug 29 20:50:14.624: INFO: Waiting for pod pod-619c5104-c2ca-4e47-abc1-03cf2eed136d to disappear
    Aug 29 20:50:14.629: INFO: Pod pod-619c5104-c2ca-4e47-abc1-03cf2eed136d 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:186
    Aug 29 20:50:14.629: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-3282" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0666,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":10,"skipped":230,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Watchers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:50:21.017: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "watch-1863" 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":2,"skipped":33,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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/storage/projected_downwardapi.go:41
    [It] should provide container's cpu limit [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test downward API volume plugin
    Aug 29 20:50:21.095: INFO: Waiting up to 5m0s for pod "downwardapi-volume-2017a01e-5fb9-430e-a8df-009e237690f4" in namespace "projected-2727" to be "Succeeded or Failed"

    Aug 29 20:50:21.098: INFO: Pod "downwardapi-volume-2017a01e-5fb9-430e-a8df-009e237690f4": Phase="Pending", Reason="", readiness=false. Elapsed: 2.581169ms
    Aug 29 20:50:23.102: INFO: Pod "downwardapi-volume-2017a01e-5fb9-430e-a8df-009e237690f4": Phase="Running", Reason="", readiness=true. Elapsed: 2.006891218s
    Aug 29 20:50:25.109: INFO: Pod "downwardapi-volume-2017a01e-5fb9-430e-a8df-009e237690f4": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.013085188s
    STEP: Saw pod success
    Aug 29 20:50:25.109: INFO: Pod "downwardapi-volume-2017a01e-5fb9-430e-a8df-009e237690f4" satisfied condition "Succeeded or Failed"

    Aug 29 20:50:25.116: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod downwardapi-volume-2017a01e-5fb9-430e-a8df-009e237690f4 container client-container: <nil>
    STEP: delete the pod
    Aug 29 20:50:25.159: INFO: Waiting for pod downwardapi-volume-2017a01e-5fb9-430e-a8df-009e237690f4 to disappear
    Aug 29 20:50:25.162: INFO: Pod downwardapi-volume-2017a01e-5fb9-430e-a8df-009e237690f4 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:186
    Aug 29 20:50:25.162: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-2727" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should provide container's cpu limit [NodeConformance] [Conformance]","total":-1,"completed":3,"skipped":54,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:50:25.301: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-8181" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Secrets should patch a secret [Conformance]","total":-1,"completed":4,"skipped":71,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] ReplicaSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:50:28.462: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replicaset-4648" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicaSet Replace and Patch tests [Conformance]","total":-1,"completed":11,"skipped":239,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:50:25.339: 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 container's args [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test substitution in container's args
    Aug 29 20:50:25.404: INFO: Waiting up to 5m0s for pod "var-expansion-9efd3b07-35c2-47e3-aaba-a97295b13c88" in namespace "var-expansion-2480" to be "Succeeded or Failed"

    Aug 29 20:50:25.416: INFO: Pod "var-expansion-9efd3b07-35c2-47e3-aaba-a97295b13c88": Phase="Pending", Reason="", readiness=false. Elapsed: 11.262691ms
    Aug 29 20:50:27.420: INFO: Pod "var-expansion-9efd3b07-35c2-47e3-aaba-a97295b13c88": Phase="Running", Reason="", readiness=true. Elapsed: 2.016031318s
    Aug 29 20:50:29.426: INFO: Pod "var-expansion-9efd3b07-35c2-47e3-aaba-a97295b13c88": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.021306831s
    STEP: Saw pod success
    Aug 29 20:50:29.426: INFO: Pod "var-expansion-9efd3b07-35c2-47e3-aaba-a97295b13c88" satisfied condition "Succeeded or Failed"

    Aug 29 20:50:29.430: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod var-expansion-9efd3b07-35c2-47e3-aaba-a97295b13c88 container dapi-container: <nil>
    STEP: delete the pod
    Aug 29 20:50:29.443: INFO: Waiting for pod var-expansion-9efd3b07-35c2-47e3-aaba-a97295b13c88 to disappear
    Aug 29 20:50:29.446: INFO: Pod var-expansion-9efd3b07-35c2-47e3-aaba-a97295b13c88 no longer exists
    [AfterEach] [sig-node] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:50:29.446: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-2480" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Variable Expansion should allow substituting values in a container's args [NodeConformance] [Conformance]","total":-1,"completed":5,"skipped":77,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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/storage/downwardapi_volume.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:630
    STEP: Creating a pod to test downward API volume plugin
    Aug 29 20:50:28.522: INFO: Waiting up to 5m0s for pod "downwardapi-volume-fb698ea1-9996-4eea-905b-639781d0b489" in namespace "downward-api-2428" to be "Succeeded or Failed"

    Aug 29 20:50:28.525: INFO: Pod "downwardapi-volume-fb698ea1-9996-4eea-905b-639781d0b489": Phase="Pending", Reason="", readiness=false. Elapsed: 3.499194ms
    Aug 29 20:50:30.530: INFO: Pod "downwardapi-volume-fb698ea1-9996-4eea-905b-639781d0b489": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.0078452s
    STEP: Saw pod success
    Aug 29 20:50:30.530: INFO: Pod "downwardapi-volume-fb698ea1-9996-4eea-905b-639781d0b489" satisfied condition "Succeeded or Failed"

    Aug 29 20:50:30.534: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod downwardapi-volume-fb698ea1-9996-4eea-905b-639781d0b489 container client-container: <nil>
    STEP: delete the pod
    Aug 29 20:50:30.557: INFO: Waiting for pod downwardapi-volume-fb698ea1-9996-4eea-905b-639781d0b489 to disappear
    Aug 29 20:50:30.560: INFO: Pod downwardapi-volume-fb698ea1-9996-4eea-905b-639781d0b489 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:186
... skipping 20 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:50:36.079: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-2869" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should update labels on modification [NodeConformance] [Conformance]","total":-1,"completed":6,"skipped":80,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-apps] Job
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:50:39.413: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "job-893" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Job should delete a job [Conformance]","total":-1,"completed":12,"skipped":196,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-network] EndpointSlice
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:50:39.516: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "endpointslice-5064" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] EndpointSlice should create and delete Endpoints and EndpointSlices for a Service with a selector specified [Conformance]","total":-1,"completed":13,"skipped":202,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:50:43.146: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-5566" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and ensure its status is promptly calculated. [Conformance]","total":-1,"completed":7,"skipped":84,"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:185
    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:186
    Aug 29 20:50:55.670: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-2041" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should verify ResourceQuota with best effort scope. [Conformance]","total":-1,"completed":14,"skipped":206,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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/storage/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:630
    STEP: Creating a pod to test downward API volume plugin
    Aug 29 20:50:55.733: INFO: Waiting up to 5m0s for pod "downwardapi-volume-f7f05555-9026-4117-95bc-027ab54881f2" in namespace "projected-7374" to be "Succeeded or Failed"

    Aug 29 20:50:55.737: INFO: Pod "downwardapi-volume-f7f05555-9026-4117-95bc-027ab54881f2": Phase="Pending", Reason="", readiness=false. Elapsed: 3.24903ms
    Aug 29 20:50:57.741: INFO: Pod "downwardapi-volume-f7f05555-9026-4117-95bc-027ab54881f2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007390028s
    STEP: Saw pod success
    Aug 29 20:50:57.741: INFO: Pod "downwardapi-volume-f7f05555-9026-4117-95bc-027ab54881f2" satisfied condition "Succeeded or Failed"

    Aug 29 20:50:57.744: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-exv40f pod downwardapi-volume-f7f05555-9026-4117-95bc-027ab54881f2 container client-container: <nil>
    STEP: delete the pod
    Aug 29 20:50:57.762: INFO: Waiting for pod downwardapi-volume-f7f05555-9026-4117-95bc-027ab54881f2 to disappear
    Aug 29 20:50:57.765: INFO: Pod downwardapi-volume-f7f05555-9026-4117-95bc-027ab54881f2 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:186
    Aug 29 20:50:57.765: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-7374" 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":15,"skipped":217,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Pods Extended
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:50:57.851: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-4449" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods Extended Pods Set QOS Class should be set on Pods with matching resource requests and limits for memory and cpu [Conformance]","total":-1,"completed":16,"skipped":242,"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:185
    STEP: Creating a kubernetes client
... skipping 12 lines ...
    Aug 29 20:50:46.546: 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:630
    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:186
    Aug 29 20:50:58.650: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "webhook-8443" for this suite.
    STEP: Destroying namespace "webhook-8443-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:102
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]","total":-1,"completed":8,"skipped":100,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Downward API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:50:57.908: 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:630
    STEP: Creating a pod to test downward api env vars
    Aug 29 20:50:57.952: INFO: Waiting up to 5m0s for pod "downward-api-329bd845-59a1-47c9-9ea3-dea82c1231a3" in namespace "downward-api-4113" to be "Succeeded or Failed"

    Aug 29 20:50:57.956: INFO: Pod "downward-api-329bd845-59a1-47c9-9ea3-dea82c1231a3": Phase="Pending", Reason="", readiness=false. Elapsed: 2.787079ms
    Aug 29 20:50:59.959: INFO: Pod "downward-api-329bd845-59a1-47c9-9ea3-dea82c1231a3": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006524708s
    STEP: Saw pod success
    Aug 29 20:50:59.960: INFO: Pod "downward-api-329bd845-59a1-47c9-9ea3-dea82c1231a3" satisfied condition "Succeeded or Failed"

    Aug 29 20:50:59.962: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod downward-api-329bd845-59a1-47c9-9ea3-dea82c1231a3 container dapi-container: <nil>
    STEP: delete the pod
    Aug 29 20:50:59.976: INFO: Waiting for pod downward-api-329bd845-59a1-47c9-9ea3-dea82c1231a3 to disappear
    Aug 29 20:50:59.979: INFO: Pod downward-api-329bd845-59a1-47c9-9ea3-dea82c1231a3 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:186
    Aug 29 20:50:59.979: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-4113" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Downward API should provide pod UID as env vars [NodeConformance] [Conformance]","total":-1,"completed":17,"skipped":268,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Watchers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:51:00.050: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "watch-8068" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Watchers should be able to start watching from a specific resource version [Conformance]","total":-1,"completed":18,"skipped":270,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 21 lines ...
    STEP: Destroying namespace "crd-webhook-8470" 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":9,"skipped":157,"failed":0}

    
    SSSSSSSSSSSSSSSSSS
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should set mode on item file [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":12,"skipped":247,"failed":0}

    [BeforeEach] [sig-api-machinery] Garbage collector
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:50:30.571: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename gc
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 42 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:51:10.943: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "gc-4075" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Garbage collector should orphan pods created by rc if delete options say so [Conformance]","total":-1,"completed":13,"skipped":247,"failed":0}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:51:13.191: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-8067" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a pod. [Conformance]","total":-1,"completed":19,"skipped":276,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:51:14.822: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-9487" 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":20,"skipped":316,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-node] Container Runtime
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:51:16.982: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-runtime-2586" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] 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":21,"skipped":319,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected secret
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:51:19.165: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-9097" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected secret optional updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":14,"skipped":254,"failed":0}

    [BeforeEach] [sig-node] Docker Containers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:51:19.191: 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 command (docker entrypoint) [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test override command
    Aug 29 20:51:19.260: INFO: Waiting up to 5m0s for pod "client-containers-3926c434-aa5d-4e61-b0e1-2830da3fdfad" in namespace "containers-6039" to be "Succeeded or Failed"

    Aug 29 20:51:19.267: INFO: Pod "client-containers-3926c434-aa5d-4e61-b0e1-2830da3fdfad": Phase="Pending", Reason="", readiness=false. Elapsed: 6.882043ms
    Aug 29 20:51:21.271: INFO: Pod "client-containers-3926c434-aa5d-4e61-b0e1-2830da3fdfad": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.01109895s
    STEP: Saw pod success
    Aug 29 20:51:21.272: INFO: Pod "client-containers-3926c434-aa5d-4e61-b0e1-2830da3fdfad" satisfied condition "Succeeded or Failed"

    Aug 29 20:51:21.274: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod client-containers-3926c434-aa5d-4e61-b0e1-2830da3fdfad container agnhost-container: <nil>
    STEP: delete the pod
    Aug 29 20:51:21.293: INFO: Waiting for pod client-containers-3926c434-aa5d-4e61-b0e1-2830da3fdfad to disappear
    Aug 29 20:51:21.296: INFO: Pod client-containers-3926c434-aa5d-4e61-b0e1-2830da3fdfad no longer exists
    [AfterEach] [sig-node] Docker Containers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:51:21.296: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "containers-6039" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Docker Containers should be able to override the image's default command (docker entrypoint) [NodeConformance] [Conformance]","total":-1,"completed":15,"skipped":254,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Probing container
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:51:43.489: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-probe-4490" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Probing container with readiness probe should not be ready before initial delay and never restart [NodeConformance] [Conformance]","total":-1,"completed":16,"skipped":337,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:51:43.503: 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:630
    STEP: Creating configMap with name projected-configmap-test-volume-map-fde7f301-2fdb-48f0-8ef5-578cf9c5f617
    STEP: Creating a pod to test consume configMaps
    Aug 29 20:51:43.550: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-cd264824-ee88-44b6-b1e5-97cddd381684" in namespace "projected-2117" to be "Succeeded or Failed"

    Aug 29 20:51:43.553: INFO: Pod "pod-projected-configmaps-cd264824-ee88-44b6-b1e5-97cddd381684": Phase="Pending", Reason="", readiness=false. Elapsed: 3.029456ms
    Aug 29 20:51:45.557: INFO: Pod "pod-projected-configmaps-cd264824-ee88-44b6-b1e5-97cddd381684": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.00707154s
    STEP: Saw pod success
    Aug 29 20:51:45.557: INFO: Pod "pod-projected-configmaps-cd264824-ee88-44b6-b1e5-97cddd381684" satisfied condition "Succeeded or Failed"

    Aug 29 20:51:45.561: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-projected-configmaps-cd264824-ee88-44b6-b1e5-97cddd381684 container agnhost-container: <nil>
    STEP: delete the pod
    Aug 29 20:51:45.577: INFO: Waiting for pod pod-projected-configmaps-cd264824-ee88-44b6-b1e5-97cddd381684 to disappear
    Aug 29 20:51:45.580: INFO: Pod pod-projected-configmaps-cd264824-ee88-44b6-b1e5-97cddd381684 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:186
    Aug 29 20:51:45.580: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-2117" 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":17,"skipped":338,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] CronJob
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:51:45.761: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "cronjob-9593" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] CronJob should support CronJob API operations [Conformance]","total":-1,"completed":18,"skipped":370,"failed":0}

    
    SSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] PreStop
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:51:54.884: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "prestop-5808" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] PreStop should call prestop when killing a pod  [Conformance]","total":-1,"completed":19,"skipped":385,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Docker Containers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:51:54.909: 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 command and arguments [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test override all
    Aug 29 20:51:54.951: INFO: Waiting up to 5m0s for pod "client-containers-3a26dda1-d367-40bf-9d59-9aaee765389f" in namespace "containers-1361" to be "Succeeded or Failed"

    Aug 29 20:51:54.956: INFO: Pod "client-containers-3a26dda1-d367-40bf-9d59-9aaee765389f": Phase="Pending", Reason="", readiness=false. Elapsed: 3.824837ms
    Aug 29 20:51:56.961: INFO: Pod "client-containers-3a26dda1-d367-40bf-9d59-9aaee765389f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.00887258s
    STEP: Saw pod success
    Aug 29 20:51:56.961: INFO: Pod "client-containers-3a26dda1-d367-40bf-9d59-9aaee765389f" satisfied condition "Succeeded or Failed"

    Aug 29 20:51:56.964: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod client-containers-3a26dda1-d367-40bf-9d59-9aaee765389f container agnhost-container: <nil>
    STEP: delete the pod
    Aug 29 20:51:56.980: INFO: Waiting for pod client-containers-3a26dda1-d367-40bf-9d59-9aaee765389f to disappear
    Aug 29 20:51:56.982: INFO: Pod client-containers-3a26dda1-d367-40bf-9d59-9aaee765389f no longer exists
    [AfterEach] [sig-node] Docker Containers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:51:56.983: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "containers-1361" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Docker Containers should be able to override the image's default command and arguments [NodeConformance] [Conformance]","total":-1,"completed":20,"skipped":393,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] Deployment
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 110 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:52:02.246: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-5710" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment should run the lifecycle of a Deployment [Conformance]","total":-1,"completed":21,"skipped":426,"failed":0}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 11 lines ...
    STEP: verifying the pod is in kubernetes
    STEP: updating the pod
    Aug 29 20:52:04.884: INFO: Successfully updated pod "pod-update-activedeadlineseconds-c11c87f0-14cd-4e58-988b-32ef12d744f2"
    Aug 29 20:52:04.884: INFO: Waiting up to 5m0s for pod "pod-update-activedeadlineseconds-c11c87f0-14cd-4e58-988b-32ef12d744f2" in namespace "pods-4411" to be "terminated due to deadline exceeded"
    Aug 29 20:52:04.886: INFO: Pod "pod-update-activedeadlineseconds-c11c87f0-14cd-4e58-988b-32ef12d744f2": Phase="Running", Reason="", readiness=true. Elapsed: 2.563878ms
    Aug 29 20:52:06.891: INFO: Pod "pod-update-activedeadlineseconds-c11c87f0-14cd-4e58-988b-32ef12d744f2": Phase="Running", Reason="", readiness=true. Elapsed: 2.007288761s
    Aug 29 20:52:08.896: INFO: Pod "pod-update-activedeadlineseconds-c11c87f0-14cd-4e58-988b-32ef12d744f2": Phase="Failed", Reason="DeadlineExceeded", readiness=false. Elapsed: 4.012397096s

    Aug 29 20:52:08.896: INFO: Pod "pod-update-activedeadlineseconds-c11c87f0-14cd-4e58-988b-32ef12d744f2" satisfied condition "terminated due to deadline exceeded"
    [AfterEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:52:08.896: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-4411" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should allow activeDeadlineSeconds to be updated [NodeConformance] [Conformance]","total":-1,"completed":22,"skipped":442,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Kubelet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:52:10.992: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubelet-test-1183" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Kubelet when scheduling a busybox Pod with hostAliases should write entries to /etc/hosts [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":23,"skipped":448,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-node] Probing container
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 20 lines ...
    • [SLOW TEST:247.195 seconds]
    [sig-node] Probing container
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/framework.go:23
      should *not* be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    ------------------------------
    {"msg":"PASSED [sig-node] Probing container should *not* be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":18,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 9 lines ...
    STEP: creating replication controller externalname-service in namespace services-9903
    I0829 20:51:05.542269      19 runners.go:190] Created replication controller with name: externalname-service, namespace: services-9903, replica count: 2
    I0829 20:51:08.593232      19 runners.go:190] externalname-service Pods: 2 out of 2 created, 2 running, 0 pending, 0 waiting, 0 inactive, 0 terminating, 0 unknown, 0 runningButNotReady 
    Aug 29 20:51:08.593: INFO: Creating new exec pod
    Aug 29 20:51:11.610: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:13.811: INFO: rc: 1
    Aug 29 20:51:13.811: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:14.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:17.032: INFO: rc: 1
    Aug 29 20:51:17.032: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:17.811: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:20.079: INFO: rc: 1
    Aug 29 20:51:20.079: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:20.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:23.004: INFO: rc: 1
    Aug 29 20:51:23.004: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:23.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:25.991: INFO: rc: 1
    Aug 29 20:51:25.991: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:26.811: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:28.982: INFO: rc: 1
    Aug 29 20:51:28.983: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:29.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:32.009: INFO: rc: 1
    Aug 29 20:51:32.009: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:32.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:34.992: INFO: rc: 1
    Aug 29 20:51:34.992: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:35.811: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:38.020: INFO: rc: 1
    Aug 29 20:51:38.020: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:38.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:40.985: INFO: rc: 1
    Aug 29 20:51:40.985: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:41.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:43.999: INFO: rc: 1
    Aug 29 20:51:43.999: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:44.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:46.984: INFO: rc: 1
    Aug 29 20:51:46.984: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:47.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:49.969: INFO: rc: 1
    Aug 29 20:51:49.969: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:50.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:52.988: INFO: rc: 1
    Aug 29 20:51:52.988: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:53.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:56.002: INFO: rc: 1
    Aug 29 20:51:56.002: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:56.811: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:51:58.982: INFO: rc: 1
    Aug 29 20:51:58.982: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:51:59.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:02.020: INFO: rc: 1
    Aug 29 20:52:02.021: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:02.813: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:04.997: INFO: rc: 1
    Aug 29 20:52:04.997: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:05.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:08.004: INFO: rc: 1
    Aug 29 20:52:08.004: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:08.811: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:11.023: INFO: rc: 1
    Aug 29 20:52:11.023: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:11.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:13.995: INFO: rc: 1
    Aug 29 20:52:13.996: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:14.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:16.988: INFO: rc: 1
    Aug 29 20:52:16.988: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:17.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:19.984: INFO: rc: 1
    Aug 29 20:52:19.984: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:20.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:23.000: INFO: rc: 1
    Aug 29 20:52:23.000: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:23.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:25.991: INFO: rc: 1
    Aug 29 20:52:25.991: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:26.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:29.028: INFO: rc: 1
    Aug 29 20:52:29.028: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:29.811: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:31.998: INFO: rc: 1
    Aug 29 20:52:31.998: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:32.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:34.996: INFO: rc: 1
    Aug 29 20:52:34.996: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:35.811: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:37.991: INFO: rc: 1
    Aug 29 20:52:37.991: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:38.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:40.990: INFO: rc: 1
    Aug 29 20:52:40.990: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:41.811: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:43.983: INFO: rc: 1
    Aug 29 20:52:43.983: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:44.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:46.999: INFO: rc: 1
    Aug 29 20:52:46.999: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:47.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:49.986: INFO: rc: 1
    Aug 29 20:52:49.986: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:50.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:52.984: INFO: rc: 1
    Aug 29 20:52:52.984: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:53.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:56.020: INFO: rc: 1
    Aug 29 20:52:56.020: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:56.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:52:58.997: INFO: rc: 1
    Aug 29 20:52:58.997: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:52:59.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:53:01.972: INFO: rc: 1
    Aug 29 20:53:01.972: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:53:02.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:53:04.986: INFO: rc: 1
    Aug 29 20:53:04.986: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:53:05.811: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:53:07.987: INFO: rc: 1
    Aug 29 20:53:07.987: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:53:08.812: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:53:10.984: INFO: rc: 1
    Aug 29 20:53:10.984: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + nc -v -t -w 2 externalname-service 80
    + echo hostName
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:53:11.811: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:53:13.975: INFO: rc: 1
    Aug 29 20:53:13.975: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:53:13.975: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Aug 29 20:53:16.187: INFO: rc: 1
    Aug 29 20:53:16.187: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-9903 exec execpodl8vjg -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80:

    Command stdout:
    
    stderr:
    + echo hostName
    + nc -v -t -w 2 externalname-service 80
    nc: connect to externalname-service port 80 (tcp) timed out: Operation in progress
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Aug 29 20:53:16.187: FAIL: Unexpected error:

        <*errors.errorString | 0xc002e2a340>: {
            s: "service is not reachable within 2m0s timeout on endpoint externalname-service:80 over TCP protocol",
        }
        service is not reachable within 2m0s timeout on endpoint externalname-service:80 over TCP protocol
    occurred
    
... skipping 20 lines ...
    • Failure [130.791 seconds]
    [sig-network] Services
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/common/framework.go:23
      should be able to change the type from ExternalName to NodePort [Conformance] [It]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    
      Aug 29 20:53:16.187: Unexpected error:

          <*errors.errorString | 0xc002e2a340>: {
              s: "service is not reachable within 2m0s timeout on endpoint externalname-service:80 over TCP protocol",
          }
          service is not reachable within 2m0s timeout on endpoint externalname-service:80 over TCP protocol
      occurred
    
... skipping 6 lines ...
    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:630
    STEP: Creating configMap with name projected-configmap-test-volume-b9127b7c-a554-473c-afe1-d8752ca30550
    STEP: Creating a pod to test consume configMaps
    Aug 29 20:53:14.603: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-257b7a17-0c64-49e3-9aa2-cc3e1459de62" in namespace "projected-5216" to be "Succeeded or Failed"

    Aug 29 20:53:14.606: INFO: Pod "pod-projected-configmaps-257b7a17-0c64-49e3-9aa2-cc3e1459de62": Phase="Pending", Reason="", readiness=false. Elapsed: 2.825151ms
    Aug 29 20:53:16.610: INFO: Pod "pod-projected-configmaps-257b7a17-0c64-49e3-9aa2-cc3e1459de62": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007271848s
    STEP: Saw pod success
    Aug 29 20:53:16.610: INFO: Pod "pod-projected-configmaps-257b7a17-0c64-49e3-9aa2-cc3e1459de62" satisfied condition "Succeeded or Failed"

    Aug 29 20:53:16.614: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod pod-projected-configmaps-257b7a17-0c64-49e3-9aa2-cc3e1459de62 container agnhost-container: <nil>
    STEP: delete the pod
    Aug 29 20:53:16.651: INFO: Waiting for pod pod-projected-configmaps-257b7a17-0c64-49e3-9aa2-cc3e1459de62 to disappear
    Aug 29 20:53:16.657: INFO: Pod pod-projected-configmaps-257b7a17-0c64-49e3-9aa2-cc3e1459de62 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:186
    Aug 29 20:53:16.657: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-5216" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap should be consumable from pods in volume [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":24,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-node] Kubelet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:53:20.725: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubelet-test-7723" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Kubelet when scheduling a busybox command that always fails in a pod should have an terminated reason [NodeConformance] [Conformance]","total":-1,"completed":3,"skipped":26,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    {"msg":"FAILED [sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]","total":-1,"completed":9,"skipped":175,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:53:16.269: 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 26 lines ...
    STEP: Destroying namespace "services-1230" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:750
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]","total":-1,"completed":10,"skipped":175,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-node] InitContainer [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:53:20.796: 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] [sig-node] InitContainer [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/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:630
    STEP: creating the pod
    Aug 29 20:53:20.821: INFO: PodSpec: initContainers in spec.initContainers
    [AfterEach] [sig-node] InitContainer [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:53:23.877: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "init-container-4369" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] InitContainer [NodeConformance] should not start app containers and fail the pod if init containers fail on a RestartNever pod [Conformance]","total":-1,"completed":4,"skipped":73,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] ReplicaSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:53:26.425: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replicaset-2846" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicaSet should adopt matching pods on creation and release no longer matching pods [Conformance]","total":-1,"completed":11,"skipped":180,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 20 lines ...
    Aug 29 20:53:26.553: INFO: ForEach: Found 1 pods from the filter.  Now looping through them.
    Aug 29 20:53:26.553: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-5464 describe pod agnhost-primary-4frn4'
    Aug 29 20:53:26.762: INFO: stderr: ""
    Aug 29 20:53:26.762: INFO: stdout: "Name:         agnhost-primary-4frn4\nNamespace:    kubectl-5464\nPriority:     0\nNode:         k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2/172.18.0.6\nStart Time:   Mon, 29 Aug 2022 20:53:24 +0000\nLabels:       app=agnhost\n              role=primary\nAnnotations:  <none>\nStatus:       Running\nIP:           192.168.1.25\nIPs:\n  IP:           192.168.1.25\nControlled By:  ReplicationController/agnhost-primary\nContainers:\n  agnhost-primary:\n    Container ID:   containerd://0bb382b41a10a4e80a8db4d042470f29de8278916338296b4e0d8bdb76824947\n    Image:          k8s.gcr.io/e2e-test-images/agnhost:2.32\n    Image ID:       k8s.gcr.io/e2e-test-images/agnhost@sha256:758db666ac7028534dba72e7e9bb1e57bb81b8196f976f7a5cc351ef8b3529e1\n    Port:           6379/TCP\n    Host Port:      0/TCP\n    State:          Running\n      Started:      Mon, 29 Aug 2022 20:53:24 +0000\n    Ready:          True\n    Restart Count:  0\n    Environment:    <none>\n    Mounts:\n      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-xs6k8 (ro)\nConditions:\n  Type              Status\n  Initialized       True \n  Ready             True \n  ContainersReady   True \n  PodScheduled      True \nVolumes:\n  kube-api-access-xs6k8:\n    Type:                    Projected (a volume that contains injected data from multiple sources)\n    TokenExpirationSeconds:  3607\n    ConfigMapName:           kube-root-ca.crt\n    ConfigMapOptional:       <nil>\n    DownwardAPI:             true\nQoS Class:                   BestEffort\nNode-Selectors:              <none>\nTolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s\n                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s\nEvents:\n  Type    Reason     Age   From               Message\n  ----    ------     ----  ----               -------\n  Normal  Scheduled  2s    default-scheduler  Successfully assigned kubectl-5464/agnhost-primary-4frn4 to k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2\n  Normal  Pulled     2s    kubelet            Container image \"k8s.gcr.io/e2e-test-images/agnhost:2.32\" already present on machine\n  Normal  Created    2s    kubelet            Created container agnhost-primary\n  Normal  Started    2s    kubelet            Started container agnhost-primary\n"
    Aug 29 20:53:26.763: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-5464 describe rc agnhost-primary'
    Aug 29 20:53:27.006: INFO: stderr: ""
    Aug 29 20:53:27.006: INFO: stdout: "Name:         agnhost-primary\nNamespace:    kubectl-5464\nSelector:     app=agnhost,role=primary\nLabels:       app=agnhost\n              role=primary\nAnnotations:  <none>\nReplicas:     1 current / 1 desired\nPods Status:  1 Running / 0 Waiting / 0 Succeeded / 0 Failed\nPod Template:\n  Labels:  app=agnhost\n           role=primary\n  Containers:\n   agnhost-primary:\n    Image:        k8s.gcr.io/e2e-test-images/agnhost:2.32\n    Port:         6379/TCP\n    Host Port:    0/TCP\n    Environment:  <none>\n    Mounts:       <none>\n  Volumes:        <none>\nEvents:\n  Type    Reason            Age   From                    Message\n  ----    ------            ----  ----                    -------\n  Normal  SuccessfulCreate  3s    replication-controller  Created pod: agnhost-primary-4frn4\n"

    Aug 29 20:53:27.006: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-5464 describe service agnhost-primary'
    Aug 29 20:53:27.156: INFO: stderr: ""
    Aug 29 20:53:27.156: INFO: stdout: "Name:              agnhost-primary\nNamespace:         kubectl-5464\nLabels:            app=agnhost\n                   role=primary\nAnnotations:       <none>\nSelector:          app=agnhost,role=primary\nType:              ClusterIP\nIP Family Policy:  SingleStack\nIP Families:       IPv4\nIP:                10.140.121.181\nIPs:               10.140.121.181\nPort:              <unset>  6379/TCP\nTargetPort:        agnhost-server/TCP\nEndpoints:         192.168.1.25:6379\nSession Affinity:  None\nEvents:            <none>\n"
    Aug 29 20:53:27.163: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-5464 describe node k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k'
    Aug 29 20:53:27.403: INFO: stderr: ""
    Aug 29 20:53:27.403: INFO: stdout: "Name:               k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k\nRoles:              control-plane,master\nLabels:             beta.kubernetes.io/arch=amd64\n                    beta.kubernetes.io/os=linux\n                    kubernetes.io/arch=amd64\n                    kubernetes.io/hostname=k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k\n                    kubernetes.io/os=linux\n                    node-role.kubernetes.io/control-plane=\n                    node-role.kubernetes.io/master=\n                    node.kubernetes.io/exclude-from-external-load-balancers=\nAnnotations:        cluster.x-k8s.io/cluster-name: k8s-upgrade-and-conformance-a00ni7\n                    cluster.x-k8s.io/cluster-namespace: k8s-upgrade-and-conformance-51nzmu\n                    cluster.x-k8s.io/machine: k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k\n                    cluster.x-k8s.io/owner-kind: KubeadmControlPlane\n                    cluster.x-k8s.io/owner-name: k8s-upgrade-and-conformance-a00ni7-9hzb6\n                    kubeadm.alpha.kubernetes.io/cri-socket: unix:///var/run/containerd/containerd.sock\n                    node.alpha.kubernetes.io/ttl: 0\n                    volumes.kubernetes.io/controller-managed-attach-detach: true\nCreationTimestamp:  Mon, 29 Aug 2022 20:43:29 +0000\nTaints:             node-role.kubernetes.io/master:NoSchedule\nUnschedulable:      false\nLease:\n  HolderIdentity:  k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k\n  AcquireTime:     <unset>\n  RenewTime:       Mon, 29 Aug 2022 20:53:21 +0000\nConditions:\n  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message\n  ----             ------  -----------------                 ------------------                ------                       -------\n  MemoryPressure   False   Mon, 29 Aug 2022 20:49:41 +0000   Mon, 29 Aug 2022 20:43:29 +0000   KubeletHasSufficientMemory   kubelet has sufficient memory available\n  DiskPressure     False   Mon, 29 Aug 2022 20:49:41 +0000   Mon, 29 Aug 2022 20:43:29 +0000   KubeletHasNoDiskPressure     kubelet has no disk pressure\n  PIDPressure      False   Mon, 29 Aug 2022 20:49:41 +0000   Mon, 29 Aug 2022 20:43:29 +0000   KubeletHasSufficientPID      kubelet has sufficient PID available\n  Ready            True    Mon, 29 Aug 2022 20:49:41 +0000   Mon, 29 Aug 2022 20:44:40 +0000   KubeletReady                 kubelet is posting ready status\nAddresses:\n  InternalIP:  172.18.0.9\n  Hostname:    k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k\nCapacity:\n  cpu:                8\n  ephemeral-storage:  253882800Ki\n  hugepages-1Gi:      0\n  hugepages-2Mi:      0\n  memory:             65860680Ki\n  pods:               110\nAllocatable:\n  cpu:                8\n  ephemeral-storage:  253882800Ki\n  hugepages-1Gi:      0\n  hugepages-2Mi:      0\n  memory:             65860680Ki\n  pods:               110\nSystem Info:\n  Machine ID:                 b82aa005d9074ef2800216c62c6fc28c\n  System UUID:                1df0008a-1a78-47e5-9026-6319a4045bda\n  Boot ID:                    53a27ae4-f27a-4e7f-8dc7-824060a65be4\n  Kernel Version:             5.4.0-1072-gke\n  OS Image:                   Ubuntu 21.10\n  Operating System:           linux\n  Architecture:               amd64\n  Container Runtime Version:  containerd://1.6.4\n  Kubelet Version:            v1.21.14\n  Kube-Proxy Version:         v1.21.14\nPodCIDR:                      192.168.5.0/24\nPodCIDRs:                     192.168.5.0/24\nProviderID:                   docker:////k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k\nNon-terminated Pods:          (6 in total)\n  Namespace                   Name                                                                      CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age\n  ---------                   ----                                                                      ------------  ----------  ---------------  -------------  ---\n  kube-system                 etcd-k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k                       100m (1%)     0 (0%)      100Mi (0%)       0 (0%)         9m53s\n  kube-system                 kindnet-xt62s                                                             100m (1%)     100m (1%)   50Mi (0%)        50Mi (0%)      9m58s\n  kube-system                 kube-apiserver-k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k             250m (3%)     0 (0%)      0 (0%)           0 (0%)         9m57s\n  kube-system                 kube-controller-manager-k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k    200m (2%)     0 (0%)      0 (0%)           0 (0%)         9m57s\n  kube-system                 kube-proxy-f8cvk                                                          0 (0%)        0 (0%)      0 (0%)           0 (0%)         4m24s\n  kube-system                 kube-scheduler-k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k             100m (1%)     0 (0%)      0 (0%)           0 (0%)         9m57s\nAllocated resources:\n  (Total limits may be over 100 percent, i.e., overcommitted.)\n  Resource           Requests    Limits\n  --------           --------    ------\n  cpu                750m (9%)   100m (1%)\n  memory             150Mi (0%)  50Mi (0%)\n  ephemeral-storage  0 (0%)      0 (0%)\n  hugepages-1Gi      0 (0%)      0 (0%)\n  hugepages-2Mi      0 (0%)      0 (0%)\nEvents:\n  Type     Reason                    Age                    From        Message\n  ----     ------                    ----                   ----        -------\n  Normal   Starting                  9m58s                  kubelet     Starting kubelet.\n  Warning  InvalidDiskCapacity       9m58s                  kubelet     invalid capacity 0 on image filesystem\n  Normal   NodeHasSufficientMemory   9m58s (x2 over 9m58s)  kubelet     Node k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k status is now: NodeHasSufficientMemory\n  Normal   NodeHasNoDiskPressure     9m58s (x2 over 9m58s)  kubelet     Node k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k status is now: NodeHasNoDiskPressure\n  Normal   NodeHasSufficientPID      9m58s (x2 over 9m58s)  kubelet     Node k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k status is now: NodeHasSufficientPID\n  Normal   NodeAllocatableEnforced   9m58s                  kubelet     Updated Node Allocatable limit across pods\n  Warning  CheckLimitsForResolvConf  9m58s                  kubelet     Resolv.conf file '/etc/resolv.conf' contains search line consisting of more than 3 domains!\n  Normal   Starting                  9m38s                  kube-proxy  Starting kube-proxy.\n  Normal   NodeReady                 8m47s (x2 over 9m8s)   kubelet     Node k8s-upgrade-and-conformance-a00ni7-9hzb6-7nq5k status is now: NodeReady\n  Normal   Starting                  4m22s                  kube-proxy  Starting kube-proxy.\n"
... skipping 4 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:53:27.596: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-5464" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl describe should check if kubectl describe prints relevant information for rc and pods  [Conformance]","total":-1,"completed":5,"skipped":110,"failed":0}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Container Runtime
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:53:27.670: 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:630
    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
    Aug 29 20:53:29.769: INFO: Expected: &{DONE} to match Container's Termination Message: DONE --
    STEP: delete the container
    [AfterEach] [sig-node] Container Runtime
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:53:29.788: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-runtime-8017" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] 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":6,"skipped":126,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected secret
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:53:29.852: 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:630
    STEP: Creating projection with secret that has name projected-secret-test-368ee48d-1e49-4b28-b59a-5cca0ade49ef
    STEP: Creating a pod to test consume secrets
    Aug 29 20:53:29.922: INFO: Waiting up to 5m0s for pod "pod-projected-secrets-886216ce-b805-42b8-b6cc-f2e762ef55ea" in namespace "projected-5668" to be "Succeeded or Failed"

    Aug 29 20:53:29.932: INFO: Pod "pod-projected-secrets-886216ce-b805-42b8-b6cc-f2e762ef55ea": Phase="Pending", Reason="", readiness=false. Elapsed: 9.255916ms
    Aug 29 20:53:31.936: INFO: Pod "pod-projected-secrets-886216ce-b805-42b8-b6cc-f2e762ef55ea": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.013138705s
    STEP: Saw pod success
    Aug 29 20:53:31.936: INFO: Pod "pod-projected-secrets-886216ce-b805-42b8-b6cc-f2e762ef55ea" satisfied condition "Succeeded or Failed"

    Aug 29 20:53:31.939: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-izhnvy pod pod-projected-secrets-886216ce-b805-42b8-b6cc-f2e762ef55ea container projected-secret-volume-test: <nil>
    STEP: delete the pod
    Aug 29 20:53:31.958: INFO: Waiting for pod pod-projected-secrets-886216ce-b805-42b8-b6cc-f2e762ef55ea to disappear
    Aug 29 20:53:31.962: INFO: Pod pod-projected-secrets-886216ce-b805-42b8-b6cc-f2e762ef55ea 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:186
    Aug 29 20:53:31.962: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-5668" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected secret should be consumable from pods in volume [NodeConformance] [Conformance]","total":-1,"completed":7,"skipped":146,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 52 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:53:33.989: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-9555" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl logs should be able to retrieve and filter logs  [Conformance]","total":-1,"completed":12,"skipped":217,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:746
    [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:630
    STEP: creating service multi-endpoint-test in namespace services-4093
    STEP: waiting up to 3m0s for service multi-endpoint-test in namespace services-4093 to expose endpoints map[]
    Aug 29 20:53:34.098: INFO: Failed go get Endpoints object: endpoints "multi-endpoint-test" not found

    Aug 29 20:53:35.108: INFO: successfully validated that service multi-endpoint-test in namespace services-4093 exposes endpoints map[]
    STEP: Creating pod pod1 in namespace services-4093
    Aug 29 20:53:35.124: INFO: The status of Pod pod1 is Pending, waiting for it to be Running (with Ready = true)
    Aug 29 20:53:37.129: INFO: The status of Pod pod1 is Running (Ready = true)
    STEP: waiting up to 3m0s for service multi-endpoint-test in namespace services-4093 to expose endpoints map[pod1:[100]]
    Aug 29 20:53:37.151: INFO: successfully validated that service multi-endpoint-test in namespace services-4093 exposes endpoints map[pod1:[100]]
... skipping 14 lines ...
    STEP: Destroying namespace "services-4093" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:750
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should serve multiport endpoints from pods  [Conformance]","total":-1,"completed":13,"skipped":247,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Probing container
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:54:01.495: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-probe-3135" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Probing container should be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]","total":-1,"completed":14,"skipped":268,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 59 lines ...
    STEP: Destroying namespace "services-7367" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:750
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should have session affinity timeout work for service with type clusterIP [LinuxOnly] [Conformance]","total":-1,"completed":8,"skipped":147,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Downward API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:54:17.595: 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:630
    STEP: Creating a pod to test downward api env vars
    Aug 29 20:54:17.648: INFO: Waiting up to 5m0s for pod "downward-api-356d1dce-d586-4d5e-b13e-44dff45b7845" in namespace "downward-api-418" to be "Succeeded or Failed"

    Aug 29 20:54:17.656: INFO: Pod "downward-api-356d1dce-d586-4d5e-b13e-44dff45b7845": Phase="Pending", Reason="", readiness=false. Elapsed: 7.724594ms
    Aug 29 20:54:19.660: INFO: Pod "downward-api-356d1dce-d586-4d5e-b13e-44dff45b7845": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.011444561s
    STEP: Saw pod success
    Aug 29 20:54:19.660: INFO: Pod "downward-api-356d1dce-d586-4d5e-b13e-44dff45b7845" satisfied condition "Succeeded or Failed"

    Aug 29 20:54:19.662: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-izhnvy pod downward-api-356d1dce-d586-4d5e-b13e-44dff45b7845 container dapi-container: <nil>
    STEP: delete the pod
    Aug 29 20:54:19.676: INFO: Waiting for pod downward-api-356d1dce-d586-4d5e-b13e-44dff45b7845 to disappear
    Aug 29 20:54:19.678: INFO: Pod downward-api-356d1dce-d586-4d5e-b13e-44dff45b7845 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:186
    Aug 29 20:54:19.678: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-418" 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":9,"skipped":155,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Sysctls [LinuxOnly] [NodeFeature:Sysctls]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/sysctl.go:35
    [BeforeEach] [sig-node] Sysctls [LinuxOnly] [NodeFeature:Sysctls]
... skipping 4 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-node] Sysctls [LinuxOnly] [NodeFeature:Sysctls]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/sysctl.go:64
    [It] should support unsafe sysctls which are actually allowed [MinimumKubeletVersion:1.21] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod with the kernel.shm_rmid_forced sysctl
    STEP: Watching for error events or started pod

    STEP: Waiting for pod completion
    STEP: Checking that the pod succeeded
    STEP: Getting logs from the pod
    STEP: Checking that the sysctl is actually updated
    [AfterEach] [sig-node] Sysctls [LinuxOnly] [NodeFeature:Sysctls]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:54:21.748: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "sysctl-740" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Sysctls [LinuxOnly] [NodeFeature:Sysctls] should support unsafe sysctls which are actually allowed [MinimumKubeletVersion:1.21] [Conformance]","total":-1,"completed":10,"skipped":161,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Container Runtime
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:54:45.006: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-runtime-6487" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Container Runtime blackbox test when starting a container that exits should run with the expected status [NodeConformance] [Conformance]","total":-1,"completed":11,"skipped":192,"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:185
    STEP: Creating a kubernetes client
    Aug 29 20:54:45.034: 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:630
    STEP: Creating a pod to test emptydir 0644 on node default medium
    Aug 29 20:54:45.069: INFO: Waiting up to 5m0s for pod "pod-a447f5c2-7fec-41b3-a347-8dd1d64f7098" in namespace "emptydir-2874" to be "Succeeded or Failed"

    Aug 29 20:54:45.072: INFO: Pod "pod-a447f5c2-7fec-41b3-a347-8dd1d64f7098": Phase="Pending", Reason="", readiness=false. Elapsed: 2.825213ms
    Aug 29 20:54:47.077: INFO: Pod "pod-a447f5c2-7fec-41b3-a347-8dd1d64f7098": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007620308s
    STEP: Saw pod success
    Aug 29 20:54:47.077: INFO: Pod "pod-a447f5c2-7fec-41b3-a347-8dd1d64f7098" satisfied condition "Succeeded or Failed"

    Aug 29 20:54:47.080: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-a447f5c2-7fec-41b3-a347-8dd1d64f7098 container test-container: <nil>
    STEP: delete the pod
    Aug 29 20:54:47.106: INFO: Waiting for pod pod-a447f5c2-7fec-41b3-a347-8dd1d64f7098 to disappear
    Aug 29 20:54:47.109: INFO: Pod pod-a447f5c2-7fec-41b3-a347-8dd1d64f7098 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:186
    Aug 29 20:54:47.109: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-2874" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0644,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":12,"skipped":207,"failed":0}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:52:11.006: 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 verify that a failing subpath expansion can be modified during the lifecycle of a container [Slow] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: creating the pod with failed condition

    STEP: updating the pod
    Aug 29 20:54:11.563: INFO: Successfully updated pod "var-expansion-50576cd7-f86f-48c9-9846-6f65e1c3c486"
    STEP: waiting for pod running
    STEP: deleting the pod gracefully
    Aug 29 20:54:13.571: INFO: Deleting pod "var-expansion-50576cd7-f86f-48c9-9846-6f65e1c3c486" in namespace "var-expansion-3779"
    Aug 29 20:54:13.576: INFO: Wait up to 5m0s for pod "var-expansion-50576cd7-f86f-48c9-9846-6f65e1c3c486" to be fully deleted
... skipping 6 lines ...
    • [SLOW TEST:160.587 seconds]
    [sig-node] Variable Expansion
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/framework.go:23
      should verify that a failing subpath expansion can be modified during the lifecycle of a container [Slow] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    ------------------------------
    {"msg":"PASSED [sig-node] Variable Expansion should verify that a failing subpath expansion can be modified during the lifecycle of a container [Slow] [Conformance]","total":-1,"completed":24,"skipped":450,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-instrumentation] Events API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:54:51.701: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-8570" 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":25,"skipped":460,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-apps] Deployment
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:54:52.228: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-9844" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment deployment should delete old replica sets [Conformance]","total":-1,"completed":13,"skipped":223,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-apps] Deployment
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:54:53.835: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-3055" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment Deployment should have a working scale subresource [Conformance]","total":-1,"completed":26,"skipped":464,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] EndpointSlice
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:54:53.941: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "endpointslice-8414" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] EndpointSlice should have Endpoints and EndpointSlices pointing to API Server [Conformance]","total":-1,"completed":27,"skipped":472,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:54:54.008: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-113" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be immutable if `immutable` field is set [Conformance]","total":-1,"completed":28,"skipped":474,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:54:52.264: 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:630
    STEP: Creating configMap with name configmap-test-volume-map-88c9a985-5a72-4ee4-8d1f-d603b7ac17a3
    STEP: Creating a pod to test consume configMaps
    Aug 29 20:54:52.305: INFO: Waiting up to 5m0s for pod "pod-configmaps-8851b293-5760-4f1c-b6aa-5f3a7390c26c" in namespace "configmap-6553" to be "Succeeded or Failed"

    Aug 29 20:54:52.308: INFO: Pod "pod-configmaps-8851b293-5760-4f1c-b6aa-5f3a7390c26c": Phase="Pending", Reason="", readiness=false. Elapsed: 3.217699ms
    Aug 29 20:54:54.313: INFO: Pod "pod-configmaps-8851b293-5760-4f1c-b6aa-5f3a7390c26c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007485547s
    STEP: Saw pod success
    Aug 29 20:54:54.313: INFO: Pod "pod-configmaps-8851b293-5760-4f1c-b6aa-5f3a7390c26c" satisfied condition "Succeeded or Failed"

    Aug 29 20:54:54.316: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-configmaps-8851b293-5760-4f1c-b6aa-5f3a7390c26c container agnhost-container: <nil>
    STEP: delete the pod
    Aug 29 20:54:54.330: INFO: Waiting for pod pod-configmaps-8851b293-5760-4f1c-b6aa-5f3a7390c26c to disappear
    Aug 29 20:54:54.333: INFO: Pod pod-configmaps-8851b293-5760-4f1c-b6aa-5f3a7390c26c no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:54:54.333: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-6553" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with mappings [NodeConformance] [Conformance]","total":-1,"completed":14,"skipped":226,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [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:185
    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:186
    Aug 29 20:54:54.383: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "tables-6829" 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":15,"skipped":236,"failed":0}

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

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-node] Probing container
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:55:01.668: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-probe-8245" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Probing container with readiness probe that fails should never be ready and never restart [NodeConformance] [Conformance]","total":-1,"completed":15,"skipped":287,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 33 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:55:07.706: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-69" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl expose should create services for rc  [Conformance]","total":-1,"completed":30,"skipped":484,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:55:08.274: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-574" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should update annotations on modification [NodeConformance] [Conformance]","total":-1,"completed":16,"skipped":291,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] PodTemplates
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:55:08.414: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "podtemplate-6391" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] PodTemplates should delete a collection of pod templates [Conformance]","total":-1,"completed":17,"skipped":309,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 10 lines ...
    STEP: Destroying namespace "services-1565" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:750
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should provide secure master service  [Conformance]","total":-1,"completed":18,"skipped":320,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:55:08.676: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-7709" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl api-versions should check if v1 is in available api versions  [Conformance]","total":-1,"completed":19,"skipped":332,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:55:08.898: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-1909" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl version should check is all data is printed  [Conformance]","total":-1,"completed":20,"skipped":358,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Downward API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:55:08.918: 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:630
    STEP: Creating a pod to test downward api env vars
    Aug 29 20:55:08.964: INFO: Waiting up to 5m0s for pod "downward-api-c017e355-e0f7-40d6-a407-db9895402fc9" in namespace "downward-api-122" to be "Succeeded or Failed"

    Aug 29 20:55:08.968: INFO: Pod "downward-api-c017e355-e0f7-40d6-a407-db9895402fc9": Phase="Pending", Reason="", readiness=false. Elapsed: 3.68159ms
    Aug 29 20:55:10.972: INFO: Pod "downward-api-c017e355-e0f7-40d6-a407-db9895402fc9": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007412752s
    STEP: Saw pod success
    Aug 29 20:55:10.972: INFO: Pod "downward-api-c017e355-e0f7-40d6-a407-db9895402fc9" satisfied condition "Succeeded or Failed"

    Aug 29 20:55:10.974: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-exv40f pod downward-api-c017e355-e0f7-40d6-a407-db9895402fc9 container dapi-container: <nil>
    STEP: delete the pod
    Aug 29 20:55:10.994: INFO: Waiting for pod downward-api-c017e355-e0f7-40d6-a407-db9895402fc9 to disappear
    Aug 29 20:55:10.997: INFO: Pod downward-api-c017e355-e0f7-40d6-a407-db9895402fc9 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:186
    Aug 29 20:55:10.997: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-122" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Downward API should provide default limits.cpu/memory from node allocatable [NodeConformance] [Conformance]","total":-1,"completed":21,"skipped":365,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-node] KubeletManagedEtcHosts
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:55:15.814: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "e2e-kubelet-etc-hosts-4310" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] KubeletManagedEtcHosts should test kubelet managed /etc/hosts file [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":22,"skipped":368,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:630
    STEP: Creating pod pod-subpath-test-configmap-spnj
    STEP: Creating a pod to test atomic-volume-subpath
    Aug 29 20:55:15.899: INFO: Waiting up to 5m0s for pod "pod-subpath-test-configmap-spnj" in namespace "subpath-2992" to be "Succeeded or Failed"

    Aug 29 20:55:15.902: INFO: Pod "pod-subpath-test-configmap-spnj": Phase="Pending", Reason="", readiness=false. Elapsed: 3.065938ms
    Aug 29 20:55:17.906: INFO: Pod "pod-subpath-test-configmap-spnj": Phase="Running", Reason="", readiness=true. Elapsed: 2.007516221s
    Aug 29 20:55:19.910: INFO: Pod "pod-subpath-test-configmap-spnj": Phase="Running", Reason="", readiness=true. Elapsed: 4.010838778s
    Aug 29 20:55:21.914: INFO: Pod "pod-subpath-test-configmap-spnj": Phase="Running", Reason="", readiness=true. Elapsed: 6.015294156s
    Aug 29 20:55:23.921: INFO: Pod "pod-subpath-test-configmap-spnj": Phase="Running", Reason="", readiness=true. Elapsed: 8.02206085s
    Aug 29 20:55:25.926: INFO: Pod "pod-subpath-test-configmap-spnj": Phase="Running", Reason="", readiness=true. Elapsed: 10.026791534s
    Aug 29 20:55:27.930: INFO: Pod "pod-subpath-test-configmap-spnj": Phase="Running", Reason="", readiness=true. Elapsed: 12.031524342s
    Aug 29 20:55:29.935: INFO: Pod "pod-subpath-test-configmap-spnj": Phase="Running", Reason="", readiness=true. Elapsed: 14.035720967s
    Aug 29 20:55:31.940: INFO: Pod "pod-subpath-test-configmap-spnj": Phase="Running", Reason="", readiness=true. Elapsed: 16.041290988s
    Aug 29 20:55:33.945: INFO: Pod "pod-subpath-test-configmap-spnj": Phase="Running", Reason="", readiness=true. Elapsed: 18.045894707s
    Aug 29 20:55:35.949: INFO: Pod "pod-subpath-test-configmap-spnj": Phase="Running", Reason="", readiness=true. Elapsed: 20.050422865s
    Aug 29 20:55:37.953: INFO: Pod "pod-subpath-test-configmap-spnj": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.05429959s
    STEP: Saw pod success
    Aug 29 20:55:37.953: INFO: Pod "pod-subpath-test-configmap-spnj" satisfied condition "Succeeded or Failed"

    Aug 29 20:55:37.956: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-subpath-test-configmap-spnj container test-container-subpath-configmap-spnj: <nil>
    STEP: delete the pod
    Aug 29 20:55:37.969: INFO: Waiting for pod pod-subpath-test-configmap-spnj to disappear
    Aug 29 20:55:37.971: INFO: Pod pod-subpath-test-configmap-spnj no longer exists
    STEP: Deleting pod pod-subpath-test-configmap-spnj
    Aug 29 20:55:37.971: INFO: Deleting pod "pod-subpath-test-configmap-spnj" in namespace "subpath-2992"
    [AfterEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:55:37.975: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "subpath-2992" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Subpath Atomic writer volumes should support subpaths with configmap pod [LinuxOnly] [Conformance]","total":-1,"completed":23,"skipped":392,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:55:38.090: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-7856" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Secrets should be immutable if `immutable` field is set [Conformance]","total":-1,"completed":24,"skipped":424,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-apps] ReplicationController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:55:43.159: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-146" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should release no longer matching pods [Conformance]","total":-1,"completed":25,"skipped":428,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 89 lines ...
    STEP: Destroying namespace "services-4338" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:750
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]","total":-1,"completed":16,"skipped":243,"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:185
    STEP: Creating a kubernetes client
... skipping 24 lines ...
    STEP: Destroying namespace "webhook-3852-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:102
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny attaching pod [Conformance]","total":-1,"completed":17,"skipped":260,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:55:53.416: 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:630
    STEP: Creating projection with secret that has name secret-emptykey-test-47c8189a-bfb6-4f01-b211-9327cf78b330
    [AfterEach] [sig-node] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:55:53.457: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-3712" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Secrets should fail to create secret due to empty secret key [Conformance]","total":-1,"completed":18,"skipped":277,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:55:53.544: 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:630
    STEP: Creating configMap with name projected-configmap-test-volume-map-e3b0a08a-fc35-4fc1-9e7f-8ba621ab11d3
    STEP: Creating a pod to test consume configMaps
    Aug 29 20:55:53.593: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-45ec1de8-b3bf-42cc-92b0-24c70fdc9141" in namespace "projected-8667" to be "Succeeded or Failed"

    Aug 29 20:55:53.596: INFO: Pod "pod-projected-configmaps-45ec1de8-b3bf-42cc-92b0-24c70fdc9141": Phase="Pending", Reason="", readiness=false. Elapsed: 2.634031ms
    Aug 29 20:55:55.601: INFO: Pod "pod-projected-configmaps-45ec1de8-b3bf-42cc-92b0-24c70fdc9141": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007417348s
    STEP: Saw pod success
    Aug 29 20:55:55.601: INFO: Pod "pod-projected-configmaps-45ec1de8-b3bf-42cc-92b0-24c70fdc9141" satisfied condition "Succeeded or Failed"

    Aug 29 20:55:55.604: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-projected-configmaps-45ec1de8-b3bf-42cc-92b0-24c70fdc9141 container agnhost-container: <nil>
    STEP: delete the pod
    Aug 29 20:55:55.617: INFO: Waiting for pod pod-projected-configmaps-45ec1de8-b3bf-42cc-92b0-24c70fdc9141 to disappear
    Aug 29 20:55:55.620: INFO: Pod pod-projected-configmaps-45ec1de8-b3bf-42cc-92b0-24c70fdc9141 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:186
    Aug 29 20:55:55.620: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-8667" 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":19,"skipped":316,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-instrumentation] Events
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:55:55.703: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-1540" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-instrumentation] Events should ensure that an event can be fetched, patched, deleted, and listed [Conformance]","total":-1,"completed":20,"skipped":324,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:55:55.759: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename security-context
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should support pod.Spec.SecurityContext.RunAsUser And pod.Spec.SecurityContext.RunAsGroup [LinuxOnly] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test pod.Spec.SecurityContext.RunAsUser
    Aug 29 20:55:55.789: INFO: Waiting up to 5m0s for pod "security-context-68811311-8f92-4d6d-b7b7-49a9b5f58c52" in namespace "security-context-3511" to be "Succeeded or Failed"

    Aug 29 20:55:55.795: INFO: Pod "security-context-68811311-8f92-4d6d-b7b7-49a9b5f58c52": Phase="Pending", Reason="", readiness=false. Elapsed: 5.687992ms
    Aug 29 20:55:57.799: INFO: Pod "security-context-68811311-8f92-4d6d-b7b7-49a9b5f58c52": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.009912856s
    STEP: Saw pod success
    Aug 29 20:55:57.799: INFO: Pod "security-context-68811311-8f92-4d6d-b7b7-49a9b5f58c52" satisfied condition "Succeeded or Failed"

    Aug 29 20:55:57.802: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod security-context-68811311-8f92-4d6d-b7b7-49a9b5f58c52 container test-container: <nil>
    STEP: delete the pod
    Aug 29 20:55:57.813: INFO: Waiting for pod security-context-68811311-8f92-4d6d-b7b7-49a9b5f58c52 to disappear
    Aug 29 20:55:57.818: INFO: Pod security-context-68811311-8f92-4d6d-b7b7-49a9b5f58c52 no longer exists
    [AfterEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 20:55:57.818: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "security-context-3511" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Security Context should support pod.Spec.SecurityContext.RunAsUser And pod.Spec.SecurityContext.RunAsGroup [LinuxOnly] [Conformance]","total":-1,"completed":21,"skipped":358,"failed":0}

    
    SSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Networking
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:56:05.660: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pod-network-test-8051" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: udp [NodeConformance] [Conformance]","total":-1,"completed":26,"skipped":452,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 20:56:05.676: 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:630
    STEP: Creating configMap with name projected-configmap-test-volume-f139ab1d-b0f6-44b5-9acd-3df05f6e2f13
    STEP: Creating a pod to test consume configMaps
    Aug 29 20:56:05.711: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-452d6b11-4b8c-4c2f-b9c8-ea6e545202cb" in namespace "projected-4602" to be "Succeeded or Failed"

    Aug 29 20:56:05.714: INFO: Pod "pod-projected-configmaps-452d6b11-4b8c-4c2f-b9c8-ea6e545202cb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.469011ms
    Aug 29 20:56:07.718: INFO: Pod "pod-projected-configmaps-452d6b11-4b8c-4c2f-b9c8-ea6e545202cb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007170826s
    STEP: Saw pod success
    Aug 29 20:56:07.719: INFO: Pod "pod-projected-configmaps-452d6b11-4b8c-4c2f-b9c8-ea6e545202cb" satisfied condition "Succeeded or Failed"

    Aug 29 20:56:07.724: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod pod-projected-configmaps-452d6b11-4b8c-4c2f-b9c8-ea6e545202cb container agnhost-container: <nil>
    STEP: delete the pod
    Aug 29 20:56:07.742: INFO: Waiting for pod pod-projected-configmaps-452d6b11-4b8c-4c2f-b9c8-ea6e545202cb to disappear
    Aug 29 20:56:07.745: INFO: Pod pod-projected-configmaps-452d6b11-4b8c-4c2f-b9c8-ea6e545202cb 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:186
    Aug 29 20:56:07.745: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-4602" 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":27,"skipped":456,"failed":1,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]"]}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 20:56:08.998: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-246" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a service. [Conformance]","total":-1,"completed":22,"skipped":371,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 9 lines ...
    STEP: creating replication controller affinity-clusterip-transition in namespace services-1305
    I0829 20:55:07.764144      18 runners.go:190] Created replication controller with name: affinity-clusterip-transition, namespace: services-1305, replica count: 3
    I0829 20:55:10.816294      18 runners.go:190] affinity-clusterip-transition Pods: 3 out of 3 created, 3 running, 0 pending, 0 waiting, 0 inactive, 0 terminating, 0 unknown, 0 runningButNotReady 
    Aug 29 20:55:10.822: INFO: Creating new exec pod
    Aug 29 20:55:13.835: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:16.109: INFO: rc: 1
    Aug 29 20:55:16.109: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:17.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:19.314: INFO: rc: 1
    Aug 29 20:55:19.314: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:20.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:22.302: INFO: rc: 1
    Aug 29 20:55:22.302: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:23.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:25.274: INFO: rc: 1
    Aug 29 20:55:25.274: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:26.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:28.302: INFO: rc: 1
    Aug 29 20:55:28.302: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:29.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:31.279: INFO: rc: 1
    Aug 29 20:55:31.279: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:32.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:34.318: INFO: rc: 1
    Aug 29 20:55:34.318: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:35.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:37.282: INFO: rc: 1
    Aug 29 20:55:37.282: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:38.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:40.289: INFO: rc: 1
    Aug 29 20:55:40.289: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:41.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:43.283: INFO: rc: 1
    Aug 29 20:55:43.284: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:44.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:46.280: INFO: rc: 1
    Aug 29 20:55:46.280: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:47.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:49.290: INFO: rc: 1
    Aug 29 20:55:49.290: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:50.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:52.322: INFO: rc: 1
    Aug 29 20:55:52.322: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:53.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:55.293: INFO: rc: 1
    Aug 29 20:55:55.293: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:56.110: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:55:58.292: INFO: rc: 1
    Aug 29 20:55:58.292: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:55:59.110: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:01.286: INFO: rc: 1
    Aug 29 20:56:01.286: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:02.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:04.282: INFO: rc: 1
    Aug 29 20:56:04.282: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:05.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:07.268: INFO: rc: 1
    Aug 29 20:56:07.268: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:08.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:10.303: INFO: rc: 1
    Aug 29 20:56:10.303: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:11.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:13.392: INFO: rc: 1
    Aug 29 20:56:13.392: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:14.110: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:16.298: INFO: rc: 1
    Aug 29 20:56:16.298: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:17.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:19.270: INFO: rc: 1
    Aug 29 20:56:19.270: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:20.110: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:22.283: INFO: rc: 1
    Aug 29 20:56:22.283: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:23.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:25.294: INFO: rc: 1
    Aug 29 20:56:25.294: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:26.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:28.281: INFO: rc: 1
    Aug 29 20:56:28.281: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:29.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:31.282: INFO: rc: 1
    Aug 29 20:56:31.282: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:32.110: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:34.290: INFO: rc: 1
    Aug 29 20:56:34.290: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:35.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:37.282: INFO: rc: 1
    Aug 29 20:56:37.282: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:38.110: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:40.281: INFO: rc: 1
    Aug 29 20:56:40.281: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:41.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:43.287: INFO: rc: 1
    Aug 29 20:56:43.287: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:44.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:46.306: INFO: rc: 1
    Aug 29 20:56:46.306: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:47.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:49.287: INFO: rc: 1
    Aug 29 20:56:49.287: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:50.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:52.286: INFO: rc: 1
    Aug 29 20:56:52.286: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:53.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:55.292: INFO: rc: 1
    Aug 29 20:56:55.292: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:56.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:56:58.306: INFO: rc: 1
    Aug 29 20:56:58.306: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:56:59.110: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:57:01.308: INFO: rc: 1
    Aug 29 20:57:01.308: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:57:02.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:57:04.285: INFO: rc: 1
    Aug 29 20:57:04.286: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:57:05.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:57:07.284: INFO: rc: 1
    Aug 29 20:57:07.284: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:57:08.110: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:57:10.279: INFO: rc: 1
    Aug 29 20:57:10.279: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:57:11.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:57:13.279: INFO: rc: 1
    Aug 29 20:57:13.279: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:57:14.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:57:16.283: INFO: rc: 1
    Aug 29 20:57:16.283: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:57:16.283: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80'
    Aug 29 20:57:18.459: INFO: rc: 1
    Aug 29 20:57:18.459: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-1305 exec execpod-affinitykznzq -- /bin/sh -x -c echo hostName | nc -v -t -w 2 affinity-clusterip-transition 80:

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

    exit status 1
    Retrying...
    Aug 29 20:57:18.459: FAIL: Unexpected error:

        <*errors.errorString | 0xc00410e9c0>: {
            s: "service is not reachable within 2m0s timeout on endpoint affinity-clusterip-transition:80 over TCP protocol",
        }
        service is not reachable within 2m0s timeout on endpoint affinity-clusterip-transition:80 over TCP protocol
    occurred
    
... skipping 27 lines ...
    • Failure [141.747 seconds]
    [sig-network] Services
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/common/framework.go:23
      should be able to switch session affinity 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:630
    
      Aug 29 20:57:18.459: Unexpected error:

          <*errors.errorString | 0xc00410e9c0>: {
              s: "service is not reachable within 2m0s timeout on endpoint affinity-clusterip-transition:80 over TCP protocol",
          }
          service is not reachable within 2m0s timeout on endpoint affinity-clusterip-transition:80 over TCP protocol
      occurred
    
... skipping 23 lines ...
    • [SLOW TEST:300.078 seconds]
    [sig-apps] CronJob
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/framework.go:23
      should not schedule jobs when suspended [Slow] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    ------------------------------
    {"msg":"PASSED [sig-apps] CronJob should not schedule jobs when suspended [Slow] [Conformance]","total":-1,"completed":23,"skipped":388,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:01:11.607: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "dns-4599" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] DNS should support configurable pod DNS nameservers [Conformance]","total":-1,"completed":24,"skipped":390,"failed":0}

    
    SSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:01:12.309: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-8766" 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":25,"skipped":403,"failed":0}

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

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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/storage/projected_downwardapi.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:630
    STEP: Creating a pod to test downward API volume plugin
    Aug 29 21:01:30.262: INFO: Waiting up to 5m0s for pod "downwardapi-volume-e11bf83e-e948-4476-9186-b9b03d3446e8" in namespace "projected-3638" to be "Succeeded or Failed"

    Aug 29 21:01:30.273: INFO: Pod "downwardapi-volume-e11bf83e-e948-4476-9186-b9b03d3446e8": Phase="Pending", Reason="", readiness=false. Elapsed: 10.630536ms
    Aug 29 21:01:32.280: INFO: Pod "downwardapi-volume-e11bf83e-e948-4476-9186-b9b03d3446e8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.017020197s
    STEP: Saw pod success
    Aug 29 21:01:32.280: INFO: Pod "downwardapi-volume-e11bf83e-e948-4476-9186-b9b03d3446e8" satisfied condition "Succeeded or Failed"

    Aug 29 21:01:32.285: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-izhnvy pod downwardapi-volume-e11bf83e-e948-4476-9186-b9b03d3446e8 container client-container: <nil>
    STEP: delete the pod
    Aug 29 21:01:32.324: INFO: Waiting for pod downwardapi-volume-e11bf83e-e948-4476-9186-b9b03d3446e8 to disappear
    Aug 29 21:01:32.330: INFO: Pod downwardapi-volume-e11bf83e-e948-4476-9186-b9b03d3446e8 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:186
    Aug 29 21:01:32.331: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-3638" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should provide node allocatable (memory) as default memory limit if the limit is not set [NodeConformance] [Conformance]","total":-1,"completed":27,"skipped":430,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] PodTemplates
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:01:32.511: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "podtemplate-8707" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] PodTemplates should run the lifecycle of PodTemplates [Conformance]","total":-1,"completed":28,"skipped":452,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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/storage/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:630
    STEP: Creating a pod to test downward API volume plugin
    Aug 29 21:01:32.651: INFO: Waiting up to 5m0s for pod "downwardapi-volume-7a6cfdd6-5a14-4019-a4c9-a776e1b6281b" in namespace "downward-api-6060" to be "Succeeded or Failed"

    Aug 29 21:01:32.667: INFO: Pod "downwardapi-volume-7a6cfdd6-5a14-4019-a4c9-a776e1b6281b": Phase="Pending", Reason="", readiness=false. Elapsed: 16.231908ms
    Aug 29 21:01:34.675: INFO: Pod "downwardapi-volume-7a6cfdd6-5a14-4019-a4c9-a776e1b6281b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.023861946s
    STEP: Saw pod success
    Aug 29 21:01:34.675: INFO: Pod "downwardapi-volume-7a6cfdd6-5a14-4019-a4c9-a776e1b6281b" satisfied condition "Succeeded or Failed"

    Aug 29 21:01:34.680: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod downwardapi-volume-7a6cfdd6-5a14-4019-a4c9-a776e1b6281b container client-container: <nil>
    STEP: delete the pod
    Aug 29 21:01:34.719: INFO: Waiting for pod downwardapi-volume-7a6cfdd6-5a14-4019-a4c9-a776e1b6281b to disappear
    Aug 29 21:01:34.724: INFO: Pod downwardapi-volume-7a6cfdd6-5a14-4019-a4c9-a776e1b6281b 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:186
    Aug 29 21:01:34.724: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-6060" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should set DefaultMode on files [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":29,"skipped":482,"failed":0}

    
    SSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] server version
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:01:34.816: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "server-version-3580" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] server version should find the server version [Conformance]","total":-1,"completed":30,"skipped":489,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:01:34.840: 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,default) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test emptydir 0666 on node default medium
    Aug 29 21:01:34.897: INFO: Waiting up to 5m0s for pod "pod-4c425ea4-1ea3-4f34-9a8b-d3721daf5250" in namespace "emptydir-6329" to be "Succeeded or Failed"

    Aug 29 21:01:34.901: INFO: Pod "pod-4c425ea4-1ea3-4f34-9a8b-d3721daf5250": Phase="Pending", Reason="", readiness=false. Elapsed: 3.783598ms
    Aug 29 21:01:36.912: INFO: Pod "pod-4c425ea4-1ea3-4f34-9a8b-d3721daf5250": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.014257711s
    STEP: Saw pod success
    Aug 29 21:01:36.912: INFO: Pod "pod-4c425ea4-1ea3-4f34-9a8b-d3721daf5250" satisfied condition "Succeeded or Failed"

    Aug 29 21:01:36.916: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-4c425ea4-1ea3-4f34-9a8b-d3721daf5250 container test-container: <nil>
    STEP: delete the pod
    Aug 29 21:01:36.938: INFO: Waiting for pod pod-4c425ea4-1ea3-4f34-9a8b-d3721daf5250 to disappear
    Aug 29 21:01:36.944: INFO: Pod pod-4c425ea4-1ea3-4f34-9a8b-d3721daf5250 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:186
    Aug 29 21:01:36.944: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-6329" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0666,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":31,"skipped":492,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Garbage collector
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 41 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:01:47.797: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "gc-2145" for this suite.
    
    •
    ------------------------------
    {"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":32,"skipped":570,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Watchers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:01:48.160: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "watch-6308" 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":33,"skipped":602,"failed":0}

    
    SSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:01:50.394: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-7917" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should get a host IP [NodeConformance] [Conformance]","total":-1,"completed":34,"skipped":615,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-apps] StatefulSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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-539
    STEP: Creating statefulset with conflicting port in namespace statefulset-539
    STEP: Waiting until pod test-pod will start running in namespace statefulset-539
    STEP: Waiting until stateful pod ss-0 will be recreated and deleted at least once in namespace statefulset-539
    Aug 29 21:01:54.509: INFO: Observed stateful pod in namespace: statefulset-539, name: ss-0, uid: 0e066ea1-4f15-416c-a866-aaebc8355957, status phase: Pending. Waiting for statefulset controller to delete.
    Aug 29 21:01:54.900: INFO: Observed stateful pod in namespace: statefulset-539, name: ss-0, uid: 0e066ea1-4f15-416c-a866-aaebc8355957, status phase: Failed. Waiting for statefulset controller to delete.

    Aug 29 21:01:54.910: INFO: Observed stateful pod in namespace: statefulset-539, name: ss-0, uid: 0e066ea1-4f15-416c-a866-aaebc8355957, status phase: Failed. Waiting for statefulset controller to delete.

    Aug 29 21:01:54.914: INFO: Observed delete event for stateful pod ss-0 in namespace statefulset-539
    STEP: Removing pod with conflicting port in namespace statefulset-539
    STEP: Waiting when stateful pod ss-0 will be recreated in namespace statefulset-539 and will be in running state
    [AfterEach] Basic StatefulSet functionality [StatefulSetBasic]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/statefulset.go:116
    Aug 29 21:01:58.948: INFO: Deleting all statefulset in ns statefulset-539
... skipping 4 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:02:09.013: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-539" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Should recreate evicted statefulset [Conformance]","total":-1,"completed":35,"skipped":618,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:02:09.133: 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 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:630
    STEP: Creating configMap with name projected-configmap-test-volume-fa88d9f0-c49b-42f9-86d0-be1fc4eb46b3
    STEP: Creating a pod to test consume configMaps
    Aug 29 21:02:09.220: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-7bf62052-fc63-4b69-ad1f-79223540554d" in namespace "projected-6630" to be "Succeeded or Failed"

    Aug 29 21:02:09.227: INFO: Pod "pod-projected-configmaps-7bf62052-fc63-4b69-ad1f-79223540554d": Phase="Pending", Reason="", readiness=false. Elapsed: 6.989258ms
    Aug 29 21:02:11.234: INFO: Pod "pod-projected-configmaps-7bf62052-fc63-4b69-ad1f-79223540554d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.014079976s
    STEP: Saw pod success
    Aug 29 21:02:11.234: INFO: Pod "pod-projected-configmaps-7bf62052-fc63-4b69-ad1f-79223540554d" satisfied condition "Succeeded or Failed"

    Aug 29 21:02:11.238: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-projected-configmaps-7bf62052-fc63-4b69-ad1f-79223540554d container projected-configmap-volume-test: <nil>
    STEP: delete the pod
    Aug 29 21:02:11.271: INFO: Waiting for pod pod-projected-configmaps-7bf62052-fc63-4b69-ad1f-79223540554d to disappear
    Aug 29 21:02:11.276: INFO: Pod pod-projected-configmaps-7bf62052-fc63-4b69-ad1f-79223540554d 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:186
    Aug 29 21:02:11.276: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-6630" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap should be consumable in multiple volumes in the same pod [NodeConformance] [Conformance]","total":-1,"completed":36,"skipped":647,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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/storage/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:630
    STEP: Creating a pod to test downward API volume plugin
    Aug 29 21:02:11.480: INFO: Waiting up to 5m0s for pod "downwardapi-volume-bed8e700-94d6-4d0b-a59e-760d631c8f9e" in namespace "downward-api-6505" to be "Succeeded or Failed"

    Aug 29 21:02:11.492: INFO: Pod "downwardapi-volume-bed8e700-94d6-4d0b-a59e-760d631c8f9e": Phase="Pending", Reason="", readiness=false. Elapsed: 11.432585ms
    Aug 29 21:02:13.498: INFO: Pod "downwardapi-volume-bed8e700-94d6-4d0b-a59e-760d631c8f9e": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.017468465s
    STEP: Saw pod success
    Aug 29 21:02:13.499: INFO: Pod "downwardapi-volume-bed8e700-94d6-4d0b-a59e-760d631c8f9e" satisfied condition "Succeeded or Failed"

    Aug 29 21:02:13.503: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod downwardapi-volume-bed8e700-94d6-4d0b-a59e-760d631c8f9e container client-container: <nil>
    STEP: delete the pod
    Aug 29 21:02:13.526: INFO: Waiting for pod downwardapi-volume-bed8e700-94d6-4d0b-a59e-760d631c8f9e to disappear
    Aug 29 21:02:13.529: INFO: Pod downwardapi-volume-bed8e700-94d6-4d0b-a59e-760d631c8f9e 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:186
    Aug 29 21:02:13.530: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-6505" 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":37,"skipped":681,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourceConversionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 23 lines ...
    STEP: Destroying namespace "crd-webhook-9061" 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 a non homogeneous list of CRs [Conformance]","total":-1,"completed":38,"skipped":702,"failed":0}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 22 lines ...
    STEP: Destroying namespace "webhook-2885-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:102
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should deny crd creation [Conformance]","total":-1,"completed":39,"skipped":716,"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:185
    STEP: Creating a kubernetes client
... skipping 28 lines ...
    STEP: Destroying namespace "webhook-9204-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:102
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should be able to deny pod and configmap creation [Conformance]","total":-1,"completed":40,"skipped":717,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] HostPort
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:02:53.451: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "hostport-4421" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] HostPort validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]","total":-1,"completed":41,"skipped":727,"failed":0}

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

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Container Runtime
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:02:55.865: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-runtime-1951" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Container Runtime blackbox test on terminated container should report termination message [LinuxOnly] as empty when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]","total":-1,"completed":43,"skipped":764,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 37 lines ...
    Aug 29 21:03:06.000: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=crd-publish-openapi-4268 explain e2e-test-crd-publish-openapi-3316-crds.spec'
    Aug 29 21:03:06.595: INFO: stderr: ""
    Aug 29 21:03:06.595: INFO: stdout: "KIND:     E2e-test-crd-publish-openapi-3316-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"
    Aug 29 21:03:06.596: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=crd-publish-openapi-4268 explain e2e-test-crd-publish-openapi-3316-crds.spec.bars'
    Aug 29 21:03:07.108: INFO: stderr: ""
    Aug 29 21:03:07.108: INFO: stdout: "KIND:     E2e-test-crd-publish-openapi-3316-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

    Aug 29 21:03:07.109: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=crd-publish-openapi-4268 explain e2e-test-crd-publish-openapi-3316-crds.spec.bars2'
    Aug 29 21:03:07.674: 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:186
    Aug 29 21:03:12.952: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-4268" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD with validation schema [Conformance]","total":-1,"completed":44,"skipped":799,"failed":0}

    
    SSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Discovery
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 89 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:03:13.753: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "discovery-1776" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Discovery should validate PreferredVersion for each APIGroup [Conformance]","total":-1,"completed":45,"skipped":817,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [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:185
    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:186
    Aug 29 21:03:17.089: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "custom-resource-definition-5830" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] custom resource defaulting for requests and from storage works  [Conformance]","total":-1,"completed":46,"skipped":825,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:03:17.182: 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 [Slow] [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    Aug 29 21:03:19.239: INFO: Deleting pod "var-expansion-b978fe29-9578-4501-9ead-dab109cc263b" in namespace "var-expansion-7000"
    Aug 29 21:03:19.246: INFO: Wait up to 5m0s for pod "var-expansion-b978fe29-9578-4501-9ead-dab109cc263b" to be fully deleted
    [AfterEach] [sig-node] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:03:31.257: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-7000" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Variable Expansion should fail substituting values in a volume subpath with backticks [Slow] [Conformance]","total":-1,"completed":47,"skipped":877,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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/storage/downwardapi_volume.go:41
    [It] should provide container's cpu limit [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test downward API volume plugin
    Aug 29 21:03:31.333: INFO: Waiting up to 5m0s for pod "downwardapi-volume-f0aa9e50-f8b7-4a21-b695-ca411917ee04" in namespace "downward-api-5853" to be "Succeeded or Failed"

    Aug 29 21:03:31.339: INFO: Pod "downwardapi-volume-f0aa9e50-f8b7-4a21-b695-ca411917ee04": Phase="Pending", Reason="", readiness=false. Elapsed: 5.405304ms
    Aug 29 21:03:33.344: INFO: Pod "downwardapi-volume-f0aa9e50-f8b7-4a21-b695-ca411917ee04": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.01065115s
    STEP: Saw pod success
    Aug 29 21:03:33.344: INFO: Pod "downwardapi-volume-f0aa9e50-f8b7-4a21-b695-ca411917ee04" satisfied condition "Succeeded or Failed"

    Aug 29 21:03:33.348: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-izhnvy pod downwardapi-volume-f0aa9e50-f8b7-4a21-b695-ca411917ee04 container client-container: <nil>
    STEP: delete the pod
    Aug 29 21:03:33.379: INFO: Waiting for pod downwardapi-volume-f0aa9e50-f8b7-4a21-b695-ca411917ee04 to disappear
    Aug 29 21:03:33.382: INFO: Pod downwardapi-volume-f0aa9e50-f8b7-4a21-b695-ca411917ee04 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:186
    Aug 29 21:03:33.382: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-5853" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should provide container's cpu limit [NodeConformance] [Conformance]","total":-1,"completed":48,"skipped":886,"failed":0}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-apps] CronJob
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:05:01.468: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "cronjob-3777" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] CronJob should replace jobs when ReplaceConcurrent [Conformance]","total":-1,"completed":49,"skipped":891,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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/storage/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:630
    STEP: Creating a pod to test downward API volume plugin
    Aug 29 21:05:01.574: INFO: Waiting up to 5m0s for pod "downwardapi-volume-dccd07ab-3de7-4834-a897-c622e71463d1" in namespace "projected-2981" to be "Succeeded or Failed"

    Aug 29 21:05:01.579: INFO: Pod "downwardapi-volume-dccd07ab-3de7-4834-a897-c622e71463d1": Phase="Pending", Reason="", readiness=false. Elapsed: 4.636569ms
    Aug 29 21:05:03.584: INFO: Pod "downwardapi-volume-dccd07ab-3de7-4834-a897-c622e71463d1": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.009606927s
    STEP: Saw pod success
    Aug 29 21:05:03.584: INFO: Pod "downwardapi-volume-dccd07ab-3de7-4834-a897-c622e71463d1" satisfied condition "Succeeded or Failed"

    Aug 29 21:05:03.588: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-izhnvy pod downwardapi-volume-dccd07ab-3de7-4834-a897-c622e71463d1 container client-container: <nil>
    STEP: delete the pod
    Aug 29 21:05:03.611: INFO: Waiting for pod downwardapi-volume-dccd07ab-3de7-4834-a897-c622e71463d1 to disappear
    Aug 29 21:05:03.616: INFO: Pod downwardapi-volume-dccd07ab-3de7-4834-a897-c622e71463d1 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:186
    Aug 29 21:05:03.616: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-2981" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should provide container's memory request [NodeConformance] [Conformance]","total":-1,"completed":50,"skipped":930,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:05:03.645: 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] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/security_context.go:46
    [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:630
    Aug 29 21:05:03.685: INFO: Waiting up to 5m0s for pod "alpine-nnp-false-160db1b9-346d-4da7-8d59-8ffaec730856" in namespace "security-context-test-8061" to be "Succeeded or Failed"

    Aug 29 21:05:03.688: INFO: Pod "alpine-nnp-false-160db1b9-346d-4da7-8d59-8ffaec730856": Phase="Pending", Reason="", readiness=false. Elapsed: 2.977265ms
    Aug 29 21:05:05.693: INFO: Pod "alpine-nnp-false-160db1b9-346d-4da7-8d59-8ffaec730856": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007584932s
    Aug 29 21:05:07.698: INFO: Pod "alpine-nnp-false-160db1b9-346d-4da7-8d59-8ffaec730856": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.012740509s
    Aug 29 21:05:07.698: INFO: Pod "alpine-nnp-false-160db1b9-346d-4da7-8d59-8ffaec730856" satisfied condition "Succeeded or Failed"

    [AfterEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:05:07.713: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "security-context-test-8061" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Security Context when creating containers with AllowPrivilegeEscalation should not allow privilege escalation when false [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":51,"skipped":941,"failed":0}

    
    SSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:05:07.741: 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:630
    STEP: Creating secret with name secret-test-map-02afe147-80aa-4c6e-9254-205bf54a2f0d
    STEP: Creating a pod to test consume secrets
    Aug 29 21:05:07.788: INFO: Waiting up to 5m0s for pod "pod-secrets-c31dcf4f-0ecd-4208-8c71-6e031242b97d" in namespace "secrets-6811" to be "Succeeded or Failed"

    Aug 29 21:05:07.794: INFO: Pod "pod-secrets-c31dcf4f-0ecd-4208-8c71-6e031242b97d": Phase="Pending", Reason="", readiness=false. Elapsed: 5.761388ms
    Aug 29 21:05:09.798: INFO: Pod "pod-secrets-c31dcf4f-0ecd-4208-8c71-6e031242b97d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.009389243s
    STEP: Saw pod success
    Aug 29 21:05:09.798: INFO: Pod "pod-secrets-c31dcf4f-0ecd-4208-8c71-6e031242b97d" satisfied condition "Succeeded or Failed"

    Aug 29 21:05:09.801: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-izhnvy pod pod-secrets-c31dcf4f-0ecd-4208-8c71-6e031242b97d container secret-volume-test: <nil>
    STEP: delete the pod
    Aug 29 21:05:09.817: INFO: Waiting for pod pod-secrets-c31dcf4f-0ecd-4208-8c71-6e031242b97d to disappear
    Aug 29 21:05:09.820: INFO: Pod pod-secrets-c31dcf4f-0ecd-4208-8c71-6e031242b97d no longer exists
    [AfterEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:05:09.820: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-6811" 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":52,"skipped":953,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-node] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:05:09.839: 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:630
    STEP: Creating secret with name secret-test-5e066d43-97fc-4ec9-83b5-5658f7516b79
    STEP: Creating a pod to test consume secrets
    Aug 29 21:05:09.886: INFO: Waiting up to 5m0s for pod "pod-secrets-032a977d-c319-454c-afb2-0e08ff541600" in namespace "secrets-1616" to be "Succeeded or Failed"

    Aug 29 21:05:09.890: INFO: Pod "pod-secrets-032a977d-c319-454c-afb2-0e08ff541600": Phase="Pending", Reason="", readiness=false. Elapsed: 3.235816ms
    Aug 29 21:05:11.893: INFO: Pod "pod-secrets-032a977d-c319-454c-afb2-0e08ff541600": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007076845s
    STEP: Saw pod success
    Aug 29 21:05:11.893: INFO: Pod "pod-secrets-032a977d-c319-454c-afb2-0e08ff541600" satisfied condition "Succeeded or Failed"

    Aug 29 21:05:11.897: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-izhnvy pod pod-secrets-032a977d-c319-454c-afb2-0e08ff541600 container secret-env-test: <nil>
    STEP: delete the pod
    Aug 29 21:05:11.914: INFO: Waiting for pod pod-secrets-032a977d-c319-454c-afb2-0e08ff541600 to disappear
    Aug 29 21:05:11.918: INFO: Pod pod-secrets-032a977d-c319-454c-afb2-0e08ff541600 no longer exists
    [AfterEach] [sig-node] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:05:11.918: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-1616" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Secrets should be consumable from pods in env vars [NodeConformance] [Conformance]","total":-1,"completed":53,"skipped":957,"failed":0}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:05:11.983: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-4498" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] ConfigMap should run through a ConfigMap lifecycle [Conformance]","total":-1,"completed":54,"skipped":962,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:05:12.013: 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] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/security_context.go:46
    [It] should run the container with uid 65534 [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    Aug 29 21:05:12.050: INFO: Waiting up to 5m0s for pod "busybox-user-65534-6054be6e-4912-49b8-b451-869725edcfde" in namespace "security-context-test-6284" to be "Succeeded or Failed"

    Aug 29 21:05:12.054: INFO: Pod "busybox-user-65534-6054be6e-4912-49b8-b451-869725edcfde": Phase="Pending", Reason="", readiness=false. Elapsed: 3.662359ms
    Aug 29 21:05:14.058: INFO: Pod "busybox-user-65534-6054be6e-4912-49b8-b451-869725edcfde": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007251885s
    Aug 29 21:05:14.058: INFO: Pod "busybox-user-65534-6054be6e-4912-49b8-b451-869725edcfde" satisfied condition "Succeeded or Failed"

    [AfterEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:05:14.058: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "security-context-test-6284" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Security Context When creating a container with runAsUser should run the container with uid 65534 [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":55,"skipped":972,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:05:22.211: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "dns-8559" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] DNS should provide DNS for pods for Hostname [LinuxOnly] [Conformance]","total":-1,"completed":56,"skipped":973,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] ReplicaSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:05:32.522: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replicaset-7844" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicaSet should serve a basic image on each replica with a public image  [Conformance]","total":-1,"completed":57,"skipped":990,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-apps] DisruptionController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:05:36.630: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "disruption-7747" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] DisruptionController should observe PodDisruptionBudget status updated [Conformance]","total":-1,"completed":58,"skipped":994,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-node] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:05:36.642: 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 [Slow] [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    Aug 29 21:05:38.683: INFO: Deleting pod "var-expansion-e97f1189-1611-487d-bb49-2cf56ba83667" in namespace "var-expansion-9323"
    Aug 29 21:05:38.690: INFO: Wait up to 5m0s for pod "var-expansion-e97f1189-1611-487d-bb49-2cf56ba83667" to be fully deleted
    [AfterEach] [sig-node] Variable Expansion
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:05:50.697: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-9323" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Variable Expansion should fail substituting values in a volume subpath with absolute path [Slow] [Conformance]","total":-1,"completed":59,"skipped":996,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 36 lines ...
    Aug 29 20:56:15.915: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:15.921: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:15.924: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:15.928: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:15.931: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:15.934: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:15.934: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718 wheezy_udp@dns-test-service.dns-3718.svc wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718 jessie_udp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718.svc jessie_udp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:56:20.938: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:20.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:20.944: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:20.947: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:20.950: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 17 lines ...
    Aug 29 20:56:20.998: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:21.001: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:21.004: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:21.007: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:21.014: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:21.016: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:21.017: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718 wheezy_udp@dns-test-service.dns-3718.svc wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718 jessie_udp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718.svc jessie_udp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:56:25.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:25.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:25.945: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:25.947: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:25.950: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 17 lines ...
    Aug 29 20:56:25.998: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:26.001: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:26.003: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:26.006: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:26.008: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:26.011: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:26.011: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718 wheezy_udp@dns-test-service.dns-3718.svc wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718 jessie_udp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718.svc jessie_udp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:56:30.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:30.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:30.946: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:30.949: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:30.953: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 17 lines ...
    Aug 29 20:56:31.014: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:31.018: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:31.021: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:31.024: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:31.027: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:31.030: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:31.030: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718 wheezy_udp@dns-test-service.dns-3718.svc wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718 jessie_udp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718.svc jessie_udp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:56:35.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:35.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:35.945: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:35.948: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:35.951: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 17 lines ...
    Aug 29 20:56:36.030: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:36.033: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:36.036: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:36.040: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:36.045: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:36.048: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:36.048: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718 wheezy_udp@dns-test-service.dns-3718.svc wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718 jessie_udp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718.svc jessie_udp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:56:40.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:40.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:40.950: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:40.953: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:40.956: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 16 lines ...
    Aug 29 20:56:41.006: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:41.009: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:41.012: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:41.014: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:41.017: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:41.020: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:41.020: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_udp@dns-test-service.dns-3718.svc wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718 jessie_udp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718.svc jessie_udp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:56:45.938: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:45.941: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:45.948: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:45.951: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:45.954: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 15 lines ...
    Aug 29 20:56:46.003: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:46.006: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:46.008: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:46.011: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:46.014: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:46.017: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:46.017: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_udp@dns-test-service.dns-3718.svc wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_udp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718.svc jessie_udp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:56:50.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:50.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:50.948: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:50.951: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:50.954: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 15 lines ...
    Aug 29 20:56:51.012: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:51.016: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:51.019: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:51.023: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:51.027: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:51.030: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:51.030: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_udp@dns-test-service.dns-3718.svc wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_udp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718.svc jessie_udp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:56:55.938: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:55.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:55.948: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:55.951: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:55.955: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 14 lines ...
    Aug 29 20:56:56.020: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:56.023: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:56.027: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:56.030: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:56.034: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:56.037: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:56:56.037: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_udp@dns-test-service.dns-3718.svc wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_udp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:57:00.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:00.943: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:00.949: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:00.952: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:00.955: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 14 lines ...
    Aug 29 20:57:01.021: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:01.025: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:01.028: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:01.032: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:01.035: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:01.039: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:01.039: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_udp@dns-test-service.dns-3718.svc wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_udp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:57:05.938: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:05.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:05.948: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:05.952: INFO: Unable to read wheezy_udp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:05.954: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 14 lines ...
    Aug 29 20:57:05.996: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:05.999: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:06.002: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:06.005: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:06.008: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:06.010: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:06.010: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_udp@dns-test-service.dns-3718.svc wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_udp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:57:10.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:10.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:10.948: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:10.955: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:10.958: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 13 lines ...
    Aug 29 20:57:11.005: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:11.007: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:11.010: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:11.014: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:11.018: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:11.021: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:11.022: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_udp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:57:15.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:15.943: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:15.949: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:15.956: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:15.959: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 12 lines ...
    Aug 29 20:57:16.020: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:16.023: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:16.027: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:16.030: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:16.032: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:16.036: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:16.036: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:57:20.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:20.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:20.949: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:20.956: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:20.959: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 12 lines ...
    Aug 29 20:57:21.015: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:21.022: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:21.026: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:21.029: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:21.032: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:21.034: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:21.034: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_udp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:57:25.938: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:25.941: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:25.947: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:25.953: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:25.956: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 11 lines ...
    Aug 29 20:57:25.995: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:26.000: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:26.004: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:26.006: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:26.009: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:26.016: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:26.016: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:57:30.938: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:30.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:30.948: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:30.954: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:30.956: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 11 lines ...
    Aug 29 20:57:31.000: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:31.006: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:31.011: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:31.016: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:31.019: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:31.024: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:31.024: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:57:35.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:35.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:35.947: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:35.952: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:35.955: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 11 lines ...
    Aug 29 20:57:36.019: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:36.030: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:36.035: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:36.043: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:36.047: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:36.052: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:36.052: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:57:40.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:40.943: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:40.950: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:40.956: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:40.962: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 10 lines ...
    Aug 29 20:57:41.036: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:41.043: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:41.046: INFO: Unable to read jessie_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:41.049: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:41.052: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:41.056: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:41.056: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:57:45.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:45.943: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:45.951: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:45.958: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:45.966: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 9 lines ...
    Aug 29 20:57:46.021: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:46.029: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:46.037: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:46.045: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:46.048: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:46.052: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:46.053: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:57:50.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:50.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:50.949: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:50.956: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:50.962: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 9 lines ...
    Aug 29 20:57:51.001: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:51.007: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:51.013: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:51.020: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:51.023: INFO: Unable to read 10.137.176.252_udp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:51.026: INFO: Unable to read 10.137.176.252_tcp@PTR from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:51.026: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc jessie_tcp@PodARecord 10.137.176.252_udp@PTR 10.137.176.252_tcp@PTR]

    
    Aug 29 20:57:55.938: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:55.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:55.950: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:55.956: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:55.961: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
... skipping 2 lines ...
    Aug 29 20:57:55.970: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:55.973: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:55.990: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:55.996: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:56.002: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:56.008: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:57:56.020: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3718.svc wheezy_udp@_http._tcp.test-service-2.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:58:00.938: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:00.941: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:00.947: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:00.952: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:00.963: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:00.966: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:00.969: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:00.992: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:00.999: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:01.005: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:01.012: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:01.027: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:58:05.941: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:05.946: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:05.953: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:05.959: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:05.972: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:05.975: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:05.978: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:05.997: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:06.005: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:06.011: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:06.019: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:06.031: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:58:10.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:10.943: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:10.950: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:10.956: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:10.969: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:10.972: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:10.976: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:10.999: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:11.005: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:11.012: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:11.018: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:11.031: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:58:15.938: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:15.941: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:15.948: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:15.954: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:15.965: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:15.968: INFO: Unable to read wheezy_udp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:15.971: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:15.991: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:15.997: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:16.006: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:16.015: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:16.027: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_tcp@_http._tcp.test-service-2.dns-3718.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:58:20.939: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:20.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:20.949: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:20.956: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:20.975: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:20.994: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:20.999: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:21.005: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:21.011: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:21.023: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:58:25.938: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:25.942: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:25.948: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:25.954: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:25.974: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:25.991: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:25.996: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:26.002: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:26.008: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:26.020: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:58:30.948: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:30.953: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:30.985: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:30.991: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:30.996: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:31.001: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:31.013: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:58:35.949: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:35.955: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:35.990: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:35.996: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:36.004: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:36.012: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:36.027: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718 wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:58:40.958: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:40.994: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:41.000: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:41.006: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:41.012: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:41.022: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:58:45.961: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:46.002: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:46.009: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:46.016: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:46.022: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:46.043: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:58:50.955: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:50.997: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:51.003: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:51.012: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:51.020: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:51.034: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:58:55.954: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:55.987: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:55.994: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:56.001: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:56.007: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:58:56.019: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:59:00.952: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:00.982: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:00.987: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:00.992: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:00.998: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:01.007: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:59:05.961: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:06.004: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:06.011: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:06.018: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:06.025: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:06.038: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:59:10.956: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:10.996: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:11.002: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:11.009: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:11.015: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:11.029: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:59:15.953: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:15.990: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:15.997: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:16.004: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:16.012: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:16.023: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:59:20.953: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:20.987: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:20.993: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:20.999: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:21.007: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:21.017: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:59:25.955: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:25.994: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:26.001: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:26.007: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:26.014: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:26.025: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:59:30.959: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:31.000: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:31.007: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:31.013: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:31.021: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:31.036: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:59:35.951: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:35.983: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:35.988: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:35.993: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:35.999: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:36.011: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:59:40.957: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:41.000: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:41.008: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:41.017: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:41.024: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:41.037: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:59:45.953: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:45.985: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:45.990: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:45.996: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:46.002: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:46.014: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:59:50.957: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:51.010: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:51.018: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:51.026: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:51.033: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:51.050: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 20:59:55.953: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:55.988: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:55.994: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:56.000: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:56.007: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 20:59:56.022: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:00:00.957: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:00.998: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:01.005: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:01.011: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:01.017: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:01.028: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:00:05.960: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:05.998: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:06.004: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:06.011: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:06.017: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:06.030: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:00:10.953: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:10.988: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:10.993: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:11.000: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:11.005: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:11.017: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:00:15.961: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:16.001: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:16.006: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:16.013: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:16.019: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:16.033: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:00:20.955: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:20.988: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:20.992: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:20.997: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:21.003: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:21.015: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:00:25.955: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:26.001: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:26.008: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:26.015: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:26.021: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:26.033: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:00:30.969: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:31.033: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:31.044: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:31.053: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:31.064: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:31.085: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:00:35.972: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:36.054: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:36.065: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:36.078: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:36.088: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:36.111: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:00:40.974: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:41.069: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:41.085: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:41.098: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:41.110: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:41.134: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:00:45.973: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:46.040: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:46.052: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:46.063: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:46.072: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:46.091: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:00:50.966: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:51.028: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:51.038: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:51.048: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:51.058: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:51.090: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:00:55.978: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:56.049: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:56.061: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:56.072: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:56.086: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:00:56.107: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:01:00.977: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:01.059: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:01.068: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:01.078: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:01.088: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:01.108: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:01:05.969: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:06.034: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:06.045: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:06.057: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:06.071: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:06.091: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:01:10.969: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:11.053: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:11.064: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:11.074: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:11.084: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:11.108: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:01:15.973: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:16.065: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:16.077: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:16.089: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:16.101: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:16.134: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:01:20.972: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:21.055: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:21.068: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:21.080: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:21.095: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:21.118: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:01:25.971: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:26.036: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:26.046: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:26.058: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:26.070: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:26.092: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:01:30.978: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:31.058: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:31.070: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:31.080: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:31.096: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:31.129: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:01:35.981: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:36.060: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:36.071: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:36.085: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:36.097: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:36.120: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:01:40.971: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:41.052: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:41.064: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:41.076: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:41.092: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:41.120: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:01:45.970: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:46.037: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:46.048: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:46.059: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:46.071: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:46.098: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:01:50.966: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:51.032: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:51.041: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:51.050: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:51.062: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:51.086: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:01:55.969: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:56.037: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:56.047: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:56.058: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:56.066: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:01:56.084: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:02:00.982: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:01.078: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:01.092: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:01.106: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:01.122: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:01.151: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:02:05.974: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:06.039: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:06.048: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:06.058: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:06.068: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:06.093: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:02:10.970: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:11.026: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:11.037: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:11.047: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:11.056: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:11.077: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:02:15.969: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:16.037: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:16.048: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:16.062: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:16.071: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:16.093: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:02:21.031: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:21.151: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:21.170: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:21.188: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:21.203: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:21.234: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:02:25.997: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:26.155: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:26.169: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:26.181: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:26.194: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:26.226: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:02:30.968: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:31.037: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:31.048: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:31.058: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:31.068: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:31.089: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:02:35.967: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:36.036: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:36.047: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:36.058: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:36.070: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:36.095: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.test-service-2.dns-3718.svc]

    
    Aug 29 21:02:40.979: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:41.053: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:41.063: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:41.076: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:41.116: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:02:45.972: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:46.056: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:46.068: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:46.079: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:46.110: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:02:50.971: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:51.038: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:51.048: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:51.059: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:51.093: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:02:55.972: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:56.055: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:56.071: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:56.082: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:02:56.123: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:03:00.979: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:01.087: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:01.105: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:01.117: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:01.150: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:03:05.979: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:06.062: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:06.078: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:06.092: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:06.129: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:03:10.976: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:11.037: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:11.047: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:11.056: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:11.085: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:03:15.967: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:16.024: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:16.031: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:16.040: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:16.065: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:03:20.958: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:21.007: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:21.014: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:21.023: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:21.044: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:03:25.957: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:26.001: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:26.012: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:26.019: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:26.044: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:03:30.959: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:31.000: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:31.008: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:31.015: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:31.036: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [wheezy_tcp@dns-test-service.dns-3718.svc jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:03:35.993: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:35.999: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:36.005: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:36.024: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:03:41.005: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:41.013: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:41.020: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:41.042: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:03:46.003: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:46.009: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:46.016: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:46.038: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@dns-test-service.dns-3718.svc jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:03:51.006: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:51.022: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:51.043: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:03:56.000: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:56.014: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:03:56.035: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:04:00.993: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:01.005: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:01.026: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:04:06.005: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:06.018: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:06.038: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:04:10.995: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:11.012: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:11.034: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:04:15.993: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:16.008: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:16.031: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:04:21.005: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:21.018: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:21.038: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:04:25.996: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:26.010: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:26.029: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:04:31.002: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:31.016: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:31.038: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:04:35.996: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:36.010: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:36.029: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:04:40.994: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:41.010: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:41.029: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:04:45.989: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:45.999: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:46.015: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:04:50.990: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:51.004: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:51.027: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:04:55.991: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:56.004: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:04:56.024: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:05:01.020: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:01.036: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:01.057: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:05:06.008: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:06.022: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:06.046: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:05:10.994: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:11.006: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:11.027: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:05:16.004: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:16.018: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:16.037: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:05:20.989: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:21.000: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:21.015: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:05:25.988: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:26.000: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:26.018: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:05:30.990: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:31.001: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:31.021: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:05:35.995: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:36.008: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:36.027: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:05:40.992: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:41.006: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:41.027: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718 jessie_tcp@_http._tcp.dns-test-service.dns-3718.svc]

    
    Aug 29 21:05:46.006: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:46.044: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718]

    
    Aug 29 21:05:50.994: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:51.025: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718]

    
    Aug 29 21:05:55.997: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:05:56.028: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718]

    
    Aug 29 21:06:01.008: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:06:01.048: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718]

    
    Aug 29 21:06:06.006: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:06:06.040: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718]

    
    Aug 29 21:06:10.992: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:06:11.021: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718]

    
    Aug 29 21:06:15.996: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:06:16.026: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718]

    
    Aug 29 21:06:16.083: INFO: Unable to read jessie_tcp@dns-test-service.dns-3718 from pod dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45: the server could not find the requested resource (get pods dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45)
    Aug 29 21:06:16.239: INFO: Lookups using dns-3718/dns-test-acaae798-44d2-4f3a-a8ee-febee3d16b45 failed for: [jessie_tcp@dns-test-service.dns-3718]

    
    Aug 29 21:06:16.239: FAIL: Unexpected error:

        <*errors.errorString | 0xc0002b4280>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 26 lines ...
    • Failure [608.728 seconds]
    [sig-network] DNS
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/common/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:630
    
      Aug 29 21:06:16.239: Unexpected error:

          <*errors.errorString | 0xc0002b4280>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
... skipping 32 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:06:50.794: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "watch-2585" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Watchers should observe add, update, and delete watch notifications on configmaps [Conformance]","total":-1,"completed":60,"skipped":1000,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:06:57.336: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-7456" 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":61,"skipped":1004,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:06:59.113: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-974" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should run through the lifecycle of Pods and PodStatus [Conformance]","total":-1,"completed":62,"skipped":1055,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Networking
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 38 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:07:17.617: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pod-network-test-74" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Networking Granular Checks: Pods should function for node-pod communication: udp [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":63,"skipped":1061,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:07:19.800: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-9152" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should support remote command execution over websockets [NodeConformance] [Conformance]","total":-1,"completed":64,"skipped":1089,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-auth] Certificates API [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:07:20.668: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "certificates-5102" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-auth] Certificates API [Privileged:ClusterAdmin] should support CSR API operations [Conformance]","total":-1,"completed":65,"skipped":1098,"failed":0}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:07:27.317: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-7621" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD without validation schema [Conformance]","total":-1,"completed":66,"skipped":1102,"failed":0}

    [BeforeEach] [sig-node] Kubelet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:07:27.337: 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 7 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:07:29.412: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubelet-test-5205" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Kubelet when scheduling a read only busybox container should not write to root filesystem [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":67,"skipped":1102,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 43 lines ...
    STEP: Destroying namespace "services-4656" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:750
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should complete a service status lifecycle [Conformance]","total":-1,"completed":68,"skipped":1133,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:07:29.679: 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:630
    STEP: Creating configMap configmap-5959/configmap-test-232f42f9-64ed-4540-a62e-64ddca553999
    STEP: Creating a pod to test consume configMaps
    Aug 29 21:07:29.782: INFO: Waiting up to 5m0s for pod "pod-configmaps-7995c368-2e36-45e0-9356-e7f3d1bec6ed" in namespace "configmap-5959" to be "Succeeded or Failed"

    Aug 29 21:07:29.786: INFO: Pod "pod-configmaps-7995c368-2e36-45e0-9356-e7f3d1bec6ed": Phase="Pending", Reason="", readiness=false. Elapsed: 4.524236ms
    Aug 29 21:07:31.791: INFO: Pod "pod-configmaps-7995c368-2e36-45e0-9356-e7f3d1bec6ed": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.009514362s
    STEP: Saw pod success
    Aug 29 21:07:31.791: INFO: Pod "pod-configmaps-7995c368-2e36-45e0-9356-e7f3d1bec6ed" satisfied condition "Succeeded or Failed"

    Aug 29 21:07:31.794: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-izhnvy pod pod-configmaps-7995c368-2e36-45e0-9356-e7f3d1bec6ed container env-test: <nil>
    STEP: delete the pod
    Aug 29 21:07:31.817: INFO: Waiting for pod pod-configmaps-7995c368-2e36-45e0-9356-e7f3d1bec6ed to disappear
    Aug 29 21:07:31.820: INFO: Pod pod-configmaps-7995c368-2e36-45e0-9356-e7f3d1bec6ed no longer exists
    [AfterEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:07:31.820: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-5959" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] ConfigMap should be consumable via environment variable [NodeConformance] [Conformance]","total":-1,"completed":69,"skipped":1153,"failed":0}

    
    SSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] DisruptionController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:07:37.931: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "disruption-1535" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] DisruptionController should create a PodDisruptionBudget [Conformance]","total":-1,"completed":70,"skipped":1163,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:08:06.083: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-5572" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a configMap. [Conformance]","total":-1,"completed":71,"skipped":1204,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-apps] ReplicationController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:08:16.156: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-6908" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","total":-1,"completed":72,"skipped":1206,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-node] RuntimeClass
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:08:16.278: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "runtimeclass-3743" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] RuntimeClass  should support RuntimeClasses API operations [Conformance]","total":-1,"completed":73,"skipped":1207,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-auth] ServiceAccounts
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:08:16.315: 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:630
    STEP: Creating a pod to test service account token: 
    Aug 29 21:08:16.353: INFO: Waiting up to 5m0s for pod "test-pod-8377b00a-f0c9-46ba-91e3-bc3ab17c0920" in namespace "svcaccounts-7698" to be "Succeeded or Failed"

    Aug 29 21:08:16.356: INFO: Pod "test-pod-8377b00a-f0c9-46ba-91e3-bc3ab17c0920": Phase="Pending", Reason="", readiness=false. Elapsed: 2.877981ms
    Aug 29 21:08:18.360: INFO: Pod "test-pod-8377b00a-f0c9-46ba-91e3-bc3ab17c0920": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007210246s
    STEP: Saw pod success
    Aug 29 21:08:18.360: INFO: Pod "test-pod-8377b00a-f0c9-46ba-91e3-bc3ab17c0920" satisfied condition "Succeeded or Failed"

    Aug 29 21:08:18.363: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod test-pod-8377b00a-f0c9-46ba-91e3-bc3ab17c0920 container agnhost-container: <nil>
    STEP: delete the pod
    Aug 29 21:08:18.380: INFO: Waiting for pod test-pod-8377b00a-f0c9-46ba-91e3-bc3ab17c0920 to disappear
    Aug 29 21:08:18.383: INFO: Pod test-pod-8377b00a-f0c9-46ba-91e3-bc3ab17c0920 no longer exists
    [AfterEach] [sig-auth] ServiceAccounts
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:08:18.383: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "svcaccounts-7698" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-auth] ServiceAccounts should mount projected service account token [Conformance]","total":-1,"completed":74,"skipped":1224,"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:185
    STEP: Creating a kubernetes client
    Aug 29 21:08:18.408: 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:630
    STEP: Creating a pod to test emptydir volume type on node default medium
    Aug 29 21:08:18.444: INFO: Waiting up to 5m0s for pod "pod-b0ded30e-bd32-4a74-992f-46c2866f6b56" in namespace "emptydir-726" to be "Succeeded or Failed"

    Aug 29 21:08:18.447: INFO: Pod "pod-b0ded30e-bd32-4a74-992f-46c2866f6b56": Phase="Pending", Reason="", readiness=false. Elapsed: 3.294211ms
    Aug 29 21:08:20.451: INFO: Pod "pod-b0ded30e-bd32-4a74-992f-46c2866f6b56": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007256907s
    STEP: Saw pod success
    Aug 29 21:08:20.451: INFO: Pod "pod-b0ded30e-bd32-4a74-992f-46c2866f6b56" satisfied condition "Succeeded or Failed"

    Aug 29 21:08:20.454: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-izhnvy pod pod-b0ded30e-bd32-4a74-992f-46c2866f6b56 container test-container: <nil>
    STEP: delete the pod
    Aug 29 21:08:20.473: INFO: Waiting for pod pod-b0ded30e-bd32-4a74-992f-46c2866f6b56 to disappear
    Aug 29 21:08:20.476: INFO: Pod pod-b0ded30e-bd32-4a74-992f-46c2866f6b56 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:186
    Aug 29 21:08:20.476: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-726" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes volume on default medium should have the correct mode [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":75,"skipped":1234,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 25 lines ...
    STEP: Destroying namespace "webhook-9902-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:102
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should not be able to mutate or prevent deletion of webhook configuration objects [Conformance]","total":-1,"completed":76,"skipped":1262,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:08:24.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 (root,0777,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test emptydir 0777 on tmpfs
    Aug 29 21:08:24.270: INFO: Waiting up to 5m0s for pod "pod-9373a792-d4b0-4a3f-aa4b-8a7dd185de89" in namespace "emptydir-5893" to be "Succeeded or Failed"

    Aug 29 21:08:24.273: INFO: Pod "pod-9373a792-d4b0-4a3f-aa4b-8a7dd185de89": Phase="Pending", Reason="", readiness=false. Elapsed: 3.430485ms
    Aug 29 21:08:26.278: INFO: Pod "pod-9373a792-d4b0-4a3f-aa4b-8a7dd185de89": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007614175s
    STEP: Saw pod success
    Aug 29 21:08:26.278: INFO: Pod "pod-9373a792-d4b0-4a3f-aa4b-8a7dd185de89" satisfied condition "Succeeded or Failed"

    Aug 29 21:08:26.280: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-9373a792-d4b0-4a3f-aa4b-8a7dd185de89 container test-container: <nil>
    STEP: delete the pod
    Aug 29 21:08:26.294: INFO: Waiting for pod pod-9373a792-d4b0-4a3f-aa4b-8a7dd185de89 to disappear
    Aug 29 21:08:26.296: INFO: Pod pod-9373a792-d4b0-4a3f-aa4b-8a7dd185de89 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:186
    Aug 29 21:08:26.296: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-5893" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0777,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":77,"skipped":1285,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:08:39.932: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-4883" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl server-side dry-run should check if kubectl can dry-run update Pods [Conformance]","total":-1,"completed":78,"skipped":1291,"failed":0}

    [BeforeEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:08:39.941: 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] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/security_context.go:46
    [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:630
    Aug 29 21:08:39.977: INFO: Waiting up to 5m0s for pod "busybox-readonly-false-d747f33f-375e-4bd3-8832-31bfa2eba67b" in namespace "security-context-test-9715" to be "Succeeded or Failed"

    Aug 29 21:08:39.982: INFO: Pod "busybox-readonly-false-d747f33f-375e-4bd3-8832-31bfa2eba67b": Phase="Pending", Reason="", readiness=false. Elapsed: 5.138274ms
    Aug 29 21:08:41.987: INFO: Pod "busybox-readonly-false-d747f33f-375e-4bd3-8832-31bfa2eba67b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.009459721s
    Aug 29 21:08:41.987: INFO: Pod "busybox-readonly-false-d747f33f-375e-4bd3-8832-31bfa2eba67b" satisfied condition "Succeeded or Failed"

    [AfterEach] [sig-node] Security Context
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:08:41.987: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "security-context-test-9715" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Security Context When creating a pod with readOnlyRootFilesystem should run the container with writable rootfs when readOnlyRootFilesystem=false [NodeConformance] [Conformance]","total":-1,"completed":79,"skipped":1291,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:08:42.006: 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:630
    STEP: Creating a pod to test emptydir 0666 on tmpfs
    Aug 29 21:08:42.040: INFO: Waiting up to 5m0s for pod "pod-c865fee4-fb02-4d7a-be2c-409211c44727" in namespace "emptydir-4876" to be "Succeeded or Failed"

    Aug 29 21:08:42.043: INFO: Pod "pod-c865fee4-fb02-4d7a-be2c-409211c44727": Phase="Pending", Reason="", readiness=false. Elapsed: 2.705894ms
    Aug 29 21:08:44.047: INFO: Pod "pod-c865fee4-fb02-4d7a-be2c-409211c44727": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006938819s
    STEP: Saw pod success
    Aug 29 21:08:44.047: INFO: Pod "pod-c865fee4-fb02-4d7a-be2c-409211c44727" satisfied condition "Succeeded or Failed"

    Aug 29 21:08:44.050: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-c865fee4-fb02-4d7a-be2c-409211c44727 container test-container: <nil>
    STEP: delete the pod
    Aug 29 21:08:44.062: INFO: Waiting for pod pod-c865fee4-fb02-4d7a-be2c-409211c44727 to disappear
    Aug 29 21:08:44.067: INFO: Pod pod-c865fee4-fb02-4d7a-be2c-409211c44727 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:186
    Aug 29 21:08:44.067: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-4876" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0666,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":80,"skipped":1297,"failed":0}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Container Lifecycle Hook
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:08:58.205: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-lifecycle-hook-9753" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart exec hook properly [NodeConformance] [Conformance]","total":-1,"completed":81,"skipped":1313,"failed":0}

    
    SSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:08:58.234: 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:630
    STEP: Creating configMap with name configmap-test-volume-a2a7e5b6-bc44-4771-81dd-ec5154320256
    STEP: Creating a pod to test consume configMaps
    Aug 29 21:08:58.276: INFO: Waiting up to 5m0s for pod "pod-configmaps-1377faec-ad18-4129-a08b-0d1cc1afb7a5" in namespace "configmap-1221" to be "Succeeded or Failed"

    Aug 29 21:08:58.280: INFO: Pod "pod-configmaps-1377faec-ad18-4129-a08b-0d1cc1afb7a5": Phase="Pending", Reason="", readiness=false. Elapsed: 3.275076ms
    Aug 29 21:09:00.284: INFO: Pod "pod-configmaps-1377faec-ad18-4129-a08b-0d1cc1afb7a5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007643727s
    STEP: Saw pod success
    Aug 29 21:09:00.284: INFO: Pod "pod-configmaps-1377faec-ad18-4129-a08b-0d1cc1afb7a5" satisfied condition "Succeeded or Failed"

    Aug 29 21:09:00.287: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod pod-configmaps-1377faec-ad18-4129-a08b-0d1cc1afb7a5 container agnhost-container: <nil>
    STEP: delete the pod
    Aug 29 21:09:00.309: INFO: Waiting for pod pod-configmaps-1377faec-ad18-4129-a08b-0d1cc1afb7a5 to disappear
    Aug 29 21:09:00.312: INFO: Pod pod-configmaps-1377faec-ad18-4129-a08b-0d1cc1afb7a5 no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:09:00.312: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-1221" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume as non-root [NodeConformance] [Conformance]","total":-1,"completed":82,"skipped":1326,"failed":0}

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

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-apps] ReplicaSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:09:13.178: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replicaset-8731" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicaSet Replicaset should have a working scale subresource [Conformance]","total":-1,"completed":84,"skipped":1334,"failed":0}

    
    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:185
    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:186
    Aug 29 21:09:39.390: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-171" 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":85,"skipped":1356,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Container Lifecycle Hook
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:09:49.530: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-lifecycle-hook-566" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop http hook properly [NodeConformance] [Conformance]","total":-1,"completed":86,"skipped":1379,"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:185
    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:186
    Aug 29 21:09:51.680: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-5532" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes pod should support shared volumes between containers [Conformance]","total":-1,"completed":87,"skipped":1391,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected combined
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:630
    STEP: Creating configMap with name configmap-projected-all-test-volume-252ece36-1099-4565-8fda-76e69cab4338
    STEP: Creating secret with name secret-projected-all-test-volume-76b7289b-57b0-494c-9226-2dde77de15a0
    STEP: Creating a pod to test Check all projections for projected volume plugin
    Aug 29 21:09:51.749: INFO: Waiting up to 5m0s for pod "projected-volume-dc601e3c-80c2-4d98-b2a1-fa314d58f767" in namespace "projected-284" to be "Succeeded or Failed"

    Aug 29 21:09:51.751: INFO: Pod "projected-volume-dc601e3c-80c2-4d98-b2a1-fa314d58f767": Phase="Pending", Reason="", readiness=false. Elapsed: 2.325596ms
    Aug 29 21:09:53.757: INFO: Pod "projected-volume-dc601e3c-80c2-4d98-b2a1-fa314d58f767": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007880423s
    STEP: Saw pod success
    Aug 29 21:09:53.757: INFO: Pod "projected-volume-dc601e3c-80c2-4d98-b2a1-fa314d58f767" satisfied condition "Succeeded or Failed"

    Aug 29 21:09:53.760: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod projected-volume-dc601e3c-80c2-4d98-b2a1-fa314d58f767 container projected-all-volume-test: <nil>
    STEP: delete the pod
    Aug 29 21:09:53.780: INFO: Waiting for pod projected-volume-dc601e3c-80c2-4d98-b2a1-fa314d58f767 to disappear
    Aug 29 21:09:53.783: INFO: Pod projected-volume-dc601e3c-80c2-4d98-b2a1-fa314d58f767 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:186
    Aug 29 21:09:53.783: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-284" 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":88,"skipped":1397,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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/storage/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:630
    STEP: Creating a pod to test downward API volume plugin
    Aug 29 21:09:53.869: INFO: Waiting up to 5m0s for pod "downwardapi-volume-86f421e5-6a0c-4eb9-826a-2e34effe5f0a" in namespace "projected-1605" to be "Succeeded or Failed"

    Aug 29 21:09:53.872: INFO: Pod "downwardapi-volume-86f421e5-6a0c-4eb9-826a-2e34effe5f0a": Phase="Pending", Reason="", readiness=false. Elapsed: 3.009555ms
    Aug 29 21:09:55.877: INFO: Pod "downwardapi-volume-86f421e5-6a0c-4eb9-826a-2e34effe5f0a": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007829974s
    STEP: Saw pod success
    Aug 29 21:09:55.877: INFO: Pod "downwardapi-volume-86f421e5-6a0c-4eb9-826a-2e34effe5f0a" satisfied condition "Succeeded or Failed"

    Aug 29 21:09:55.881: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod downwardapi-volume-86f421e5-6a0c-4eb9-826a-2e34effe5f0a container client-container: <nil>
    STEP: delete the pod
    Aug 29 21:09:55.896: INFO: Waiting for pod downwardapi-volume-86f421e5-6a0c-4eb9-826a-2e34effe5f0a to disappear
    Aug 29 21:09:55.899: INFO: Pod downwardapi-volume-86f421e5-6a0c-4eb9-826a-2e34effe5f0a 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:186
    Aug 29 21:09:55.899: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-1605" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should set mode on item file [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":89,"skipped":1403,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] Deployment
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:09:58.079: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-4150" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment RecreateDeployment should delete old pods and create new ones [Conformance]","total":-1,"completed":90,"skipped":1441,"failed":0}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-auth] ServiceAccounts
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:10:01.256: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "svcaccounts-9948" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-auth] ServiceAccounts should mount an API token into pods  [Conformance]","total":-1,"completed":91,"skipped":1455,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:11:23.679: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-217" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":92,"skipped":1475,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:11:23.698: 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:630
    STEP: Creating configMap with name configmap-test-volume-1bf3dc1c-e4c9-43ca-9286-d870dd90b324
    STEP: Creating a pod to test consume configMaps
    Aug 29 21:11:23.742: INFO: Waiting up to 5m0s for pod "pod-configmaps-5c323169-fecd-46c3-a484-6e969e3eee22" in namespace "configmap-6564" to be "Succeeded or Failed"

    Aug 29 21:11:23.746: INFO: Pod "pod-configmaps-5c323169-fecd-46c3-a484-6e969e3eee22": Phase="Pending", Reason="", readiness=false. Elapsed: 3.901028ms
    Aug 29 21:11:25.751: INFO: Pod "pod-configmaps-5c323169-fecd-46c3-a484-6e969e3eee22": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.008721293s
    STEP: Saw pod success
    Aug 29 21:11:25.751: INFO: Pod "pod-configmaps-5c323169-fecd-46c3-a484-6e969e3eee22" satisfied condition "Succeeded or Failed"

    Aug 29 21:11:25.755: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-configmaps-5c323169-fecd-46c3-a484-6e969e3eee22 container agnhost-container: <nil>
    STEP: delete the pod
    Aug 29 21:11:25.781: INFO: Waiting for pod pod-configmaps-5c323169-fecd-46c3-a484-6e969e3eee22 to disappear
    Aug 29 21:11:25.784: INFO: Pod pod-configmaps-5c323169-fecd-46c3-a484-6e969e3eee22 no longer exists
    [AfterEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:11:25.784: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-6564" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with defaultMode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":93,"skipped":1481,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Probing container
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 18 lines ...
    • [SLOW TEST:242.794 seconds]
    [sig-node] Probing container
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/framework.go:23
      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:630
    ------------------------------
    {"msg":"PASSED [sig-node] Probing container should *not* be restarted with a tcp:8080 liveness probe [NodeConformance] [Conformance]","total":-1,"completed":94,"skipped":1512,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 65 lines ...
    STEP: Destroying namespace "services-658" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:750
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should have session affinity timeout work for NodePort service [LinuxOnly] [Conformance]","total":-1,"completed":95,"skipped":1514,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:16:14.345: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-4553" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":96,"skipped":1522,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    {"msg":"FAILED [sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]","total":-1,"completed":27,"skipped":463,"failed":2,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]","[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]"]}

    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:06:16.507: 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 33 lines ...
    Aug 29 21:06:18.727: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:18.731: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:18.735: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:18.738: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:18.742: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:18.747: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:18.747: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_udp@dns-test-service.dns-3900.svc wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_udp@dns-test-service.dns-3900.svc jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:06:23.753: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:23.759: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:23.763: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:23.766: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:23.769: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 17 lines ...
    Aug 29 21:06:23.837: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:23.841: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:23.844: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:23.847: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:23.850: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:23.853: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:23.854: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_udp@dns-test-service.dns-3900.svc wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_udp@dns-test-service.dns-3900.svc jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:06:28.754: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:28.758: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:28.762: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:28.765: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:28.771: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 17 lines ...
    Aug 29 21:06:28.845: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:28.848: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:28.852: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:28.855: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:28.859: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:28.865: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:28.865: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_udp@dns-test-service.dns-3900.svc wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_udp@dns-test-service.dns-3900.svc jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:06:33.752: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:33.758: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:33.761: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:33.765: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:33.768: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 17 lines ...
    Aug 29 21:06:33.828: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:33.831: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:33.834: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:33.838: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:33.840: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:33.843: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:33.843: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_udp@dns-test-service.dns-3900.svc wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_udp@dns-test-service.dns-3900.svc jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:06:38.755: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:38.759: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:38.762: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:38.770: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:38.777: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 17 lines ...
    Aug 29 21:06:38.853: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:38.856: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:38.859: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:38.862: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:38.865: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:38.869: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:38.869: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_udp@dns-test-service.dns-3900.svc wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_udp@dns-test-service.dns-3900.svc jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:06:43.753: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:43.758: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:43.762: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:43.765: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:43.768: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 17 lines ...
    Aug 29 21:06:43.842: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:43.846: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:43.850: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:43.854: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:43.857: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:43.863: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:43.863: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_udp@dns-test-service.dns-3900.svc wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_udp@dns-test-service.dns-3900.svc jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:06:48.753: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:48.757: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:48.760: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:48.764: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:48.767: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 17 lines ...
    Aug 29 21:06:48.839: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:48.845: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:48.850: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:48.854: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:48.857: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:48.860: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:48.860: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_udp@dns-test-service.dns-3900.svc wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_udp@dns-test-service.dns-3900.svc jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:06:53.753: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:53.756: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:53.760: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:53.763: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:53.766: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 17 lines ...
    Aug 29 21:06:53.824: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:53.827: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:53.829: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:53.833: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:53.836: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:53.841: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:53.841: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_udp@dns-test-service.dns-3900.svc wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_udp@dns-test-service.dns-3900.svc jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:06:58.752: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:58.755: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:58.761: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:58.764: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:58.768: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 16 lines ...
    Aug 29 21:06:58.844: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:58.852: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:58.861: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:58.866: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:58.869: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:58.872: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:06:58.872: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_udp@dns-test-service.dns-3900.svc wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:07:03.754: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:03.760: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:03.764: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:03.767: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:03.771: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 16 lines ...
    Aug 29 21:07:03.827: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:03.830: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:03.834: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:03.837: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:03.839: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:03.842: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:03.842: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_udp@dns-test-service.dns-3900.svc wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:07:08.754: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:08.760: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:08.764: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:08.767: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:08.770: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 16 lines ...
    Aug 29 21:07:08.829: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:08.832: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:08.835: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:08.838: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:08.842: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:08.844: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:08.844: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_udp@dns-test-service.dns-3900.svc wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:07:13.752: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:13.755: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:13.759: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:13.762: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:13.764: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 16 lines ...
    Aug 29 21:07:13.817: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:13.820: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:13.825: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:13.828: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:13.830: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:13.833: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:13.833: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_udp@dns-test-service.dns-3900.svc wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:07:18.752: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:18.756: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:18.760: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:18.763: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:18.769: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 15 lines ...
    Aug 29 21:07:18.828: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:18.832: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:18.836: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:18.839: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:18.842: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:18.845: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:18.845: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:07:23.751: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:23.755: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:23.762: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:23.765: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:23.772: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 15 lines ...
    Aug 29 21:07:23.846: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:23.853: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:23.857: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:23.860: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:23.864: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:23.868: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:23.868: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.dns-test-service.dns-3900.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_udp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:07:28.754: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:28.757: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:28.761: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:28.764: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:28.785: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 12 lines ...
    Aug 29 21:07:28.849: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:28.853: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:28.857: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:28.861: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:28.865: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:28.869: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:28.869: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:07:33.751: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:33.755: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:33.762: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:33.765: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:33.780: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 12 lines ...
    Aug 29 21:07:33.838: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:33.842: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:33.845: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:33.849: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:33.853: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:33.857: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:33.857: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:07:38.752: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:38.756: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:38.764: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:38.768: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:38.781: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 12 lines ...
    Aug 29 21:07:38.846: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:38.849: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:38.852: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:38.855: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:38.859: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:38.862: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:38.862: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:07:43.752: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:43.755: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:43.758: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:43.761: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:43.773: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 12 lines ...
    Aug 29 21:07:43.827: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:43.830: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:43.833: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:43.837: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:43.841: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:43.844: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:43.844: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@_http._tcp.dns-test-service.dns-3900.svc wheezy_udp@_http._tcp.test-service-2.dns-3900.svc wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_udp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:07:48.753: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:48.757: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:48.760: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:48.764: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:48.784: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 9 lines ...
    Aug 29 21:07:48.842: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:48.849: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:48.853: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:48.857: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:48.860: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:48.864: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:48.864: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:07:53.752: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:53.755: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:53.762: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:53.765: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:53.793: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 9 lines ...
    Aug 29 21:07:53.857: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:53.864: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:53.868: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:53.872: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:53.876: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:53.880: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:53.880: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@_http._tcp.test-service-2.dns-3900.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:07:58.752: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:58.757: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:58.761: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:58.765: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:58.798: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 7 lines ...
    Aug 29 21:07:58.843: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:58.853: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:58.858: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:58.862: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:58.866: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:58.870: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:07:58.870: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:08:03.753: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:03.757: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:03.761: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:03.764: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:03.789: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 7 lines ...
    Aug 29 21:08:03.819: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:03.828: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:03.835: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:03.839: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:03.843: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:03.846: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:03.846: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:08:08.761: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:08.767: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:08.772: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:08.776: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:08.812: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 7 lines ...
    Aug 29 21:08:08.848: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:08.854: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:08.857: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:08.860: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:08.863: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:08.866: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:08.866: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:08:13.751: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:13.754: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:13.760: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:13.763: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:13.790: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 7 lines ...
    Aug 29 21:08:13.823: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:13.829: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:13.832: INFO: Unable to read jessie_udp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:13.835: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:13.838: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:13.842: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:13.842: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:08:18.753: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:18.757: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:18.761: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:18.765: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:18.794: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 6 lines ...
    Aug 29 21:08:18.837: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:18.845: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:18.853: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:18.860: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:18.863: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:18.867: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:18.867: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:08:23.753: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:23.758: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:23.762: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:23.766: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:23.794: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
... skipping 6 lines ...
    Aug 29 21:08:23.824: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:23.832: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:23.838: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:23.845: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:23.849: INFO: Unable to read 10.132.187.111_udp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:23.852: INFO: Unable to read 10.132.187.111_tcp@PTR from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:23.852: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc jessie_tcp@PodARecord 10.132.187.111_udp@PTR 10.132.187.111_tcp@PTR]

    
    Aug 29 21:08:28.754: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:28.757: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:28.760: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:28.763: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:28.791: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:28.803: INFO: Unable to read jessie_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:28.806: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:28.810: INFO: Unable to read jessie_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:28.813: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:28.822: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:28.832: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:28.842: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:28.856: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:08:33.751: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:33.755: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:33.759: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:33.763: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:33.789: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:33.809: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:33.816: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:33.828: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:33.834: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:33.846: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:08:38.754: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:38.760: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:38.763: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:38.766: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:38.794: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:38.819: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:38.826: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:38.832: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:38.837: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:38.852: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:08:43.752: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:43.755: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:43.759: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:43.761: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:43.788: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:43.807: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:43.814: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:43.824: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:43.831: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:43.846: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:08:48.751: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:48.755: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:48.758: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:48.763: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:48.788: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:48.814: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:48.820: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:48.827: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:48.834: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:48.846: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:08:53.751: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:53.755: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:53.761: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:53.764: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:53.793: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:53.816: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:53.824: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:53.831: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:53.839: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:53.854: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:08:58.757: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:58.761: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:58.764: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:58.795: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:58.817: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:58.831: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:58.839: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:58.845: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:08:58.858: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:09:03.756: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:03.759: INFO: Unable to read wheezy_udp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:03.762: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:03.787: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:03.809: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:03.819: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:03.825: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:03.833: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:03.845: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3900 wheezy_tcp@dns-test-service.dns-3900 wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:09:08.806: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:08.832: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:08.840: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:08.848: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:08.855: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:08.873: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:09:13.787: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:13.809: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:13.818: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:13.824: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:13.831: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:13.845: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:09:18.820: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:18.861: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:18.881: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:18.896: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:18.908: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:18.924: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:09:23.797: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:23.819: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:23.826: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:23.832: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:23.839: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:23.852: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:09:28.814: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:28.838: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:28.849: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:28.860: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:28.872: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:28.899: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:09:33.795: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:33.817: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:33.825: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:33.831: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:33.839: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:33.854: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:09:38.794: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:38.818: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:38.830: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:38.837: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:38.844: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:38.861: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:09:43.792: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:43.814: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:43.821: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:43.828: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:43.834: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:43.848: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:09:48.795: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:48.829: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:48.836: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:48.843: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:48.851: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:48.866: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:09:53.801: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:53.832: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:53.841: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:53.849: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:53.869: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:53.886: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:09:58.796: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:58.849: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:58.857: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:58.867: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:58.875: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:09:58.891: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:10:03.791: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:03.813: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:03.822: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:03.829: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:03.837: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:03.854: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:10:08.797: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:08.826: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:08.834: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:08.842: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:08.850: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:08.861: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:10:13.791: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:13.822: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:13.830: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:13.837: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:13.845: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:13.862: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:10:18.792: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:18.826: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:18.834: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:18.842: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:18.849: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:18.866: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:10:23.795: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:23.817: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:23.825: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:23.832: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:23.837: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:23.849: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:10:28.785: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:28.808: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:28.815: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:28.824: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:28.831: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:28.844: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:10:33.787: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:33.808: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:33.816: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:33.824: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:33.831: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:33.846: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:10:38.805: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:38.835: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:38.844: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:38.852: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:38.860: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:38.878: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:10:43.789: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:43.810: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:43.818: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:43.826: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:43.833: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:43.850: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:10:48.784: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:48.808: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:48.815: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:48.821: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:48.827: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:48.838: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:10:53.790: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:53.808: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:53.816: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:53.822: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:53.829: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:53.842: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:10:58.802: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:58.830: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:58.837: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:58.844: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:58.852: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:10:58.873: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:11:03.798: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:03.818: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:03.828: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:03.834: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:03.841: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:03.855: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:11:08.797: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:08.828: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:08.835: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:08.845: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:08.852: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:08.867: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:11:13.798: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:13.822: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:13.829: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:13.837: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:13.845: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:13.860: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:11:18.797: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:18.820: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:18.832: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:18.839: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:18.847: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:18.861: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:11:23.810: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:23.846: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:23.856: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:23.865: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:23.875: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:23.893: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:11:28.811: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:28.844: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:28.854: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:28.864: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:28.872: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:28.890: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:11:33.793: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:33.819: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:33.828: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:33.835: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:33.843: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:33.859: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:11:38.789: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:38.815: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:38.823: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:38.830: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:38.837: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:38.856: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:11:43.788: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:43.810: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:43.817: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:43.823: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:43.830: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:43.843: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:11:48.808: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:48.836: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:48.843: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:48.850: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:48.856: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:48.874: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:11:53.790: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:53.808: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:53.816: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:53.824: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:53.830: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:53.842: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:11:58.788: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:58.807: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:58.814: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:58.822: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:58.829: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:11:58.846: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:12:03.795: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:03.812: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:03.818: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:03.825: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:03.830: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:03.842: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:12:08.812: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:08.843: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:08.850: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:08.858: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:08.866: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:08.887: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:12:13.789: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:13.807: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:13.813: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:13.822: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:13.832: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:13.846: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:12:18.790: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:18.818: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:18.825: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:18.832: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:18.839: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:18.851: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:12:23.797: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:23.821: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:23.829: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:23.836: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:23.843: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:23.862: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:12:28.786: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:28.809: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:28.816: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:28.822: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:28.829: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:28.844: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:12:33.789: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:33.812: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:33.819: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:33.825: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:33.832: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:33.845: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:12:38.799: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:38.825: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:38.834: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:38.841: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:38.848: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:38.863: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:12:43.792: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:43.813: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:43.820: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:43.832: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:43.838: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:43.850: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:12:48.794: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:48.819: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:48.826: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:48.832: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:48.838: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:48.854: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:12:53.797: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:53.822: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:53.830: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:53.838: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:53.846: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:53.860: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:12:58.800: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:58.827: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:58.835: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:58.844: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:58.851: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:12:58.870: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:13:03.789: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:03.808: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:03.815: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:03.825: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:03.831: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:03.847: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:13:08.802: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:08.834: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:08.843: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:08.850: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:08.857: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:08.871: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:13:13.791: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:13.811: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:13.819: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:13.827: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:13.833: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:13.845: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:13:18.798: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:18.824: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:18.838: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:18.845: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:18.852: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:18.870: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:13:23.823: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:23.860: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:23.876: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:23.888: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:23.898: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:23.919: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:13:28.824: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:28.857: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:28.868: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:28.880: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:28.893: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:28.918: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:13:33.818: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:33.858: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:33.869: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:33.880: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:33.895: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:33.925: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:13:38.842: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:38.880: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:38.893: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:38.909: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:38.924: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:38.947: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:13:43.825: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:43.864: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:43.876: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:43.889: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:43.904: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:43.930: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:13:48.839: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:48.874: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:48.885: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:48.895: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:48.905: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:48.922: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:13:53.818: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:53.856: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:53.873: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:53.887: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:53.898: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:53.926: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:13:58.843: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:58.882: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:58.895: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:58.907: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:58.922: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:13:58.948: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:14:03.818: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:03.852: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:03.863: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:03.874: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:03.885: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:03.908: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:14:08.857: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:08.894: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:08.908: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:08.923: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:08.936: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:08.963: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:14:13.819: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:13.853: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:13.866: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:13.881: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:13.892: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:13.919: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:14:18.830: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:18.875: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:18.886: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:18.904: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:18.919: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:18.943: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:14:23.819: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:23.863: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:23.879: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:23.891: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:23.906: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:23.929: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:14:28.829: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:28.866: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:28.878: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:28.895: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:28.907: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:28.932: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:14:33.830: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:33.874: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:33.886: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:33.897: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:33.908: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:33.932: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:14:38.834: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:38.873: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:38.884: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:38.896: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:38.908: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:38.937: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:14:43.833: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:43.865: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:43.881: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:43.892: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:43.904: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:43.924: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:14:48.816: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:48.844: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:48.855: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:48.865: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:48.876: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:48.909: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:14:53.820: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:53.865: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:53.876: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:53.895: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:53.907: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:53.932: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:14:58.827: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:58.862: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:58.878: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:58.892: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:58.907: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:14:58.934: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:15:03.825: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:03.868: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:03.877: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:03.889: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:03.904: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:03.930: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:15:08.830: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:08.864: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:08.874: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:08.886: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:08.897: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:08.919: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:15:13.824: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:13.866: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:13.879: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:13.891: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:13.905: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:13.938: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:15:18.841: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:18.883: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:18.895: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:18.906: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:18.921: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:18.947: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:15:23.814: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:23.854: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:23.863: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:23.874: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:23.886: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:23.910: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:15:28.864: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:28.905: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:28.923: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:28.949: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:28.971: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:29.000: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:15:33.851: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:33.896: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:33.908: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:33.920: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:33.936: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:33.956: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:15:38.888: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:38.939: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:38.952: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:38.975: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:38.999: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:39.048: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:15:43.824: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:43.865: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:43.877: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:43.887: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:43.897: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:43.920: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:15:48.835: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:48.877: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:48.889: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:48.899: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:48.909: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:48.930: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:15:53.827: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:53.870: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:53.885: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:53.897: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:53.908: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:53.929: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:15:58.841: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:58.924: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:58.939: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:58.950: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:58.966: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:15:58.991: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:16:03.824: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:03.858: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:03.872: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:03.886: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:03.896: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:03.917: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:16:08.850: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:08.886: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:08.897: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:08.910: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:08.921: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:08.942: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:16:13.825: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:13.864: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:13.880: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:13.893: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:13.904: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:13.928: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:16:18.834: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:18.875: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:18.884: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:18.897: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:18.908: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:18.936: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:16:18.999: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:19.030: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900 from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:19.039: INFO: Unable to read jessie_tcp@dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:19.047: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:19.054: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3900.svc from pod dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25: the server could not find the requested resource (get pods dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25)
    Aug 29 21:16:19.070: INFO: Lookups using dns-3900/dns-test-6be3504e-5c0a-4b09-90f6-2b262ca0da25 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-3900 jessie_tcp@dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.dns-test-service.dns-3900.svc jessie_tcp@_http._tcp.test-service-2.dns-3900.svc]

    
    Aug 29 21:16:19.071: FAIL: Unexpected error:

        <*errors.errorString | 0xc0002b4280>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 26 lines ...
    • Failure [602.805 seconds]
    [sig-network] DNS
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/common/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:630
    
      Aug 29 21:16:19.071: Unexpected error:

          <*errors.errorString | 0xc0002b4280>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
... skipping 35 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:16:30.549: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-lifecycle-hook-7051" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute poststart http hook properly [NodeConformance] [Conformance]","total":-1,"completed":97,"skipped":1546,"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:185
    STEP: Creating a kubernetes client
... skipping 68 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:16:44.059: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-3560" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","total":-1,"completed":98,"skipped":1551,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Container Lifecycle Hook
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 30 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:17:00.167: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-lifecycle-hook-8663" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]","total":-1,"completed":99,"skipped":1560,"failed":0}

    
    SSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:17:00.198: 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,default) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test emptydir 0666 on node default medium
    Aug 29 21:17:00.236: INFO: Waiting up to 5m0s for pod "pod-c8c5ff92-282f-4657-9599-dc0934403898" in namespace "emptydir-1384" to be "Succeeded or Failed"

    Aug 29 21:17:00.240: INFO: Pod "pod-c8c5ff92-282f-4657-9599-dc0934403898": Phase="Pending", Reason="", readiness=false. Elapsed: 3.867726ms
    Aug 29 21:17:02.244: INFO: Pod "pod-c8c5ff92-282f-4657-9599-dc0934403898": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.008308207s
    STEP: Saw pod success
    Aug 29 21:17:02.244: INFO: Pod "pod-c8c5ff92-282f-4657-9599-dc0934403898" satisfied condition "Succeeded or Failed"

    Aug 29 21:17:02.247: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-c8c5ff92-282f-4657-9599-dc0934403898 container test-container: <nil>
    STEP: delete the pod
    Aug 29 21:17:02.259: INFO: Waiting for pod pod-c8c5ff92-282f-4657-9599-dc0934403898 to disappear
    Aug 29 21:17:02.263: INFO: Pod pod-c8c5ff92-282f-4657-9599-dc0934403898 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:186
    Aug 29 21:17:02.263: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-1384" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0666,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":100,"skipped":1573,"failed":0}

    [BeforeEach] [sig-apps] StatefulSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:17:02.273: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename statefulset
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 39 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:18:52.568: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-1109" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform canary updates and phased rolling updates of template modifications [Conformance]","total":-1,"completed":101,"skipped":1573,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:18:52.583: 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:630
    STEP: Creating secret with name secret-test-e1b43037-2f4e-41d4-b541-48b1edfb3220
    STEP: Creating a pod to test consume secrets
    Aug 29 21:18:52.621: INFO: Waiting up to 5m0s for pod "pod-secrets-f947fff1-a2f1-4bc4-a0db-14a2b1f92ea0" in namespace "secrets-357" to be "Succeeded or Failed"

    Aug 29 21:18:52.624: INFO: Pod "pod-secrets-f947fff1-a2f1-4bc4-a0db-14a2b1f92ea0": Phase="Pending", Reason="", readiness=false. Elapsed: 3.004942ms
    Aug 29 21:18:54.629: INFO: Pod "pod-secrets-f947fff1-a2f1-4bc4-a0db-14a2b1f92ea0": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007480419s
    STEP: Saw pod success
    Aug 29 21:18:54.629: INFO: Pod "pod-secrets-f947fff1-a2f1-4bc4-a0db-14a2b1f92ea0" satisfied condition "Succeeded or Failed"

    Aug 29 21:18:54.631: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-secrets-f947fff1-a2f1-4bc4-a0db-14a2b1f92ea0 container secret-volume-test: <nil>
    STEP: delete the pod
    Aug 29 21:18:54.655: INFO: Waiting for pod pod-secrets-f947fff1-a2f1-4bc4-a0db-14a2b1f92ea0 to disappear
    Aug 29 21:18:54.659: INFO: Pod pod-secrets-f947fff1-a2f1-4bc4-a0db-14a2b1f92ea0 no longer exists
    [AfterEach] [sig-storage] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:18:54.659: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-357" 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":102,"skipped":1576,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:630
    STEP: Creating pod pod-subpath-test-configmap-q6ms
    STEP: Creating a pod to test atomic-volume-subpath
    Aug 29 21:18:54.838: INFO: Waiting up to 5m0s for pod "pod-subpath-test-configmap-q6ms" in namespace "subpath-9147" to be "Succeeded or Failed"

    Aug 29 21:18:54.841: INFO: Pod "pod-subpath-test-configmap-q6ms": Phase="Pending", Reason="", readiness=false. Elapsed: 2.954321ms
    Aug 29 21:18:56.846: INFO: Pod "pod-subpath-test-configmap-q6ms": Phase="Running", Reason="", readiness=true. Elapsed: 2.007566222s
    Aug 29 21:18:58.855: INFO: Pod "pod-subpath-test-configmap-q6ms": Phase="Running", Reason="", readiness=true. Elapsed: 4.017244152s
    Aug 29 21:19:00.859: INFO: Pod "pod-subpath-test-configmap-q6ms": Phase="Running", Reason="", readiness=true. Elapsed: 6.021356865s
    Aug 29 21:19:02.865: INFO: Pod "pod-subpath-test-configmap-q6ms": Phase="Running", Reason="", readiness=true. Elapsed: 8.026522261s
    Aug 29 21:19:04.869: INFO: Pod "pod-subpath-test-configmap-q6ms": Phase="Running", Reason="", readiness=true. Elapsed: 10.030993511s
    Aug 29 21:19:06.882: INFO: Pod "pod-subpath-test-configmap-q6ms": Phase="Running", Reason="", readiness=true. Elapsed: 12.043518808s
    Aug 29 21:19:08.886: INFO: Pod "pod-subpath-test-configmap-q6ms": Phase="Running", Reason="", readiness=true. Elapsed: 14.047732077s
    Aug 29 21:19:10.891: INFO: Pod "pod-subpath-test-configmap-q6ms": Phase="Running", Reason="", readiness=true. Elapsed: 16.052413276s
    Aug 29 21:19:12.895: INFO: Pod "pod-subpath-test-configmap-q6ms": Phase="Running", Reason="", readiness=true. Elapsed: 18.057364351s
    Aug 29 21:19:14.900: INFO: Pod "pod-subpath-test-configmap-q6ms": Phase="Running", Reason="", readiness=true. Elapsed: 20.061607083s
    Aug 29 21:19:16.904: INFO: Pod "pod-subpath-test-configmap-q6ms": Phase="Succeeded", Reason="", readiness=false. Elapsed: 22.06595395s
    STEP: Saw pod success
    Aug 29 21:19:16.904: INFO: Pod "pod-subpath-test-configmap-q6ms" satisfied condition "Succeeded or Failed"

    Aug 29 21:19:16.908: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-subpath-test-configmap-q6ms container test-container-subpath-configmap-q6ms: <nil>
    STEP: delete the pod
    Aug 29 21:19:16.927: INFO: Waiting for pod pod-subpath-test-configmap-q6ms to disappear
    Aug 29 21:19:16.930: INFO: Pod pod-subpath-test-configmap-q6ms no longer exists
    STEP: Deleting pod pod-subpath-test-configmap-q6ms
    Aug 29 21:19:16.930: INFO: Deleting pod "pod-subpath-test-configmap-q6ms" in namespace "subpath-9147"
    [AfterEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:19:16.934: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "subpath-9147" 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":103,"skipped":1662,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 16 lines ...
    Aug 29 21:19:19.071: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:19.074: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:19.084: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:19.087: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:19.090: INFO: Unable to read jessie_udp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:19.094: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:19.100: INFO: Lookups using dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local wheezy_udp@dns-test-service-2.dns-9564.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-9564.svc.cluster.local jessie_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local jessie_udp@dns-test-service-2.dns-9564.svc.cluster.local jessie_tcp@dns-test-service-2.dns-9564.svc.cluster.local]

    
    Aug 29 21:19:24.105: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:24.108: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:24.111: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:24.114: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:24.123: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:24.126: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:24.129: INFO: Unable to read jessie_udp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:24.132: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:24.138: INFO: Lookups using dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local wheezy_udp@dns-test-service-2.dns-9564.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-9564.svc.cluster.local jessie_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local jessie_udp@dns-test-service-2.dns-9564.svc.cluster.local jessie_tcp@dns-test-service-2.dns-9564.svc.cluster.local]

    
    Aug 29 21:19:29.105: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:29.109: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:29.112: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:29.116: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:29.126: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:29.129: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:29.133: INFO: Unable to read jessie_udp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:29.136: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:29.143: INFO: Lookups using dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local wheezy_udp@dns-test-service-2.dns-9564.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-9564.svc.cluster.local jessie_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local jessie_udp@dns-test-service-2.dns-9564.svc.cluster.local jessie_tcp@dns-test-service-2.dns-9564.svc.cluster.local]

    
    Aug 29 21:19:34.105: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:34.109: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:34.112: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:34.116: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:34.125: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:34.128: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:34.131: INFO: Unable to read jessie_udp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:34.134: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:34.140: INFO: Lookups using dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local wheezy_udp@dns-test-service-2.dns-9564.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-9564.svc.cluster.local jessie_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local jessie_udp@dns-test-service-2.dns-9564.svc.cluster.local jessie_tcp@dns-test-service-2.dns-9564.svc.cluster.local]

    
    Aug 29 21:19:39.107: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:39.110: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:39.113: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:39.116: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:39.125: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:39.129: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:39.132: INFO: Unable to read jessie_udp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:39.136: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:39.143: INFO: Lookups using dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local wheezy_udp@dns-test-service-2.dns-9564.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-9564.svc.cluster.local jessie_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local jessie_udp@dns-test-service-2.dns-9564.svc.cluster.local jessie_tcp@dns-test-service-2.dns-9564.svc.cluster.local]

    
    Aug 29 21:19:44.107: INFO: Unable to read wheezy_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:44.110: INFO: Unable to read wheezy_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:44.113: INFO: Unable to read wheezy_udp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:44.116: INFO: Unable to read wheezy_tcp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:44.126: INFO: Unable to read jessie_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:44.130: INFO: Unable to read jessie_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:44.133: INFO: Unable to read jessie_udp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:44.136: INFO: Unable to read jessie_tcp@dns-test-service-2.dns-9564.svc.cluster.local from pod dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9: the server could not find the requested resource (get pods dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9)
    Aug 29 21:19:44.142: INFO: Lookups using dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9 failed for: [wheezy_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local wheezy_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local wheezy_udp@dns-test-service-2.dns-9564.svc.cluster.local wheezy_tcp@dns-test-service-2.dns-9564.svc.cluster.local jessie_udp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local jessie_tcp@dns-querier-2.dns-test-service-2.dns-9564.svc.cluster.local jessie_udp@dns-test-service-2.dns-9564.svc.cluster.local jessie_tcp@dns-test-service-2.dns-9564.svc.cluster.local]

    
    Aug 29 21:19:49.139: INFO: DNS probes using dns-9564/dns-test-e195c772-d4e4-4f5f-86eb-1898f8a236d9 succeeded
    
    STEP: deleting the pod
    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:186
    Aug 29 21:19:49.184: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "dns-9564" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] DNS should provide DNS for pods for Subdomain [Conformance]","total":-1,"completed":104,"skipped":1689,"failed":0}

    
    SSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:19:51.280: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-8504" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should support retrieving logs from the container over websockets [NodeConformance] [Conformance]","total":-1,"completed":105,"skipped":1695,"failed":0}

    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:19:51.293: 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:630
    STEP: Creating configMap with name projected-configmap-test-volume-map-3a2ef622-7f11-42c1-8b06-f572d519b453
    STEP: Creating a pod to test consume configMaps
    Aug 29 21:19:51.342: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-49b0be1d-973c-48d0-8f41-73f1b016608f" in namespace "projected-2133" to be "Succeeded or Failed"

    Aug 29 21:19:51.346: INFO: Pod "pod-projected-configmaps-49b0be1d-973c-48d0-8f41-73f1b016608f": Phase="Pending", Reason="", readiness=false. Elapsed: 4.072294ms
    Aug 29 21:19:53.350: INFO: Pod "pod-projected-configmaps-49b0be1d-973c-48d0-8f41-73f1b016608f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.008184266s
    STEP: Saw pod success
    Aug 29 21:19:53.350: INFO: Pod "pod-projected-configmaps-49b0be1d-973c-48d0-8f41-73f1b016608f" satisfied condition "Succeeded or Failed"

    Aug 29 21:19:53.353: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod pod-projected-configmaps-49b0be1d-973c-48d0-8f41-73f1b016608f container agnhost-container: <nil>
    STEP: delete the pod
    Aug 29 21:19:53.380: INFO: Waiting for pod pod-projected-configmaps-49b0be1d-973c-48d0-8f41-73f1b016608f to disappear
    Aug 29 21:19:53.383: INFO: Pod pod-projected-configmaps-49b0be1d-973c-48d0-8f41-73f1b016608f 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:186
    Aug 29 21:19:53.383: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-2133" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap should be consumable from pods in volume with mappings [NodeConformance] [Conformance]","total":-1,"completed":106,"skipped":1695,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] Garbage collector
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 34 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:20:03.606: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "gc-8231" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Garbage collector should delete pods created by rc when not orphaning [Conformance]","total":-1,"completed":107,"skipped":1703,"failed":0}

    
    SSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 24 lines ...
    STEP: Destroying namespace "webhook-6517-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:102
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate custom resource with different stored version [Conformance]","total":-1,"completed":108,"skipped":1715,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:20:21.744: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-6141" 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":109,"skipped":1732,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 16 lines ...
    Aug 29 21:20:23.962: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:23.966: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:23.991: INFO: Unable to read jessie_udp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:23.995: INFO: Unable to read jessie_tcp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:23.998: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:24.001: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:24.023: INFO: Lookups using dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a failed for: [wheezy_udp@dns-test-service.dns-9030.svc.cluster.local wheezy_tcp@dns-test-service.dns-9030.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local jessie_udp@dns-test-service.dns-9030.svc.cluster.local jessie_tcp@dns-test-service.dns-9030.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local]

    
    Aug 29 21:20:29.027: INFO: Unable to read wheezy_udp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:29.030: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:29.034: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:29.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:29.059: INFO: Unable to read jessie_udp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:29.062: INFO: Unable to read jessie_tcp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:29.066: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:29.070: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:29.090: INFO: Lookups using dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a failed for: [wheezy_udp@dns-test-service.dns-9030.svc.cluster.local wheezy_tcp@dns-test-service.dns-9030.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local jessie_udp@dns-test-service.dns-9030.svc.cluster.local jessie_tcp@dns-test-service.dns-9030.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local]

    
    Aug 29 21:20:34.027: INFO: Unable to read wheezy_udp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:34.031: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:34.035: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:34.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:34.061: INFO: Unable to read jessie_udp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:34.067: INFO: Unable to read jessie_tcp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:34.070: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:34.073: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:34.092: INFO: Lookups using dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a failed for: [wheezy_udp@dns-test-service.dns-9030.svc.cluster.local wheezy_tcp@dns-test-service.dns-9030.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local jessie_udp@dns-test-service.dns-9030.svc.cluster.local jessie_tcp@dns-test-service.dns-9030.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local]

    
    Aug 29 21:20:39.028: INFO: Unable to read wheezy_udp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:39.032: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:39.036: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:39.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:39.066: INFO: Unable to read jessie_udp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:39.069: INFO: Unable to read jessie_tcp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:39.073: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:39.077: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:39.098: INFO: Lookups using dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a failed for: [wheezy_udp@dns-test-service.dns-9030.svc.cluster.local wheezy_tcp@dns-test-service.dns-9030.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local jessie_udp@dns-test-service.dns-9030.svc.cluster.local jessie_tcp@dns-test-service.dns-9030.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local]

    
    Aug 29 21:20:44.028: INFO: Unable to read wheezy_udp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:44.031: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:44.035: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:44.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:44.062: INFO: Unable to read jessie_udp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:44.065: INFO: Unable to read jessie_tcp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:44.069: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:44.073: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:44.096: INFO: Lookups using dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a failed for: [wheezy_udp@dns-test-service.dns-9030.svc.cluster.local wheezy_tcp@dns-test-service.dns-9030.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local jessie_udp@dns-test-service.dns-9030.svc.cluster.local jessie_tcp@dns-test-service.dns-9030.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local]

    
    Aug 29 21:20:49.028: INFO: Unable to read wheezy_udp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:49.032: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:49.035: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:49.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:49.065: INFO: Unable to read jessie_udp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:49.069: INFO: Unable to read jessie_tcp@dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:49.073: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:49.076: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local from pod dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a: the server could not find the requested resource (get pods dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a)
    Aug 29 21:20:49.096: INFO: Lookups using dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a failed for: [wheezy_udp@dns-test-service.dns-9030.svc.cluster.local wheezy_tcp@dns-test-service.dns-9030.svc.cluster.local wheezy_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local wheezy_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local jessie_udp@dns-test-service.dns-9030.svc.cluster.local jessie_tcp@dns-test-service.dns-9030.svc.cluster.local jessie_udp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local jessie_tcp@_http._tcp.dns-test-service.dns-9030.svc.cluster.local]

    
    Aug 29 21:20:54.083: INFO: DNS probes using dns-9030/dns-test-1373fbc4-42ed-425b-b143-e9b942cf294a 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:186
    Aug 29 21:20:54.218: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "dns-9030" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] DNS should provide DNS for services  [Conformance]","total":-1,"completed":110,"skipped":1801,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:20:56.367: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-1936" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap binary data should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":111,"skipped":1828,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-apps] ReplicationController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:20:59.457: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-2290" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should test the lifecycle of a ReplicationController [Conformance]","total":-1,"completed":112,"skipped":1831,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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:185
    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:186
    Aug 29 21:21:05.747: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "custom-resource-definition-2502" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition listing custom resource definition objects works  [Conformance]","total":-1,"completed":113,"skipped":1886,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:21:19.938: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-7038" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl replace should update a single-container pod's image  [Conformance]","total":-1,"completed":114,"skipped":1926,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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/storage/projected_downwardapi.go:41
    [It] should provide container's memory limit [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test downward API volume plugin
    Aug 29 21:21:20.004: INFO: Waiting up to 5m0s for pod "downwardapi-volume-9c4b2599-a717-4780-a812-fa72c7c966c7" in namespace "projected-2533" to be "Succeeded or Failed"

    Aug 29 21:21:20.007: INFO: Pod "downwardapi-volume-9c4b2599-a717-4780-a812-fa72c7c966c7": Phase="Pending", Reason="", readiness=false. Elapsed: 3.107313ms
    Aug 29 21:21:22.012: INFO: Pod "downwardapi-volume-9c4b2599-a717-4780-a812-fa72c7c966c7": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.008155561s
    STEP: Saw pod success
    Aug 29 21:21:22.012: INFO: Pod "downwardapi-volume-9c4b2599-a717-4780-a812-fa72c7c966c7" satisfied condition "Succeeded or Failed"

    Aug 29 21:21:22.016: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-izhnvy pod downwardapi-volume-9c4b2599-a717-4780-a812-fa72c7c966c7 container client-container: <nil>
    STEP: delete the pod
    Aug 29 21:21:22.040: INFO: Waiting for pod downwardapi-volume-9c4b2599-a717-4780-a812-fa72c7c966c7 to disappear
    Aug 29 21:21:22.045: INFO: Pod downwardapi-volume-9c4b2599-a717-4780-a812-fa72c7c966c7 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:186
    Aug 29 21:21:22.045: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-2533" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should provide container's memory limit [NodeConformance] [Conformance]","total":-1,"completed":115,"skipped":1943,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:21:29.934: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-3060" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should be submitted and removed [NodeConformance] [Conformance]","total":-1,"completed":116,"skipped":2010,"failed":0}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 21 lines ...
    STEP: Destroying namespace "webhook-1739-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:102
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should mutate configmap [Conformance]","total":-1,"completed":117,"skipped":2026,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:21:35.733: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "dns-1295" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] DNS should provide /etc/hosts entries for the cluster [LinuxOnly] [Conformance]","total":-1,"completed":118,"skipped":2066,"failed":0}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:21:50.168: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-5472" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of different groups [Conformance]","total":-1,"completed":119,"skipped":2069,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Docker Containers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:21:50.252: 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:630
    STEP: Creating a pod to test override arguments
    Aug 29 21:21:50.282: INFO: Waiting up to 5m0s for pod "client-containers-9ed71814-03fd-44ac-bc5c-f24fba62fa10" in namespace "containers-9749" to be "Succeeded or Failed"

    Aug 29 21:21:50.285: INFO: Pod "client-containers-9ed71814-03fd-44ac-bc5c-f24fba62fa10": Phase="Pending", Reason="", readiness=false. Elapsed: 2.203822ms
    Aug 29 21:21:52.288: INFO: Pod "client-containers-9ed71814-03fd-44ac-bc5c-f24fba62fa10": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006101526s
    STEP: Saw pod success
    Aug 29 21:21:52.289: INFO: Pod "client-containers-9ed71814-03fd-44ac-bc5c-f24fba62fa10" satisfied condition "Succeeded or Failed"

    Aug 29 21:21:52.291: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod client-containers-9ed71814-03fd-44ac-bc5c-f24fba62fa10 container agnhost-container: <nil>
    STEP: delete the pod
    Aug 29 21:21:52.310: INFO: Waiting for pod client-containers-9ed71814-03fd-44ac-bc5c-f24fba62fa10 to disappear
    Aug 29 21:21:52.313: INFO: Pod client-containers-9ed71814-03fd-44ac-bc5c-f24fba62fa10 no longer exists
    [AfterEach] [sig-node] Docker Containers
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:21:52.314: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "containers-9749" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Docker Containers should be able to override the image's default arguments (docker cmd) [NodeConformance] [Conformance]","total":-1,"completed":120,"skipped":2123,"failed":0}

    [BeforeEach] [sig-apps] ReplicationController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:21:52.331: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename replication-controller
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:21:55.403: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-5392" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should surface a failure condition on a common issue like exceeded quota [Conformance]","total":-1,"completed":121,"skipped":2123,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 24 lines ...
    STEP: Destroying namespace "webhook-7430-markers" for this suite.
    [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:102
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] patching/updating a mutating webhook should work [Conformance]","total":-1,"completed":122,"skipped":2147,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] version v1
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 336 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:22:09.936: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "proxy-8169" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Proxy version v1 should proxy through a service and a pod  [Conformance]","total":-1,"completed":123,"skipped":2178,"failed":0}

    
    SSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Ingress API
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:22:10.081: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "ingress-3981" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Ingress API should support creating Ingress API operations [Conformance]","total":-1,"completed":124,"skipped":2196,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] EndpointSliceMirroring
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:22:16.212: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "endpointslicemirroring-7640" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] EndpointSliceMirroring should mirror a custom Endpoints resource through create update and delete [Conformance]","total":-1,"completed":125,"skipped":2222,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 160 lines ...
    Aug 29 21:22:18.410: INFO: stdout: "deployment.apps/agnhost-replica created\n"
    STEP: validating guestbook app
    Aug 29 21:22:18.410: INFO: Waiting for all frontend pods to be Running.
    Aug 29 21:22:23.462: INFO: Waiting for frontend to serve content.
    Aug 29 21:22:23.471: INFO: Trying to add a new entry to the guestbook.
    Aug 29 21:22:23.482: INFO: Verifying that added entry can be retrieved.
    Aug 29 21:22:28.489: INFO: Failed to get response from guestbook. err: the server responded with the status code 417 but did not return more information (get services frontend), response: 

    STEP: using delete to clean up resources
    Aug 29 21:22:33.502: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6406 delete --grace-period=0 --force -f -'
    Aug 29 21:22:33.690: INFO: stderr: "warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely.\n"
    Aug 29 21:22:33.690: INFO: stdout: "service \"agnhost-replica\" force deleted\n"
    STEP: using delete to clean up resources
    Aug 29 21:22:33.690: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6406 delete --grace-period=0 --force -f -'
... skipping 19 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:22:34.495: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-6406" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Guestbook application should create and stop a working application  [Conformance]","total":-1,"completed":126,"skipped":2223,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 3 lines ...
    [BeforeEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/pods.go:186
    [It] should contain environment variables for services [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    Aug 29 21:22:34.585: INFO: The status of Pod server-envvars-6f1577db-1d85-4e9c-94b9-6da85079af9c is Pending, waiting for it to be Running (with Ready = true)
    Aug 29 21:22:36.589: INFO: The status of Pod server-envvars-6f1577db-1d85-4e9c-94b9-6da85079af9c is Running (Ready = true)
    Aug 29 21:22:36.612: INFO: Waiting up to 5m0s for pod "client-envvars-03e392fc-9271-4edb-8f73-df9c3daa7eac" in namespace "pods-7718" to be "Succeeded or Failed"

    Aug 29 21:22:36.619: INFO: Pod "client-envvars-03e392fc-9271-4edb-8f73-df9c3daa7eac": Phase="Pending", Reason="", readiness=false. Elapsed: 7.682201ms
    Aug 29 21:22:38.624: INFO: Pod "client-envvars-03e392fc-9271-4edb-8f73-df9c3daa7eac": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.012472569s
    STEP: Saw pod success
    Aug 29 21:22:38.624: INFO: Pod "client-envvars-03e392fc-9271-4edb-8f73-df9c3daa7eac" satisfied condition "Succeeded or Failed"

    Aug 29 21:22:38.627: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod client-envvars-03e392fc-9271-4edb-8f73-df9c3daa7eac container env3cont: <nil>
    STEP: delete the pod
    Aug 29 21:22:38.651: INFO: Waiting for pod client-envvars-03e392fc-9271-4edb-8f73-df9c3daa7eac to disappear
    Aug 29 21:22:38.655: INFO: Pod client-envvars-03e392fc-9271-4edb-8f73-df9c3daa7eac no longer exists
    [AfterEach] [sig-node] Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:22:38.655: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-7718" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should contain environment variables for services [NodeConformance] [Conformance]","total":-1,"completed":127,"skipped":2224,"failed":0}

    
    SSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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/storage/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:630
    STEP: Creating a pod to test downward API volume plugin
    Aug 29 21:22:38.729: INFO: Waiting up to 5m0s for pod "downwardapi-volume-ff01a24b-0fb7-4c8c-9b3b-ef8131280934" in namespace "downward-api-5107" to be "Succeeded or Failed"

    Aug 29 21:22:38.733: INFO: Pod "downwardapi-volume-ff01a24b-0fb7-4c8c-9b3b-ef8131280934": Phase="Pending", Reason="", readiness=false. Elapsed: 3.310924ms
    Aug 29 21:22:40.738: INFO: Pod "downwardapi-volume-ff01a24b-0fb7-4c8c-9b3b-ef8131280934": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.008068485s
    STEP: Saw pod success
    Aug 29 21:22:40.738: INFO: Pod "downwardapi-volume-ff01a24b-0fb7-4c8c-9b3b-ef8131280934" satisfied condition "Succeeded or Failed"

    Aug 29 21:22:40.741: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod downwardapi-volume-ff01a24b-0fb7-4c8c-9b3b-ef8131280934 container client-container: <nil>
    STEP: delete the pod
    Aug 29 21:22:40.758: INFO: Waiting for pod downwardapi-volume-ff01a24b-0fb7-4c8c-9b3b-ef8131280934 to disappear
    Aug 29 21:22:40.761: INFO: Pod downwardapi-volume-ff01a24b-0fb7-4c8c-9b3b-ef8131280934 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:186
    Aug 29 21:22:40.761: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-5107" 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":128,"skipped":2237,"failed":0}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 45 lines ...
    STEP: Destroying namespace "services-2566" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:750
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should have session affinity work for service with type clusterIP [LinuxOnly] [Conformance]","total":-1,"completed":129,"skipped":2251,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:23:06.663: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-3967" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should update labels on modification [NodeConformance] [Conformance]","total":-1,"completed":130,"skipped":2252,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] StatefulSet
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:23:36.854: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-2199" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should have a working scale subresource [Conformance]","total":-1,"completed":131,"skipped":2299,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 11 lines ...
    STEP: Destroying namespace "services-6520" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:750
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should find a service from listing all namespaces [Conformance]","total":-1,"completed":132,"skipped":2333,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 24 lines ...
    STEP: retrieving the pod
    STEP: looking for the results for each expected name from probers
    Aug 29 21:23:41.076: INFO: File wheezy_udp@dns-test-service-3.dns-2851.svc.cluster.local from pod  dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Aug 29 21:23:41.080: INFO: File jessie_udp@dns-test-service-3.dns-2851.svc.cluster.local from pod  dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Aug 29 21:23:41.080: INFO: Lookups using dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa failed for: [wheezy_udp@dns-test-service-3.dns-2851.svc.cluster.local jessie_udp@dns-test-service-3.dns-2851.svc.cluster.local]

    
    Aug 29 21:23:46.085: INFO: File wheezy_udp@dns-test-service-3.dns-2851.svc.cluster.local from pod  dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Aug 29 21:23:46.088: INFO: File jessie_udp@dns-test-service-3.dns-2851.svc.cluster.local from pod  dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Aug 29 21:23:46.088: INFO: Lookups using dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa failed for: [wheezy_udp@dns-test-service-3.dns-2851.svc.cluster.local jessie_udp@dns-test-service-3.dns-2851.svc.cluster.local]

    
    Aug 29 21:23:51.085: INFO: File wheezy_udp@dns-test-service-3.dns-2851.svc.cluster.local from pod  dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Aug 29 21:23:51.088: INFO: File jessie_udp@dns-test-service-3.dns-2851.svc.cluster.local from pod  dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Aug 29 21:23:51.088: INFO: Lookups using dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa failed for: [wheezy_udp@dns-test-service-3.dns-2851.svc.cluster.local jessie_udp@dns-test-service-3.dns-2851.svc.cluster.local]

    
    Aug 29 21:23:56.085: INFO: File wheezy_udp@dns-test-service-3.dns-2851.svc.cluster.local from pod  dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Aug 29 21:23:56.088: INFO: File jessie_udp@dns-test-service-3.dns-2851.svc.cluster.local from pod  dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Aug 29 21:23:56.088: INFO: Lookups using dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa failed for: [wheezy_udp@dns-test-service-3.dns-2851.svc.cluster.local jessie_udp@dns-test-service-3.dns-2851.svc.cluster.local]

    
    Aug 29 21:24:01.086: INFO: File wheezy_udp@dns-test-service-3.dns-2851.svc.cluster.local from pod  dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Aug 29 21:24:01.090: INFO: File jessie_udp@dns-test-service-3.dns-2851.svc.cluster.local from pod  dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Aug 29 21:24:01.090: INFO: Lookups using dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa failed for: [wheezy_udp@dns-test-service-3.dns-2851.svc.cluster.local jessie_udp@dns-test-service-3.dns-2851.svc.cluster.local]

    
    Aug 29 21:24:06.086: INFO: File wheezy_udp@dns-test-service-3.dns-2851.svc.cluster.local from pod  dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Aug 29 21:24:06.089: INFO: File jessie_udp@dns-test-service-3.dns-2851.svc.cluster.local from pod  dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa contains 'foo.example.com.
    ' instead of 'bar.example.com.'
    Aug 29 21:24:06.089: INFO: Lookups using dns-2851/dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa failed for: [wheezy_udp@dns-test-service-3.dns-2851.svc.cluster.local jessie_udp@dns-test-service-3.dns-2851.svc.cluster.local]

    
    Aug 29 21:24:11.091: INFO: DNS probes using dns-test-878eccae-3343-4ceb-9ca0-b91f56034afa 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-2851.svc.cluster.local A > /results/wheezy_udp@dns-test-service-3.dns-2851.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:186
    Aug 29 21:24:13.196: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "dns-2851" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] DNS should provide DNS for ExternalName services [Conformance]","total":-1,"completed":133,"skipped":2344,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:24:28.404: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-9947" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for multiple CRDs of same group and version but different kinds [Conformance]","total":-1,"completed":134,"skipped":2398,"failed":0}

    
    SSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] Service endpoints latency
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:24:39.204: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "svc-latency-1162" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Service endpoints latency should not be very high  [Conformance]","total":-1,"completed":135,"skipped":2410,"failed":0}

    
    S
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir wrapper volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 11 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Aug 29 21:24:41.291: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-wrapper-7437" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir wrapper volumes should not conflict [Conformance]","total":-1,"completed":136,"skipped":2411,"failed":0}

    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:24:41.303: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename projected
    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/storage/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:630
    STEP: Creating a pod to test downward API volume plugin
    Aug 29 21:24:41.352: INFO: Waiting up to 5m0s for pod "downwardapi-volume-134742ed-9477-4f72-a0c6-30fe1643fbab" in namespace "projected-94" to be "Succeeded or Failed"

    Aug 29 21:24:41.356: INFO: Pod "downwardapi-volume-134742ed-9477-4f72-a0c6-30fe1643fbab": Phase="Pending", Reason="", readiness=false. Elapsed: 3.594971ms
    Aug 29 21:24:43.360: INFO: Pod "downwardapi-volume-134742ed-9477-4f72-a0c6-30fe1643fbab": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.00828043s
    STEP: Saw pod success
    Aug 29 21:24:43.361: INFO: Pod "downwardapi-volume-134742ed-9477-4f72-a0c6-30fe1643fbab" satisfied condition "Succeeded or Failed"

    Aug 29 21:24:43.364: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-worker-izhnvy pod downwardapi-volume-134742ed-9477-4f72-a0c6-30fe1643fbab container client-container: <nil>
    STEP: delete the pod
    Aug 29 21:24:43.387: INFO: Waiting for pod downwardapi-volume-134742ed-9477-4f72-a0c6-30fe1643fbab to disappear
    Aug 29 21:24:43.390: INFO: Pod downwardapi-volume-134742ed-9477-4f72-a0c6-30fe1643fbab 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:186
    Aug 29 21:24:43.390: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-94" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should provide container's cpu request [NodeConformance] [Conformance]","total":-1,"completed":137,"skipped":2411,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:24:43.467: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-6450" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should be able to update and delete ResourceQuota. [Conformance]","total":-1,"completed":138,"skipped":2413,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-instrumentation] Events
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:24:43.625: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-4078" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-instrumentation] Events should delete a collection of events [Conformance]","total":-1,"completed":139,"skipped":2457,"failed":0}

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

    
    SS
    ------------------------------
    [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:185
    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:186
    Aug 29 21:24:51.248: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "custom-resource-definition-9788" 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":141,"skipped":2473,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:24:51.287: 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:630
    STEP: Creating a pod to test emptydir volume type on tmpfs
    Aug 29 21:24:51.320: INFO: Waiting up to 5m0s for pod "pod-fbdb6a9d-1868-4520-8ac0-42c34c788620" in namespace "emptydir-4937" to be "Succeeded or Failed"

    Aug 29 21:24:51.322: INFO: Pod "pod-fbdb6a9d-1868-4520-8ac0-42c34c788620": Phase="Pending", Reason="", readiness=false. Elapsed: 2.244973ms
    Aug 29 21:24:53.326: INFO: Pod "pod-fbdb6a9d-1868-4520-8ac0-42c34c788620": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.006138475s
    STEP: Saw pod success
    Aug 29 21:24:53.326: INFO: Pod "pod-fbdb6a9d-1868-4520-8ac0-42c34c788620" satisfied condition "Succeeded or Failed"

    Aug 29 21:24:53.329: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-6g6tc pod pod-fbdb6a9d-1868-4520-8ac0-42c34c788620 container test-container: <nil>
    STEP: delete the pod
    Aug 29 21:24:53.352: INFO: Waiting for pod pod-fbdb6a9d-1868-4520-8ac0-42c34c788620 to disappear
    Aug 29 21:24:53.355: INFO: Pod pod-fbdb6a9d-1868-4520-8ac0-42c34c788620 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:186
    Aug 29 21:24:53.355: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-4937" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes volume on tmpfs should have the correct mode [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":142,"skipped":2495,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:24:53.419: 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,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test emptydir 0644 on tmpfs
    Aug 29 21:24:53.451: INFO: Waiting up to 5m0s for pod "pod-4e4a0301-abb9-4730-8885-03f42c81dc19" in namespace "emptydir-632" to be "Succeeded or Failed"

    Aug 29 21:24:53.455: INFO: Pod "pod-4e4a0301-abb9-4730-8885-03f42c81dc19": Phase="Pending", Reason="", readiness=false. Elapsed: 3.02016ms
    Aug 29 21:24:55.459: INFO: Pod "pod-4e4a0301-abb9-4730-8885-03f42c81dc19": Phase="Succeeded", Reason="", readiness=false. Elapsed: 2.007825408s
    STEP: Saw pod success
    Aug 29 21:24:55.459: INFO: Pod "pod-4e4a0301-abb9-4730-8885-03f42c81dc19" satisfied condition "Succeeded or Failed"

    Aug 29 21:24:55.462: INFO: Trying to get logs from node k8s-upgrade-and-conformance-a00ni7-md-0-bhd5t-69bbff5968-4vgg2 pod pod-4e4a0301-abb9-4730-8885-03f42c81dc19 container test-container: <nil>
    STEP: delete the pod
    Aug 29 21:24:55.490: INFO: Waiting for pod pod-4e4a0301-abb9-4730-8885-03f42c81dc19 to disappear
    Aug 29 21:24:55.493: INFO: Pod pod-4e4a0301-abb9-4730-8885-03f42c81dc19 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:186
    Aug 29 21:24:55.493: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-632" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0644,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":143,"skipped":2536,"failed":0}

    
    SSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-cli] Kubectl client
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:25:07.498: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-6207" 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":144,"skipped":2554,"failed":0}

    
    SS
    ------------------------------
    [BeforeEach] [sig-storage] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:25:13.634: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-356" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap optional updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":145,"skipped":2556,"failed":0}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected downwardAPI
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:25:20.242: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-9684" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should update annotations on modification [NodeConformance] [Conformance]","total":-1,"completed":146,"skipped":2561,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-apps] DisruptionController
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    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:186
    Aug 29 21:25:26.444: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "disruption-4759" for this suite.
    
    •
    ------------------------------
    {"msg":"FAILED [sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]","total":-1,"completed":27,"skipped":463,"failed":3,"failures":["[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]","[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]","[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]"]}

    [BeforeEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Aug 29 21:16:19.405: 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 33 lines ...
    Aug 29 21:16:23.702: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1808.svc from pod dns-1808/dns-test-5eb77744-033a-48da-b10f-95d5047e5fce: the server could not find the requested resource (get pods dns-test-5eb77744-033a-48da-b10f-95d5047e5fce)
    Aug 29 21:16:23.706: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1808.svc from pod dns-1808/dns-test-5eb77744-033a-48da-b10f-95d5047e5fce: the server could not find the requested resource (get pods dns-test-5eb77744-033a-48da-b10f-95d5047e5fce)
    Aug 29 21:16:23.712: INFO: Unable to read jessie_udp@PodARecord from pod dns-1808/dns-test-5eb77744-033a-48da-b10f-95d5047e5fce: the server could not find the requested resource (get pods dns-test-5eb77744-033a-48da-b10f-95d5047e5fce)
    Aug 29 21:16:23.716: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1808/dns-test-5eb77744-033a-48da-b10f-95d5047e5fce: the server could not find the requested resource (get pods dns-test-5eb77744-033a-48da-b10f-95d5047e5fce)
    Aug 29 21:16:23.720: INFO: Unable to read 10.140.149.199_udp@PTR from pod dns-1808/dns-test-5eb77744-033a-48da-b10f-95d5047e5fce: the server could not find the requested resource (get pods dns-test-5eb77744-033a-48da-b10f-95d5047e5fce)
    Aug 29 21:16:23.726: INFO: Unable to read 10.140.149.199_tcp@PTR from pod dns-1808/dns-test-5eb77744-033a-48da-b10f-95d5047e5fce: the server could not find the requested resource (get pods dns-test-5eb77744-033a-48da-b10f-95d5047e5fce)
    Aug 29 21:16:23.726: INFO: Lookups using dns-1808/dns-test-5eb77744-033a-48da-b10f-95d5047e5fce failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1808 wheezy_tcp@dns-test-service.dns-1808 wheezy_udp@dns-test-service.dns-1808.svc wheezy_tcp@dns-test-service.dns-1808.svc wheezy_udp@_http._tcp.dns-test-service.dns-1808.svc wheezy_tcp@_http._tcp.dns-test-service.dns-1808.svc wheezy_udp@_http._tcp.test-service-2.dns-1808.svc wheezy_tcp@_http._tcp.test-service-2.dns-1808.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.149.199_udp@PTR 10.140.149.199_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1808 jessie_tcp@dns-test-service.dns-1808 jessie_udp@dns-test-service.dns-1808.svc jessie_tcp@dns-test-service.dns-1808.svc jessie_udp@_http._tcp.dns-test-service.dns-1808.svc jessie_tcp@_http._tcp.dns-test-service.dns-1808.svc jessie_udp@_http._tcp.tes