This job view page is being replaced by Spyglass soon. Check out the new job view.
PRoscr: ⚠️ Use Kubernetes 1.25 in Quick Start docs and CAPD.
Resultfailure
Tests 0 failed / 7 succeeded
Started2022-09-03 08:57
Elapsed1h7m
Revision
Refs 7156
uploadercrier
uploadercrier

No Test Failures!


Show 7 Passed Tests

Show 20 Skipped Tests

Error lines from build-log.txt

... skipping 905 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/api v0.24.2
go: downloading k8s.io/apimachinery v0.24.2
... skipping 225 lines ...
    kubeadmconfig.bootstrap.cluster.x-k8s.io/k8s-upgrade-and-conformance-z5d79l-mp-0-config created
    kubeadmconfig.bootstrap.cluster.x-k8s.io/k8s-upgrade-and-conformance-z5d79l-mp-0-config-cgroupfs created
    cluster.cluster.x-k8s.io/k8s-upgrade-and-conformance-z5d79l created
    machinepool.cluster.x-k8s.io/k8s-upgrade-and-conformance-z5d79l-mp-0 created
    dockermachinepool.infrastructure.cluster.x-k8s.io/k8s-upgrade-and-conformance-z5d79l-dmp-0 created

    Failed to get logs for Machine k8s-upgrade-and-conformance-z5d79l-jdxfp-fw2qk, Cluster k8s-upgrade-and-conformance-oap2ri/k8s-upgrade-and-conformance-z5d79l: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-jh8sn, Cluster k8s-upgrade-and-conformance-oap2ri/k8s-upgrade-and-conformance-z5d79l: exit status 2
    Failed to get logs for Machine k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl, Cluster k8s-upgrade-and-conformance-oap2ri/k8s-upgrade-and-conformance-z5d79l: exit status 2
    Failed to get logs for MachinePool k8s-upgrade-and-conformance-z5d79l-mp-0, Cluster k8s-upgrade-and-conformance-oap2ri/k8s-upgrade-and-conformance-z5d79l: exit status 2
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    STEP: Creating a namespace for hosting the "k8s-upgrade-and-conformance" test spec 09/03/22 09:07:53.619
    INFO: Creating namespace k8s-upgrade-and-conformance-oap2ri
    INFO: Creating event watcher for namespace "k8s-upgrade-and-conformance-oap2ri"
... skipping 92 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:14:46.286: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "svcaccounts-8918" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-auth] ServiceAccounts should mount an API token into pods  [Conformance]","total":-1,"completed":1,"skipped":1,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 4 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
    Sep  3 09:14:39.172: INFO: Waiting up to 5m0s for pod "downwardapi-volume-307d203c-0720-48ba-a1c7-45f10f2c6f7b" in namespace "projected-6102" to be "Succeeded or Failed"

    Sep  3 09:14:39.183: INFO: Pod "downwardapi-volume-307d203c-0720-48ba-a1c7-45f10f2c6f7b": Phase="Pending", Reason="", readiness=false. Elapsed: 11.472244ms
    Sep  3 09:14:41.188: INFO: Pod "downwardapi-volume-307d203c-0720-48ba-a1c7-45f10f2c6f7b": Phase="Pending", Reason="", readiness=false. Elapsed: 2.016230045s
    Sep  3 09:14:43.192: INFO: Pod "downwardapi-volume-307d203c-0720-48ba-a1c7-45f10f2c6f7b": Phase="Pending", Reason="", readiness=false. Elapsed: 4.02035312s
    Sep  3 09:14:45.198: INFO: Pod "downwardapi-volume-307d203c-0720-48ba-a1c7-45f10f2c6f7b": Phase="Running", Reason="", readiness=true. Elapsed: 6.025694927s
    Sep  3 09:14:47.201: INFO: Pod "downwardapi-volume-307d203c-0720-48ba-a1c7-45f10f2c6f7b": Phase="Running", Reason="", readiness=false. Elapsed: 8.029285529s
    Sep  3 09:14:49.207: INFO: Pod "downwardapi-volume-307d203c-0720-48ba-a1c7-45f10f2c6f7b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.034980092s
    STEP: Saw pod success
    Sep  3 09:14:49.207: INFO: Pod "downwardapi-volume-307d203c-0720-48ba-a1c7-45f10f2c6f7b" satisfied condition "Succeeded or Failed"

    Sep  3 09:14:49.213: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-wggvfg pod downwardapi-volume-307d203c-0720-48ba-a1c7-45f10f2c6f7b container client-container: <nil>
    STEP: delete the pod
    Sep  3 09:14:49.252: INFO: Waiting for pod downwardapi-volume-307d203c-0720-48ba-a1c7-45f10f2c6f7b to disappear
    Sep  3 09:14:49.258: INFO: Pod downwardapi-volume-307d203c-0720-48ba-a1c7-45f10f2c6f7b 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
    Sep  3 09:14:49.258: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-6102" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should provide container's memory limit [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":36,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [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 3 lines ...
    Sep  3 09:14:39.190: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume 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-a661d7de-78d0-4a9f-a1b9-b092458bff50
    STEP: Creating a pod to test consume configMaps
    Sep  3 09:14:39.214: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-25a3f373-ec44-4c49-958d-c1ed04671031" in namespace "projected-1746" to be "Succeeded or Failed"

    Sep  3 09:14:39.226: INFO: Pod "pod-projected-configmaps-25a3f373-ec44-4c49-958d-c1ed04671031": Phase="Pending", Reason="", readiness=false. Elapsed: 11.604713ms
    Sep  3 09:14:41.231: INFO: Pod "pod-projected-configmaps-25a3f373-ec44-4c49-958d-c1ed04671031": Phase="Pending", Reason="", readiness=false. Elapsed: 2.016456076s
    Sep  3 09:14:43.235: INFO: Pod "pod-projected-configmaps-25a3f373-ec44-4c49-958d-c1ed04671031": Phase="Pending", Reason="", readiness=false. Elapsed: 4.020478368s
    Sep  3 09:14:45.238: INFO: Pod "pod-projected-configmaps-25a3f373-ec44-4c49-958d-c1ed04671031": Phase="Running", Reason="", readiness=true. Elapsed: 6.024007943s
    Sep  3 09:14:47.242: INFO: Pod "pod-projected-configmaps-25a3f373-ec44-4c49-958d-c1ed04671031": Phase="Running", Reason="", readiness=false. Elapsed: 8.028132673s
    Sep  3 09:14:49.251: INFO: Pod "pod-projected-configmaps-25a3f373-ec44-4c49-958d-c1ed04671031": Phase="Succeeded", Reason="", readiness=false. Elapsed: 10.036849911s
    STEP: Saw pod success
    Sep  3 09:14:49.251: INFO: Pod "pod-projected-configmaps-25a3f373-ec44-4c49-958d-c1ed04671031" satisfied condition "Succeeded or Failed"

    Sep  3 09:14:49.256: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod pod-projected-configmaps-25a3f373-ec44-4c49-958d-c1ed04671031 container agnhost-container: <nil>
    STEP: delete the pod
    Sep  3 09:14:49.301: INFO: Waiting for pod pod-projected-configmaps-25a3f373-ec44-4c49-958d-c1ed04671031 to disappear
    Sep  3 09:14:49.306: INFO: Pod pod-projected-configmaps-25a3f373-ec44-4c49-958d-c1ed04671031 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
    Sep  3 09:14:49.306: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-1746" 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":1,"skipped":45,"failed":0}

    
    SSSSS
    ------------------------------
    [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
... skipping 6 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:14:51.404: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "containers-8098" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Docker Containers should use the image defaults if command and args are blank [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":45,"failed":0}

    
    SSSSSSS
    ------------------------------
    [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
    Sep  3 09:14:49.340: 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
    Sep  3 09:14:49.416: INFO: Waiting up to 5m0s for pod "client-containers-61f1002e-d738-4336-aa24-4ca7dae7000d" in namespace "containers-9214" to be "Succeeded or Failed"

    Sep  3 09:14:49.425: INFO: Pod "client-containers-61f1002e-d738-4336-aa24-4ca7dae7000d": Phase="Pending", Reason="", readiness=false. Elapsed: 9.051498ms
    Sep  3 09:14:51.429: INFO: Pod "client-containers-61f1002e-d738-4336-aa24-4ca7dae7000d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.012849377s
    Sep  3 09:14:53.433: INFO: Pod "client-containers-61f1002e-d738-4336-aa24-4ca7dae7000d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.017040084s
    STEP: Saw pod success
    Sep  3 09:14:53.433: INFO: Pod "client-containers-61f1002e-d738-4336-aa24-4ca7dae7000d" satisfied condition "Succeeded or Failed"

    Sep  3 09:14:53.435: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod client-containers-61f1002e-d738-4336-aa24-4ca7dae7000d container agnhost-container: <nil>
    STEP: delete the pod
    Sep  3 09:14:53.446: INFO: Waiting for pod client-containers-61f1002e-d738-4336-aa24-4ca7dae7000d to disappear
    Sep  3 09:14:53.448: INFO: Pod client-containers-61f1002e-d738-4336-aa24-4ca7dae7000d 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
    Sep  3 09:14:53.448: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "containers-9214" 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":2,"skipped":50,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:14:57.645: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "endpointslice-6899" 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":3,"skipped":116,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-network] IngressClass 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 22 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:14:57.733: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "ingressclass-5906" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] IngressClass API  should support creating IngressClass API operations [Conformance]","total":-1,"completed":4,"skipped":124,"failed":0}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [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 podname only [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
    Sep  3 09:14:57.840: INFO: Waiting up to 5m0s for pod "downwardapi-volume-19fb7191-a45a-4533-9e89-38f9854da4c3" in namespace "projected-723" to be "Succeeded or Failed"

    Sep  3 09:14:57.843: INFO: Pod "downwardapi-volume-19fb7191-a45a-4533-9e89-38f9854da4c3": Phase="Pending", Reason="", readiness=false. Elapsed: 2.89201ms
    Sep  3 09:14:59.847: INFO: Pod "downwardapi-volume-19fb7191-a45a-4533-9e89-38f9854da4c3": Phase="Pending", Reason="", readiness=false. Elapsed: 2.006730247s
    Sep  3 09:15:01.852: INFO: Pod "downwardapi-volume-19fb7191-a45a-4533-9e89-38f9854da4c3": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.011169739s
    STEP: Saw pod success
    Sep  3 09:15:01.852: INFO: Pod "downwardapi-volume-19fb7191-a45a-4533-9e89-38f9854da4c3" satisfied condition "Succeeded or Failed"

    Sep  3 09:15:01.854: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod downwardapi-volume-19fb7191-a45a-4533-9e89-38f9854da4c3 container client-container: <nil>
    STEP: delete the pod
    Sep  3 09:15:01.868: INFO: Waiting for pod downwardapi-volume-19fb7191-a45a-4533-9e89-38f9854da4c3 to disappear
    Sep  3 09:15:01.871: INFO: Pod downwardapi-volume-19fb7191-a45a-4533-9e89-38f9854da4c3 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
    Sep  3 09:15:01.871: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-723" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should provide podname only [NodeConformance] [Conformance]","total":-1,"completed":5,"skipped":138,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 14 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:15:04.985: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-134" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should surface a failure condition on a common issue like exceeded quota [Conformance]","total":-1,"completed":6,"skipped":169,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 12 lines ...
    I0903 09:14:39.124088      16 runners.go:190] Created replication controller with name: externalname-service, namespace: services-7756, replica count: 2
    I0903 09:14:42.175839      16 runners.go:190] externalname-service Pods: 2 out of 2 created, 0 running, 2 pending, 0 waiting, 0 inactive, 0 terminating, 0 unknown, 0 runningButNotReady 
    I0903 09:14:45.176086      16 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 
    Sep  3 09:14:45.176: INFO: Creating new exec pod
    Sep  3 09:14:48.195: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7756 exec execpod978sm -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Sep  3 09:14:53.354: INFO: rc: 1
    Sep  3 09:14:53.354: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7756 exec execpod978sm -- /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: getaddrinfo: Try again
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  3 09:14:54.354: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7756 exec execpod978sm -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Sep  3 09:14:59.524: INFO: rc: 1
    Sep  3 09:14:59.524: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7756 exec execpod978sm -- /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: getaddrinfo: Try again
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  3 09:15:00.354: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7756 exec execpod978sm -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Sep  3 09:15:05.545: INFO: rc: 1
    Sep  3 09:15:05.545: INFO: Service reachability failing with error: error running /usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7756 exec execpod978sm -- /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: getaddrinfo: Try again
    command terminated with exit code 1
    
    error:

    exit status 1
    Retrying...
    Sep  3 09:15:06.355: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7756 exec execpod978sm -- /bin/sh -x -c echo hostName | nc -v -t -w 2 externalname-service 80'
    Sep  3 09:15:09.126: INFO: stderr: "+ nc -v -t -w 2 externalname-service 80\n+ echo hostName\nConnection to externalname-service 80 port [tcp/http] succeeded!\n"
    Sep  3 09:15:09.126: INFO: stdout: "externalname-service-qdnnp"
    Sep  3 09:15:09.126: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=services-7756 exec execpod978sm -- /bin/sh -x -c echo hostName | nc -v -t -w 2 10.134.226.26 80'
... skipping 12 lines ...
    STEP: Destroying namespace "services-7756" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]","total":-1,"completed":1,"skipped":11,"failed":0}

    
    SSSS
    ------------------------------
    [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 48 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:15:11.396: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pod-network-test-2739" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: udp [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":67,"failed":0}

    
    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
    Sep  3 09:15:14.720: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-3512" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should adopt matching pods on creation [Conformance]","total":-1,"completed":3,"skipped":71,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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:188
    [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
    Sep  3 09:15:09.664: INFO: The status of Pod server-envvars-a8cbaa63-0358-489d-b7e8-5dffcb956f63 is Pending, waiting for it to be Running (with Ready = true)
    Sep  3 09:15:11.691: INFO: The status of Pod server-envvars-a8cbaa63-0358-489d-b7e8-5dffcb956f63 is Running (Ready = true)
    Sep  3 09:15:11.741: INFO: Waiting up to 5m0s for pod "client-envvars-fd75bdd1-2a5c-410b-80ca-237b23d34b94" in namespace "pods-8752" to be "Succeeded or Failed"

    Sep  3 09:15:11.746: INFO: Pod "client-envvars-fd75bdd1-2a5c-410b-80ca-237b23d34b94": Phase="Pending", Reason="", readiness=false. Elapsed: 4.378308ms
    Sep  3 09:15:13.749: INFO: Pod "client-envvars-fd75bdd1-2a5c-410b-80ca-237b23d34b94": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007413805s
    Sep  3 09:15:15.751: INFO: Pod "client-envvars-fd75bdd1-2a5c-410b-80ca-237b23d34b94": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.009981911s
    STEP: Saw pod success
    Sep  3 09:15:15.751: INFO: Pod "client-envvars-fd75bdd1-2a5c-410b-80ca-237b23d34b94" satisfied condition "Succeeded or Failed"

    Sep  3 09:15:15.754: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod client-envvars-fd75bdd1-2a5c-410b-80ca-237b23d34b94 container env3cont: <nil>
    STEP: delete the pod
    Sep  3 09:15:15.776: INFO: Waiting for pod client-envvars-fd75bdd1-2a5c-410b-80ca-237b23d34b94 to disappear
    Sep  3 09:15:15.782: INFO: Pod client-envvars-fd75bdd1-2a5c-410b-80ca-237b23d34b94 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
    Sep  3 09:15:15.782: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-8752" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should contain environment variables for services [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":15,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:15:16.132: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-730" 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":7,"skipped":189,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:15:15.867: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename secrets
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable via the environment [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: creating secret secrets-8470/secret-test-1dc48031-08e9-48cf-b7db-e1032ca2206f
    STEP: Creating a pod to test consume secrets
    Sep  3 09:15:15.915: INFO: Waiting up to 5m0s for pod "pod-configmaps-325777b9-b53e-45e4-9920-757581b1fdc6" in namespace "secrets-8470" to be "Succeeded or Failed"

    Sep  3 09:15:15.918: INFO: Pod "pod-configmaps-325777b9-b53e-45e4-9920-757581b1fdc6": Phase="Pending", Reason="", readiness=false. Elapsed: 3.200254ms
    Sep  3 09:15:17.925: INFO: Pod "pod-configmaps-325777b9-b53e-45e4-9920-757581b1fdc6": Phase="Pending", Reason="", readiness=false. Elapsed: 2.010126044s
    Sep  3 09:15:19.929: INFO: Pod "pod-configmaps-325777b9-b53e-45e4-9920-757581b1fdc6": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.014287249s
    STEP: Saw pod success
    Sep  3 09:15:19.929: INFO: Pod "pod-configmaps-325777b9-b53e-45e4-9920-757581b1fdc6" satisfied condition "Succeeded or Failed"

    Sep  3 09:15:19.932: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-jh8sn pod pod-configmaps-325777b9-b53e-45e4-9920-757581b1fdc6 container env-test: <nil>
    STEP: delete the pod
    Sep  3 09:15:19.957: INFO: Waiting for pod pod-configmaps-325777b9-b53e-45e4-9920-757581b1fdc6 to disappear
    Sep  3 09:15:19.960: INFO: Pod pod-configmaps-325777b9-b53e-45e4-9920-757581b1fdc6 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
    Sep  3 09:15:19.960: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-8470" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Secrets should be consumable via the environment [NodeConformance] [Conformance]","total":-1,"completed":3,"skipped":54,"failed":0}

    
    S
    ------------------------------
    [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
    Sep  3 09:15:16.181: 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-2e5bc239-582f-49dc-b06c-8a2bbe5bacee
    STEP: Creating a pod to test consume secrets
    Sep  3 09:15:16.214: INFO: Waiting up to 5m0s for pod "pod-projected-secrets-0e7fe582-e745-4f01-97b0-3f130739c3dd" in namespace "projected-2099" to be "Succeeded or Failed"

    Sep  3 09:15:16.218: INFO: Pod "pod-projected-secrets-0e7fe582-e745-4f01-97b0-3f130739c3dd": Phase="Pending", Reason="", readiness=false. Elapsed: 3.778375ms
    Sep  3 09:15:18.223: INFO: Pod "pod-projected-secrets-0e7fe582-e745-4f01-97b0-3f130739c3dd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.008138628s
    Sep  3 09:15:20.227: INFO: Pod "pod-projected-secrets-0e7fe582-e745-4f01-97b0-3f130739c3dd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.011990044s
    STEP: Saw pod success
    Sep  3 09:15:20.227: INFO: Pod "pod-projected-secrets-0e7fe582-e745-4f01-97b0-3f130739c3dd" satisfied condition "Succeeded or Failed"

    Sep  3 09:15:20.229: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-jh8sn pod pod-projected-secrets-0e7fe582-e745-4f01-97b0-3f130739c3dd container projected-secret-volume-test: <nil>
    STEP: delete the pod
    Sep  3 09:15:20.243: INFO: Waiting for pod pod-projected-secrets-0e7fe582-e745-4f01-97b0-3f130739c3dd to disappear
    Sep  3 09:15:20.245: INFO: Pod pod-projected-secrets-0e7fe582-e745-4f01-97b0-3f130739c3dd 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
    Sep  3 09:15:20.246: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-2099" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected secret should be consumable from pods in volume [NodeConformance] [Conformance]","total":-1,"completed":8,"skipped":218,"failed":0}

    
    SSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:15:20.853: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "endpointslicemirroring-9711" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] EndpointSliceMirroring should mirror a custom Endpoints resource through create update and delete [Conformance]","total":-1,"completed":4,"skipped":93,"failed":0}

    
    SSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:15:20.877: 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-1e3de82a-959f-4149-9889-8eca74eaabcc
    STEP: Creating a pod to test consume secrets
    Sep  3 09:15:20.918: INFO: Waiting up to 5m0s for pod "pod-projected-secrets-92d25b28-2e74-4145-af96-311852270a42" in namespace "projected-8714" to be "Succeeded or Failed"

    Sep  3 09:15:20.926: INFO: Pod "pod-projected-secrets-92d25b28-2e74-4145-af96-311852270a42": Phase="Pending", Reason="", readiness=false. Elapsed: 7.098224ms
    Sep  3 09:15:22.930: INFO: Pod "pod-projected-secrets-92d25b28-2e74-4145-af96-311852270a42": Phase="Pending", Reason="", readiness=false. Elapsed: 2.010896992s
    Sep  3 09:15:24.936: INFO: Pod "pod-projected-secrets-92d25b28-2e74-4145-af96-311852270a42": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.016765429s
    STEP: Saw pod success
    Sep  3 09:15:24.936: INFO: Pod "pod-projected-secrets-92d25b28-2e74-4145-af96-311852270a42" satisfied condition "Succeeded or Failed"

    Sep  3 09:15:24.941: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod pod-projected-secrets-92d25b28-2e74-4145-af96-311852270a42 container projected-secret-volume-test: <nil>
    STEP: delete the pod
    Sep  3 09:15:24.961: INFO: Waiting for pod pod-projected-secrets-92d25b28-2e74-4145-af96-311852270a42 to disappear
    Sep  3 09:15:24.963: INFO: Pod pod-projected-secrets-92d25b28-2e74-4145-af96-311852270a42 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
    Sep  3 09:15:24.964: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-8714" 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":5,"skipped":105,"failed":0}

    
    SSSSSSSSS
    ------------------------------
    [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 30 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:15:29.135: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-7441" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":6,"skipped":114,"failed":0}

    
    SSSSS
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Garbage collector should not be blocked by dependency circle [Conformance]","total":-1,"completed":4,"skipped":55,"failed":0}

    [BeforeEach] [sig-storage] Downward API volume
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep  3 09:15:25.082: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename downward-api
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 9 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:15:29.682: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-4195" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should update labels on modification [NodeConformance] [Conformance]","total":-1,"completed":5,"skipped":55,"failed":0}

    
    SSSS
    ------------------------------
    [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
    Sep  3 09:15:29.731: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "endpointslice-6023" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] EndpointSlice should have Endpoints and EndpointSlices pointing to API Server [Conformance]","total":-1,"completed":6,"skipped":59,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 48 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:15:33.411: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-3376" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Kubectl label should update the label on a resource  [Conformance]","total":-1,"completed":7,"skipped":110,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:15:34.256: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-runtime-1143" 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":7,"skipped":119,"failed":0}

    
    SSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:15:39.570: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-7805" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap optional updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":8,"skipped":139,"failed":0}

    
    SSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected configMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep  3 09:15:39.597: 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-60d25270-3cda-42c7-b154-faccce268432
    STEP: Creating a pod to test consume configMaps
    Sep  3 09:15:39.632: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-56235a0e-3588-47ce-903e-4442d716df78" in namespace "projected-401" to be "Succeeded or Failed"

    Sep  3 09:15:39.635: INFO: Pod "pod-projected-configmaps-56235a0e-3588-47ce-903e-4442d716df78": Phase="Pending", Reason="", readiness=false. Elapsed: 2.554353ms
    Sep  3 09:15:41.640: INFO: Pod "pod-projected-configmaps-56235a0e-3588-47ce-903e-4442d716df78": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007403354s
    Sep  3 09:15:43.644: INFO: Pod "pod-projected-configmaps-56235a0e-3588-47ce-903e-4442d716df78": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.011825029s
    STEP: Saw pod success
    Sep  3 09:15:43.644: INFO: Pod "pod-projected-configmaps-56235a0e-3588-47ce-903e-4442d716df78" satisfied condition "Succeeded or Failed"

    Sep  3 09:15:43.647: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-jh8sn pod pod-projected-configmaps-56235a0e-3588-47ce-903e-4442d716df78 container agnhost-container: <nil>
    STEP: delete the pod
    Sep  3 09:15:43.660: INFO: Waiting for pod pod-projected-configmaps-56235a0e-3588-47ce-903e-4442d716df78 to disappear
    Sep  3 09:15:43.662: INFO: Pod pod-projected-configmaps-56235a0e-3588-47ce-903e-4442d716df78 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
    Sep  3 09:15:43.662: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-401" 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":9,"skipped":151,"failed":0}

    
    SSSSSSS
    ------------------------------
    [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
    Sep  3 09:15:43.679: 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-cec19dc5-4dbc-4dfa-8b58-0014c077c219
    STEP: Creating a pod to test consume secrets
    Sep  3 09:15:43.719: INFO: Waiting up to 5m0s for pod "pod-secrets-93844ece-cb56-4300-bc34-f819affc0287" in namespace "secrets-9480" to be "Succeeded or Failed"

    Sep  3 09:15:43.721: INFO: Pod "pod-secrets-93844ece-cb56-4300-bc34-f819affc0287": Phase="Pending", Reason="", readiness=false. Elapsed: 2.170531ms
    Sep  3 09:15:45.727: INFO: Pod "pod-secrets-93844ece-cb56-4300-bc34-f819affc0287": Phase="Pending", Reason="", readiness=false. Elapsed: 2.008313303s
    Sep  3 09:15:47.730: INFO: Pod "pod-secrets-93844ece-cb56-4300-bc34-f819affc0287": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.011747158s
    STEP: Saw pod success
    Sep  3 09:15:47.730: INFO: Pod "pod-secrets-93844ece-cb56-4300-bc34-f819affc0287" satisfied condition "Succeeded or Failed"

    Sep  3 09:15:47.733: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-secrets-93844ece-cb56-4300-bc34-f819affc0287 container secret-env-test: <nil>
    STEP: delete the pod
    Sep  3 09:15:47.749: INFO: Waiting for pod pod-secrets-93844ece-cb56-4300-bc34-f819affc0287 to disappear
    Sep  3 09:15:47.751: INFO: Pod pod-secrets-93844ece-cb56-4300-bc34-f819affc0287 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
    Sep  3 09:15:47.751: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-9480" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Secrets should be consumable from pods in env vars [NodeConformance] [Conformance]","total":-1,"completed":10,"skipped":158,"failed":0}

    
    S
    ------------------------------
    [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
    Sep  3 09:15:47.762: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should fail to create ConfigMap with empty key [Conformance]

      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating configMap that has name configmap-test-emptyKey-e91931b1-7245-4018-9c15-a0aca53fbd5c
    [AfterEach] [sig-node] ConfigMap
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:15:47.800: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-759" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] ConfigMap should fail to create ConfigMap with empty key [Conformance]","total":-1,"completed":11,"skipped":159,"failed":0}

    
    SSSSS
    ------------------------------
    [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
    Sep  3 09:15:49.856: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubelet-test-3813" 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":12,"skipped":164,"failed":0}

    
    SS
    ------------------------------
    [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 19 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:16:52.991: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-watch-6344" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceDefinition Watch [Privileged:ClusterAdmin] CustomResourceDefinition Watch watch on custom resource definition objects [Conformance]","total":-1,"completed":13,"skipped":166,"failed":0}

    
    S
    ------------------------------
    [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
    Sep  3 09:17:07.459: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pod-network-test-1335" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Networking Granular Checks: Pods should function for node-pod communication: http [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":14,"skipped":167,"failed":0}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [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 16 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:17:15.559: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replicaset-8437" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicaSet should adopt matching pods on creation and release no longer matching pods [Conformance]","total":-1,"completed":15,"skipped":181,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 138 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:17:30.344: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-3223" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Update Demo should scale a replication controller  [Conformance]","total":-1,"completed":16,"skipped":205,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:17:42.127: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-1569" 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":17,"skipped":237,"failed":0}

    
    SSSSSS
    ------------------------------
    [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
    Sep  3 09:17:42.150: 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
    Sep  3 09:17:44.191: INFO: Deleting pod "var-expansion-4fc16e0c-3bff-4449-878b-8d4342edcbe9" in namespace "var-expansion-9634"
    Sep  3 09:17:44.196: INFO: Wait up to 5m0s for pod "var-expansion-4fc16e0c-3bff-4449-878b-8d4342edcbe9" 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
    Sep  3 09:17:46.203: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-9634" 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":18,"skipped":243,"failed":0}

    
    SSSS
    ------------------------------
    [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
    Sep  3 09:17:46.219: 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
    Sep  3 09:17:46.254: INFO: Waiting up to 5m0s for pod "pod-2e4f0dc1-9a63-4ad1-8dc4-1dd68ce16b01" in namespace "emptydir-8599" to be "Succeeded or Failed"

    Sep  3 09:17:46.257: INFO: Pod "pod-2e4f0dc1-9a63-4ad1-8dc4-1dd68ce16b01": Phase="Pending", Reason="", readiness=false. Elapsed: 3.214007ms
    Sep  3 09:17:48.261: INFO: Pod "pod-2e4f0dc1-9a63-4ad1-8dc4-1dd68ce16b01": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007110102s
    Sep  3 09:17:50.266: INFO: Pod "pod-2e4f0dc1-9a63-4ad1-8dc4-1dd68ce16b01": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.012119629s
    STEP: Saw pod success
    Sep  3 09:17:50.266: INFO: Pod "pod-2e4f0dc1-9a63-4ad1-8dc4-1dd68ce16b01" satisfied condition "Succeeded or Failed"

    Sep  3 09:17:50.269: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod pod-2e4f0dc1-9a63-4ad1-8dc4-1dd68ce16b01 container test-container: <nil>
    STEP: delete the pod
    Sep  3 09:17:50.288: INFO: Waiting for pod pod-2e4f0dc1-9a63-4ad1-8dc4-1dd68ce16b01 to disappear
    Sep  3 09:17:50.290: INFO: Pod pod-2e4f0dc1-9a63-4ad1-8dc4-1dd68ce16b01 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
    Sep  3 09:17:50.290: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-8599" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0777,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":19,"skipped":247,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:17:50.355: 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
    Sep  3 09:17:50.390: INFO: Waiting up to 5m0s for pod "downward-api-c9805ae4-e5f5-47da-8ef2-8139ebdd7282" in namespace "downward-api-6448" to be "Succeeded or Failed"

    Sep  3 09:17:50.393: INFO: Pod "downward-api-c9805ae4-e5f5-47da-8ef2-8139ebdd7282": Phase="Pending", Reason="", readiness=false. Elapsed: 2.691888ms
    Sep  3 09:17:52.398: INFO: Pod "downward-api-c9805ae4-e5f5-47da-8ef2-8139ebdd7282": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007715356s
    Sep  3 09:17:54.403: INFO: Pod "downward-api-c9805ae4-e5f5-47da-8ef2-8139ebdd7282": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.012691006s
    STEP: Saw pod success
    Sep  3 09:17:54.403: INFO: Pod "downward-api-c9805ae4-e5f5-47da-8ef2-8139ebdd7282" satisfied condition "Succeeded or Failed"

    Sep  3 09:17:54.406: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod downward-api-c9805ae4-e5f5-47da-8ef2-8139ebdd7282 container dapi-container: <nil>
    STEP: delete the pod
    Sep  3 09:17:54.426: INFO: Waiting for pod downward-api-c9805ae4-e5f5-47da-8ef2-8139ebdd7282 to disappear
    Sep  3 09:17:54.428: INFO: Pod downward-api-c9805ae4-e5f5-47da-8ef2-8139ebdd7282 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
    Sep  3 09:17:54.428: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-6448" 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":20,"skipped":292,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 23 lines ...
    • [SLOW TEST:144.427 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 have monotonically increasing restart count [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 have monotonically increasing restart count [NodeConformance] [Conformance]","total":-1,"completed":8,"skipped":137,"failed":0}

    
    SSSSS
    ------------------------------
    [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 39 lines ...
    STEP: Destroying namespace "services-4944" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to create a functioning NodePort service [Conformance]","total":-1,"completed":21,"skipped":318,"failed":0}

    
    SSSSSSSSSSSSS
    ------------------------------
    [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 ...
    Sep  3 09:18:03.120: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=crd-publish-openapi-1452 explain e2e-test-crd-publish-openapi-7609-crds.spec'
    Sep  3 09:18:03.280: INFO: stderr: ""
    Sep  3 09:18:03.280: INFO: stdout: "KIND:     e2e-test-crd-publish-openapi-7609-crd\nVERSION:  crd-publish-openapi-test-foo.example.com/v1\n\nRESOURCE: spec <Object>\n\nDESCRIPTION:\n     Specification of Foo\n\nFIELDS:\n   bars\t<[]Object>\n     List of Bars and their specs.\n\n"
    Sep  3 09:18:03.281: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=crd-publish-openapi-1452 explain e2e-test-crd-publish-openapi-7609-crds.spec.bars'
    Sep  3 09:18:03.453: INFO: stderr: ""
    Sep  3 09:18:03.453: INFO: stdout: "KIND:     e2e-test-crd-publish-openapi-7609-crd\nVERSION:  crd-publish-openapi-test-foo.example.com/v1\n\nRESOURCE: bars <[]Object>\n\nDESCRIPTION:\n     List of Bars and their specs.\n\nFIELDS:\n   age\t<string>\n     Age of Bar.\n\n   bazs\t<[]string>\n     List of Bazs.\n\n   name\t<string> -required-\n     Name of Bar.\n\n"
    STEP: kubectl explain works to return error when explain is called on property that doesn't exist

    Sep  3 09:18:03.453: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=crd-publish-openapi-1452 explain e2e-test-crd-publish-openapi-7609-crds.spec.bars2'
    Sep  3 09:18:03.624: 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
    Sep  3 09:18:05.918: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-1452" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD with validation schema [Conformance]","total":-1,"completed":9,"skipped":142,"failed":0}

    
    SSSSS
    ------------------------------
    [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 63 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:18:08.027: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-7157" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment should validate Deployment Status endpoints [Conformance]","total":-1,"completed":10,"skipped":147,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:18:08.106: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-7014" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be immutable if `immutable` field is set [Conformance]","total":-1,"completed":11,"skipped":158,"failed":0}

    
    SS
    ------------------------------
    [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 15 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:18:10.748: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replicaset-6098" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicaSet should list and delete a collection of ReplicaSets [Conformance]","total":-1,"completed":22,"skipped":331,"failed":0}

    
    SS
    ------------------------------
    [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 34 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:18:13.200: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replicaset-1980" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicaSet should validate Replicaset Status endpoints [Conformance]","total":-1,"completed":12,"skipped":160,"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 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
    Sep  3 09:18:13.264: INFO: Waiting up to 5m0s for pod "downwardapi-volume-535533f9-9fbf-4cbe-a0cf-0e65324ac7cf" in namespace "downward-api-4474" to be "Succeeded or Failed"

    Sep  3 09:18:13.267: INFO: Pod "downwardapi-volume-535533f9-9fbf-4cbe-a0cf-0e65324ac7cf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.631455ms
    Sep  3 09:18:15.272: INFO: Pod "downwardapi-volume-535533f9-9fbf-4cbe-a0cf-0e65324ac7cf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007267555s
    Sep  3 09:18:17.278: INFO: Pod "downwardapi-volume-535533f9-9fbf-4cbe-a0cf-0e65324ac7cf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.01367872s
    STEP: Saw pod success
    Sep  3 09:18:17.278: INFO: Pod "downwardapi-volume-535533f9-9fbf-4cbe-a0cf-0e65324ac7cf" satisfied condition "Succeeded or Failed"

    Sep  3 09:18:17.282: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod downwardapi-volume-535533f9-9fbf-4cbe-a0cf-0e65324ac7cf container client-container: <nil>
    STEP: delete the pod
    Sep  3 09:18:17.317: INFO: Waiting for pod downwardapi-volume-535533f9-9fbf-4cbe-a0cf-0e65324ac7cf to disappear
    Sep  3 09:18:17.324: INFO: Pod downwardapi-volume-535533f9-9fbf-4cbe-a0cf-0e65324ac7cf 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
    Sep  3 09:18:17.325: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-4474" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should provide container's cpu limit [NodeConformance] [Conformance]","total":-1,"completed":13,"skipped":168,"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
    Sep  3 09:18:17.526: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "runtimeclass-5264" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] RuntimeClass  should support RuntimeClasses API operations [Conformance]","total":-1,"completed":14,"skipped":169,"failed":0}

    
    SSSSSSS
    ------------------------------
    [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-3736" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to change the type from NodePort to ExternalName [Conformance]","total":-1,"completed":23,"skipped":333,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go: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
    Sep  3 09:18:18.587: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "custom-resource-definition-9587" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] should include custom resource definition resources in discovery documents [Conformance]","total":-1,"completed":24,"skipped":344,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 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
    Sep  3 09:18:17.656: INFO: Waiting up to 5m0s for pod "downwardapi-volume-2a711930-3fb7-4678-b8c5-a5fedeebe747" in namespace "downward-api-6968" to be "Succeeded or Failed"

    Sep  3 09:18:17.671: INFO: Pod "downwardapi-volume-2a711930-3fb7-4678-b8c5-a5fedeebe747": Phase="Pending", Reason="", readiness=false. Elapsed: 14.995556ms
    Sep  3 09:18:19.678: INFO: Pod "downwardapi-volume-2a711930-3fb7-4678-b8c5-a5fedeebe747": Phase="Pending", Reason="", readiness=false. Elapsed: 2.021292952s
    Sep  3 09:18:21.685: INFO: Pod "downwardapi-volume-2a711930-3fb7-4678-b8c5-a5fedeebe747": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.028274936s
    STEP: Saw pod success
    Sep  3 09:18:21.685: INFO: Pod "downwardapi-volume-2a711930-3fb7-4678-b8c5-a5fedeebe747" satisfied condition "Succeeded or Failed"

    Sep  3 09:18:21.689: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod downwardapi-volume-2a711930-3fb7-4678-b8c5-a5fedeebe747 container client-container: <nil>
    STEP: delete the pod
    Sep  3 09:18:21.728: INFO: Waiting for pod downwardapi-volume-2a711930-3fb7-4678-b8c5-a5fedeebe747 to disappear
    Sep  3 09:18:21.732: INFO: Pod downwardapi-volume-2a711930-3fb7-4678-b8c5-a5fedeebe747 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
    Sep  3 09:18:21.732: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-6968" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should provide container's cpu request [NodeConformance] [Conformance]","total":-1,"completed":15,"skipped":176,"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 podname only [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
    Sep  3 09:18:21.858: INFO: Waiting up to 5m0s for pod "downwardapi-volume-806cb2ca-58b2-4b3d-b34d-b5be80ac82b5" in namespace "downward-api-7659" to be "Succeeded or Failed"

    Sep  3 09:18:21.868: INFO: Pod "downwardapi-volume-806cb2ca-58b2-4b3d-b34d-b5be80ac82b5": Phase="Pending", Reason="", readiness=false. Elapsed: 9.339858ms
    Sep  3 09:18:23.875: INFO: Pod "downwardapi-volume-806cb2ca-58b2-4b3d-b34d-b5be80ac82b5": Phase="Pending", Reason="", readiness=false. Elapsed: 2.01627206s
    Sep  3 09:18:25.880: INFO: Pod "downwardapi-volume-806cb2ca-58b2-4b3d-b34d-b5be80ac82b5": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.02158707s
    STEP: Saw pod success
    Sep  3 09:18:25.880: INFO: Pod "downwardapi-volume-806cb2ca-58b2-4b3d-b34d-b5be80ac82b5" satisfied condition "Succeeded or Failed"

    Sep  3 09:18:25.885: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod downwardapi-volume-806cb2ca-58b2-4b3d-b34d-b5be80ac82b5 container client-container: <nil>
    STEP: delete the pod
    Sep  3 09:18:25.908: INFO: Waiting for pod downwardapi-volume-806cb2ca-58b2-4b3d-b34d-b5be80ac82b5 to disappear
    Sep  3 09:18:25.915: INFO: Pod downwardapi-volume-806cb2ca-58b2-4b3d-b34d-b5be80ac82b5 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
    Sep  3 09:18:25.915: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-7659" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should provide podname only [NodeConformance] [Conformance]","total":-1,"completed":16,"skipped":185,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [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-8982-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 pod and apply defaults after mutation [Conformance]","total":-1,"completed":17,"skipped":196,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:18:30.296: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename emptydir
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should support (non-root,0777,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test emptydir 0777 on tmpfs
    Sep  3 09:18:30.358: INFO: Waiting up to 5m0s for pod "pod-d6bf58ec-e038-47fd-80ee-b2ebafba7ddf" in namespace "emptydir-4756" to be "Succeeded or Failed"

    Sep  3 09:18:30.363: INFO: Pod "pod-d6bf58ec-e038-47fd-80ee-b2ebafba7ddf": Phase="Pending", Reason="", readiness=false. Elapsed: 4.4294ms
    Sep  3 09:18:32.370: INFO: Pod "pod-d6bf58ec-e038-47fd-80ee-b2ebafba7ddf": Phase="Pending", Reason="", readiness=false. Elapsed: 2.011374847s
    Sep  3 09:18:34.377: INFO: Pod "pod-d6bf58ec-e038-47fd-80ee-b2ebafba7ddf": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.018271046s
    STEP: Saw pod success
    Sep  3 09:18:34.377: INFO: Pod "pod-d6bf58ec-e038-47fd-80ee-b2ebafba7ddf" satisfied condition "Succeeded or Failed"

    Sep  3 09:18:34.381: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod pod-d6bf58ec-e038-47fd-80ee-b2ebafba7ddf container test-container: <nil>
    STEP: delete the pod
    Sep  3 09:18:34.401: INFO: Waiting for pod pod-d6bf58ec-e038-47fd-80ee-b2ebafba7ddf to disappear
    Sep  3 09:18:34.405: INFO: Pod pod-d6bf58ec-e038-47fd-80ee-b2ebafba7ddf 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
    Sep  3 09:18:34.405: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-4756" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0777,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":18,"skipped":244,"failed":0}

    
    S
    ------------------------------
    [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
    Sep  3 09:18:34.425: 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 name, namespace and IP address 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
    Sep  3 09:18:34.487: INFO: Waiting up to 5m0s for pod "downward-api-bd2d6e00-b8d1-4519-8be3-03c0fc580f23" in namespace "downward-api-4621" to be "Succeeded or Failed"

    Sep  3 09:18:34.495: INFO: Pod "downward-api-bd2d6e00-b8d1-4519-8be3-03c0fc580f23": Phase="Pending", Reason="", readiness=false. Elapsed: 7.180281ms
    Sep  3 09:18:36.500: INFO: Pod "downward-api-bd2d6e00-b8d1-4519-8be3-03c0fc580f23": Phase="Pending", Reason="", readiness=false. Elapsed: 2.01304874s
    Sep  3 09:18:38.507: INFO: Pod "downward-api-bd2d6e00-b8d1-4519-8be3-03c0fc580f23": Phase="Pending", Reason="", readiness=false. Elapsed: 4.019274429s
    Sep  3 09:18:40.515: INFO: Pod "downward-api-bd2d6e00-b8d1-4519-8be3-03c0fc580f23": Phase="Succeeded", Reason="", readiness=false. Elapsed: 6.027863188s
    STEP: Saw pod success
    Sep  3 09:18:40.515: INFO: Pod "downward-api-bd2d6e00-b8d1-4519-8be3-03c0fc580f23" satisfied condition "Succeeded or Failed"

    Sep  3 09:18:40.522: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod downward-api-bd2d6e00-b8d1-4519-8be3-03c0fc580f23 container dapi-container: <nil>
    STEP: delete the pod
    Sep  3 09:18:40.551: INFO: Waiting for pod downward-api-bd2d6e00-b8d1-4519-8be3-03c0fc580f23 to disappear
    Sep  3 09:18:40.558: INFO: Pod downward-api-bd2d6e00-b8d1-4519-8be3-03c0fc580f23 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
    Sep  3 09:18:40.558: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-4621" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Downward API should provide pod name, namespace and IP address as env vars [NodeConformance] [Conformance]","total":-1,"completed":19,"skipped":245,"failed":0}

    
    SSSS
    ------------------------------
    [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 23 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:19:00.745: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-8240" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should list, patch and delete a collection of StatefulSets [Conformance]","total":-1,"completed":20,"skipped":249,"failed":0}

    
    S
    ------------------------------
    [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
    Sep  3 09:19:09.938: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "prestop-617" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] PreStop should call prestop when killing a pod  [Conformance]","total":-1,"completed":21,"skipped":250,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:19:15.396: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "init-container-2935" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] InitContainer [NodeConformance] should invoke init containers on a RestartNever pod [Conformance]","total":-1,"completed":22,"skipped":261,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 30 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:19:26.694: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-9382" 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":23,"skipped":325,"failed":0}

    
    SSSSSSS
    ------------------------------
    [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
    Sep  3 09:19:26.733: 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
    Sep  3 09:19:26.795: INFO: Waiting up to 5m0s for pod "client-containers-776a2fa7-954b-4c72-8785-357ba277354f" in namespace "containers-1346" to be "Succeeded or Failed"

    Sep  3 09:19:26.802: INFO: Pod "client-containers-776a2fa7-954b-4c72-8785-357ba277354f": Phase="Pending", Reason="", readiness=false. Elapsed: 6.563662ms
    Sep  3 09:19:28.810: INFO: Pod "client-containers-776a2fa7-954b-4c72-8785-357ba277354f": Phase="Pending", Reason="", readiness=false. Elapsed: 2.014654463s
    Sep  3 09:19:30.816: INFO: Pod "client-containers-776a2fa7-954b-4c72-8785-357ba277354f": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.020176756s
    STEP: Saw pod success
    Sep  3 09:19:30.816: INFO: Pod "client-containers-776a2fa7-954b-4c72-8785-357ba277354f" satisfied condition "Succeeded or Failed"

    Sep  3 09:19:30.819: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod client-containers-776a2fa7-954b-4c72-8785-357ba277354f container agnhost-container: <nil>
    STEP: delete the pod
    Sep  3 09:19:30.857: INFO: Waiting for pod client-containers-776a2fa7-954b-4c72-8785-357ba277354f to disappear
    Sep  3 09:19:30.863: INFO: Pod client-containers-776a2fa7-954b-4c72-8785-357ba277354f 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
    Sep  3 09:19:30.863: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "containers-1346" 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":24,"skipped":332,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 64 lines ...
    STEP: Destroying namespace "services-7749" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to switch session affinity for service with type clusterIP [LinuxOnly] [Conformance]","total":-1,"completed":25,"skipped":358,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:19:41.094: 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
    Sep  3 09:19:41.149: INFO: Waiting up to 5m0s for pod "client-containers-b394631f-52e9-4ab1-9d5e-eda57ab549a0" in namespace "containers-3068" to be "Succeeded or Failed"

    Sep  3 09:19:41.154: INFO: Pod "client-containers-b394631f-52e9-4ab1-9d5e-eda57ab549a0": Phase="Pending", Reason="", readiness=false. Elapsed: 4.876148ms
    Sep  3 09:19:43.161: INFO: Pod "client-containers-b394631f-52e9-4ab1-9d5e-eda57ab549a0": Phase="Pending", Reason="", readiness=false. Elapsed: 2.011224679s
    Sep  3 09:19:45.167: INFO: Pod "client-containers-b394631f-52e9-4ab1-9d5e-eda57ab549a0": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.017737925s
    STEP: Saw pod success
    Sep  3 09:19:45.167: INFO: Pod "client-containers-b394631f-52e9-4ab1-9d5e-eda57ab549a0" satisfied condition "Succeeded or Failed"

    Sep  3 09:19:45.172: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod client-containers-b394631f-52e9-4ab1-9d5e-eda57ab549a0 container agnhost-container: <nil>
    STEP: delete the pod
    Sep  3 09:19:45.197: INFO: Waiting for pod client-containers-b394631f-52e9-4ab1-9d5e-eda57ab549a0 to disappear
    Sep  3 09:19:45.201: INFO: Pod client-containers-b394631f-52e9-4ab1-9d5e-eda57ab549a0 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
    Sep  3 09:19:45.201: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "containers-3068" 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":26,"skipped":369,"failed":0}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:20:07.415: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-probe-9187" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Probing container should be restarted with a /healthz http liveness probe [NodeConformance] [Conformance]","total":-1,"completed":27,"skipped":383,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:20:29.602: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-probe-4446" 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":28,"skipped":416,"failed":0}

    
    SSS
    ------------------------------
    [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:752
    [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-8719
    STEP: waiting up to 3m0s for service multi-endpoint-test in namespace services-8719 to expose endpoints map[]
    Sep  3 09:20:29.718: INFO: Failed go get Endpoints object: endpoints "multi-endpoint-test" not found

    Sep  3 09:20:30.731: INFO: successfully validated that service multi-endpoint-test in namespace services-8719 exposes endpoints map[]
    STEP: Creating pod pod1 in namespace services-8719
    Sep  3 09:20:30.753: INFO: The status of Pod pod1 is Pending, waiting for it to be Running (with Ready = true)
    Sep  3 09:20:32.759: INFO: The status of Pod pod1 is Running (Ready = true)
    STEP: waiting up to 3m0s for service multi-endpoint-test in namespace services-8719 to expose endpoints map[pod1:[100]]
    Sep  3 09:20:32.780: INFO: successfully validated that service multi-endpoint-test in namespace services-8719 exposes endpoints map[pod1:[100]]
... skipping 28 lines ...
    STEP: Destroying namespace "services-8719" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should serve multiport endpoints from pods  [Conformance]","total":-1,"completed":29,"skipped":419,"failed":0}

    
    SS
    ------------------------------
    [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
    Sep  3 09:20:40.319: 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
    Sep  3 09:20:40.435: INFO: Waiting up to 5m0s for pod "pod-ac5ab7f4-8689-48a6-aec5-97a4f728eab2" in namespace "emptydir-4020" to be "Succeeded or Failed"

    Sep  3 09:20:40.443: INFO: Pod "pod-ac5ab7f4-8689-48a6-aec5-97a4f728eab2": Phase="Pending", Reason="", readiness=false. Elapsed: 7.750075ms
    Sep  3 09:20:42.449: INFO: Pod "pod-ac5ab7f4-8689-48a6-aec5-97a4f728eab2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.014320161s
    Sep  3 09:20:44.456: INFO: Pod "pod-ac5ab7f4-8689-48a6-aec5-97a4f728eab2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.02144921s
    STEP: Saw pod success
    Sep  3 09:20:44.457: INFO: Pod "pod-ac5ab7f4-8689-48a6-aec5-97a4f728eab2" satisfied condition "Succeeded or Failed"

    Sep  3 09:20:44.461: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-ac5ab7f4-8689-48a6-aec5-97a4f728eab2 container test-container: <nil>
    STEP: delete the pod
    Sep  3 09:20:44.489: INFO: Waiting for pod pod-ac5ab7f4-8689-48a6-aec5-97a4f728eab2 to disappear
    Sep  3 09:20:44.493: INFO: Pod pod-ac5ab7f4-8689-48a6-aec5-97a4f728eab2 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
    Sep  3 09:20:44.493: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-4020" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0644,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":30,"skipped":421,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 37 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:20:45.955: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "gc-3598" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Garbage collector should delete RS created by deployment when not orphaning [Conformance]","total":-1,"completed":31,"skipped":452,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 43 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:21:15.121: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pod-network-test-283" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Networking Granular Checks: Pods should function for node-pod communication: udp [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":32,"skipped":507,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-storage] Projected secret
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep  3 09:21:15.198: 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 projection with secret that has name projected-secret-test-map-d90f4f76-329f-4636-b0d7-e160f5e92e7e
    STEP: Creating a pod to test consume secrets
    Sep  3 09:21:15.277: INFO: Waiting up to 5m0s for pod "pod-projected-secrets-0a2dc333-7499-4493-9893-f02a12523d5a" in namespace "projected-5743" to be "Succeeded or Failed"

    Sep  3 09:21:15.281: INFO: Pod "pod-projected-secrets-0a2dc333-7499-4493-9893-f02a12523d5a": Phase="Pending", Reason="", readiness=false. Elapsed: 4.035701ms
    Sep  3 09:21:17.288: INFO: Pod "pod-projected-secrets-0a2dc333-7499-4493-9893-f02a12523d5a": Phase="Pending", Reason="", readiness=false. Elapsed: 2.010447809s
    Sep  3 09:21:19.294: INFO: Pod "pod-projected-secrets-0a2dc333-7499-4493-9893-f02a12523d5a": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.017120162s
    STEP: Saw pod success
    Sep  3 09:21:19.295: INFO: Pod "pod-projected-secrets-0a2dc333-7499-4493-9893-f02a12523d5a" satisfied condition "Succeeded or Failed"

    Sep  3 09:21:19.299: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-projected-secrets-0a2dc333-7499-4493-9893-f02a12523d5a container projected-secret-volume-test: <nil>
    STEP: delete the pod
    Sep  3 09:21:19.333: INFO: Waiting for pod pod-projected-secrets-0a2dc333-7499-4493-9893-f02a12523d5a to disappear
    Sep  3 09:21:19.340: INFO: Pod pod-projected-secrets-0a2dc333-7499-4493-9893-f02a12523d5a 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
    Sep  3 09:21:19.340: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-5743" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected secret should be consumable from pods in volume with mappings and Item Mode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":33,"skipped":529,"failed":0}

    
    SS
    ------------------------------
    [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
    Sep  3 09:21:19.358: 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] ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    Sep  3 09:21:19.432: INFO: created pod
    Sep  3 09:21:19.432: INFO: Waiting up to 5m0s for pod "oidc-discovery-validator" in namespace "svcaccounts-155" to be "Succeeded or Failed"

    Sep  3 09:21:19.437: INFO: Pod "oidc-discovery-validator": Phase="Pending", Reason="", readiness=false. Elapsed: 4.771842ms
    Sep  3 09:21:21.445: INFO: Pod "oidc-discovery-validator": Phase="Pending", Reason="", readiness=false. Elapsed: 2.012975337s
    Sep  3 09:21:23.452: INFO: Pod "oidc-discovery-validator": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.019547141s
    STEP: Saw pod success
    Sep  3 09:21:23.452: INFO: Pod "oidc-discovery-validator" satisfied condition "Succeeded or Failed"

    Sep  3 09:21:53.453: INFO: polling logs
    Sep  3 09:21:53.462: INFO: Pod logs: 
    I0903 09:21:20.461723       1 log.go:195] OK: Got token
    I0903 09:21:20.461877       1 log.go:195] validating with in-cluster discovery
    I0903 09:21:20.467675       1 log.go:195] OK: got issuer https://kubernetes.default.svc.cluster.local
    I0903 09:21:20.467728       1 log.go:195] Full, not-validated claims: 
... skipping 9 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:21:53.475: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "svcaccounts-155" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-auth] ServiceAccounts ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance]","total":-1,"completed":34,"skipped":531,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:21:53.692: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "watch-5466" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Watchers should be able to start watching from a specific resource version [Conformance]","total":-1,"completed":35,"skipped":576,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:21:53.754: 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-f972aaf2-38dc-4664-9113-352be5d123f9
    STEP: Creating a pod to test consume configMaps
    Sep  3 09:21:53.814: INFO: Waiting up to 5m0s for pod "pod-configmaps-782919a1-19c1-42c6-95b8-e852e1bf4aee" in namespace "configmap-2827" to be "Succeeded or Failed"

    Sep  3 09:21:53.822: INFO: Pod "pod-configmaps-782919a1-19c1-42c6-95b8-e852e1bf4aee": Phase="Pending", Reason="", readiness=false. Elapsed: 7.485519ms
    Sep  3 09:21:55.827: INFO: Pod "pod-configmaps-782919a1-19c1-42c6-95b8-e852e1bf4aee": Phase="Pending", Reason="", readiness=false. Elapsed: 2.013048544s
    Sep  3 09:21:57.836: INFO: Pod "pod-configmaps-782919a1-19c1-42c6-95b8-e852e1bf4aee": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.021705483s
    STEP: Saw pod success
    Sep  3 09:21:57.836: INFO: Pod "pod-configmaps-782919a1-19c1-42c6-95b8-e852e1bf4aee" satisfied condition "Succeeded or Failed"

    Sep  3 09:21:57.843: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-configmaps-782919a1-19c1-42c6-95b8-e852e1bf4aee container agnhost-container: <nil>
    STEP: delete the pod
    Sep  3 09:21:57.867: INFO: Waiting for pod pod-configmaps-782919a1-19c1-42c6-95b8-e852e1bf4aee to disappear
    Sep  3 09:21:57.873: INFO: Pod pod-configmaps-782919a1-19c1-42c6-95b8-e852e1bf4aee 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
    Sep  3 09:21:57.873: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-2827" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume [NodeConformance] [Conformance]","total":-1,"completed":36,"skipped":596,"failed":0}

    
    SSSSSSSSSSSSSSSS
    ------------------------------
    [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 7 lines ...
    STEP: Creating replication controller my-hostname-basic-9ad76203-c46d-4108-a611-8f603c5cb76d
    Sep  3 09:14:51.460: INFO: Pod name my-hostname-basic-9ad76203-c46d-4108-a611-8f603c5cb76d: Found 0 pods out of 1
    Sep  3 09:14:56.464: INFO: Pod name my-hostname-basic-9ad76203-c46d-4108-a611-8f603c5cb76d: Found 1 pods out of 1
    Sep  3 09:14:56.464: INFO: Ensuring all pods for ReplicationController "my-hostname-basic-9ad76203-c46d-4108-a611-8f603c5cb76d" are running
    Sep  3 09:14:56.466: INFO: Pod "my-hostname-basic-9ad76203-c46d-4108-a611-8f603c5cb76d-vmcr8" is running (conditions: [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-09-03 09:14:51 +0000 UTC Reason: Message:} {Type:Ready Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-09-03 09:14:52 +0000 UTC Reason: Message:} {Type:ContainersReady Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-09-03 09:14:52 +0000 UTC Reason: Message:} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2022-09-03 09:14:51 +0000 UTC Reason: Message:}])
    Sep  3 09:14:56.466: INFO: Trying to dial the pod
    Sep  3 09:18:35.527: INFO: Controller my-hostname-basic-9ad76203-c46d-4108-a611-8f603c5cb76d: Failed to GET from replica 1 [my-hostname-basic-9ad76203-c46d-4108-a611-8f603c5cb76d-vmcr8]: the server is currently unable to handle the request (get pods my-hostname-basic-9ad76203-c46d-4108-a611-8f603c5cb76d-vmcr8)

    pod status: v1.PodStatus{Phase:"Running", Conditions:[]v1.PodCondition{v1.PodCondition{Type:"Initialized", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63797793291, loc:(*time.Location)(0xa04a040)}}, Reason:"", Message:""}, v1.PodCondition{Type:"Ready", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63797793292, loc:(*time.Location)(0xa04a040)}}, Reason:"", Message:""}, v1.PodCondition{Type:"ContainersReady", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63797793292, loc:(*time.Location)(0xa04a040)}}, Reason:"", Message:""}, v1.PodCondition{Type:"PodScheduled", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63797793291, loc:(*time.Location)(0xa04a040)}}, Reason:"", Message:""}}, Message:"", Reason:"", NominatedNodeName:"", HostIP:"172.18.0.6", PodIP:"192.168.2.5", PodIPs:[]v1.PodIP{v1.PodIP{IP:"192.168.2.5"}}, StartTime:(*v1.Time)(0xc003b6c4e0), InitContainerStatuses:[]v1.ContainerStatus(nil), ContainerStatuses:[]v1.ContainerStatus{v1.ContainerStatus{Name:"my-hostname-basic-9ad76203-c46d-4108-a611-8f603c5cb76d", State:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(0xc003b6c4f8), Terminated:(*v1.ContainerStateTerminated)(nil)}, LastTerminationState:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(nil), Terminated:(*v1.ContainerStateTerminated)(nil)}, Ready:true, RestartCount:0, Image:"k8s.gcr.io/e2e-test-images/agnhost:2.39", ImageID:"k8s.gcr.io/e2e-test-images/agnhost@sha256:7e8bdd271312fd25fc5ff5a8f04727be84044eb3d7d8d03611972a6752e2e11e", ContainerID:"containerd://3bdb79988a81296fedcbe4753f02ec36d4e5f8f473a6bafbb6c05032708333af", Started:(*bool)(0xc003b44cea)}}, QOSClass:"BestEffort", EphemeralContainerStatuses:[]v1.ContainerStatus(nil)}
    Sep  3 09:22:08.523: INFO: Controller my-hostname-basic-9ad76203-c46d-4108-a611-8f603c5cb76d: Failed to GET from replica 1 [my-hostname-basic-9ad76203-c46d-4108-a611-8f603c5cb76d-vmcr8]: the server is currently unable to handle the request (get pods my-hostname-basic-9ad76203-c46d-4108-a611-8f603c5cb76d-vmcr8)

    pod status: v1.PodStatus{Phase:"Running", Conditions:[]v1.PodCondition{v1.PodCondition{Type:"Initialized", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63797793291, loc:(*time.Location)(0xa04a040)}}, Reason:"", Message:""}, v1.PodCondition{Type:"Ready", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63797793292, loc:(*time.Location)(0xa04a040)}}, Reason:"", Message:""}, v1.PodCondition{Type:"ContainersReady", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63797793292, loc:(*time.Location)(0xa04a040)}}, Reason:"", Message:""}, v1.PodCondition{Type:"PodScheduled", Status:"True", LastProbeTime:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63797793291, loc:(*time.Location)(0xa04a040)}}, Reason:"", Message:""}}, Message:"", Reason:"", NominatedNodeName:"", HostIP:"172.18.0.6", PodIP:"192.168.2.5", PodIPs:[]v1.PodIP{v1.PodIP{IP:"192.168.2.5"}}, StartTime:(*v1.Time)(0xc003b6c4e0), InitContainerStatuses:[]v1.ContainerStatus(nil), ContainerStatuses:[]v1.ContainerStatus{v1.ContainerStatus{Name:"my-hostname-basic-9ad76203-c46d-4108-a611-8f603c5cb76d", State:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(0xc003b6c4f8), Terminated:(*v1.ContainerStateTerminated)(nil)}, LastTerminationState:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(nil), Terminated:(*v1.ContainerStateTerminated)(nil)}, Ready:true, RestartCount:0, Image:"k8s.gcr.io/e2e-test-images/agnhost:2.39", ImageID:"k8s.gcr.io/e2e-test-images/agnhost@sha256:7e8bdd271312fd25fc5ff5a8f04727be84044eb3d7d8d03611972a6752e2e11e", ContainerID:"containerd://3bdb79988a81296fedcbe4753f02ec36d4e5f8f473a6bafbb6c05032708333af", Started:(*bool)(0xc003b44cea)}}, QOSClass:"BestEffort", EphemeralContainerStatuses:[]v1.ContainerStatus(nil)}
    Sep  3 09:22:08.523: FAIL: Did not get expected responses within the timeout period of 120.00 seconds.

    
    Full Stack Trace
    k8s.io/kubernetes/test/e2e/apps.glob..func7.2()
    	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/rc.go:65 +0x57
    k8s.io/kubernetes/test/e2e.RunE2ETests(0xc000223200)
    	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c
... skipping 16 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    
      Sep  3 09:22:08.524: Did not get expected responses within the timeout period of 120.00 seconds.
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/rc.go:65
    ------------------------------
    {"msg":"FAILED [sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","total":-1,"completed":2,"skipped":52,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    [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
    Sep  3 09:22:08.542: 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 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:22:18.632: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replication-controller-6617" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","total":-1,"completed":3,"skipped":52,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:22:18.827: INFO: Waiting up to 5m0s for pod "downwardapi-volume-c3b27cfa-e4c0-4752-8d57-ff964d16c061" in namespace "projected-2209" to be "Succeeded or Failed"

    Sep  3 09:22:18.830: INFO: Pod "downwardapi-volume-c3b27cfa-e4c0-4752-8d57-ff964d16c061": Phase="Pending", Reason="", readiness=false. Elapsed: 3.005452ms
    Sep  3 09:22:20.836: INFO: Pod "downwardapi-volume-c3b27cfa-e4c0-4752-8d57-ff964d16c061": Phase="Running", Reason="", readiness=false. Elapsed: 2.009024066s
    Sep  3 09:22:22.842: INFO: Pod "downwardapi-volume-c3b27cfa-e4c0-4752-8d57-ff964d16c061": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.01523249s
    STEP: Saw pod success
    Sep  3 09:22:22.843: INFO: Pod "downwardapi-volume-c3b27cfa-e4c0-4752-8d57-ff964d16c061" satisfied condition "Succeeded or Failed"

    Sep  3 09:22:22.847: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-wggvfg pod downwardapi-volume-c3b27cfa-e4c0-4752-8d57-ff964d16c061 container client-container: <nil>
    STEP: delete the pod
    Sep  3 09:22:22.876: INFO: Waiting for pod downwardapi-volume-c3b27cfa-e4c0-4752-8d57-ff964d16c061 to disappear
    Sep  3 09:22:22.879: INFO: Pod downwardapi-volume-c3b27cfa-e4c0-4752-8d57-ff964d16c061 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
    Sep  3 09:22:22.880: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-2209" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should set mode on item file [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":4,"skipped":101,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 101 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:23:09.917: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-6685" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Scaling should happen in predictable order and halt if any stateful pod is unhealthy [Slow] [Conformance]","total":-1,"completed":37,"skipped":612,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 7 lines ...
    STEP: Create set of pods
    Sep  3 09:23:09.981: INFO: created test-pod-1
    Sep  3 09:23:09.984: INFO: created test-pod-2
    Sep  3 09:23:09.991: INFO: created test-pod-3
    STEP: waiting for all 3 pods to be running
    Sep  3 09:23:09.991: INFO: Waiting up to 5m0s for all pods (need at least 3) in namespace 'pods-9579' to be running and ready
    Sep  3 09:23:10.003: INFO: The status of Pod test-pod-1 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  3 09:23:10.003: INFO: The status of Pod test-pod-2 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  3 09:23:10.003: INFO: The status of Pod test-pod-3 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Sep  3 09:23:10.003: INFO: 0 / 3 pods in namespace 'pods-9579' are running and ready (0 seconds elapsed)
    Sep  3 09:23:10.003: INFO: expected 0 pod replicas in namespace 'pods-9579', 0 are Running and Ready.
    Sep  3 09:23:10.003: INFO: POD         NODE                                                           PHASE    GRACE  CONDITIONS
    Sep  3 09:23:10.003: INFO: test-pod-1  k8s-upgrade-and-conformance-z5d79l-worker-wggvfg               Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-09-03 09:23:09 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-09-03 09:23:09 +0000 UTC ContainersNotReady containers with unready status: [token-test]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-09-03 09:23:09 +0000 UTC ContainersNotReady containers with unready status: [token-test]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-03 09:23:09 +0000 UTC  }]
    Sep  3 09:23:10.003: INFO: test-pod-2  k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl  Pending         [{PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-03 09:23:09 +0000 UTC  }]
    Sep  3 09:23:10.003: INFO: test-pod-3  k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1               Pending         [{PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-09-03 09:23:09 +0000 UTC  }]
... skipping 8 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:23:15.029: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-9579" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should delete a collection of pods [Conformance]","total":-1,"completed":38,"skipped":634,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] ResourceQuota
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go: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
    Sep  3 09:23:15.131: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-3784" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should be able to update and delete ResourceQuota. [Conformance]","total":-1,"completed":39,"skipped":642,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 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
    Sep  3 09:23:15.251: INFO: Waiting up to 5m0s for pod "downwardapi-volume-28e54b82-44b2-448f-8e58-94a9e5ceea80" in namespace "downward-api-848" to be "Succeeded or Failed"

    Sep  3 09:23:15.256: INFO: Pod "downwardapi-volume-28e54b82-44b2-448f-8e58-94a9e5ceea80": Phase="Pending", Reason="", readiness=false. Elapsed: 5.540332ms
    Sep  3 09:23:17.260: INFO: Pod "downwardapi-volume-28e54b82-44b2-448f-8e58-94a9e5ceea80": Phase="Running", Reason="", readiness=false. Elapsed: 2.009357706s
    Sep  3 09:23:19.264: INFO: Pod "downwardapi-volume-28e54b82-44b2-448f-8e58-94a9e5ceea80": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.013471398s
    STEP: Saw pod success
    Sep  3 09:23:19.264: INFO: Pod "downwardapi-volume-28e54b82-44b2-448f-8e58-94a9e5ceea80" satisfied condition "Succeeded or Failed"

    Sep  3 09:23:19.266: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-wggvfg pod downwardapi-volume-28e54b82-44b2-448f-8e58-94a9e5ceea80 container client-container: <nil>
    STEP: delete the pod
    Sep  3 09:23:19.280: INFO: Waiting for pod downwardapi-volume-28e54b82-44b2-448f-8e58-94a9e5ceea80 to disappear
    Sep  3 09:23:19.282: INFO: Pod downwardapi-volume-28e54b82-44b2-448f-8e58-94a9e5ceea80 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
    Sep  3 09:23:19.282: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-848" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should provide container's memory limit [NodeConformance] [Conformance]","total":-1,"completed":40,"skipped":677,"failed":0}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep  3 09:23:19.296: 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
    Sep  3 09:23:19.330: INFO: Waiting up to 5m0s for pod "pod-ea88de03-820c-432b-ac1d-bc921e3b988b" in namespace "emptydir-2981" to be "Succeeded or Failed"

    Sep  3 09:23:19.335: INFO: Pod "pod-ea88de03-820c-432b-ac1d-bc921e3b988b": Phase="Pending", Reason="", readiness=false. Elapsed: 5.194317ms
    Sep  3 09:23:21.339: INFO: Pod "pod-ea88de03-820c-432b-ac1d-bc921e3b988b": Phase="Running", Reason="", readiness=false. Elapsed: 2.009369653s
    Sep  3 09:23:23.345: INFO: Pod "pod-ea88de03-820c-432b-ac1d-bc921e3b988b": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.015024996s
    STEP: Saw pod success
    Sep  3 09:23:23.345: INFO: Pod "pod-ea88de03-820c-432b-ac1d-bc921e3b988b" satisfied condition "Succeeded or Failed"

    Sep  3 09:23:23.348: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-wggvfg pod pod-ea88de03-820c-432b-ac1d-bc921e3b988b container test-container: <nil>
    STEP: delete the pod
    Sep  3 09:23:23.364: INFO: Waiting for pod pod-ea88de03-820c-432b-ac1d-bc921e3b988b to disappear
    Sep  3 09:23:23.366: INFO: Pod pod-ea88de03-820c-432b-ac1d-bc921e3b988b 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
    Sep  3 09:23:23.366: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-2981" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (non-root,0666,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":41,"skipped":682,"failed":0}

    
    SSSSSS
    ------------------------------
    [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
    Sep  3 09:23:23.384: 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-3456/configmap-test-051b86a2-85bc-47ee-9ad8-8b854791ed70
    STEP: Creating a pod to test consume configMaps
    Sep  3 09:23:23.440: INFO: Waiting up to 5m0s for pod "pod-configmaps-ea2fdcb0-d5ec-4152-931c-56be2db9fa32" in namespace "configmap-3456" to be "Succeeded or Failed"

    Sep  3 09:23:23.447: INFO: Pod "pod-configmaps-ea2fdcb0-d5ec-4152-931c-56be2db9fa32": Phase="Pending", Reason="", readiness=false. Elapsed: 6.729275ms
    Sep  3 09:23:25.450: INFO: Pod "pod-configmaps-ea2fdcb0-d5ec-4152-931c-56be2db9fa32": Phase="Pending", Reason="", readiness=false. Elapsed: 2.010584366s
    Sep  3 09:23:27.455: INFO: Pod "pod-configmaps-ea2fdcb0-d5ec-4152-931c-56be2db9fa32": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.014864246s
    STEP: Saw pod success
    Sep  3 09:23:27.455: INFO: Pod "pod-configmaps-ea2fdcb0-d5ec-4152-931c-56be2db9fa32" satisfied condition "Succeeded or Failed"

    Sep  3 09:23:27.457: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-wggvfg pod pod-configmaps-ea2fdcb0-d5ec-4152-931c-56be2db9fa32 container env-test: <nil>
    STEP: delete the pod
    Sep  3 09:23:27.469: INFO: Waiting for pod pod-configmaps-ea2fdcb0-d5ec-4152-931c-56be2db9fa32 to disappear
    Sep  3 09:23:27.471: INFO: Pod pod-configmaps-ea2fdcb0-d5ec-4152-931c-56be2db9fa32 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
    Sep  3 09:23:27.471: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-3456" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] ConfigMap should be consumable via environment variable [NodeConformance] [Conformance]","total":-1,"completed":42,"skipped":688,"failed":0}

    
    SSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:23:37.557: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "watch-4874" 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":43,"skipped":701,"failed":0}

    
    SSS
    ------------------------------
    [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 24 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:23:37.666: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "cronjob-5533" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] CronJob should support CronJob API operations [Conformance]","total":-1,"completed":44,"skipped":704,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 15 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:23:43.871: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-4991" 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":25,"skipped":392,"failed":0}

    [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
    Sep  3 09:19:18.857: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename cronjob
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 12 lines ...
    • [SLOW TEST:300.071 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":26,"skipped":392,"failed":0}

    
    SSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:24:24.009: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "replicaset-4997" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] ReplicaSet Replicaset should have a working scale subresource [Conformance]","total":-1,"completed":27,"skipped":404,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:24:24.088: 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
    Sep  3 09:24:24.121: INFO: Waiting up to 5m0s for pod "security-context-a0fb17b0-8b63-47c7-a6cc-c9caf26998fc" in namespace "security-context-4587" to be "Succeeded or Failed"

    Sep  3 09:24:24.124: INFO: Pod "security-context-a0fb17b0-8b63-47c7-a6cc-c9caf26998fc": Phase="Pending", Reason="", readiness=false. Elapsed: 3.030896ms
    Sep  3 09:24:26.129: INFO: Pod "security-context-a0fb17b0-8b63-47c7-a6cc-c9caf26998fc": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007299196s
    Sep  3 09:24:28.134: INFO: Pod "security-context-a0fb17b0-8b63-47c7-a6cc-c9caf26998fc": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.012297483s
    STEP: Saw pod success
    Sep  3 09:24:28.134: INFO: Pod "security-context-a0fb17b0-8b63-47c7-a6cc-c9caf26998fc" satisfied condition "Succeeded or Failed"

    Sep  3 09:24:28.136: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod security-context-a0fb17b0-8b63-47c7-a6cc-c9caf26998fc container test-container: <nil>
    STEP: delete the pod
    Sep  3 09:24:28.157: INFO: Waiting for pod security-context-a0fb17b0-8b63-47c7-a6cc-c9caf26998fc to disappear
    Sep  3 09:24:28.159: INFO: Pod security-context-a0fb17b0-8b63-47c7-a6cc-c9caf26998fc 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
    Sep  3 09:24:28.159: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "security-context-4587" 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":28,"skipped":441,"failed":0}

    [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
    Sep  3 09:24:28.167: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename subpath
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] Atomic writer volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/subpath.go:38
    STEP: Setting up data
    [It] should support subpaths with downward pod [LinuxOnly] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating pod pod-subpath-test-downwardapi-8s7q
    STEP: Creating a pod to test atomic-volume-subpath
    Sep  3 09:24:28.203: INFO: Waiting up to 5m0s for pod "pod-subpath-test-downwardapi-8s7q" in namespace "subpath-6350" to be "Succeeded or Failed"

    Sep  3 09:24:28.205: INFO: Pod "pod-subpath-test-downwardapi-8s7q": Phase="Pending", Reason="", readiness=false. Elapsed: 2.014448ms
    Sep  3 09:24:30.209: INFO: Pod "pod-subpath-test-downwardapi-8s7q": Phase="Running", Reason="", readiness=true. Elapsed: 2.00594185s
    Sep  3 09:24:32.214: INFO: Pod "pod-subpath-test-downwardapi-8s7q": Phase="Running", Reason="", readiness=true. Elapsed: 4.010254927s
    Sep  3 09:24:34.217: INFO: Pod "pod-subpath-test-downwardapi-8s7q": Phase="Running", Reason="", readiness=true. Elapsed: 6.013746653s
    Sep  3 09:24:36.222: INFO: Pod "pod-subpath-test-downwardapi-8s7q": Phase="Running", Reason="", readiness=true. Elapsed: 8.018476028s
    Sep  3 09:24:38.226: INFO: Pod "pod-subpath-test-downwardapi-8s7q": Phase="Running", Reason="", readiness=true. Elapsed: 10.023124291s
... skipping 2 lines ...
    Sep  3 09:24:44.238: INFO: Pod "pod-subpath-test-downwardapi-8s7q": Phase="Running", Reason="", readiness=true. Elapsed: 16.03481549s
    Sep  3 09:24:46.243: INFO: Pod "pod-subpath-test-downwardapi-8s7q": Phase="Running", Reason="", readiness=true. Elapsed: 18.039610733s
    Sep  3 09:24:48.248: INFO: Pod "pod-subpath-test-downwardapi-8s7q": Phase="Running", Reason="", readiness=true. Elapsed: 20.04424302s
    Sep  3 09:24:50.252: INFO: Pod "pod-subpath-test-downwardapi-8s7q": Phase="Running", Reason="", readiness=false. Elapsed: 22.048573355s
    Sep  3 09:24:52.257: INFO: Pod "pod-subpath-test-downwardapi-8s7q": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.053556642s
    STEP: Saw pod success
    Sep  3 09:24:52.257: INFO: Pod "pod-subpath-test-downwardapi-8s7q" satisfied condition "Succeeded or Failed"

    Sep  3 09:24:52.260: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod pod-subpath-test-downwardapi-8s7q container test-container-subpath-downwardapi-8s7q: <nil>
    STEP: delete the pod
    Sep  3 09:24:52.272: INFO: Waiting for pod pod-subpath-test-downwardapi-8s7q to disappear
    Sep  3 09:24:52.275: INFO: Pod pod-subpath-test-downwardapi-8s7q no longer exists
    STEP: Deleting pod pod-subpath-test-downwardapi-8s7q
    Sep  3 09:24:52.275: INFO: Deleting pod "pod-subpath-test-downwardapi-8s7q" in namespace "subpath-6350"
    [AfterEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:24:52.277: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "subpath-6350" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Subpath Atomic writer volumes should support subpaths with downward pod [LinuxOnly] [Conformance]","total":-1,"completed":29,"skipped":441,"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 15 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:24:52.344: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-9335" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-instrumentation] Events should delete a collection of events [Conformance]","total":-1,"completed":30,"skipped":449,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:24:52.418: 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-fd8bf94d-8ab3-4e7c-bd59-62fcfc9c507e
    [AfterEach] [sig-node] Secrets
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:24:52.446: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-5840" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Secrets should fail to create secret due to empty secret key [Conformance]","total":-1,"completed":31,"skipped":508,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:24:54.618: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-5752" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment RecreateDeployment should delete old pods and create new ones [Conformance]","total":-1,"completed":32,"skipped":558,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:24:54.648: 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 host IP as an env var [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
    Sep  3 09:24:54.676: INFO: Waiting up to 5m0s for pod "downward-api-671131db-d520-40d5-8023-9a06a1b50e76" in namespace "downward-api-343" to be "Succeeded or Failed"

    Sep  3 09:24:54.678: INFO: Pod "downward-api-671131db-d520-40d5-8023-9a06a1b50e76": Phase="Pending", Reason="", readiness=false. Elapsed: 2.822021ms
    Sep  3 09:24:56.683: INFO: Pod "downward-api-671131db-d520-40d5-8023-9a06a1b50e76": Phase="Pending", Reason="", readiness=false. Elapsed: 2.006990176s
    Sep  3 09:24:58.686: INFO: Pod "downward-api-671131db-d520-40d5-8023-9a06a1b50e76": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.010614094s
    STEP: Saw pod success
    Sep  3 09:24:58.686: INFO: Pod "downward-api-671131db-d520-40d5-8023-9a06a1b50e76" satisfied condition "Succeeded or Failed"

    Sep  3 09:24:58.689: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-wggvfg pod downward-api-671131db-d520-40d5-8023-9a06a1b50e76 container dapi-container: <nil>
    STEP: delete the pod
    Sep  3 09:24:58.705: INFO: Waiting for pod downward-api-671131db-d520-40d5-8023-9a06a1b50e76 to disappear
    Sep  3 09:24:58.708: INFO: Pod downward-api-671131db-d520-40d5-8023-9a06a1b50e76 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
    Sep  3 09:24:58.708: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-343" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Downward API should provide host IP as an env var [NodeConformance] [Conformance]","total":-1,"completed":33,"skipped":578,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Sysctls [LinuxOnly] [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/sysctl.go:36
    [BeforeEach] [sig-node] Sysctls [LinuxOnly] [NodeConformance]
... skipping 4 lines ...
    STEP: Waiting for a default service account to be provisioned in namespace
    [BeforeEach] [sig-node] Sysctls [LinuxOnly] [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/sysctl.go:65
    [It] should support sysctls [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] [NodeConformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:25:02.800: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "sysctl-2640" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Sysctls [LinuxOnly] [NodeConformance] should support sysctls [MinimumKubeletVersion:1.21] [Conformance]","total":-1,"completed":34,"skipped":605,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:25:04.688: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-5834" 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":35,"skipped":644,"failed":0}

    
    SSSSSSSSSSSSS
    ------------------------------
    [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-9945" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should complete a service status lifecycle [Conformance]","total":-1,"completed":36,"skipped":657,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:25:11.156: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "custom-resource-definition-9911" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition listing custom resource definition objects works  [Conformance]","total":-1,"completed":37,"skipped":734,"failed":0}

    
    SS
    ------------------------------
    [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 28 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:25:18.243: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-472" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment RollingUpdateDeployment should delete old pods and create new ones [Conformance]","total":-1,"completed":38,"skipped":736,"failed":0}

    
    SSSSSSSS
    ------------------------------
    [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
    Sep  3 09:25:18.351: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "podtemplate-3452" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] PodTemplates should delete a collection of pod templates [Conformance]","total":-1,"completed":39,"skipped":744,"failed":0}

    
    SSS
    ------------------------------
    [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 ...
    Sep  3 09:15:28.415: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:28.418: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:28.420: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:28.424: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:28.427: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:28.429: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:28.429: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945 wheezy_tcp@dns-test-service.dns-9945 wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945 jessie_udp@dns-test-service.dns-9945.svc jessie_tcp@dns-test-service.dns-9945.svc jessie_udp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:15:33.436: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:33.440: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:33.444: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:33.447: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:33.450: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 17 lines ...
    Sep  3 09:15:33.518: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:33.524: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:33.526: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:33.529: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:33.532: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:33.534: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:33.534: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945 wheezy_tcp@dns-test-service.dns-9945 wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945 jessie_udp@dns-test-service.dns-9945.svc jessie_tcp@dns-test-service.dns-9945.svc jessie_udp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:15:38.436: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:38.439: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:38.443: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:38.446: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:38.449: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 17 lines ...
    Sep  3 09:15:38.502: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:38.504: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:38.508: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:38.511: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:38.513: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:38.515: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:38.515: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945 wheezy_tcp@dns-test-service.dns-9945 wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945 jessie_udp@dns-test-service.dns-9945.svc jessie_tcp@dns-test-service.dns-9945.svc jessie_udp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:15:43.435: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:43.439: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:43.442: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:43.446: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:43.448: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 17 lines ...
    Sep  3 09:15:43.495: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:43.498: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:43.500: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:43.503: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:43.506: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:43.508: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:43.508: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945 wheezy_tcp@dns-test-service.dns-9945 wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945 jessie_udp@dns-test-service.dns-9945.svc jessie_tcp@dns-test-service.dns-9945.svc jessie_udp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:15:48.434: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:48.437: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:48.440: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:48.443: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:48.445: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 17 lines ...
    Sep  3 09:15:48.498: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:48.500: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:48.503: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:48.506: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:48.510: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:48.512: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:48.512: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945 wheezy_tcp@dns-test-service.dns-9945 wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945 jessie_udp@dns-test-service.dns-9945.svc jessie_tcp@dns-test-service.dns-9945.svc jessie_udp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:15:53.436: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:53.440: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:53.448: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:53.451: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:53.453: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 15 lines ...
    Sep  3 09:15:53.491: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:53.493: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:53.495: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:53.498: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:53.501: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:53.504: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:53.504: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945 jessie_udp@dns-test-service.dns-9945.svc jessie_tcp@dns-test-service.dns-9945.svc jessie_udp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:15:58.433: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:58.436: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:58.443: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:58.445: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:58.448: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 14 lines ...
    Sep  3 09:15:58.485: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:58.487: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:58.489: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:58.491: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:58.495: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:58.497: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:15:58.497: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_udp@dns-test-service.dns-9945.svc jessie_tcp@dns-test-service.dns-9945.svc jessie_udp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:16:03.435: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:03.438: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:03.447: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:03.450: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:03.452: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 14 lines ...
    Sep  3 09:16:03.492: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:03.494: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:03.497: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:03.499: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:03.501: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:03.503: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:03.503: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_udp@dns-test-service.dns-9945.svc jessie_tcp@dns-test-service.dns-9945.svc jessie_udp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:16:08.433: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:08.436: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:08.444: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:08.447: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:08.449: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 13 lines ...
    Sep  3 09:16:08.490: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:08.492: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:08.495: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:08.497: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:08.500: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:08.502: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:08.502: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_udp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:16:13.434: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:13.437: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:13.446: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:13.448: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:13.450: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 13 lines ...
    Sep  3 09:16:13.489: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:13.491: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:13.493: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:13.496: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:13.499: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:13.501: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:13.501: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_udp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:16:18.433: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:18.436: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:18.444: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:18.446: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:18.448: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 13 lines ...
    Sep  3 09:16:18.487: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:18.490: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:18.492: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:18.494: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:18.496: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:18.498: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:18.498: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_udp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:16:23.437: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:23.440: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:23.453: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:23.456: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:23.461: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 12 lines ...
    Sep  3 09:16:23.498: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:23.500: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:23.503: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:23.505: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:23.507: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:23.509: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:23.509: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_udp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:16:28.435: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:28.437: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:28.445: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:28.447: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:28.452: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 11 lines ...
    Sep  3 09:16:28.492: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:28.494: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:28.496: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:28.498: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:28.501: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:28.503: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:28.503: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9945.svc wheezy_udp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:16:33.433: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:33.438: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:33.447: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:33.450: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:33.459: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 9 lines ...
    Sep  3 09:16:33.491: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:33.493: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:33.495: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:33.497: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:33.500: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:33.502: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:33.502: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_udp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:16:38.433: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:38.439: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:38.454: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:38.457: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:38.467: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 8 lines ...
    Sep  3 09:16:38.498: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:38.503: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:38.506: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:38.508: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:38.511: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:38.513: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:38.513: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:16:43.434: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:43.437: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:43.446: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:43.448: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:43.458: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 8 lines ...
    Sep  3 09:16:43.486: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:43.491: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:43.493: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:43.496: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:43.499: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:43.501: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:43.501: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:16:48.434: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:48.437: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:48.445: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:48.447: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:48.458: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 8 lines ...
    Sep  3 09:16:48.485: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:48.490: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:48.492: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:48.494: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:48.496: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:48.499: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:48.499: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:16:53.435: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:53.439: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:53.455: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:53.458: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:53.472: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 8 lines ...
    Sep  3 09:16:53.541: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:53.553: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:53.557: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:53.561: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:53.564: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:53.570: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:53.570: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:16:58.436: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:58.438: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:58.447: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:58.450: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:58.460: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 8 lines ...
    Sep  3 09:16:58.491: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:58.496: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:58.498: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:58.501: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:58.503: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:58.505: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:16:58.505: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:17:03.433: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:03.436: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:03.445: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:03.447: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:03.457: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 7 lines ...
    Sep  3 09:17:03.486: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:03.491: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:03.494: INFO: Unable to read jessie_udp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:03.496: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:03.498: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:03.501: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:03.501: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:17:08.434: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:08.437: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:08.446: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:08.448: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:08.458: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 6 lines ...
    Sep  3 09:17:08.482: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:08.487: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:08.492: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:08.498: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:08.501: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:08.504: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:08.504: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:17:13.434: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:13.437: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:13.447: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:13.450: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:13.460: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 6 lines ...
    Sep  3 09:17:13.488: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:13.493: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:13.498: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:13.503: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:13.506: INFO: Unable to read 10.135.113.147_udp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:13.508: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:13.508: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc jessie_tcp@PodARecord 10.135.113.147_udp@PTR 10.135.113.147_tcp@PTR]

    
    Sep  3 09:17:18.435: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:18.440: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:18.455: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:18.459: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:18.470: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 3 lines ...
    Sep  3 09:17:18.490: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:18.497: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:18.503: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:18.510: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:18.516: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:18.527: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:18.527: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc 10.135.113.147_tcp@PTR]

    
    Sep  3 09:17:23.434: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:23.438: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:23.446: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:23.448: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:23.458: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 3 lines ...
    Sep  3 09:17:23.473: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:23.478: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:23.483: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:23.488: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:23.492: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:23.502: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:23.502: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc 10.135.113.147_tcp@PTR]

    
    Sep  3 09:17:28.436: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:28.439: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:28.447: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:28.449: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:28.460: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
... skipping 3 lines ...
    Sep  3 09:17:28.476: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:28.481: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:28.487: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:28.491: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:28.497: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:28.507: INFO: Unable to read 10.135.113.147_tcp@PTR from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:28.507: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord 10.135.113.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc 10.135.113.147_tcp@PTR]

    
    Sep  3 09:17:33.437: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:33.445: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:33.448: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:33.460: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:33.465: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:33.475: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:33.478: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:33.487: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:33.492: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:33.497: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:33.502: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:33.512: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:17:38.438: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:38.448: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:38.451: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:38.462: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:38.466: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:38.474: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:38.477: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:38.482: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:38.486: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:38.491: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:38.496: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:38.506: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:17:43.439: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:43.447: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:43.449: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:43.460: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:43.465: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:43.472: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:43.474: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:43.479: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945 from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:43.484: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:43.489: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:43.494: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:43.504: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9945 jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:17:48.437: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:48.446: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:48.449: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:48.461: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:48.467: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:48.488: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:48.494: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:48.499: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:48.510: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:17:53.438: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:53.447: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:53.450: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:53.461: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:53.466: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:53.489: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:53.494: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:53.499: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:53.510: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:17:58.438: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:58.446: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:58.449: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:58.460: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:58.465: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:58.487: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:58.492: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:58.497: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:17:58.507: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:18:03.437: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:03.457: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:03.461: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:03.474: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:03.481: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:03.503: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:03.508: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:03.513: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:03.525: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:18:08.437: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:08.445: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:08.448: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:08.458: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:08.462: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:08.483: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:08.488: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:08.493: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:08.504: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:18:13.439: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:13.450: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:13.453: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:13.470: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:13.477: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:13.508: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:13.513: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:13.519: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:13.529: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:18:18.451: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:18.479: INFO: Unable to read wheezy_udp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:18.489: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:18.523: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:18.538: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:18.613: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:18.641: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:18.662: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:18.719: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9945.svc wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:18:23.441: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:23.461: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:23.485: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:23.495: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:23.544: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:23.555: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:23.568: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:23.593: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:18:28.444: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:28.465: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:28.485: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:28.495: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:28.580: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:28.599: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:28.611: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:28.640: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:18:33.444: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:33.466: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:33.489: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:33.498: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:33.546: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:33.557: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:33.569: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:33.589: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:18:38.444: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:38.465: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:38.484: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:38.492: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:38.537: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:38.549: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:38.563: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:38.587: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:18:43.443: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:43.479: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:43.503: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:43.515: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:43.558: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:43.567: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:43.575: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:43.598: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:18:48.442: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:48.460: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:48.481: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:48.491: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:48.526: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:48.533: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:48.542: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:48.562: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:18:53.446: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:53.470: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:53.500: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:53.513: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:53.612: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:53.627: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:53.643: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:53.668: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:18:58.442: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:58.463: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:58.481: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:58.490: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:58.527: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:58.538: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:58.545: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:18:58.563: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:19:03.444: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:03.471: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:03.494: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:03.512: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:03.555: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:03.566: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:03.577: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:03.595: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:19:08.444: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:08.468: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:08.485: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:08.496: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:08.532: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:08.543: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:08.553: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:08.574: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:19:13.445: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:13.472: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:13.499: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:13.509: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:13.553: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:13.564: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:13.579: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:13.600: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:19:18.440: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:18.467: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:18.486: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:18.494: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:18.535: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:18.547: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:18.561: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:18.580: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:19:23.443: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:23.465: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:23.487: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:23.498: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:23.542: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:23.558: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:23.568: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:23.586: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:19:28.442: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:28.460: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:28.488: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:28.500: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:28.545: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:28.556: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:28.566: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:28.595: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:19:33.442: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:33.465: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:33.489: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:33.499: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:33.538: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:33.548: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:33.556: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:33.575: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:19:38.443: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:38.465: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:38.497: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:38.507: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:38.550: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:38.559: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:38.568: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:38.589: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:19:43.442: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:43.461: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:43.479: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:43.487: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:43.525: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:43.539: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:43.551: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:43.571: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:19:48.443: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:48.463: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:48.481: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:48.491: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:48.531: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:48.540: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:48.552: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:48.573: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:19:53.442: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:53.466: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:53.494: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:53.504: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:53.558: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:53.573: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:53.585: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:53.606: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:19:58.446: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:58.470: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:58.490: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:58.501: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:58.546: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:58.559: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:58.569: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:19:58.592: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:20:03.443: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:03.462: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:03.526: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:03.542: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:03.585: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:03.596: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:03.606: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:03.629: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:20:08.443: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:08.469: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:08.490: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:08.500: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:08.535: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:08.544: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:08.551: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:08.568: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:20:13.444: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:13.464: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:13.485: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:13.495: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:13.531: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:13.541: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:13.552: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:13.571: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:20:18.446: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:18.470: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:18.492: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:18.504: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:18.548: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:18.559: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:18.569: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:18.595: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:20:23.441: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:23.461: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:23.484: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:23.493: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:23.529: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:23.537: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:23.545: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:23.565: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:20:28.443: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:28.462: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:28.480: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:28.489: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:28.528: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:28.541: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:28.550: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:28.567: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:20:33.445: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:33.469: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:33.487: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:33.499: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:33.543: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:33.551: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:33.561: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:33.590: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9945.svc wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:20:38.496: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:38.509: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:38.558: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:38.571: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:38.580: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:38.600: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:20:43.479: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:43.488: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:43.527: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:43.540: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:43.552: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:43.567: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:20:48.507: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:48.519: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:48.567: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:48.585: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:48.609: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:48.644: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:20:53.483: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:53.495: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:53.530: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:53.541: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:53.554: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:53.570: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:20:58.474: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:58.484: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:58.520: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:58.529: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:58.537: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:20:58.551: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:21:03.476: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:03.483: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:03.514: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:03.522: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:03.535: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:03.554: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:21:08.477: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:08.484: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:08.530: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:08.555: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:08.569: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:08.634: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:21:13.480: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:13.489: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:13.531: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:13.540: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:13.549: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:13.567: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:21:18.480: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:18.493: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:18.536: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:18.551: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:18.559: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:18.577: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:21:23.477: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:23.487: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:23.524: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:23.534: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:23.546: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:23.569: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@_http._tcp.test-service-2.dns-9945.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:21:28.497: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:28.537: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:28.547: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:28.555: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:28.572: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:21:33.486: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:33.519: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:33.528: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:33.536: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:33.556: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:21:38.535: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:38.595: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:38.611: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:38.633: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:38.667: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:21:43.497: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:43.535: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:43.543: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:43.554: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:43.571: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:21:48.490: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:48.523: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:48.534: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:48.544: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:48.564: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:21:53.499: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:53.551: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:53.562: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:53.575: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:53.602: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:21:58.490: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:58.552: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:58.573: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:58.602: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:21:58.621: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:22:03.487: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:03.522: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:03.529: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:03.542: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:03.564: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:22:08.480: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:08.515: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:08.525: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:08.534: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:08.563: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:22:13.495: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:13.555: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:13.568: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:13.580: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:13.611: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:22:18.502: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:18.564: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:18.572: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:18.582: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:18.601: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:22:23.494: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:23.530: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:23.539: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:23.551: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:23.568: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:22:28.494: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:28.543: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:28.557: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:28.569: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:28.591: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:22:33.497: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:33.538: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:33.553: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:33.567: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:33.587: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:22:38.466: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:38.485: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:38.490: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:38.496: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:38.506: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:22:43.464: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:43.483: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:43.487: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:43.492: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:43.501: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:22:48.467: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:48.498: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:48.510: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:48.515: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:48.525: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:22:53.463: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:53.483: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:53.488: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:53.493: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:53.503: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:22:58.463: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:58.483: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:58.488: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:58.493: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:22:58.503: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:23:03.466: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:03.487: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:03.492: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:03.497: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:03.506: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:23:08.466: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:08.488: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:08.494: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:08.498: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:08.509: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:23:13.468: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:13.494: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:13.500: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:13.506: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:13.520: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:23:18.465: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:18.486: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:18.492: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:18.496: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:18.506: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:23:23.470: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:23.490: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:23.495: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:23.500: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:23.510: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:23:28.462: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:28.487: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:28.492: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:28.497: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:28.506: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:23:33.462: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:33.482: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:33.486: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:33.491: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:33.500: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:23:38.469: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:38.490: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:38.496: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:38.503: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:38.516: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:23:43.463: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:43.483: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:43.488: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:43.493: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:43.504: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:23:48.466: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:48.486: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:48.491: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:48.495: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:48.507: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:23:53.466: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:53.487: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:53.492: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:53.496: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:53.507: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:23:58.464: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:58.485: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:58.489: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:58.495: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:23:58.506: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:24:03.469: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:03.488: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:03.493: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:03.499: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:03.527: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:24:08.463: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:08.481: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:08.486: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:08.491: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:08.502: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:24:13.462: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:13.485: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:13.492: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:13.498: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:13.509: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:24:18.463: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:18.483: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:18.488: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:18.493: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:18.502: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:24:23.465: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:23.486: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:23.490: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:23.495: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:23.505: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:24:28.463: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:28.484: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:28.489: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:28.493: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:28.502: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:24:33.462: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:33.482: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:33.487: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:33.491: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:33.502: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:24:38.463: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:38.485: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:38.489: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:38.494: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:38.504: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:24:43.467: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:43.488: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:43.492: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:43.497: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:43.507: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:24:48.465: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:48.486: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:48.491: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:48.496: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:48.505: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:24:53.467: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:53.487: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:53.491: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:53.495: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:53.505: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:24:58.463: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:58.482: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:58.489: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:58.494: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:24:58.505: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:25:03.473: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:03.501: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:03.511: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:03.517: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:03.528: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:25:08.462: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:08.481: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:08.485: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:08.489: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:08.499: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:25:13.466: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:13.487: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:13.492: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:13.499: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:13.510: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:25:18.465: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:18.485: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:18.490: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:18.495: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:18.505: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:25:23.470: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:23.495: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:23.501: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:23.506: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:23.515: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:25:28.461: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:28.480: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:28.484: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:28.489: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:28.499: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:25:28.529: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:28.548: INFO: Unable to read jessie_tcp@dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:28.554: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:28.559: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9945.svc from pod dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7: the server could not find the requested resource (get pods dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7)
    Sep  3 09:25:28.734: INFO: Lookups using dns-9945/dns-test-e485cb0e-8cb7-48af-afa6-59dd592e6ff7 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.dns-test-service.dns-9945.svc jessie_tcp@_http._tcp.test-service-2.dns-9945.svc]

    
    Sep  3 09:25:28.734: FAIL: Unexpected error:

        <*errors.errorString | 0xc000250290>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 26 lines ...
    • Failure [608.708 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
    
      Sep  3 09:25:28.734: Unexpected error:

          <*errors.errorString | 0xc000250290>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
... skipping 9 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-6zkg
    STEP: Creating a pod to test atomic-volume-subpath
    Sep  3 09:25:18.400: INFO: Waiting up to 5m0s for pod "pod-subpath-test-configmap-6zkg" in namespace "subpath-656" to be "Succeeded or Failed"

    Sep  3 09:25:18.402: INFO: Pod "pod-subpath-test-configmap-6zkg": Phase="Pending", Reason="", readiness=false. Elapsed: 2.39525ms
    Sep  3 09:25:20.407: INFO: Pod "pod-subpath-test-configmap-6zkg": Phase="Running", Reason="", readiness=true. Elapsed: 2.007226207s
    Sep  3 09:25:22.412: INFO: Pod "pod-subpath-test-configmap-6zkg": Phase="Running", Reason="", readiness=true. Elapsed: 4.011915694s
    Sep  3 09:25:24.416: INFO: Pod "pod-subpath-test-configmap-6zkg": Phase="Running", Reason="", readiness=true. Elapsed: 6.0155805s
    Sep  3 09:25:26.419: INFO: Pod "pod-subpath-test-configmap-6zkg": Phase="Running", Reason="", readiness=true. Elapsed: 8.018801392s
    Sep  3 09:25:28.423: INFO: Pod "pod-subpath-test-configmap-6zkg": Phase="Running", Reason="", readiness=true. Elapsed: 10.023318621s
... skipping 2 lines ...
    Sep  3 09:25:34.436: INFO: Pod "pod-subpath-test-configmap-6zkg": Phase="Running", Reason="", readiness=true. Elapsed: 16.035731186s
    Sep  3 09:25:36.439: INFO: Pod "pod-subpath-test-configmap-6zkg": Phase="Running", Reason="", readiness=true. Elapsed: 18.039484176s
    Sep  3 09:25:38.445: INFO: Pod "pod-subpath-test-configmap-6zkg": Phase="Running", Reason="", readiness=true. Elapsed: 20.044899546s
    Sep  3 09:25:40.449: INFO: Pod "pod-subpath-test-configmap-6zkg": Phase="Running", Reason="", readiness=false. Elapsed: 22.049470605s
    Sep  3 09:25:42.453: INFO: Pod "pod-subpath-test-configmap-6zkg": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.053117113s
    STEP: Saw pod success
    Sep  3 09:25:42.453: INFO: Pod "pod-subpath-test-configmap-6zkg" satisfied condition "Succeeded or Failed"

    Sep  3 09:25:42.455: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-subpath-test-configmap-6zkg container test-container-subpath-configmap-6zkg: <nil>
    STEP: delete the pod
    Sep  3 09:25:42.475: INFO: Waiting for pod pod-subpath-test-configmap-6zkg to disappear
    Sep  3 09:25:42.477: INFO: Pod pod-subpath-test-configmap-6zkg no longer exists
    STEP: Deleting pod pod-subpath-test-configmap-6zkg
    Sep  3 09:25:42.477: INFO: Deleting pod "pod-subpath-test-configmap-6zkg" in namespace "subpath-656"
    [AfterEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:25:42.480: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "subpath-656" 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":40,"skipped":747,"failed":0}

    
    SSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:25:42.561: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "podtemplate-2582" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] PodTemplates should run the lifecycle of PodTemplates [Conformance]","total":-1,"completed":41,"skipped":766,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:25:42.697: INFO: Waiting up to 5m0s for pod "downwardapi-volume-96f7e41d-540f-4d9d-b506-3b408abf39bd" in namespace "projected-5937" to be "Succeeded or Failed"

    Sep  3 09:25:42.700: INFO: Pod "downwardapi-volume-96f7e41d-540f-4d9d-b506-3b408abf39bd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.402144ms
    Sep  3 09:25:44.705: INFO: Pod "downwardapi-volume-96f7e41d-540f-4d9d-b506-3b408abf39bd": Phase="Pending", Reason="", readiness=false. Elapsed: 2.00729444s
    Sep  3 09:25:46.709: INFO: Pod "downwardapi-volume-96f7e41d-540f-4d9d-b506-3b408abf39bd": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.011545953s
    STEP: Saw pod success
    Sep  3 09:25:46.709: INFO: Pod "downwardapi-volume-96f7e41d-540f-4d9d-b506-3b408abf39bd" satisfied condition "Succeeded or Failed"

    Sep  3 09:25:46.712: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod downwardapi-volume-96f7e41d-540f-4d9d-b506-3b408abf39bd container client-container: <nil>
    STEP: delete the pod
    Sep  3 09:25:46.730: INFO: Waiting for pod downwardapi-volume-96f7e41d-540f-4d9d-b506-3b408abf39bd to disappear
    Sep  3 09:25:46.732: INFO: Pod downwardapi-volume-96f7e41d-540f-4d9d-b506-3b408abf39bd 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
    Sep  3 09:25:46.732: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-5937" 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":42,"skipped":850,"failed":0}

    
    SSSSS
    ------------------------------
    [BeforeEach] [sig-storage] EmptyDir volumes
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
    Sep  3 09:25:46.747: 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
    Sep  3 09:25:46.774: INFO: Waiting up to 5m0s for pod "pod-c82f5f4e-47b2-46ed-979e-d1544a70b3cb" in namespace "emptydir-7712" to be "Succeeded or Failed"

    Sep  3 09:25:46.776: INFO: Pod "pod-c82f5f4e-47b2-46ed-979e-d1544a70b3cb": Phase="Pending", Reason="", readiness=false. Elapsed: 1.82893ms
    Sep  3 09:25:48.780: INFO: Pod "pod-c82f5f4e-47b2-46ed-979e-d1544a70b3cb": Phase="Pending", Reason="", readiness=false. Elapsed: 2.005586698s
    Sep  3 09:25:50.784: INFO: Pod "pod-c82f5f4e-47b2-46ed-979e-d1544a70b3cb": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.009312188s
    STEP: Saw pod success
    Sep  3 09:25:50.784: INFO: Pod "pod-c82f5f4e-47b2-46ed-979e-d1544a70b3cb" satisfied condition "Succeeded or Failed"

    Sep  3 09:25:50.787: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-c82f5f4e-47b2-46ed-979e-d1544a70b3cb container test-container: <nil>
    STEP: delete the pod
    Sep  3 09:25:50.800: INFO: Waiting for pod pod-c82f5f4e-47b2-46ed-979e-d1544a70b3cb to disappear
    Sep  3 09:25:50.802: INFO: Pod pod-c82f5f4e-47b2-46ed-979e-d1544a70b3cb 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
    Sep  3 09:25:50.802: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-7712" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0644,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":43,"skipped":855,"failed":0}

    
    SSSSSSSSSSS
    ------------------------------
    [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 31 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:25:54.830: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-248" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should run through the lifecycle of Pods and PodStatus [Conformance]","total":-1,"completed":44,"skipped":866,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:25:57.030: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-3773" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should support remote command execution over websockets [NodeConformance] [Conformance]","total":-1,"completed":45,"skipped":911,"failed":0}

    
    S
    ------------------------------
    [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
    Sep  3 09:26:03.120: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "disruption-4571" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] DisruptionController should create a PodDisruptionBudget [Conformance]","total":-1,"completed":46,"skipped":912,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:26:16.322: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-7818" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should create a ResourceQuota and capture the life of a pod. [Conformance]","total":-1,"completed":47,"skipped":1001,"failed":0}

    
    SSSS
    ------------------------------
    [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 17 lines ...
    • [SLOW TEST:338.093 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 new jobs when ForbidConcurrent [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 new jobs when ForbidConcurrent [Slow] [Conformance]","total":-1,"completed":5,"skipped":154,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    
    SSS
    ------------------------------
    [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
    Sep  3 09:28:03.656: INFO: Successfully updated pod "pod-update-activedeadlineseconds-3d0b4e45-325e-4157-ac13-7a3da120e1d8"
    Sep  3 09:28:03.657: INFO: Waiting up to 5m0s for pod "pod-update-activedeadlineseconds-3d0b4e45-325e-4157-ac13-7a3da120e1d8" in namespace "pods-7100" to be "terminated due to deadline exceeded"
    Sep  3 09:28:03.660: INFO: Pod "pod-update-activedeadlineseconds-3d0b4e45-325e-4157-ac13-7a3da120e1d8": Phase="Running", Reason="", readiness=true. Elapsed: 2.706407ms
    Sep  3 09:28:05.664: INFO: Pod "pod-update-activedeadlineseconds-3d0b4e45-325e-4157-ac13-7a3da120e1d8": Phase="Running", Reason="", readiness=true. Elapsed: 2.006956031s
    Sep  3 09:28:07.669: INFO: Pod "pod-update-activedeadlineseconds-3d0b4e45-325e-4157-ac13-7a3da120e1d8": Phase="Failed", Reason="DeadlineExceeded", readiness=false. Elapsed: 4.012138044s

    Sep  3 09:28:07.669: INFO: Pod "pod-update-activedeadlineseconds-3d0b4e45-325e-4157-ac13-7a3da120e1d8" 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
    Sep  3 09:28:07.669: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-7100" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should allow activeDeadlineSeconds to be updated [NodeConformance] [Conformance]","total":-1,"completed":6,"skipped":157,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    
    SSSSSSSSS
    ------------------------------
    [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 71 lines ...
    STEP: Destroying namespace "services-2867" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should have session affinity timeout work for service with type clusterIP [LinuxOnly] [Conformance]","total":-1,"completed":48,"skipped":1005,"failed":0}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:28:09.559: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "certificates-124" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-auth] Certificates API [Privileged:ClusterAdmin] should support CSR API operations [Conformance]","total":-1,"completed":49,"skipped":1022,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:28:10.171: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-3264" 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":7,"skipped":166,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:28:15.310: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-7937" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment should run the lifecycle of a Deployment [Conformance]","total":-1,"completed":8,"skipped":193,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:28:15.966: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "custom-resource-definition-6847" 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":9,"skipped":218,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    
    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 45 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:28:37.139: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-2660" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment deployment should support rollover [Conformance]","total":-1,"completed":10,"skipped":251,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    
    SSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 27 lines ...
    STEP: Destroying namespace "webhook-8516-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":11,"skipped":254,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    
    SSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:28:46.115: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-6611" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should support retrieving logs from the container over websockets [NodeConformance] [Conformance]","total":-1,"completed":12,"skipped":263,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    
    SSSSSSSS
    ------------------------------
    [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 68 lines ...
    STEP: Destroying namespace "services-5397" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should have session affinity timeout work for NodePort service [LinuxOnly] [Conformance]","total":-1,"completed":50,"skipped":1090,"failed":0}

    
    SSS
    ------------------------------
    [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
    Sep  3 09:29:01.615: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable in multiple volumes in the same pod [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating configMap with name configmap-test-volume-ffa1b9f6-c74a-4b1c-8d18-01817204b308
    STEP: Creating a pod to test consume configMaps
    Sep  3 09:29:01.646: INFO: Waiting up to 5m0s for pod "pod-configmaps-d1aac2ff-3cb1-46dc-828d-37d881a60090" in namespace "configmap-7786" to be "Succeeded or Failed"

    Sep  3 09:29:01.649: INFO: Pod "pod-configmaps-d1aac2ff-3cb1-46dc-828d-37d881a60090": Phase="Pending", Reason="", readiness=false. Elapsed: 3.294882ms
    Sep  3 09:29:03.653: INFO: Pod "pod-configmaps-d1aac2ff-3cb1-46dc-828d-37d881a60090": Phase="Pending", Reason="", readiness=false. Elapsed: 2.006835237s
    Sep  3 09:29:05.656: INFO: Pod "pod-configmaps-d1aac2ff-3cb1-46dc-828d-37d881a60090": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.010665692s
    STEP: Saw pod success
    Sep  3 09:29:05.657: INFO: Pod "pod-configmaps-d1aac2ff-3cb1-46dc-828d-37d881a60090" satisfied condition "Succeeded or Failed"

    Sep  3 09:29:05.659: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-configmaps-d1aac2ff-3cb1-46dc-828d-37d881a60090 container configmap-volume-test: <nil>
    STEP: delete the pod
    Sep  3 09:29:05.670: INFO: Waiting for pod pod-configmaps-d1aac2ff-3cb1-46dc-828d-37d881a60090 to disappear
    Sep  3 09:29:05.672: INFO: Pod pod-configmaps-d1aac2ff-3cb1-46dc-828d-37d881a60090 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
    Sep  3 09:29:05.672: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-7786" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable in multiple volumes in the same pod [NodeConformance] [Conformance]","total":-1,"completed":51,"skipped":1093,"failed":0}

    [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
    Sep  3 09:29:05.681: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename kubectl
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 9 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:29:05.771: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-9519" 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":52,"skipped":1093,"failed":0}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected secret optional updates should be reflected in volume [NodeConformance] [Conformance]","total":-1,"completed":45,"skipped":746,"failed":0}

    [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
    Sep  3 09:23:43.882: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename pod-network-test
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 274 lines ...
      ----    ------     ----  ----               -------
      Normal  Scheduled  22s   default-scheduler  Successfully assigned pod-network-test-9693/netserver-3 to k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1
      Normal  Pulled     21s   kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.39" already present on machine
      Normal  Created    21s   kubelet            Created container webserver
      Normal  Started    21s   kubelet            Started container webserver
    
    Sep  3 09:24:05.606: INFO: encountered error during dial (did not find expected responses... 

    Tries 1
    Command curl -g -q -s 'http://192.168.0.46:9080/dial?request=hostname&protocol=http&host=192.168.2.15&port=8083&tries=1'
    retrieved map[]
    expected map[netserver-2:{}])
    Sep  3 09:24:05.606: INFO: ...failed...will try again in next pass

    Sep  3 09:24:05.606: INFO: Breadth first check of 192.168.6.34 on host 172.18.0.5...
    Sep  3 09:24:05.609: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s 'http://192.168.0.46:9080/dial?request=hostname&protocol=http&host=192.168.6.34&port=8083&tries=1'] Namespace:pod-network-test-9693 PodName:test-container-pod ContainerName:webserver Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
    Sep  3 09:24:05.609: INFO: >>> kubeConfig: /tmp/kubeconfig
    Sep  3 09:24:05.692: INFO: Waiting for responses: map[]
    Sep  3 09:24:05.692: INFO: reached 192.168.6.34 after 0/1 tries
    Sep  3 09:24:05.692: INFO: Going to retry 1 out of 4 pods....
... skipping 382 lines ...
      ----    ------     ----   ----               -------
      Normal  Scheduled  5m48s  default-scheduler  Successfully assigned pod-network-test-9693/netserver-3 to k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1
      Normal  Pulled     5m47s  kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.39" already present on machine
      Normal  Created    5m47s  kubelet            Created container webserver
      Normal  Started    5m47s  kubelet            Started container webserver
    
    Sep  3 09:29:31.966: INFO: encountered error during dial (did not find expected responses... 

    Tries 46
    Command curl -g -q -s 'http://192.168.0.46:9080/dial?request=hostname&protocol=http&host=192.168.2.15&port=8083&tries=1'
    retrieved map[]
    expected map[netserver-2:{}])
    Sep  3 09:29:31.966: INFO: ... Done probing pod [[[ 192.168.2.15 ]]]
    Sep  3 09:29:31.966: INFO: succeeded at polling 3 out of 4 connections
    Sep  3 09:29:31.966: INFO: pod polling failure summary:
    Sep  3 09:29:31.966: INFO: Collected error: did not find expected responses... 

    Tries 46
    Command curl -g -q -s 'http://192.168.0.46:9080/dial?request=hostname&protocol=http&host=192.168.2.15&port=8083&tries=1'
    retrieved map[]
    expected map[netserver-2:{}]
    Sep  3 09:29:31.966: FAIL: failed,  1 out of 4 connections failed

    
    Full Stack Trace
    k8s.io/kubernetes/test/e2e/common/network.glob..func1.1.2()
    	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/network/networking.go:82 +0x69
    k8s.io/kubernetes/test/e2e.RunE2ETests(0xc000c68a80)
    	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c
... skipping 14 lines ...
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/network/framework.go:23
      Granular Checks: Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/network/networking.go:30
        should function for intra-pod communication: http [NodeConformance] [Conformance] [It]
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    
        Sep  3 09:29:31.966: failed,  1 out of 4 connections failed

    
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/network/networking.go:82
    ------------------------------
    [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 9 lines ...
    STEP: creating a pod to probe /etc/hosts
    STEP: submitting the pod to kubernetes
    STEP: retrieving the pod
    STEP: looking for the results for each expected name from probers
    Sep  3 09:28:48.194: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:28:48.203: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:28:48.203: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  3 09:28:53.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:28:53.226: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:28:53.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

    
    Sep  3 09:28:58.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:28:58.229: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:29:03.220: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:29:03.230: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:29:08.219: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:29:08.230: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:29:13.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:29:13.231: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:29:18.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:29:18.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:29:23.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:29:23.228: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:29:28.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:29:28.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:29:33.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:29:33.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:29:38.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:29:38.229: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:29:43.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:29:43.228: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:29:48.218: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:29:48.230: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:29:53.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:29:53.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:29:58.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:29:58.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:30:03.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:30:03.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:30:08.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:30:08.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:30:13.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:30:13.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:30:18.220: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:30:18.231: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:30:23.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:30:23.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:30:28.214: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:30:28.225: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:30:33.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:30:33.229: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:30:38.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:30:38.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:30:43.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:30:43.228: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:30:48.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:30:48.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:30:53.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:30:53.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:30:58.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:30:58.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:31:03.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:31:03.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:31:08.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:31:08.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:31:13.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:31:13.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:31:18.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:31:18.229: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:31:23.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:31:23.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:31:28.218: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:31:28.230: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:31:33.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:31:33.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:31:38.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:31:38.228: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:31:43.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:31:43.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:31:48.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:31:48.228: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:31:53.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:31:53.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:31:58.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:31:58.228: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:32:03.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:32:03.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:32:08.220: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:32:08.235: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:32:13.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:32:13.228: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:32:18.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:32:18.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:32:23.218: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:32:23.229: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:32:28.221: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:32:28.233: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:32:33.220: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:32:33.230: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:32:38.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:32:38.229: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:32:43.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:32:43.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:32:48.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:32:48.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:32:53.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:32:53.225: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:32:58.218: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:32:58.229: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:33:03.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:33:03.228: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:33:08.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:33:08.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:33:13.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:33:13.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:33:18.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:33:18.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:33:23.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:33:23.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:33:28.219: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:33:28.229: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:33:33.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:33:33.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:33:38.218: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:33:38.229: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:33:43.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:33:43.225: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:33:48.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:33:48.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:33:53.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:33:53.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:33:58.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:33:58.227: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:34:03.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:34:03.231: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:34:08.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:34:08.226: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:34:13.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51: the server could not find the requested resource (get pods dns-test-d2d085de-979c-418b-a988-d0ec922d1f51)
    Sep  3 09:34:13.228: INFO: Lookups using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 failed for: [wheezy_tcp@PodARecord]

    
    Sep  3 09:34:18.229: INFO: DNS probes using dns-2480/dns-test-d2d085de-979c-418b-a988-d0ec922d1f51 succeeded
    
    STEP: deleting the pod
    [AfterEach] [sig-network] DNS
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
... skipping 4 lines ...
    • [SLOW TEST:332.117 seconds]
    [sig-network] DNS
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/common/framework.go:23
      should provide /etc/hosts entries for the cluster [LinuxOnly] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    ------------------------------
    {"msg":"PASSED [sig-network] DNS should provide /etc/hosts entries for the cluster [LinuxOnly] [Conformance]","total":-1,"completed":13,"skipped":271,"failed":1,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]"]}

    
    SSSSSSS
    ------------------------------
    [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 29 lines ...
    Sep  3 09:34:36.345: INFO: Pod pod-with-prestop-exec-hook still exists
    Sep  3 09:34:38.342: INFO: Waiting for pod pod-with-prestop-exec-hook to disappear
    Sep  3 09:34:38.345: INFO: Pod pod-with-prestop-exec-hook still exists
    Sep  3 09:34:40.342: INFO: Waiting for pod pod-with-prestop-exec-hook to disappear
    Sep  3 09:34:40.345: INFO: Pod pod-with-prestop-exec-hook no longer exists
    STEP: check prestop hook
    Sep  3 09:35:10.346: FAIL: Timed out after 30.000s.

    Expected
        <*errors.errorString | 0xc0043e3470>: {
            s: "failed to match regexp \"GET /echo\\\\?msg=prestop\" in output \"I0903 09:34:18.965259       1 log.go:195] Started HTTP server on port 8080\\nI0903 09:34:18.965904       1 log.go:195] Started UDP server on port  8081\\n\"",

        }
    to be nil
    
    Full Stack Trace
    k8s.io/kubernetes/test/e2e/common/node.glob..func11.1.2(0xc00278b400)
    	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/lifecycle_hook.go:79 +0x342
... skipping 21 lines ...
        should execute prestop exec hook properly [NodeConformance] [Conformance] [It]
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    
        Sep  3 09:35:10.346: Timed out after 30.000s.
        Expected
            <*errors.errorString | 0xc0043e3470>: {
                s: "failed to match regexp \"GET /echo\\\\?msg=prestop\" in output \"I0903 09:34:18.965259       1 log.go:195] Started HTTP server on port 8080\\nI0903 09:34:18.965904       1 log.go:195] Started UDP server on port  8081\\n\"",

            }
        to be nil
    
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node/lifecycle_hook.go:79
    ------------------------------
    {"msg":"FAILED [sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]","total":-1,"completed":13,"skipped":278,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    [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
    Sep  3 09:35:10.360: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename container-lifecycle-hook
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 17 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:35:16.445: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "container-lifecycle-hook-6627" 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":14,"skipped":278,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSS
    ------------------------------
    [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
    Sep  3 09:35:16.463: 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 container.SecurityContext.RunAsUser And container.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
    Sep  3 09:35:16.496: INFO: Waiting up to 5m0s for pod "security-context-401b0691-7935-43b2-8f8f-799f9a9dd745" in namespace "security-context-6354" to be "Succeeded or Failed"

    Sep  3 09:35:16.499: INFO: Pod "security-context-401b0691-7935-43b2-8f8f-799f9a9dd745": Phase="Pending", Reason="", readiness=false. Elapsed: 2.731981ms
    Sep  3 09:35:18.502: INFO: Pod "security-context-401b0691-7935-43b2-8f8f-799f9a9dd745": Phase="Pending", Reason="", readiness=false. Elapsed: 2.006081411s
    Sep  3 09:35:20.506: INFO: Pod "security-context-401b0691-7935-43b2-8f8f-799f9a9dd745": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.010273985s
    STEP: Saw pod success
    Sep  3 09:35:20.506: INFO: Pod "security-context-401b0691-7935-43b2-8f8f-799f9a9dd745" satisfied condition "Succeeded or Failed"

    Sep  3 09:35:20.509: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod security-context-401b0691-7935-43b2-8f8f-799f9a9dd745 container test-container: <nil>
    STEP: delete the pod
    Sep  3 09:35:20.526: INFO: Waiting for pod security-context-401b0691-7935-43b2-8f8f-799f9a9dd745 to disappear
    Sep  3 09:35:20.528: INFO: Pod security-context-401b0691-7935-43b2-8f8f-799f9a9dd745 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
    Sep  3 09:35:20.528: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "security-context-6354" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Security Context should support container.SecurityContext.RunAsUser And container.SecurityContext.RunAsGroup [LinuxOnly] [Conformance]","total":-1,"completed":15,"skipped":285,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 22 lines ...
    STEP: Destroying namespace "webhook-8355-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":16,"skipped":289,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:35:27.345: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "tables-3905" for this suite.
    
    •
    ------------------------------
    {"msg":"FAILED [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","total":-1,"completed":45,"skipped":746,"failed":1,"failures":["[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]"]}

    [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
    Sep  3 09:29:31.979: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename pod-network-test
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 222 lines ...
    
    Sep  3 09:30:03.562: INFO: 
    Output of kubectl describe pod pod-network-test-7731/netserver-3:
    
    Sep  3 09:30:03.563: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=pod-network-test-7731 describe pod netserver-3 --namespace=pod-network-test-7731'
    Sep  3 09:30:03.643: INFO: stderr: ""
    Sep  3 09:30:03.643: INFO: stdout: "Name:         netserver-3\nNamespace:    pod-network-test-7731\nPriority:     0\nNode:         k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1/172.18.0.5\nStart Time:   Sat, 03 Sep 2022 09:29:32 +0000\nLabels:       selector-395d237f-7d9f-4760-bd30-2dc73aaf4fe3=true\nAnnotations:  <none>\nStatus:       Running\nIP:           192.168.6.43\nIPs:\n  IP:  192.168.6.43\nContainers:\n  webserver:\n    Container ID:  containerd://f81e0a89352ba678fa795664b6307b4cc8029fe690d06df3662521403fd332c6\n    Image:         k8s.gcr.io/e2e-test-images/agnhost:2.39\n    Image ID:      k8s.gcr.io/e2e-test-images/agnhost@sha256:7e8bdd271312fd25fc5ff5a8f04727be84044eb3d7d8d03611972a6752e2e11e\n    Ports:         8083/TCP, 8081/UDP\n    Host Ports:    0/TCP, 0/UDP\n    Args:\n      netexec\n      --http-port=8083\n      --udp-port=8081\n    State:          Running\n      Started:      Sat, 03 Sep 2022 09:29:34 +0000\n    Ready:          True\n    Restart Count:  0\n    Liveness:       http-get http://:8083/healthz delay=10s timeout=30s period=10s #success=1 #failure=3\n    Readiness:      http-get http://:8083/healthz delay=10s timeout=30s period=10s #success=1 #failure=3\n    Environment:    <none>\n    Mounts:\n      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-rjbps (ro)\nConditions:\n  Type              Status\n  Initialized       True \n  Ready             True \n  ContainersReady   True \n  PodScheduled      True \nVolumes:\n  kube-api-access-rjbps:\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:              kubernetes.io/hostname=k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1\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    31s   default-scheduler  Successfully assigned pod-network-test-7731/netserver-3 to k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1\n  Warning  FailedMount  30s   kubelet            MountVolume.SetUp failed for volume \"kube-api-access-rjbps\" : failed to sync configmap cache: timed out waiting for the condition\n  Normal   Pulled       30s   kubelet            Container image \"k8s.gcr.io/e2e-test-images/agnhost:2.39\" already present on machine\n  Normal   Created      29s   kubelet            Created container webserver\n  Normal   Started      29s   kubelet            Started container webserver\n"

    Sep  3 09:30:03.643: INFO: Name:         netserver-3
    Namespace:    pod-network-test-7731
    Priority:     0
    Node:         k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1/172.18.0.5
    Start Time:   Sat, 03 Sep 2022 09:29:32 +0000
    Labels:       selector-395d237f-7d9f-4760-bd30-2dc73aaf4fe3=true
... skipping 40 lines ...
    Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
    Events:
      Type     Reason       Age   From               Message
      ----     ------       ----  ----               -------
      Normal   Scheduled    31s   default-scheduler  Successfully assigned pod-network-test-7731/netserver-3 to k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1
      Warning  FailedMount  30s   kubelet            MountVolume.SetUp failed for volume "kube-api-access-rjbps" : failed to sync configmap cache: timed out waiting for the condition

      Normal   Pulled       30s   kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.39" already present on machine
      Normal   Created      29s   kubelet            Created container webserver
      Normal   Started      29s   kubelet            Started container webserver
    
    Sep  3 09:30:03.643: INFO: encountered error during dial (did not find expected responses... 

    Tries 1
    Command curl -g -q -s 'http://192.168.0.68:9080/dial?request=hostname&protocol=http&host=192.168.2.23&port=8083&tries=1'
    retrieved map[]
    expected map[netserver-2:{}])
    Sep  3 09:30:03.643: INFO: ...failed...will try again in next pass

    Sep  3 09:30:03.643: INFO: Breadth first check of 192.168.6.43 on host 172.18.0.5...
    Sep  3 09:30:03.645: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s 'http://192.168.0.68:9080/dial?request=hostname&protocol=http&host=192.168.6.43&port=8083&tries=1'] Namespace:pod-network-test-7731 PodName:test-container-pod ContainerName:webserver Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
    Sep  3 09:30:03.646: INFO: >>> kubeConfig: /tmp/kubeconfig
    Sep  3 09:30:03.736: INFO: Waiting for responses: map[]
    Sep  3 09:30:03.736: INFO: reached 192.168.6.43 after 0/1 tries
    Sep  3 09:30:03.736: INFO: Going to retry 1 out of 4 pods....
... skipping 325 lines ...
    
    Sep  3 09:35:29.782: INFO: 
    Output of kubectl describe pod pod-network-test-7731/netserver-3:
    
    Sep  3 09:35:29.782: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=pod-network-test-7731 describe pod netserver-3 --namespace=pod-network-test-7731'
    Sep  3 09:35:29.862: INFO: stderr: ""
    Sep  3 09:35:29.862: INFO: stdout: "Name:         netserver-3\nNamespace:    pod-network-test-7731\nPriority:     0\nNode:         k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1/172.18.0.5\nStart Time:   Sat, 03 Sep 2022 09:29:32 +0000\nLabels:       selector-395d237f-7d9f-4760-bd30-2dc73aaf4fe3=true\nAnnotations:  <none>\nStatus:       Running\nIP:           192.168.6.43\nIPs:\n  IP:  192.168.6.43\nContainers:\n  webserver:\n    Container ID:  containerd://f81e0a89352ba678fa795664b6307b4cc8029fe690d06df3662521403fd332c6\n    Image:         k8s.gcr.io/e2e-test-images/agnhost:2.39\n    Image ID:      k8s.gcr.io/e2e-test-images/agnhost@sha256:7e8bdd271312fd25fc5ff5a8f04727be84044eb3d7d8d03611972a6752e2e11e\n    Ports:         8083/TCP, 8081/UDP\n    Host Ports:    0/TCP, 0/UDP\n    Args:\n      netexec\n      --http-port=8083\n      --udp-port=8081\n    State:          Running\n      Started:      Sat, 03 Sep 2022 09:29:34 +0000\n    Ready:          True\n    Restart Count:  0\n    Liveness:       http-get http://:8083/healthz delay=10s timeout=30s period=10s #success=1 #failure=3\n    Readiness:      http-get http://:8083/healthz delay=10s timeout=30s period=10s #success=1 #failure=3\n    Environment:    <none>\n    Mounts:\n      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-rjbps (ro)\nConditions:\n  Type              Status\n  Initialized       True \n  Ready             True \n  ContainersReady   True \n  PodScheduled      True \nVolumes:\n  kube-api-access-rjbps:\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:              kubernetes.io/hostname=k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1\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    5m57s  default-scheduler  Successfully assigned pod-network-test-7731/netserver-3 to k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1\n  Warning  FailedMount  5m56s  kubelet            MountVolume.SetUp failed for volume \"kube-api-access-rjbps\" : failed to sync configmap cache: timed out waiting for the condition\n  Normal   Pulled       5m56s  kubelet            Container image \"k8s.gcr.io/e2e-test-images/agnhost:2.39\" already present on machine\n  Normal   Created      5m55s  kubelet            Created container webserver\n  Normal   Started      5m55s  kubelet            Started container webserver\n"

    Sep  3 09:35:29.863: INFO: Name:         netserver-3
    Namespace:    pod-network-test-7731
    Priority:     0
    Node:         k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1/172.18.0.5
    Start Time:   Sat, 03 Sep 2022 09:29:32 +0000
    Labels:       selector-395d237f-7d9f-4760-bd30-2dc73aaf4fe3=true
... skipping 40 lines ...
    Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
    Events:
      Type     Reason       Age    From               Message
      ----     ------       ----   ----               -------
      Normal   Scheduled    5m57s  default-scheduler  Successfully assigned pod-network-test-7731/netserver-3 to k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1
      Warning  FailedMount  5m56s  kubelet            MountVolume.SetUp failed for volume "kube-api-access-rjbps" : failed to sync configmap cache: timed out waiting for the condition

      Normal   Pulled       5m56s  kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.39" already present on machine
      Normal   Created      5m55s  kubelet            Created container webserver
      Normal   Started      5m55s  kubelet            Started container webserver
    
    Sep  3 09:35:29.863: INFO: encountered error during dial (did not find expected responses... 

    Tries 46
    Command curl -g -q -s 'http://192.168.0.68:9080/dial?request=hostname&protocol=http&host=192.168.2.23&port=8083&tries=1'
    retrieved map[]
    expected map[netserver-2:{}])
    Sep  3 09:35:29.863: INFO: ... Done probing pod [[[ 192.168.2.23 ]]]
    Sep  3 09:35:29.863: INFO: succeeded at polling 3 out of 4 connections
    Sep  3 09:35:29.863: INFO: pod polling failure summary:
    Sep  3 09:35:29.863: INFO: Collected error: did not find expected responses... 

    Tries 46
    Command curl -g -q -s 'http://192.168.0.68:9080/dial?request=hostname&protocol=http&host=192.168.2.23&port=8083&tries=1'
    retrieved map[]
    expected map[netserver-2:{}]
    Sep  3 09:35:29.863: FAIL: failed,  1 out of 4 connections failed

    
    Full Stack Trace
    k8s.io/kubernetes/test/e2e/common/network.glob..func1.1.2()
    	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/network/networking.go:82 +0x69
    k8s.io/kubernetes/test/e2e.RunE2ETests(0xc000c68a80)
    	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c
... skipping 14 lines ...
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/network/framework.go:23
      Granular Checks: Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/network/networking.go:30
        should function for intra-pod communication: http [NodeConformance] [Conformance] [It]
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    
        Sep  3 09:35:29.863: failed,  1 out of 4 connections failed

    
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/network/networking.go:82
    ------------------------------
    {"msg":"FAILED [sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]","total":-1,"completed":8,"skipped":237,"failed":1,"failures":["[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
    Sep  3 09:25:29.007: 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 ...
    Sep  3 09:25:31.160: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:31.163: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:31.166: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:31.169: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:31.171: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:31.174: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:31.174: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-6870 wheezy_tcp@dns-test-service.dns-6870 wheezy_udp@dns-test-service.dns-6870.svc wheezy_tcp@dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_udp@dns-test-service.dns-6870.svc jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:25:36.180: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:36.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:36.187: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:36.189: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:36.191: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 17 lines ...
    Sep  3 09:25:36.239: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:36.241: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:36.244: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:36.247: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:36.249: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:36.252: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:36.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-6870 wheezy_tcp@dns-test-service.dns-6870 wheezy_udp@dns-test-service.dns-6870.svc wheezy_tcp@dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_udp@dns-test-service.dns-6870.svc jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:25:41.181: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:41.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:41.188: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:41.190: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:41.193: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 17 lines ...
    Sep  3 09:25:41.240: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:41.242: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:41.245: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:41.247: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:41.250: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:41.253: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:41.253: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-6870 wheezy_tcp@dns-test-service.dns-6870 wheezy_udp@dns-test-service.dns-6870.svc wheezy_tcp@dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_udp@dns-test-service.dns-6870.svc jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:25:46.181: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:46.185: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:46.187: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:46.190: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:46.194: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 17 lines ...
    Sep  3 09:25:46.243: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:46.246: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:46.248: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:46.251: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:46.254: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:46.256: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:46.256: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-6870 wheezy_tcp@dns-test-service.dns-6870 wheezy_udp@dns-test-service.dns-6870.svc wheezy_tcp@dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_udp@dns-test-service.dns-6870.svc jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:25:51.182: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:51.185: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:51.188: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:51.190: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:51.193: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 17 lines ...
    Sep  3 09:25:51.246: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:51.249: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:51.252: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:51.257: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:51.260: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:51.263: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:51.263: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-6870 wheezy_tcp@dns-test-service.dns-6870 wheezy_udp@dns-test-service.dns-6870.svc wheezy_tcp@dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_udp@dns-test-service.dns-6870.svc jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:25:56.181: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:56.185: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:56.188: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:56.191: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:56.194: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 17 lines ...
    Sep  3 09:25:56.242: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:56.245: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:56.247: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:56.250: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:56.253: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:56.255: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:25:56.255: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-6870 wheezy_tcp@dns-test-service.dns-6870 wheezy_udp@dns-test-service.dns-6870.svc wheezy_tcp@dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_udp@dns-test-service.dns-6870.svc jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:26:01.181: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:01.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:01.191: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:01.194: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:01.196: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 16 lines ...
    Sep  3 09:26:01.241: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:01.244: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:01.246: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:01.248: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:01.251: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:01.254: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:01.254: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-6870 wheezy_udp@dns-test-service.dns-6870.svc wheezy_tcp@dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_udp@dns-test-service.dns-6870.svc jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:26:06.179: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:06.182: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:06.187: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:06.189: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:06.192: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 16 lines ...
    Sep  3 09:26:06.237: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:06.240: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:06.242: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:06.247: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:06.250: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:06.253: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:06.253: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-6870 wheezy_udp@dns-test-service.dns-6870.svc wheezy_tcp@dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_udp@dns-test-service.dns-6870.svc jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:26:11.178: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:11.181: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:11.190: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:11.193: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:11.196: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 15 lines ...
    Sep  3 09:26:11.238: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:11.241: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:11.243: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:11.246: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:11.254: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:11.259: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:11.259: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-6870 wheezy_udp@dns-test-service.dns-6870.svc wheezy_tcp@dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:26:16.181: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:16.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:16.189: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:16.191: INFO: Unable to read wheezy_udp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:16.194: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 15 lines ...
    Sep  3 09:26:16.234: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:16.237: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:16.240: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:16.243: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:16.245: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:16.248: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:16.248: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-6870 wheezy_udp@dns-test-service.dns-6870.svc wheezy_tcp@dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:26:21.181: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:21.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:21.196: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:21.198: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:21.201: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 13 lines ...
    Sep  3 09:26:21.238: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:21.241: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:21.243: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:21.246: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:21.248: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:21.250: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:21.250: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:26:26.182: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:26.185: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:26.195: INFO: Unable to read wheezy_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:26.198: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:26.200: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 13 lines ...
    Sep  3 09:26:26.235: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:26.238: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:26.240: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:26.242: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:26.245: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:26.248: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:26.248: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.dns-test-service.dns-6870.svc wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:26:31.182: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:31.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:31.199: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:31.201: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:31.204: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 11 lines ...
    Sep  3 09:26:31.239: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:31.241: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:31.243: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:31.246: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:31.248: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:31.250: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:31.250: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:26:36.179: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:36.182: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:36.197: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:36.199: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:36.202: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 11 lines ...
    Sep  3 09:26:36.261: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:36.263: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:36.266: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:36.268: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:36.271: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:36.274: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:36.274: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870.svc jessie_udp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:26:41.180: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:41.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:41.200: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:41.202: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:41.205: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 10 lines ...
    Sep  3 09:26:41.243: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:41.246: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:41.249: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:41.252: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:41.256: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:41.259: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:41.259: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:26:46.181: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:46.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:46.200: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:46.202: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:46.204: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 10 lines ...
    Sep  3 09:26:46.239: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:46.242: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:46.245: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:46.247: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:46.250: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:46.252: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:46.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-6870.svc wheezy_udp@_http._tcp.test-service-2.dns-6870.svc wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:26:51.181: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:51.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:51.208: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:51.211: INFO: Unable to read wheezy_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:51.213: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 8 lines ...
    Sep  3 09:26:51.240: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:51.242: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:51.244: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:51.247: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:51.249: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:51.251: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:51.251: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:26:56.181: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:56.186: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:56.209: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:56.211: INFO: Unable to read wheezy_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:56.214: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 8 lines ...
    Sep  3 09:26:56.242: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:56.244: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:56.247: INFO: Unable to read jessie_udp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:56.249: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:56.252: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:56.255: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:26:56.255: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.test-service-2.dns-6870.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_udp@_http._tcp.test-service-2.dns-6870.svc jessie_tcp@_http._tcp.test-service-2.dns-6870.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:27:01.178: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:01.180: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:01.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:01.211: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:01.213: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 3 lines ...
    Sep  3 09:27:01.224: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:01.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:01.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:01.244: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:01.247: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:01.249: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:01.249: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:27:06.179: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:06.183: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:06.210: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:06.212: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:06.215: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
... skipping 3 lines ...
    Sep  3 09:27:06.225: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:06.231: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:06.237: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:06.247: INFO: Unable to read jessie_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:06.250: INFO: Unable to read 10.134.128.128_udp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:06.252: INFO: Unable to read 10.134.128.128_tcp@PTR from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:06.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc jessie_tcp@PodARecord 10.134.128.128_udp@PTR 10.134.128.128_tcp@PTR]

    
    Sep  3 09:27:11.179: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:11.182: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:11.209: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:11.216: INFO: Unable to read jessie_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:11.219: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:11.221: INFO: Unable to read jessie_udp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:11.224: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870 from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:11.229: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:11.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:11.250: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870 jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:27:16.181: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:16.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:16.209: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:16.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:16.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:16.248: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:27:21.181: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:21.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:21.210: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:21.231: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:21.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:21.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:27:26.178: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:26.190: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:26.234: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:26.255: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:26.260: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:26.275: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:27:31.181: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:31.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:31.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:31.234: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:31.239: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:31.255: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:27:36.181: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:36.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:36.209: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:36.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:36.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:36.251: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:27:41.177: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:41.180: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:41.206: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:41.226: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:41.230: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:41.246: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:27:46.180: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:46.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:46.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:46.236: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:46.241: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:46.256: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:27:51.185: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:51.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:51.227: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:51.231: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:51.247: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:27:56.198: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:56.262: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:56.303: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:56.310: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:27:56.343: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:28:01.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:01.214: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:01.235: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:01.241: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:01.256: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:28:06.183: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:06.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:06.246: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:06.252: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:06.270: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:28:11.182: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:11.214: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:11.253: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:11.258: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:11.272: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:28:16.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:16.214: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:16.237: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:16.243: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:16.261: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:28:21.185: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:21.213: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:21.233: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:21.238: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:21.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:28:26.185: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:26.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:26.227: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:26.232: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:26.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:28:31.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:31.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:31.231: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:31.236: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:31.251: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:28:36.180: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:36.205: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:36.225: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:36.230: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:36.250: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:28:41.181: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:41.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:41.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:41.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:41.247: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:28:46.186: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:46.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:46.239: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:46.244: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:46.261: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:28:51.182: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:51.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:51.233: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:51.239: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:51.254: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:28:56.182: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:56.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:56.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:56.236: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:28:56.259: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:29:01.183: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:01.209: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:01.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:01.232: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:01.248: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:29:06.183: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:06.207: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:06.232: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:06.242: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:06.267: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:29:11.180: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:11.206: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:11.226: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:11.231: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:11.247: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:29:16.187: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:16.214: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:16.234: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:16.240: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:16.259: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:29:21.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:21.217: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:21.239: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:21.248: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:21.262: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:29:26.181: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:26.214: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:26.244: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:26.250: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:26.270: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:29:31.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:31.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:31.231: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:31.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:31.250: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:29:36.182: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:36.211: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:36.231: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:36.236: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:36.251: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:29:41.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:41.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:41.227: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:41.231: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:41.247: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:29:46.185: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:46.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:46.234: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:46.238: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:46.254: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:29:51.185: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:51.218: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:51.238: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:51.247: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:51.263: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:29:56.186: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:56.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:56.235: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:56.248: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:29:56.267: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:30:01.185: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:01.211: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:01.229: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:01.234: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:01.248: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:30:06.185: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:06.209: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:06.229: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:06.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:06.248: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:30:11.180: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:11.205: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:11.225: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:11.231: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:11.247: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:30:16.182: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:16.207: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:16.227: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:16.231: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:16.245: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:30:21.185: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:21.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:21.232: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:21.237: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:21.255: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:30:26.181: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:26.206: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:26.227: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:26.232: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:26.247: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:30:31.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:31.218: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:31.258: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:31.263: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:31.278: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:30:36.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:36.209: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:36.231: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:36.236: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:36.251: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:30:41.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:41.209: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:41.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:41.232: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:41.246: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:30:46.182: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:46.207: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:46.227: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:46.232: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:46.255: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:30:51.182: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:51.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:51.234: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:51.238: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:51.259: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:30:56.184: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:56.211: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:56.231: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:56.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:30:56.253: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:31:01.183: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:01.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:01.232: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:01.238: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:01.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@dns-test-service wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:31:06.206: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:06.225: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:06.230: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:06.245: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:31:11.210: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:11.230: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:11.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:11.251: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:31:16.211: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:16.230: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:16.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:16.249: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:31:21.211: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:21.230: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:21.241: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:21.273: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:31:26.206: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:26.227: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:26.232: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:26.247: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:31:31.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:31.230: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:31.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:31.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:31:36.211: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:36.232: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:36.238: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:36.254: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:31:41.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:41.233: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:41.237: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:41.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:31:46.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:46.237: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:46.243: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:46.259: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:31:51.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:51.227: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:51.232: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:51.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:31:56.206: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:56.226: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:56.231: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:31:56.246: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:32:01.211: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:01.232: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:01.236: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:01.251: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:32:06.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:06.232: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:06.237: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:06.255: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:32:11.213: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:11.233: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:11.237: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:11.276: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:32:16.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:16.227: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:16.232: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:16.247: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:32:21.210: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:21.230: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:21.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:21.248: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:32:26.207: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:26.226: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:26.232: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:26.247: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:32:31.209: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:31.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:31.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:31.250: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:32:36.210: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:36.230: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:36.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:36.250: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:32:41.215: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:41.237: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:41.241: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:41.257: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:32:46.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:46.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:46.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:46.251: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:32:51.211: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:51.233: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:51.238: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:51.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:32:56.204: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:56.224: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:56.229: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:32:56.244: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:33:01.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:01.231: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:01.236: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:01.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:33:06.207: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:06.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:06.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:06.248: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:33:11.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:11.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:11.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:11.246: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:33:16.209: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:16.230: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:16.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:16.249: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:33:21.209: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:21.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:21.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:21.248: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:33:26.210: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:26.229: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:26.234: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:26.248: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:33:31.213: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:31.233: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:31.238: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:31.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:33:36.210: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:36.230: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:36.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:36.253: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:33:41.207: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:41.227: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:41.232: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:41.246: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:33:46.214: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:46.234: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:46.239: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:46.267: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:33:51.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:51.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:51.234: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:51.247: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:33:56.214: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:56.232: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:56.237: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:33:56.251: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:34:01.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:01.229: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:01.234: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:01.250: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:34:06.206: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:06.225: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:06.229: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:06.243: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:34:11.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:11.231: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:11.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:11.250: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:34:16.212: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:16.231: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:16.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:16.250: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:34:21.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:21.230: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:21.234: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:21.255: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:34:26.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:26.230: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:26.234: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:26.251: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:34:31.208: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:31.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:31.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:31.247: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:34:36.211: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:36.230: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:36.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:36.249: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:34:41.207: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:41.227: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:41.232: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:41.247: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:34:46.207: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:46.227: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:46.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:46.249: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:34:51.206: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:51.225: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:51.230: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:51.244: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:34:56.210: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:56.231: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:56.236: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:34:56.252: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:35:01.216: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:01.246: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:01.252: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:01.266: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:35:06.209: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:06.228: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:06.234: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:06.248: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:35:11.210: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:11.227: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:11.234: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:11.249: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:35:16.218: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:16.240: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:16.245: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:16.260: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:35:21.211: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:21.229: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:21.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:21.246: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:35:26.210: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:26.230: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:26.235: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:26.250: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:35:31.210: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:31.229: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:31.233: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:31.247: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:35:31.283: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:31.308: INFO: Unable to read jessie_tcp@dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:31.313: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc from pod dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8: the server could not find the requested resource (get pods dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8)
    Sep  3 09:35:31.481: INFO: Lookups using dns-6870/dns-test-fb65f985-1de5-4bd4-8807-5c770ce3f5f8 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-6870.svc jessie_tcp@_http._tcp.dns-test-service.dns-6870.svc]

    
    Sep  3 09:35:31.481: FAIL: Unexpected error:

        <*errors.errorString | 0xc000250290>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    occurred
    
... skipping 26 lines ...
    • Failure [602.725 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
    
      Sep  3 09:35:31.481: Unexpected error:

          <*errors.errorString | 0xc000250290>: {
              s: "timed out waiting for the condition",
          }
          timed out waiting for the condition
      occurred
    
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:463
    ------------------------------
    {"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":17,"skipped":306,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    [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
    Sep  3 09:35:27.362: 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 31 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:35:47.486: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-3508" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should validate Statefulset Status endpoints [Conformance]","total":-1,"completed":18,"skipped":306,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSS
    ------------------------------
    [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
    Sep  3 09:35:47.502: 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 projection with secret that has name projected-secret-test-map-6a8a5067-eef2-463a-86b0-170c46959dc3
    STEP: Creating a pod to test consume secrets
    Sep  3 09:35:47.536: INFO: Waiting up to 5m0s for pod "pod-projected-secrets-36c51f34-738f-46ed-bf84-716bdf9af483" in namespace "projected-9027" to be "Succeeded or Failed"

    Sep  3 09:35:47.539: INFO: Pod "pod-projected-secrets-36c51f34-738f-46ed-bf84-716bdf9af483": Phase="Pending", Reason="", readiness=false. Elapsed: 2.253762ms
    Sep  3 09:35:49.544: INFO: Pod "pod-projected-secrets-36c51f34-738f-46ed-bf84-716bdf9af483": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007240517s
    Sep  3 09:35:51.548: INFO: Pod "pod-projected-secrets-36c51f34-738f-46ed-bf84-716bdf9af483": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.01126055s
    STEP: Saw pod success
    Sep  3 09:35:51.548: INFO: Pod "pod-projected-secrets-36c51f34-738f-46ed-bf84-716bdf9af483" satisfied condition "Succeeded or Failed"

    Sep  3 09:35:51.551: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-projected-secrets-36c51f34-738f-46ed-bf84-716bdf9af483 container projected-secret-volume-test: <nil>
    STEP: delete the pod
    Sep  3 09:35:51.568: INFO: Waiting for pod pod-projected-secrets-36c51f34-738f-46ed-bf84-716bdf9af483 to disappear
    Sep  3 09:35:51.573: INFO: Pod pod-projected-secrets-36c51f34-738f-46ed-bf84-716bdf9af483 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
    Sep  3 09:35:51.573: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-9027" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected secret should be consumable from pods in volume with mappings [NodeConformance] [Conformance]","total":-1,"completed":19,"skipped":311,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:35:51.637: 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-365c07df-273a-44f4-87f1-e11424caaa6c
    STEP: Creating a pod to test consume configMaps
    Sep  3 09:35:51.677: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-bc538ecc-e50f-4644-bac9-2d2a6ddf49c0" in namespace "projected-6808" to be "Succeeded or Failed"

    Sep  3 09:35:51.681: INFO: Pod "pod-projected-configmaps-bc538ecc-e50f-4644-bac9-2d2a6ddf49c0": Phase="Pending", Reason="", readiness=false. Elapsed: 4.086138ms
    Sep  3 09:35:53.685: INFO: Pod "pod-projected-configmaps-bc538ecc-e50f-4644-bac9-2d2a6ddf49c0": Phase="Running", Reason="", readiness=false. Elapsed: 2.008402978s
    Sep  3 09:35:55.690: INFO: Pod "pod-projected-configmaps-bc538ecc-e50f-4644-bac9-2d2a6ddf49c0": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.012713457s
    STEP: Saw pod success
    Sep  3 09:35:55.690: INFO: Pod "pod-projected-configmaps-bc538ecc-e50f-4644-bac9-2d2a6ddf49c0" satisfied condition "Succeeded or Failed"

    Sep  3 09:35:55.693: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-projected-configmaps-bc538ecc-e50f-4644-bac9-2d2a6ddf49c0 container projected-configmap-volume-test: <nil>
    STEP: delete the pod
    Sep  3 09:35:55.708: INFO: Waiting for pod pod-projected-configmaps-bc538ecc-e50f-4644-bac9-2d2a6ddf49c0 to disappear
    Sep  3 09:35:55.711: INFO: Pod pod-projected-configmaps-bc538ecc-e50f-4644-bac9-2d2a6ddf49c0 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
    Sep  3 09:35:55.711: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-6808" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected configMap should be consumable in multiple volumes in the same pod [NodeConformance] [Conformance]","total":-1,"completed":20,"skipped":352,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 17 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:35:58.304: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "pods-6122" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Pods should be updated [NodeConformance] [Conformance]","total":-1,"completed":21,"skipped":372,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSS
    ------------------------------
    [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 16 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:36:02.448: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "disruption-5757" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] DisruptionController should update/patch PodDisruptionBudget status [Conformance]","total":-1,"completed":22,"skipped":386,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 12 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:36:20.644: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "crd-publish-openapi-5638" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] updates the published spec when one version gets renamed [Conformance]","total":-1,"completed":23,"skipped":412,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:36:20.724: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "server-version-4380" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] server version should find the server version [Conformance]","total":-1,"completed":24,"skipped":438,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSS
    ------------------------------
    [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
    Sep  3 09:36:20.740: 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
    Sep  3 09:36:20.767: INFO: Waiting up to 5m0s for pod "alpine-nnp-false-fd2119c5-6417-4fcf-8c64-e4243ff464a2" in namespace "security-context-test-7527" to be "Succeeded or Failed"

    Sep  3 09:36:20.769: INFO: Pod "alpine-nnp-false-fd2119c5-6417-4fcf-8c64-e4243ff464a2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.096643ms
    Sep  3 09:36:22.773: INFO: Pod "alpine-nnp-false-fd2119c5-6417-4fcf-8c64-e4243ff464a2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.0061036s
    Sep  3 09:36:24.777: INFO: Pod "alpine-nnp-false-fd2119c5-6417-4fcf-8c64-e4243ff464a2": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.009940538s
    Sep  3 09:36:24.777: INFO: Pod "alpine-nnp-false-fd2119c5-6417-4fcf-8c64-e4243ff464a2" 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
    Sep  3 09:36:24.783: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "security-context-test-7527" 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":25,"skipped":445,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSS
    ------------------------------
    [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 25 lines ...
    Sep  3 09:29:12.018: INFO: stderr: ""
    Sep  3 09:29:12.018: INFO: stdout: "true"
    Sep  3 09:29:12.018: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1781 get pods update-demo-nautilus-c4gvz -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
    Sep  3 09:29:12.082: INFO: stderr: ""
    Sep  3 09:29:12.082: INFO: stdout: "k8s.gcr.io/e2e-test-images/nautilus:1.4"
    Sep  3 09:29:12.082: INFO: validating pod update-demo-nautilus-c4gvz
    Sep  3 09:32:45.450: INFO: update-demo-nautilus-c4gvz is running right image but validator function failed: the server is currently unable to handle the request (get pods update-demo-nautilus-c4gvz)

    Sep  3 09:32:50.454: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1781 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo'
    Sep  3 09:32:50.528: INFO: stderr: ""
    Sep  3 09:32:50.528: INFO: stdout: "update-demo-nautilus-c4gvz update-demo-nautilus-wsbjf "
    Sep  3 09:32:50.528: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1781 get pods update-demo-nautilus-c4gvz -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}'
    Sep  3 09:32:50.594: INFO: stderr: ""
    Sep  3 09:32:50.594: INFO: stdout: "true"
    Sep  3 09:32:50.594: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1781 get pods update-demo-nautilus-c4gvz -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}'
    Sep  3 09:32:50.660: INFO: stderr: ""
    Sep  3 09:32:50.660: INFO: stdout: "k8s.gcr.io/e2e-test-images/nautilus:1.4"
    Sep  3 09:32:50.660: INFO: validating pod update-demo-nautilus-c4gvz
    Sep  3 09:36:24.582: INFO: update-demo-nautilus-c4gvz is running right image but validator function failed: the server is currently unable to handle the request (get pods update-demo-nautilus-c4gvz)

    Sep  3 09:36:29.583: FAIL: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state

    
    Full Stack Trace
    k8s.io/kubernetes/test/e2e/kubectl.glob..func1.6.2()
    	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:314 +0x2a5
    k8s.io/kubernetes/test/e2e.RunE2ETests(0xc000362300)
    	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c
... skipping 54 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:36:32.892: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "dns-7044" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] DNS should provide DNS for the cluster  [Conformance]","total":-1,"completed":26,"skipped":456,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSS
    ------------------------------
    [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-6665" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should test the lifecycle of an Endpoint [Conformance]","total":-1,"completed":27,"skipped":464,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    {"msg":"FAILED [sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]","total":-1,"completed":52,"skipped":1144,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

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

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:36:33.018: 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 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 secret with name secret-test-26711470-eaea-4d44-86ce-2ef53c313092
    STEP: Creating a pod to test consume secrets
    Sep  3 09:36:33.067: INFO: Waiting up to 5m0s for pod "pod-secrets-91e8140b-c09a-49c1-80d6-dfe784d9a2a3" in namespace "secrets-3856" to be "Succeeded or Failed"

    Sep  3 09:36:33.070: INFO: Pod "pod-secrets-91e8140b-c09a-49c1-80d6-dfe784d9a2a3": Phase="Pending", Reason="", readiness=false. Elapsed: 3.156253ms
    Sep  3 09:36:35.075: INFO: Pod "pod-secrets-91e8140b-c09a-49c1-80d6-dfe784d9a2a3": Phase="Pending", Reason="", readiness=false. Elapsed: 2.007846728s
    Sep  3 09:36:37.080: INFO: Pod "pod-secrets-91e8140b-c09a-49c1-80d6-dfe784d9a2a3": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.012524493s
    STEP: Saw pod success
    Sep  3 09:36:37.080: INFO: Pod "pod-secrets-91e8140b-c09a-49c1-80d6-dfe784d9a2a3" satisfied condition "Succeeded or Failed"

    Sep  3 09:36:37.082: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-secrets-91e8140b-c09a-49c1-80d6-dfe784d9a2a3 container secret-volume-test: <nil>
    STEP: delete the pod
    Sep  3 09:36:37.094: INFO: Waiting for pod pod-secrets-91e8140b-c09a-49c1-80d6-dfe784d9a2a3 to disappear
    Sep  3 09:36:37.097: INFO: Pod pod-secrets-91e8140b-c09a-49c1-80d6-dfe784d9a2a3 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
    Sep  3 09:36:37.097: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-3856" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Secrets should be consumable from pods in volume with defaultMode set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":28,"skipped":487,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSS
    ------------------------------
    [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
    Sep  3 09:36:37.200: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "events-4584" 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":29,"skipped":495,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 25 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:36:39.070: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-4598" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment Deployment should have a working scale subresource [Conformance]","total":-1,"completed":54,"skipped":1161,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:36:39.192: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "kubectl-489" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-cli] Kubectl client Proxy server should support --unix-socket=/path  [Conformance]","total":-1,"completed":55,"skipped":1178,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:36:37.277: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename var-expansion
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should allow composing env vars into new env vars [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating a pod to test env composition
    Sep  3 09:36:37.308: INFO: Waiting up to 5m0s for pod "var-expansion-e91a20b9-6dd9-4e97-a6c8-b2a40f96e58a" in namespace "var-expansion-5776" to be "Succeeded or Failed"

    Sep  3 09:36:37.311: INFO: Pod "var-expansion-e91a20b9-6dd9-4e97-a6c8-b2a40f96e58a": Phase="Pending", Reason="", readiness=false. Elapsed: 2.51618ms
    Sep  3 09:36:39.315: INFO: Pod "var-expansion-e91a20b9-6dd9-4e97-a6c8-b2a40f96e58a": Phase="Pending", Reason="", readiness=false. Elapsed: 2.006422633s
    Sep  3 09:36:41.319: INFO: Pod "var-expansion-e91a20b9-6dd9-4e97-a6c8-b2a40f96e58a": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.010513717s
    STEP: Saw pod success
    Sep  3 09:36:41.319: INFO: Pod "var-expansion-e91a20b9-6dd9-4e97-a6c8-b2a40f96e58a" satisfied condition "Succeeded or Failed"

    Sep  3 09:36:41.322: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-jh8sn pod var-expansion-e91a20b9-6dd9-4e97-a6c8-b2a40f96e58a container dapi-container: <nil>
    STEP: delete the pod
    Sep  3 09:36:41.334: INFO: Waiting for pod var-expansion-e91a20b9-6dd9-4e97-a6c8-b2a40f96e58a to disappear
    Sep  3 09:36:41.336: INFO: Pod var-expansion-e91a20b9-6dd9-4e97-a6c8-b2a40f96e58a 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
    Sep  3 09:36:41.336: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-5776" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Variable Expansion should allow composing env vars into new env vars [NodeConformance] [Conformance]","total":-1,"completed":30,"skipped":554,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:36:45.785: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-4677" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected downwardAPI should update labels on modification [NodeConformance] [Conformance]","total":-1,"completed":56,"skipped":1188,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    [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
    Sep  3 09:36:45.796: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename discovery
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 82 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:36:46.230: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "discovery-1503" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Discovery should validate PreferredVersion for each APIGroup [Conformance]","total":-1,"completed":57,"skipped":1188,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    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 27 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:36:47.500: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "disruption-3803" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] DisruptionController should block an eviction until the PDB is updated to allow it [Conformance]","total":-1,"completed":31,"skipped":574,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    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
    Sep  3 09:36:46.251: 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 in multiple volumes in a pod [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-5862a9a2-1ced-4fc1-a145-a4362a003703
    STEP: Creating a pod to test consume secrets
    Sep  3 09:36:46.291: INFO: Waiting up to 5m0s for pod "pod-secrets-32a157f1-0105-432a-9119-6e39241eaa6d" in namespace "secrets-2771" to be "Succeeded or Failed"

    Sep  3 09:36:46.294: INFO: Pod "pod-secrets-32a157f1-0105-432a-9119-6e39241eaa6d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.748118ms
    Sep  3 09:36:48.297: INFO: Pod "pod-secrets-32a157f1-0105-432a-9119-6e39241eaa6d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.006148923s
    Sep  3 09:36:50.301: INFO: Pod "pod-secrets-32a157f1-0105-432a-9119-6e39241eaa6d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.010058119s
    STEP: Saw pod success
    Sep  3 09:36:50.301: INFO: Pod "pod-secrets-32a157f1-0105-432a-9119-6e39241eaa6d" satisfied condition "Succeeded or Failed"

    Sep  3 09:36:50.304: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod pod-secrets-32a157f1-0105-432a-9119-6e39241eaa6d container secret-volume-test: <nil>
    STEP: delete the pod
    Sep  3 09:36:50.324: INFO: Waiting for pod pod-secrets-32a157f1-0105-432a-9119-6e39241eaa6d to disappear
    Sep  3 09:36:50.326: INFO: Pod pod-secrets-32a157f1-0105-432a-9119-6e39241eaa6d 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
    Sep  3 09:36:50.326: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-2771" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Secrets should be consumable in multiple volumes in a pod [NodeConformance] [Conformance]","total":-1,"completed":58,"skipped":1198,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:36:50.405: 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 [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-f8ea7891-25ce-4480-aa84-06e446fd95da
    STEP: Creating a pod to test consume secrets
    Sep  3 09:36:50.436: INFO: Waiting up to 5m0s for pod "pod-secrets-25a8cf51-f56a-470d-9f61-dcf71925fa68" in namespace "secrets-7788" to be "Succeeded or Failed"

    Sep  3 09:36:50.440: INFO: Pod "pod-secrets-25a8cf51-f56a-470d-9f61-dcf71925fa68": Phase="Pending", Reason="", readiness=false. Elapsed: 3.964041ms
    Sep  3 09:36:52.445: INFO: Pod "pod-secrets-25a8cf51-f56a-470d-9f61-dcf71925fa68": Phase="Pending", Reason="", readiness=false. Elapsed: 2.00846535s
    Sep  3 09:36:54.449: INFO: Pod "pod-secrets-25a8cf51-f56a-470d-9f61-dcf71925fa68": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.012471952s
    STEP: Saw pod success
    Sep  3 09:36:54.449: INFO: Pod "pod-secrets-25a8cf51-f56a-470d-9f61-dcf71925fa68" satisfied condition "Succeeded or Failed"

    Sep  3 09:36:54.451: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod pod-secrets-25a8cf51-f56a-470d-9f61-dcf71925fa68 container secret-volume-test: <nil>
    STEP: delete the pod
    Sep  3 09:36:54.463: INFO: Waiting for pod pod-secrets-25a8cf51-f56a-470d-9f61-dcf71925fa68 to disappear
    Sep  3 09:36:54.465: INFO: Pod pod-secrets-25a8cf51-f56a-470d-9f61-dcf71925fa68 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
    Sep  3 09:36:54.465: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-7788" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Secrets should be consumable from pods in volume [NodeConformance] [Conformance]","total":-1,"completed":59,"skipped":1263,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    S
    ------------------------------
    [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-9463" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should find a service from listing all namespaces [Conformance]","total":-1,"completed":60,"skipped":1264,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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-1147
    STEP: Waiting until pod test-pod will start running in namespace statefulset-1147
    STEP: Creating statefulset with conflicting port in namespace statefulset-1147
    STEP: Waiting until stateful pod ss-0 will be recreated and deleted at least once in namespace statefulset-1147
    Sep  3 09:36:56.606: INFO: Observed stateful pod in namespace: statefulset-1147, name: ss-0, uid: 3fdbfe90-7920-4a80-90ea-76f66dcf88c1, status phase: Pending. Waiting for statefulset controller to delete.
    Sep  3 09:36:56.618: INFO: Observed stateful pod in namespace: statefulset-1147, name: ss-0, uid: 3fdbfe90-7920-4a80-90ea-76f66dcf88c1, status phase: Failed. Waiting for statefulset controller to delete.

    Sep  3 09:36:56.625: INFO: Observed stateful pod in namespace: statefulset-1147, name: ss-0, uid: 3fdbfe90-7920-4a80-90ea-76f66dcf88c1, status phase: Failed. Waiting for statefulset controller to delete.

    Sep  3 09:36:56.627: INFO: Observed delete event for stateful pod ss-0 in namespace statefulset-1147
    STEP: Removing pod with conflicting port in namespace statefulset-1147
    STEP: Waiting when stateful pod ss-0 will be recreated in namespace statefulset-1147 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:118
    Sep  3 09:36:58.648: INFO: Deleting all statefulset in ns statefulset-1147
... skipping 4 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:37:08.677: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-1147" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Should recreate evicted statefulset [Conformance]","total":-1,"completed":61,"skipped":1297,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSS
    ------------------------------
    [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-3869-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 pruning [Conformance]","total":-1,"completed":62,"skipped":1306,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:37:15.557: 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-fad16b70-adb9-4bf8-985f-a5017e46f29d
    STEP: Creating a pod to test consume secrets
    Sep  3 09:37:15.609: INFO: Waiting up to 5m0s for pod "pod-secrets-b9bcdf92-d1c9-44b1-9f94-fafc74c06532" in namespace "secrets-2211" to be "Succeeded or Failed"

    Sep  3 09:37:15.613: INFO: Pod "pod-secrets-b9bcdf92-d1c9-44b1-9f94-fafc74c06532": Phase="Pending", Reason="", readiness=false. Elapsed: 3.192641ms
    Sep  3 09:37:17.618: INFO: Pod "pod-secrets-b9bcdf92-d1c9-44b1-9f94-fafc74c06532": Phase="Pending", Reason="", readiness=false. Elapsed: 2.008262198s
    Sep  3 09:37:19.622: INFO: Pod "pod-secrets-b9bcdf92-d1c9-44b1-9f94-fafc74c06532": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.012238069s
    STEP: Saw pod success
    Sep  3 09:37:19.622: INFO: Pod "pod-secrets-b9bcdf92-d1c9-44b1-9f94-fafc74c06532" satisfied condition "Succeeded or Failed"

    Sep  3 09:37:19.625: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-secrets-b9bcdf92-d1c9-44b1-9f94-fafc74c06532 container secret-volume-test: <nil>
    STEP: delete the pod
    Sep  3 09:37:19.638: INFO: Waiting for pod pod-secrets-b9bcdf92-d1c9-44b1-9f94-fafc74c06532 to disappear
    Sep  3 09:37:19.640: INFO: Pod pod-secrets-b9bcdf92-d1c9-44b1-9f94-fafc74c06532 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
    Sep  3 09:37:19.640: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-2211" 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":63,"skipped":1361,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
... skipping 20 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:37:24.287: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-3394" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Variable Expansion should succeed in writing subpaths in container [Slow] [Conformance]","total":-1,"completed":32,"skipped":586,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:37:24.323: 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-1a15c34f-64c1-44e2-a3a5-143c9c4a7b7a
    STEP: Creating a pod to test consume configMaps
    Sep  3 09:37:24.358: INFO: Waiting up to 5m0s for pod "pod-configmaps-1bc74f5c-4426-418b-b62c-7e4df364c13d" in namespace "configmap-8025" to be "Succeeded or Failed"

    Sep  3 09:37:24.361: INFO: Pod "pod-configmaps-1bc74f5c-4426-418b-b62c-7e4df364c13d": Phase="Pending", Reason="", readiness=false. Elapsed: 3.197179ms
    Sep  3 09:37:26.365: INFO: Pod "pod-configmaps-1bc74f5c-4426-418b-b62c-7e4df364c13d": Phase="Pending", Reason="", readiness=false. Elapsed: 2.006665608s
    Sep  3 09:37:28.368: INFO: Pod "pod-configmaps-1bc74f5c-4426-418b-b62c-7e4df364c13d": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.010381597s
    STEP: Saw pod success
    Sep  3 09:37:28.369: INFO: Pod "pod-configmaps-1bc74f5c-4426-418b-b62c-7e4df364c13d" satisfied condition "Succeeded or Failed"

    Sep  3 09:37:28.371: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-configmaps-1bc74f5c-4426-418b-b62c-7e4df364c13d container agnhost-container: <nil>
    STEP: delete the pod
    Sep  3 09:37:28.386: INFO: Waiting for pod pod-configmaps-1bc74f5c-4426-418b-b62c-7e4df364c13d to disappear
    Sep  3 09:37:28.388: INFO: Pod pod-configmaps-1bc74f5c-4426-418b-b62c-7e4df364c13d 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
    Sep  3 09:37:28.388: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-8025" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume as non-root [NodeConformance] [Conformance]","total":-1,"completed":33,"skipped":610,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:37:30.521: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-wrapper-2672" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir wrapper volumes should not conflict [Conformance]","total":-1,"completed":34,"skipped":663,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSS
    ------------------------------
    [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
    Sep  3 09:37:31.167: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "svcaccounts-8644" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-auth] ServiceAccounts should allow opting out of API token automount  [Conformance]","total":-1,"completed":35,"skipped":670,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 9 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:37:36.097: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "watch-9" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Watchers should receive events on concurrent watches in same order [Conformance]","total":-1,"completed":36,"skipped":742,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    [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
    Sep  3 09:37:36.199: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename secrets
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 3 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:37:36.253: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-2787" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Secrets should be immutable if `immutable` field is set [Conformance]","total":-1,"completed":37,"skipped":742,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:37:39.814: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-7871" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should have a working scale subresource [Conformance]","total":-1,"completed":64,"skipped":1405,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    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 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
    Sep  3 09:37:36.327: INFO: Waiting up to 5m0s for pod "downwardapi-volume-c00e3f61-c457-41d4-816a-34e6f469b793" in namespace "downward-api-7506" to be "Succeeded or Failed"

    Sep  3 09:37:36.334: INFO: Pod "downwardapi-volume-c00e3f61-c457-41d4-816a-34e6f469b793": Phase="Pending", Reason="", readiness=false. Elapsed: 6.306968ms
    Sep  3 09:37:38.338: INFO: Pod "downwardapi-volume-c00e3f61-c457-41d4-816a-34e6f469b793": Phase="Pending", Reason="", readiness=false. Elapsed: 2.010148013s
    Sep  3 09:37:40.342: INFO: Pod "downwardapi-volume-c00e3f61-c457-41d4-816a-34e6f469b793": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.014859899s
    STEP: Saw pod success
    Sep  3 09:37:40.342: INFO: Pod "downwardapi-volume-c00e3f61-c457-41d4-816a-34e6f469b793" satisfied condition "Succeeded or Failed"

    Sep  3 09:37:40.345: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod downwardapi-volume-c00e3f61-c457-41d4-816a-34e6f469b793 container client-container: <nil>
    STEP: delete the pod
    Sep  3 09:37:40.359: INFO: Waiting for pod downwardapi-volume-c00e3f61-c457-41d4-816a-34e6f469b793 to disappear
    Sep  3 09:37:40.361: INFO: Pod downwardapi-volume-c00e3f61-c457-41d4-816a-34e6f469b793 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
    Sep  3 09:37:40.361: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-7506" 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":38,"skipped":762,"failed":2,"failures":["[sig-apps] ReplicationController should serve a basic image on each replica with a public image  [Conformance]","[sig-node] Container Lifecycle Hook when create a pod with lifecycle hook should execute prestop exec hook properly [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:37:39.841: 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-0bfd1555-dc33-45cd-90bc-1adc54354326
    STEP: Creating a pod to test consume secrets
    Sep  3 09:37:39.895: INFO: Waiting up to 5m0s for pod "pod-secrets-5b1e2b0d-d4b2-47d4-8c46-4a4465565605" in namespace "secrets-8316" to be "Succeeded or Failed"

    Sep  3 09:37:39.898: INFO: Pod "pod-secrets-5b1e2b0d-d4b2-47d4-8c46-4a4465565605": Phase="Pending", Reason="", readiness=false. Elapsed: 2.308228ms
    Sep  3 09:37:41.901: INFO: Pod "pod-secrets-5b1e2b0d-d4b2-47d4-8c46-4a4465565605": Phase="Pending", Reason="", readiness=false. Elapsed: 2.005775503s
    Sep  3 09:37:43.906: INFO: Pod "pod-secrets-5b1e2b0d-d4b2-47d4-8c46-4a4465565605": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.010257263s
    STEP: Saw pod success
    Sep  3 09:37:43.906: INFO: Pod "pod-secrets-5b1e2b0d-d4b2-47d4-8c46-4a4465565605" satisfied condition "Succeeded or Failed"

    Sep  3 09:37:43.909: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-wggvfg pod pod-secrets-5b1e2b0d-d4b2-47d4-8c46-4a4465565605 container secret-volume-test: <nil>
    STEP: delete the pod
    Sep  3 09:37:43.934: INFO: Waiting for pod pod-secrets-5b1e2b0d-d4b2-47d4-8c46-4a4465565605 to disappear
    Sep  3 09:37:43.937: INFO: Pod pod-secrets-5b1e2b0d-d4b2-47d4-8c46-4a4465565605 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
    Sep  3 09:37:43.937: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "secrets-8316" for this suite.
    STEP: Destroying namespace "secret-namespace-239" 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":65,"skipped":1414,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSS
    ------------------------------
    [BeforeEach] [sig-node] Lease
      /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
    Sep  3 09:37:44.063: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "lease-test-2635" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Lease lease API should be available [Conformance]","total":-1,"completed":66,"skipped":1426,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:37:44.084: 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
    Sep  3 09:37:44.127: INFO: Waiting up to 5m0s for pod "pod-64c944ed-4e63-4839-ba6c-4709dc67589c" in namespace "emptydir-1150" to be "Succeeded or Failed"

    Sep  3 09:37:44.130: INFO: Pod "pod-64c944ed-4e63-4839-ba6c-4709dc67589c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.811883ms
    Sep  3 09:37:46.134: INFO: Pod "pod-64c944ed-4e63-4839-ba6c-4709dc67589c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.006925294s
    Sep  3 09:37:48.138: INFO: Pod "pod-64c944ed-4e63-4839-ba6c-4709dc67589c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.010697218s
    STEP: Saw pod success
    Sep  3 09:37:48.138: INFO: Pod "pod-64c944ed-4e63-4839-ba6c-4709dc67589c" satisfied condition "Succeeded or Failed"

    Sep  3 09:37:48.140: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod pod-64c944ed-4e63-4839-ba6c-4709dc67589c container test-container: <nil>
    STEP: delete the pod
    Sep  3 09:37:48.154: INFO: Waiting for pod pod-64c944ed-4e63-4839-ba6c-4709dc67589c to disappear
    Sep  3 09:37:48.156: INFO: Pod pod-64c944ed-4e63-4839-ba6c-4709dc67589c 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
    Sep  3 09:37:48.157: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-1150" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes volume on tmpfs should have the correct mode [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":67,"skipped":1435,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 106 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:38:49.680: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-9739" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] Burst scaling should run to completion even with unhealthy pods [Slow] [Conformance]","total":-1,"completed":68,"skipped":1504,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SS
    ------------------------------
    [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
    Sep  3 09:38:49.698: 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
    Sep  3 09:38:49.733: INFO: Waiting up to 5m0s for pod "pod-99a032dc-4dc9-4919-8094-1f72dbd4685c" in namespace "emptydir-7698" to be "Succeeded or Failed"

    Sep  3 09:38:49.736: INFO: Pod "pod-99a032dc-4dc9-4919-8094-1f72dbd4685c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.305575ms
    Sep  3 09:38:51.740: INFO: Pod "pod-99a032dc-4dc9-4919-8094-1f72dbd4685c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.006821921s
    Sep  3 09:38:53.744: INFO: Pod "pod-99a032dc-4dc9-4919-8094-1f72dbd4685c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.010204627s
    STEP: Saw pod success
    Sep  3 09:38:53.744: INFO: Pod "pod-99a032dc-4dc9-4919-8094-1f72dbd4685c" satisfied condition "Succeeded or Failed"

    Sep  3 09:38:53.746: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-99a032dc-4dc9-4919-8094-1f72dbd4685c container test-container: <nil>
    STEP: delete the pod
    Sep  3 09:38:53.758: INFO: Waiting for pod pod-99a032dc-4dc9-4919-8094-1f72dbd4685c to disappear
    Sep  3 09:38:53.761: INFO: Pod pod-99a032dc-4dc9-4919-8094-1f72dbd4685c 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
    Sep  3 09:38:53.761: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "emptydir-7698" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] EmptyDir volumes should support (root,0666,default) [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":69,"skipped":1506,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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-2421-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 include webhook resources in discovery documents [Conformance]","total":-1,"completed":70,"skipped":1585,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    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 25 lines ...
    STEP: Destroying namespace "services-1019" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should be able to change the type from ClusterIP to ExternalName [Conformance]","total":-1,"completed":71,"skipped":1589,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    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
    Sep  3 09:39:06.168: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "custom-resource-definition-2484" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] Simple CustomResourceDefinition creating/deleting custom resource definition objects works  [Conformance]","total":-1,"completed":72,"skipped":1597,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:39:12.774: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-9991" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Downward API volume should update annotations on modification [NodeConformance] [Conformance]","total":-1,"completed":73,"skipped":1617,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSS
    ------------------------------
    [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:185
    STEP: Creating a kubernetes client
... skipping 25 lines ...
    STEP: Destroying namespace "webhook-5672-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 validating webhook should work [Conformance]","total":-1,"completed":74,"skipped":1621,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    S
    ------------------------------
    [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
    Sep  3 09:39:16.714: 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 command [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 command
    Sep  3 09:39:16.764: INFO: Waiting up to 5m0s for pod "var-expansion-b88ebcee-bc69-4d04-9f64-62e94f18153c" in namespace "var-expansion-4933" to be "Succeeded or Failed"

    Sep  3 09:39:16.767: INFO: Pod "var-expansion-b88ebcee-bc69-4d04-9f64-62e94f18153c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.927473ms
    Sep  3 09:39:18.770: INFO: Pod "var-expansion-b88ebcee-bc69-4d04-9f64-62e94f18153c": Phase="Pending", Reason="", readiness=false. Elapsed: 2.00615863s
    Sep  3 09:39:20.775: INFO: Pod "var-expansion-b88ebcee-bc69-4d04-9f64-62e94f18153c": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.011039896s
    STEP: Saw pod success
    Sep  3 09:39:20.775: INFO: Pod "var-expansion-b88ebcee-bc69-4d04-9f64-62e94f18153c" satisfied condition "Succeeded or Failed"

    Sep  3 09:39:20.777: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod var-expansion-b88ebcee-bc69-4d04-9f64-62e94f18153c container dapi-container: <nil>
    STEP: delete the pod
    Sep  3 09:39:20.789: INFO: Waiting for pod var-expansion-b88ebcee-bc69-4d04-9f64-62e94f18153c to disappear
    Sep  3 09:39:20.791: INFO: Pod var-expansion-b88ebcee-bc69-4d04-9f64-62e94f18153c 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
    Sep  3 09:39:20.791: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "var-expansion-4933" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Variable Expansion should allow substituting values in a container's command [NodeConformance] [Conformance]","total":-1,"completed":75,"skipped":1622,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:39:26.944: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "disruption-9931" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] DisruptionController Listing PodDisruptionBudgets for all namespaces should list and delete a collection of PodDisruptionBudgets [Conformance]","total":-1,"completed":76,"skipped":1654,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:39:43.105: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-3925" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should verify ResourceQuota with terminating scopes. [Conformance]","total":-1,"completed":77,"skipped":1688,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 10 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:41:01.187: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "cronjob-1391" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] CronJob should schedule multiple jobs concurrently [Conformance]","total":-1,"completed":78,"skipped":1710,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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 33 lines ...
    
    Sep  3 09:41:07.380: INFO: New ReplicaSet "webserver-deployment-795d758f88" of Deployment "webserver-deployment":
    &ReplicaSet{ObjectMeta:{webserver-deployment-795d758f88  deployment-703  c329a6fd-025c-4e28-9c99-b4426c18f2a4 12849 3 2022-09-03 09:41:05 +0000 UTC <nil> <nil> map[name:httpd pod-template-hash:795d758f88] map[deployment.kubernetes.io/desired-replicas:30 deployment.kubernetes.io/max-replicas:33 deployment.kubernetes.io/revision:2] [{apps/v1 Deployment webserver-deployment d03a5ddc-76a0-42cd-aa50-33c20904fb10 0xc004920f67 0xc004920f68}] []  [{kube-controller-manager Update apps/v1 2022-09-03 09:41:05 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:deployment.kubernetes.io/desired-replicas":{},"f:deployment.kubernetes.io/max-replicas":{},"f:deployment.kubernetes.io/revision":{}},"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"d03a5ddc-76a0-42cd-aa50-33c20904fb10\"}":{}}},"f:spec":{"f:replicas":{},"f:selector":{},"f:template":{"f:metadata":{"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"httpd\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}}}} } {kube-controller-manager Update apps/v1 2022-09-03 09:41:05 +0000 UTC FieldsV1 {"f:status":{"f:fullyLabeledReplicas":{},"f:observedGeneration":{},"f:replicas":{}}} status}]},Spec:ReplicaSetSpec{Replicas:*13,Selector:&v1.LabelSelector{MatchLabels:map[string]string{name: httpd,pod-template-hash: 795d758f88,},MatchExpressions:[]LabelSelectorRequirement{},},Template:{{      0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[name:httpd pod-template-hash:795d758f88] map[] [] []  []} {[] [] [{httpd webserver:404 [] []  [] [] [] {map[] map[]} [] [] nil nil nil nil /dev/termination-log File IfNotPresent SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,} false false false}] [] Always 0xc004921008 <nil> ClusterFirst map[]   <nil>  false false false <nil> &PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,} []   nil default-scheduler [] []  <nil> nil [] <nil> <nil> <nil> map[] [] <nil>}},MinReadySeconds:0,},Status:ReplicaSetStatus{Replicas:5,FullyLabeledReplicas:5,ObservedGeneration:2,ReadyReplicas:0,AvailableReplicas:0,Conditions:[]ReplicaSetCondition{},},}
    Sep  3 09:41:07.380: INFO: All old ReplicaSets of Deployment "webserver-deployment":
    Sep  3 09:41:07.381: INFO: &ReplicaSet{ObjectMeta:{webserver-deployment-847dcfb7fb  deployment-703  7896d98a-3123-4b2c-83f0-b3988bdd1f2c 12846 3 2022-09-03 09:41:01 +0000 UTC <nil> <nil> map[name:httpd pod-template-hash:847dcfb7fb] map[deployment.kubernetes.io/desired-replicas:30 deployment.kubernetes.io/max-replicas:33 deployment.kubernetes.io/revision:1] [{apps/v1 Deployment webserver-deployment d03a5ddc-76a0-42cd-aa50-33c20904fb10 0xc004921067 0xc004921068}] []  [{kube-controller-manager Update apps/v1 2022-09-03 09:41:01 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:deployment.kubernetes.io/desired-replicas":{},"f:deployment.kubernetes.io/max-replicas":{},"f:deployment.kubernetes.io/revision":{}},"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"d03a5ddc-76a0-42cd-aa50-33c20904fb10\"}":{}}},"f:spec":{"f:replicas":{},"f:selector":{},"f:template":{"f:metadata":{"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"httpd\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}}}} } {kube-controller-manager Update apps/v1 2022-09-03 09:41:02 +0000 UTC FieldsV1 {"f:status":{"f:availableReplicas":{},"f:fullyLabeledReplicas":{},"f:observedGeneration":{},"f:readyReplicas":{},"f:replicas":{}}} status}]},Spec:ReplicaSetSpec{Replicas:*20,Selector:&v1.LabelSelector{MatchLabels:map[string]string{name: httpd,pod-template-hash: 847dcfb7fb,},MatchExpressions:[]LabelSelectorRequirement{},},Template:{{      0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[name:httpd pod-template-hash:847dcfb7fb] map[] [] []  []} {[] [] [{httpd k8s.gcr.io/e2e-test-images/httpd:2.4.38-1 [] []  [] [] [] {map[] map[]} [] [] nil nil nil nil /dev/termination-log File IfNotPresent SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,} false false false}] [] Always 0xc0049210f8 <nil> ClusterFirst map[]   <nil>  false false false <nil> &PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,} []   nil default-scheduler [] []  <nil> nil [] <nil> <nil> <nil> map[] [] <nil>}},MinReadySeconds:0,},Status:ReplicaSetStatus{Replicas:8,FullyLabeledReplicas:8,ObservedGeneration:2,ReadyReplicas:8,AvailableReplicas:8,Conditions:[]ReplicaSetCondition{},},}
    Sep  3 09:41:07.389: INFO: Pod "webserver-deployment-795d758f88-2pr58" is not available:
    &Pod{ObjectMeta:{webserver-deployment-795d758f88-2pr58 webserver-deployment-795d758f88- deployment-703  4d5992e6-eb19-4136-b3aa-5272ae1bb049 12824 0 2022-09-03 09:41:05 +0000 UTC <nil> <nil> map[name:httpd pod-template-hash:795d758f88] map[] [{apps/v1 ReplicaSet webserver-deployment-795d758f88 c329a6fd-025c-4e28-9c99-b4426c18f2a4 0xc0049215b7 0xc0049215b8}] []  [{kube-controller-manager Update v1 2022-09-03 09:41:05 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{},"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"c329a6fd-025c-4e28-9c99-b4426c18f2a4\"}":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"httpd\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}} } {kubelet Update v1 2022-09-03 09:41:06 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"ContainersReady\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Initialized\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:containerStatuses":{},"f:hostIP":{},"f:podIP":{},"f:podIPs":{".":{},"k:{\"ip\":\"192.168.0.105\"}":{".":{},"f:ip":{}}},"f:startTime":{}}} status}]},Spec:PodSpec{Volumes:[]Volume{Volume{Name:kube-api-access-dlrdz,VolumeSource:VolumeSource{HostPath:nil,EmptyDir:nil,GCEPersistentDisk:nil,AWSElasticBlockStore:nil,GitRepo:nil,Secret:nil,NFS:nil,ISCSI:nil,Glusterfs:nil,PersistentVolumeClaim:nil,RBD:nil,FlexVolume:nil,Cinder:nil,CephFS:nil,Flocker:nil,DownwardAPI:nil,FC:nil,AzureFile:nil,ConfigMap:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Projected:&ProjectedVolumeSource{Sources:[]VolumeProjection{VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:nil,ServiceAccountToken:&ServiceAccountTokenProjection{Audience:,ExpirationSeconds:*3607,Path:token,},},VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:&ConfigMapProjection{LocalObjectReference:LocalObjectReference{Name:kube-root-ca.crt,},Items:[]KeyToPath{KeyToPath{Key:ca.crt,Path:ca.crt,Mode:nil,},},Optional:nil,},ServiceAccountToken:nil,},VolumeProjection{Secret:nil,DownwardAPI:&DownwardAPIProjection{Items:[]DownwardAPIVolumeFile{DownwardAPIVolumeFile{Path:namespace,FieldRef:&ObjectFieldSelector{APIVersion:v1,FieldPath:metadata.namespace,},ResourceFieldRef:nil,Mode:nil,},},},ConfigMap:nil,ServiceAccountToken:nil,},},DefaultMode:*420,},StorageOS:nil,CSI:nil,Ephemeral:nil,},},},Containers:[]Container{Container{Name:httpd,Image:webserver:404,Command:[],Args:[],WorkingDir:,Ports:[]ContainerPort{},Env:[]EnvVar{},Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},},VolumeMounts:[]VolumeMount{VolumeMount{Name:kube-api-access-dlrdz,ReadOnly:true,MountPath:/var/run/secrets/kubernetes.io/serviceaccount,SubPath:,MountPropagation:nil,SubPathExpr:,},},LivenessProbe:nil,ReadinessProbe:nil,Lifecycle:nil,TerminationMessagePath:/dev/termination-log,ImagePullPolicy:IfNotPresent,SecurityContext:&SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,},Stdin:false,StdinOnce:false,TTY:false,EnvFrom:[]EnvFromSource{},TerminationMessagePolicy:File,VolumeDevices:[]VolumeDevice{},StartupProbe:nil,},},RestartPolicy:Always,TerminationGracePeriodSeconds:*0,ActiveDeadlineSeconds:nil,DNSPolicy:ClusterFirst,NodeSelector:map[string]string{},ServiceAccountName:default,DeprecatedServiceAccount:default,NodeName:k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl,HostNetwork:false,HostPID:false,HostIPC:false,SecurityContext:&PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,},ImagePullSecrets:[]LocalObjectReference{},Hostname:,Subdomain:,Affinity:nil,SchedulerName:default-scheduler,InitContainers:[]Container{},AutomountServiceAccountToken:nil,Tolerations:[]Toleration{Toleration{Key:node.kubernetes.io/not-ready,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},Toleration{Key:node.kubernetes.io/unreachable,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},},HostAliases:[]HostAlias{},PriorityClassName:,Priority:*0,DNSConfig:nil,ShareProcessNamespace:nil,ReadinessGates:[]PodReadinessGate{},RuntimeClassName:nil,EnableServiceLinks:*true,PreemptionPolicy:*PreemptLowerPriority,Overhead:ResourceList{},TopologySpreadConstraints:[]TopologySpreadConstraint{},EphemeralContainers:[]EphemeralContainer{},SetHostnameAsFQDN:nil,},Status:PodStatus{Phase:Pending,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:ContainersNotReady,Message:containers with unready status: [httpd],},PodCondition{Type:ContainersReady,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:ContainersNotReady,Message:containers with unready status: [httpd],},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:172.18.0.4,PodIP:192.168.0.105,StartTime:2022-09-03 09:41:05 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:httpd,State:ContainerState{Waiting:&ContainerStateWaiting{Reason:ErrImagePull,Message:rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/webserver:404": failed to resolve reference "docker.io/library/webserver:404": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed,},Running:nil,Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:false,RestartCount:0,Image:webserver:404,ImageID:,ContainerID:,Started:*false,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:192.168.0.105,},},EphemeralContainerStatuses:[]ContainerStatus{},},}

    Sep  3 09:41:07.390: INFO: Pod "webserver-deployment-795d758f88-5nc5s" is not available:
    &Pod{ObjectMeta:{webserver-deployment-795d758f88-5nc5s webserver-deployment-795d758f88- deployment-703  b4d66704-9a17-4144-9ac8-aefc0209accd 12840 0 2022-09-03 09:41:05 +0000 UTC <nil> <nil> map[name:httpd pod-template-hash:795d758f88] map[] [{apps/v1 ReplicaSet webserver-deployment-795d758f88 c329a6fd-025c-4e28-9c99-b4426c18f2a4 0xc0049217c0 0xc0049217c1}] []  [{kube-controller-manager Update v1 2022-09-03 09:41:05 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{},"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"c329a6fd-025c-4e28-9c99-b4426c18f2a4\"}":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"httpd\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}} } {kubelet Update v1 2022-09-03 09:41:06 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"ContainersReady\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Initialized\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:containerStatuses":{},"f:hostIP":{},"f:podIP":{},"f:podIPs":{".":{},"k:{\"ip\":\"192.168.1.40\"}":{".":{},"f:ip":{}}},"f:startTime":{}}} status}]},Spec:PodSpec{Volumes:[]Volume{Volume{Name:kube-api-access-js5mx,VolumeSource:VolumeSource{HostPath:nil,EmptyDir:nil,GCEPersistentDisk:nil,AWSElasticBlockStore:nil,GitRepo:nil,Secret:nil,NFS:nil,ISCSI:nil,Glusterfs:nil,PersistentVolumeClaim:nil,RBD:nil,FlexVolume:nil,Cinder:nil,CephFS:nil,Flocker:nil,DownwardAPI:nil,FC:nil,AzureFile:nil,ConfigMap:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Projected:&ProjectedVolumeSource{Sources:[]VolumeProjection{VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:nil,ServiceAccountToken:&ServiceAccountTokenProjection{Audience:,ExpirationSeconds:*3607,Path:token,},},VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:&ConfigMapProjection{LocalObjectReference:LocalObjectReference{Name:kube-root-ca.crt,},Items:[]KeyToPath{KeyToPath{Key:ca.crt,Path:ca.crt,Mode:nil,},},Optional:nil,},ServiceAccountToken:nil,},VolumeProjection{Secret:nil,DownwardAPI:&DownwardAPIProjection{Items:[]DownwardAPIVolumeFile{DownwardAPIVolumeFile{Path:namespace,FieldRef:&ObjectFieldSelector{APIVersion:v1,FieldPath:metadata.namespace,},ResourceFieldRef:nil,Mode:nil,},},},ConfigMap:nil,ServiceAccountToken:nil,},},DefaultMode:*420,},StorageOS:nil,CSI:nil,Ephemeral:nil,},},},Containers:[]Container{Container{Name:httpd,Image:webserver:404,Command:[],Args:[],WorkingDir:,Ports:[]ContainerPort{},Env:[]EnvVar{},Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},},VolumeMounts:[]VolumeMount{VolumeMount{Name:kube-api-access-js5mx,ReadOnly:true,MountPath:/var/run/secrets/kubernetes.io/serviceaccount,SubPath:,MountPropagation:nil,SubPathExpr:,},},LivenessProbe:nil,ReadinessProbe:nil,Lifecycle:nil,TerminationMessagePath:/dev/termination-log,ImagePullPolicy:IfNotPresent,SecurityContext:&SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,},Stdin:false,StdinOnce:false,TTY:false,EnvFrom:[]EnvFromSource{},TerminationMessagePolicy:File,VolumeDevices:[]VolumeDevice{},StartupProbe:nil,},},RestartPolicy:Always,TerminationGracePeriodSeconds:*0,ActiveDeadlineSeconds:nil,DNSPolicy:ClusterFirst,NodeSelector:map[string]string{},ServiceAccountName:default,DeprecatedServiceAccount:default,NodeName:k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-jh8sn,HostNetwork:false,HostPID:false,HostIPC:false,SecurityContext:&PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,},ImagePullSecrets:[]LocalObjectReference{},Hostname:,Subdomain:,Affinity:nil,SchedulerName:default-scheduler,InitContainers:[]Container{},AutomountServiceAccountToken:nil,Tolerations:[]Toleration{Toleration{Key:node.kubernetes.io/not-ready,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},Toleration{Key:node.kubernetes.io/unreachable,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},},HostAliases:[]HostAlias{},PriorityClassName:,Priority:*0,DNSConfig:nil,ShareProcessNamespace:nil,ReadinessGates:[]PodReadinessGate{},RuntimeClassName:nil,EnableServiceLinks:*true,PreemptionPolicy:*PreemptLowerPriority,Overhead:ResourceList{},TopologySpreadConstraints:[]TopologySpreadConstraint{},EphemeralContainers:[]EphemeralContainer{},SetHostnameAsFQDN:nil,},Status:PodStatus{Phase:Pending,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:ContainersNotReady,Message:containers with unready status: [httpd],},PodCondition{Type:ContainersReady,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:ContainersNotReady,Message:containers with unready status: [httpd],},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:172.18.0.7,PodIP:192.168.1.40,StartTime:2022-09-03 09:41:05 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:httpd,State:ContainerState{Waiting:&ContainerStateWaiting{Reason:ErrImagePull,Message:rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/webserver:404": failed to resolve reference "docker.io/library/webserver:404": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed,},Running:nil,Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:false,RestartCount:0,Image:webserver:404,ImageID:,ContainerID:,Started:*false,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:192.168.1.40,},},EphemeralContainerStatuses:[]ContainerStatus{},},}

    Sep  3 09:41:07.390: INFO: Pod "webserver-deployment-795d758f88-97pbj" is not available:
    &Pod{ObjectMeta:{webserver-deployment-795d758f88-97pbj webserver-deployment-795d758f88- deployment-703  72ec2d37-f52b-4fb6-8c55-3ccdffb4ab4f 12837 0 2022-09-03 09:41:05 +0000 UTC <nil> <nil> map[name:httpd pod-template-hash:795d758f88] map[] [{apps/v1 ReplicaSet webserver-deployment-795d758f88 c329a6fd-025c-4e28-9c99-b4426c18f2a4 0xc0049219c0 0xc0049219c1}] []  [{kube-controller-manager Update v1 2022-09-03 09:41:05 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{},"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"c329a6fd-025c-4e28-9c99-b4426c18f2a4\"}":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"httpd\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}} } {kubelet Update v1 2022-09-03 09:41:06 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"ContainersReady\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Initialized\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:containerStatuses":{},"f:hostIP":{},"f:podIP":{},"f:podIPs":{".":{},"k:{\"ip\":\"192.168.1.39\"}":{".":{},"f:ip":{}}},"f:startTime":{}}} status}]},Spec:PodSpec{Volumes:[]Volume{Volume{Name:kube-api-access-p8j86,VolumeSource:VolumeSource{HostPath:nil,EmptyDir:nil,GCEPersistentDisk:nil,AWSElasticBlockStore:nil,GitRepo:nil,Secret:nil,NFS:nil,ISCSI:nil,Glusterfs:nil,PersistentVolumeClaim:nil,RBD:nil,FlexVolume:nil,Cinder:nil,CephFS:nil,Flocker:nil,DownwardAPI:nil,FC:nil,AzureFile:nil,ConfigMap:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Projected:&ProjectedVolumeSource{Sources:[]VolumeProjection{VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:nil,ServiceAccountToken:&ServiceAccountTokenProjection{Audience:,ExpirationSeconds:*3607,Path:token,},},VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:&ConfigMapProjection{LocalObjectReference:LocalObjectReference{Name:kube-root-ca.crt,},Items:[]KeyToPath{KeyToPath{Key:ca.crt,Path:ca.crt,Mode:nil,},},Optional:nil,},ServiceAccountToken:nil,},VolumeProjection{Secret:nil,DownwardAPI:&DownwardAPIProjection{Items:[]DownwardAPIVolumeFile{DownwardAPIVolumeFile{Path:namespace,FieldRef:&ObjectFieldSelector{APIVersion:v1,FieldPath:metadata.namespace,},ResourceFieldRef:nil,Mode:nil,},},},ConfigMap:nil,ServiceAccountToken:nil,},},DefaultMode:*420,},StorageOS:nil,CSI:nil,Ephemeral:nil,},},},Containers:[]Container{Container{Name:httpd,Image:webserver:404,Command:[],Args:[],WorkingDir:,Ports:[]ContainerPort{},Env:[]EnvVar{},Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},},VolumeMounts:[]VolumeMount{VolumeMount{Name:kube-api-access-p8j86,ReadOnly:true,MountPath:/var/run/secrets/kubernetes.io/serviceaccount,SubPath:,MountPropagation:nil,SubPathExpr:,},},LivenessProbe:nil,ReadinessProbe:nil,Lifecycle:nil,TerminationMessagePath:/dev/termination-log,ImagePullPolicy:IfNotPresent,SecurityContext:&SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,},Stdin:false,StdinOnce:false,TTY:false,EnvFrom:[]EnvFromSource{},TerminationMessagePolicy:File,VolumeDevices:[]VolumeDevice{},StartupProbe:nil,},},RestartPolicy:Always,TerminationGracePeriodSeconds:*0,ActiveDeadlineSeconds:nil,DNSPolicy:ClusterFirst,NodeSelector:map[string]string{},ServiceAccountName:default,DeprecatedServiceAccount:default,NodeName:k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-jh8sn,HostNetwork:false,HostPID:false,HostIPC:false,SecurityContext:&PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,},ImagePullSecrets:[]LocalObjectReference{},Hostname:,Subdomain:,Affinity:nil,SchedulerName:default-scheduler,InitContainers:[]Container{},AutomountServiceAccountToken:nil,Tolerations:[]Toleration{Toleration{Key:node.kubernetes.io/not-ready,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},Toleration{Key:node.kubernetes.io/unreachable,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},},HostAliases:[]HostAlias{},PriorityClassName:,Priority:*0,DNSConfig:nil,ShareProcessNamespace:nil,ReadinessGates:[]PodReadinessGate{},RuntimeClassName:nil,EnableServiceLinks:*true,PreemptionPolicy:*PreemptLowerPriority,Overhead:ResourceList{},TopologySpreadConstraints:[]TopologySpreadConstraint{},EphemeralContainers:[]EphemeralContainer{},SetHostnameAsFQDN:nil,},Status:PodStatus{Phase:Pending,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:ContainersNotReady,Message:containers with unready status: [httpd],},PodCondition{Type:ContainersReady,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:ContainersNotReady,Message:containers with unready status: [httpd],},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:172.18.0.7,PodIP:192.168.1.39,StartTime:2022-09-03 09:41:05 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:httpd,State:ContainerState{Waiting:&ContainerStateWaiting{Reason:ErrImagePull,Message:rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/webserver:404": failed to resolve reference "docker.io/library/webserver:404": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed,},Running:nil,Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:false,RestartCount:0,Image:webserver:404,ImageID:,ContainerID:,Started:*false,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:192.168.1.39,},},EphemeralContainerStatuses:[]ContainerStatus{},},}

    Sep  3 09:41:07.390: INFO: Pod "webserver-deployment-795d758f88-bw9cd" is not available:
    &Pod{ObjectMeta:{webserver-deployment-795d758f88-bw9cd webserver-deployment-795d758f88- deployment-703  6c6e1bdc-fd86-471f-a512-040c7ec5021c 12860 0 2022-09-03 09:41:07 +0000 UTC <nil> <nil> map[name:httpd pod-template-hash:795d758f88] map[] [{apps/v1 ReplicaSet webserver-deployment-795d758f88 c329a6fd-025c-4e28-9c99-b4426c18f2a4 0xc004921be0 0xc004921be1}] []  [{kube-controller-manager Update v1 2022-09-03 09:41:07 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{},"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"c329a6fd-025c-4e28-9c99-b4426c18f2a4\"}":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"httpd\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}} }]},Spec:PodSpec{Volumes:[]Volume{Volume{Name:kube-api-access-nxnll,VolumeSource:VolumeSource{HostPath:nil,EmptyDir:nil,GCEPersistentDisk:nil,AWSElasticBlockStore:nil,GitRepo:nil,Secret:nil,NFS:nil,ISCSI:nil,Glusterfs:nil,PersistentVolumeClaim:nil,RBD:nil,FlexVolume:nil,Cinder:nil,CephFS:nil,Flocker:nil,DownwardAPI:nil,FC:nil,AzureFile:nil,ConfigMap:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Projected:&ProjectedVolumeSource{Sources:[]VolumeProjection{VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:nil,ServiceAccountToken:&ServiceAccountTokenProjection{Audience:,ExpirationSeconds:*3607,Path:token,},},VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:&ConfigMapProjection{LocalObjectReference:LocalObjectReference{Name:kube-root-ca.crt,},Items:[]KeyToPath{KeyToPath{Key:ca.crt,Path:ca.crt,Mode:nil,},},Optional:nil,},ServiceAccountToken:nil,},VolumeProjection{Secret:nil,DownwardAPI:&DownwardAPIProjection{Items:[]DownwardAPIVolumeFile{DownwardAPIVolumeFile{Path:namespace,FieldRef:&ObjectFieldSelector{APIVersion:v1,FieldPath:metadata.namespace,},ResourceFieldRef:nil,Mode:nil,},},},ConfigMap:nil,ServiceAccountToken:nil,},},DefaultMode:*420,},StorageOS:nil,CSI:nil,Ephemeral:nil,},},},Containers:[]Container{Container{Name:httpd,Image:webserver:404,Command:[],Args:[],WorkingDir:,Ports:[]ContainerPort{},Env:[]EnvVar{},Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},},VolumeMounts:[]VolumeMount{VolumeMount{Name:kube-api-access-nxnll,ReadOnly:true,MountPath:/var/run/secrets/kubernetes.io/serviceaccount,SubPath:,MountPropagation:nil,SubPathExpr:,},},LivenessProbe:nil,ReadinessProbe:nil,Lifecycle:nil,TerminationMessagePath:/dev/termination-log,ImagePullPolicy:IfNotPresent,SecurityContext:&SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,},Stdin:false,StdinOnce:false,TTY:false,EnvFrom:[]EnvFromSource{},TerminationMessagePolicy:File,VolumeDevices:[]VolumeDevice{},StartupProbe:nil,},},RestartPolicy:Always,TerminationGracePeriodSeconds:*0,ActiveDeadlineSeconds:nil,DNSPolicy:ClusterFirst,NodeSelector:map[string]string{},ServiceAccountName:default,DeprecatedServiceAccount:default,NodeName:k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl,HostNetwork:false,HostPID:false,HostIPC:false,SecurityContext:&PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,},ImagePullSecrets:[]LocalObjectReference{},Hostname:,Subdomain:,Affinity:nil,SchedulerName:default-scheduler,InitContainers:[]Container{},AutomountServiceAccountToken:nil,Tolerations:[]Toleration{Toleration{Key:node.kubernetes.io/not-ready,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},Toleration{Key:node.kubernetes.io/unreachable,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},},HostAliases:[]HostAlias{},PriorityClassName:,Priority:*0,DNSConfig:nil,ShareProcessNamespace:nil,ReadinessGates:[]PodReadinessGate{},RuntimeClassName:nil,EnableServiceLinks:*true,PreemptionPolicy:*PreemptLowerPriority,Overhead:ResourceList{},TopologySpreadConstraints:[]TopologySpreadConstraint{},EphemeralContainers:[]EphemeralContainer{},SetHostnameAsFQDN:nil,},Status:PodStatus{Phase:Pending,Conditions:[]PodCondition{PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:07 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:,PodIP:,StartTime:<nil>,ContainerStatuses:[]ContainerStatus{},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{},EphemeralContainerStatuses:[]ContainerStatus{},},}
    Sep  3 09:41:07.390: INFO: Pod "webserver-deployment-795d758f88-c2xvj" is not available:
    &Pod{ObjectMeta:{webserver-deployment-795d758f88-c2xvj webserver-deployment-795d758f88- deployment-703  aa295519-f7ae-4824-8736-6ca4688e3706 12831 0 2022-09-03 09:41:05 +0000 UTC <nil> <nil> map[name:httpd pod-template-hash:795d758f88] map[] [{apps/v1 ReplicaSet webserver-deployment-795d758f88 c329a6fd-025c-4e28-9c99-b4426c18f2a4 0xc004921d50 0xc004921d51}] []  [{kube-controller-manager Update v1 2022-09-03 09:41:05 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{},"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"c329a6fd-025c-4e28-9c99-b4426c18f2a4\"}":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"httpd\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}} } {kubelet Update v1 2022-09-03 09:41:06 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"ContainersReady\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Initialized\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:containerStatuses":{},"f:hostIP":{},"f:podIP":{},"f:podIPs":{".":{},"k:{\"ip\":\"192.168.2.35\"}":{".":{},"f:ip":{}}},"f:startTime":{}}} status}]},Spec:PodSpec{Volumes:[]Volume{Volume{Name:kube-api-access-qw4zl,VolumeSource:VolumeSource{HostPath:nil,EmptyDir:nil,GCEPersistentDisk:nil,AWSElasticBlockStore:nil,GitRepo:nil,Secret:nil,NFS:nil,ISCSI:nil,Glusterfs:nil,PersistentVolumeClaim:nil,RBD:nil,FlexVolume:nil,Cinder:nil,CephFS:nil,Flocker:nil,DownwardAPI:nil,FC:nil,AzureFile:nil,ConfigMap:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Projected:&ProjectedVolumeSource{Sources:[]VolumeProjection{VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:nil,ServiceAccountToken:&ServiceAccountTokenProjection{Audience:,ExpirationSeconds:*3607,Path:token,},},VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:&ConfigMapProjection{LocalObjectReference:LocalObjectReference{Name:kube-root-ca.crt,},Items:[]KeyToPath{KeyToPath{Key:ca.crt,Path:ca.crt,Mode:nil,},},Optional:nil,},ServiceAccountToken:nil,},VolumeProjection{Secret:nil,DownwardAPI:&DownwardAPIProjection{Items:[]DownwardAPIVolumeFile{DownwardAPIVolumeFile{Path:namespace,FieldRef:&ObjectFieldSelector{APIVersion:v1,FieldPath:metadata.namespace,},ResourceFieldRef:nil,Mode:nil,},},},ConfigMap:nil,ServiceAccountToken:nil,},},DefaultMode:*420,},StorageOS:nil,CSI:nil,Ephemeral:nil,},},},Containers:[]Container{Container{Name:httpd,Image:webserver:404,Command:[],Args:[],WorkingDir:,Ports:[]ContainerPort{},Env:[]EnvVar{},Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},},VolumeMounts:[]VolumeMount{VolumeMount{Name:kube-api-access-qw4zl,ReadOnly:true,MountPath:/var/run/secrets/kubernetes.io/serviceaccount,SubPath:,MountPropagation:nil,SubPathExpr:,},},LivenessProbe:nil,ReadinessProbe:nil,Lifecycle:nil,TerminationMessagePath:/dev/termination-log,ImagePullPolicy:IfNotPresent,SecurityContext:&SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,},Stdin:false,StdinOnce:false,TTY:false,EnvFrom:[]EnvFromSource{},TerminationMessagePolicy:File,VolumeDevices:[]VolumeDevice{},StartupProbe:nil,},},RestartPolicy:Always,TerminationGracePeriodSeconds:*0,ActiveDeadlineSeconds:nil,DNSPolicy:ClusterFirst,NodeSelector:map[string]string{},ServiceAccountName:default,DeprecatedServiceAccount:default,NodeName:k8s-upgrade-and-conformance-z5d79l-worker-wggvfg,HostNetwork:false,HostPID:false,HostIPC:false,SecurityContext:&PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,},ImagePullSecrets:[]LocalObjectReference{},Hostname:,Subdomain:,Affinity:nil,SchedulerName:default-scheduler,InitContainers:[]Container{},AutomountServiceAccountToken:nil,Tolerations:[]Toleration{Toleration{Key:node.kubernetes.io/not-ready,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},Toleration{Key:node.kubernetes.io/unreachable,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},},HostAliases:[]HostAlias{},PriorityClassName:,Priority:*0,DNSConfig:nil,ShareProcessNamespace:nil,ReadinessGates:[]PodReadinessGate{},RuntimeClassName:nil,EnableServiceLinks:*true,PreemptionPolicy:*PreemptLowerPriority,Overhead:ResourceList{},TopologySpreadConstraints:[]TopologySpreadConstraint{},EphemeralContainers:[]EphemeralContainer{},SetHostnameAsFQDN:nil,},Status:PodStatus{Phase:Pending,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:ContainersNotReady,Message:containers with unready status: [httpd],},PodCondition{Type:ContainersReady,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:ContainersNotReady,Message:containers with unready status: [httpd],},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:172.18.0.6,PodIP:192.168.2.35,StartTime:2022-09-03 09:41:05 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:httpd,State:ContainerState{Waiting:&ContainerStateWaiting{Reason:ErrImagePull,Message:rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/webserver:404": failed to resolve reference "docker.io/library/webserver:404": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed,},Running:nil,Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:false,RestartCount:0,Image:webserver:404,ImageID:,ContainerID:,Started:*false,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:192.168.2.35,},},EphemeralContainerStatuses:[]ContainerStatus{},},}

    Sep  3 09:41:07.391: INFO: Pod "webserver-deployment-795d758f88-cswz6" is not available:
    &Pod{ObjectMeta:{webserver-deployment-795d758f88-cswz6 webserver-deployment-795d758f88- deployment-703  815a2dc1-8895-42f3-b32f-685c41c92a43 12821 0 2022-09-03 09:41:05 +0000 UTC <nil> <nil> map[name:httpd pod-template-hash:795d758f88] map[] [{apps/v1 ReplicaSet webserver-deployment-795d758f88 c329a6fd-025c-4e28-9c99-b4426c18f2a4 0xc004921f90 0xc004921f91}] []  [{kube-controller-manager Update v1 2022-09-03 09:41:05 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{},"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"c329a6fd-025c-4e28-9c99-b4426c18f2a4\"}":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"httpd\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}} } {kubelet Update v1 2022-09-03 09:41:06 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"ContainersReady\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Initialized\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}},"f:containerStatuses":{},"f:hostIP":{},"f:podIP":{},"f:podIPs":{".":{},"k:{\"ip\":\"192.168.6.60\"}":{".":{},"f:ip":{}}},"f:startTime":{}}} status}]},Spec:PodSpec{Volumes:[]Volume{Volume{Name:kube-api-access-5jrhw,VolumeSource:VolumeSource{HostPath:nil,EmptyDir:nil,GCEPersistentDisk:nil,AWSElasticBlockStore:nil,GitRepo:nil,Secret:nil,NFS:nil,ISCSI:nil,Glusterfs:nil,PersistentVolumeClaim:nil,RBD:nil,FlexVolume:nil,Cinder:nil,CephFS:nil,Flocker:nil,DownwardAPI:nil,FC:nil,AzureFile:nil,ConfigMap:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Projected:&ProjectedVolumeSource{Sources:[]VolumeProjection{VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:nil,ServiceAccountToken:&ServiceAccountTokenProjection{Audience:,ExpirationSeconds:*3607,Path:token,},},VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:&ConfigMapProjection{LocalObjectReference:LocalObjectReference{Name:kube-root-ca.crt,},Items:[]KeyToPath{KeyToPath{Key:ca.crt,Path:ca.crt,Mode:nil,},},Optional:nil,},ServiceAccountToken:nil,},VolumeProjection{Secret:nil,DownwardAPI:&DownwardAPIProjection{Items:[]DownwardAPIVolumeFile{DownwardAPIVolumeFile{Path:namespace,FieldRef:&ObjectFieldSelector{APIVersion:v1,FieldPath:metadata.namespace,},ResourceFieldRef:nil,Mode:nil,},},},ConfigMap:nil,ServiceAccountToken:nil,},},DefaultMode:*420,},StorageOS:nil,CSI:nil,Ephemeral:nil,},},},Containers:[]Container{Container{Name:httpd,Image:webserver:404,Command:[],Args:[],WorkingDir:,Ports:[]ContainerPort{},Env:[]EnvVar{},Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},},VolumeMounts:[]VolumeMount{VolumeMount{Name:kube-api-access-5jrhw,ReadOnly:true,MountPath:/var/run/secrets/kubernetes.io/serviceaccount,SubPath:,MountPropagation:nil,SubPathExpr:,},},LivenessProbe:nil,ReadinessProbe:nil,Lifecycle:nil,TerminationMessagePath:/dev/termination-log,ImagePullPolicy:IfNotPresent,SecurityContext:&SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,},Stdin:false,StdinOnce:false,TTY:false,EnvFrom:[]EnvFromSource{},TerminationMessagePolicy:File,VolumeDevices:[]VolumeDevice{},StartupProbe:nil,},},RestartPolicy:Always,TerminationGracePeriodSeconds:*0,ActiveDeadlineSeconds:nil,DNSPolicy:ClusterFirst,NodeSelector:map[string]string{},ServiceAccountName:default,DeprecatedServiceAccount:default,NodeName:k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1,HostNetwork:false,HostPID:false,HostIPC:false,SecurityContext:&PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,},ImagePullSecrets:[]LocalObjectReference{},Hostname:,Subdomain:,Affinity:nil,SchedulerName:default-scheduler,InitContainers:[]Container{},AutomountServiceAccountToken:nil,Tolerations:[]Toleration{Toleration{Key:node.kubernetes.io/not-ready,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},Toleration{Key:node.kubernetes.io/unreachable,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},},HostAliases:[]HostAlias{},PriorityClassName:,Priority:*0,DNSConfig:nil,ShareProcessNamespace:nil,ReadinessGates:[]PodReadinessGate{},RuntimeClassName:nil,EnableServiceLinks:*true,PreemptionPolicy:*PreemptLowerPriority,Overhead:ResourceList{},TopologySpreadConstraints:[]TopologySpreadConstraint{},EphemeralContainers:[]EphemeralContainer{},SetHostnameAsFQDN:nil,},Status:PodStatus{Phase:Pending,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:ContainersNotReady,Message:containers with unready status: [httpd],},PodCondition{Type:ContainersReady,Status:False,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:ContainersNotReady,Message:containers with unready status: [httpd],},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:05 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:172.18.0.5,PodIP:192.168.6.60,StartTime:2022-09-03 09:41:05 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:httpd,State:ContainerState{Waiting:&ContainerStateWaiting{Reason:ErrImagePull,Message:rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/webserver:404": failed to resolve reference "docker.io/library/webserver:404": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed,},Running:nil,Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:false,RestartCount:0,Image:webserver:404,ImageID:,ContainerID:,Started:*false,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:192.168.6.60,},},EphemeralContainerStatuses:[]ContainerStatus{},},}

    Sep  3 09:41:07.391: INFO: Pod "webserver-deployment-795d758f88-skfzm" is not available:
    &Pod{ObjectMeta:{webserver-deployment-795d758f88-skfzm webserver-deployment-795d758f88- deployment-703  22034b7e-7521-4c5d-92c8-33eee0805da5 12864 0 2022-09-03 09:41:07 +0000 UTC <nil> <nil> map[name:httpd pod-template-hash:795d758f88] map[] [{apps/v1 ReplicaSet webserver-deployment-795d758f88 c329a6fd-025c-4e28-9c99-b4426c18f2a4 0xc002fee2e0 0xc002fee2e1}] []  [{kube-controller-manager Update v1 2022-09-03 09:41:07 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{},"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"c329a6fd-025c-4e28-9c99-b4426c18f2a4\"}":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"httpd\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}} }]},Spec:PodSpec{Volumes:[]Volume{Volume{Name:kube-api-access-tmjpf,VolumeSource:VolumeSource{HostPath:nil,EmptyDir:nil,GCEPersistentDisk:nil,AWSElasticBlockStore:nil,GitRepo:nil,Secret:nil,NFS:nil,ISCSI:nil,Glusterfs:nil,PersistentVolumeClaim:nil,RBD:nil,FlexVolume:nil,Cinder:nil,CephFS:nil,Flocker:nil,DownwardAPI:nil,FC:nil,AzureFile:nil,ConfigMap:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Projected:&ProjectedVolumeSource{Sources:[]VolumeProjection{VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:nil,ServiceAccountToken:&ServiceAccountTokenProjection{Audience:,ExpirationSeconds:*3607,Path:token,},},VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:&ConfigMapProjection{LocalObjectReference:LocalObjectReference{Name:kube-root-ca.crt,},Items:[]KeyToPath{KeyToPath{Key:ca.crt,Path:ca.crt,Mode:nil,},},Optional:nil,},ServiceAccountToken:nil,},VolumeProjection{Secret:nil,DownwardAPI:&DownwardAPIProjection{Items:[]DownwardAPIVolumeFile{DownwardAPIVolumeFile{Path:namespace,FieldRef:&ObjectFieldSelector{APIVersion:v1,FieldPath:metadata.namespace,},ResourceFieldRef:nil,Mode:nil,},},},ConfigMap:nil,ServiceAccountToken:nil,},},DefaultMode:*420,},StorageOS:nil,CSI:nil,Ephemeral:nil,},},},Containers:[]Container{Container{Name:httpd,Image:webserver:404,Command:[],Args:[],WorkingDir:,Ports:[]ContainerPort{},Env:[]EnvVar{},Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},},VolumeMounts:[]VolumeMount{VolumeMount{Name:kube-api-access-tmjpf,ReadOnly:true,MountPath:/var/run/secrets/kubernetes.io/serviceaccount,SubPath:,MountPropagation:nil,SubPathExpr:,},},LivenessProbe:nil,ReadinessProbe:nil,Lifecycle:nil,TerminationMessagePath:/dev/termination-log,ImagePullPolicy:IfNotPresent,SecurityContext:&SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,},Stdin:false,StdinOnce:false,TTY:false,EnvFrom:[]EnvFromSource{},TerminationMessagePolicy:File,VolumeDevices:[]VolumeDevice{},StartupProbe:nil,},},RestartPolicy:Always,TerminationGracePeriodSeconds:*0,ActiveDeadlineSeconds:nil,DNSPolicy:ClusterFirst,NodeSelector:map[string]string{},ServiceAccountName:default,DeprecatedServiceAccount:default,NodeName:,HostNetwork:false,HostPID:false,HostIPC:false,SecurityContext:&PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,},ImagePullSecrets:[]LocalObjectReference{},Hostname:,Subdomain:,Affinity:nil,SchedulerName:default-scheduler,InitContainers:[]Container{},AutomountServiceAccountToken:nil,Tolerations:[]Toleration{Toleration{Key:node.kubernetes.io/not-ready,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},Toleration{Key:node.kubernetes.io/unreachable,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},},HostAliases:[]HostAlias{},PriorityClassName:,Priority:*0,DNSConfig:nil,ShareProcessNamespace:nil,ReadinessGates:[]PodReadinessGate{},RuntimeClassName:nil,EnableServiceLinks:*true,PreemptionPolicy:*PreemptLowerPriority,Overhead:ResourceList{},TopologySpreadConstraints:[]TopologySpreadConstraint{},EphemeralContainers:[]EphemeralContainer{},SetHostnameAsFQDN:nil,},Status:PodStatus{Phase:Pending,Conditions:[]PodCondition{},Message:,Reason:,HostIP:,PodIP:,StartTime:<nil>,ContainerStatuses:[]ContainerStatus{},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{},EphemeralContainerStatuses:[]ContainerStatus{},},}
    Sep  3 09:41:07.391: INFO: Pod "webserver-deployment-795d758f88-vdgqk" is not available:
    &Pod{ObjectMeta:{webserver-deployment-795d758f88-vdgqk webserver-deployment-795d758f88- deployment-703  5e8de9da-41b0-4622-a473-f1ad8d0fc448 12863 0 2022-09-03 09:41:07 +0000 UTC <nil> <nil> map[name:httpd pod-template-hash:795d758f88] map[] [{apps/v1 ReplicaSet webserver-deployment-795d758f88 c329a6fd-025c-4e28-9c99-b4426c18f2a4 0xc002fee547 0xc002fee548}] []  [{kube-controller-manager Update v1 2022-09-03 09:41:07 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{},"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"c329a6fd-025c-4e28-9c99-b4426c18f2a4\"}":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"httpd\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}} }]},Spec:PodSpec{Volumes:[]Volume{Volume{Name:kube-api-access-pqxv6,VolumeSource:VolumeSource{HostPath:nil,EmptyDir:nil,GCEPersistentDisk:nil,AWSElasticBlockStore:nil,GitRepo:nil,Secret:nil,NFS:nil,ISCSI:nil,Glusterfs:nil,PersistentVolumeClaim:nil,RBD:nil,FlexVolume:nil,Cinder:nil,CephFS:nil,Flocker:nil,DownwardAPI:nil,FC:nil,AzureFile:nil,ConfigMap:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Projected:&ProjectedVolumeSource{Sources:[]VolumeProjection{VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:nil,ServiceAccountToken:&ServiceAccountTokenProjection{Audience:,ExpirationSeconds:*3607,Path:token,},},VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:&ConfigMapProjection{LocalObjectReference:LocalObjectReference{Name:kube-root-ca.crt,},Items:[]KeyToPath{KeyToPath{Key:ca.crt,Path:ca.crt,Mode:nil,},},Optional:nil,},ServiceAccountToken:nil,},VolumeProjection{Secret:nil,DownwardAPI:&DownwardAPIProjection{Items:[]DownwardAPIVolumeFile{DownwardAPIVolumeFile{Path:namespace,FieldRef:&ObjectFieldSelector{APIVersion:v1,FieldPath:metadata.namespace,},ResourceFieldRef:nil,Mode:nil,},},},ConfigMap:nil,ServiceAccountToken:nil,},},DefaultMode:*420,},StorageOS:nil,CSI:nil,Ephemeral:nil,},},},Containers:[]Container{Container{Name:httpd,Image:webserver:404,Command:[],Args:[],WorkingDir:,Ports:[]ContainerPort{},Env:[]EnvVar{},Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},},VolumeMounts:[]VolumeMount{VolumeMount{Name:kube-api-access-pqxv6,ReadOnly:true,MountPath:/var/run/secrets/kubernetes.io/serviceaccount,SubPath:,MountPropagation:nil,SubPathExpr:,},},LivenessProbe:nil,ReadinessProbe:nil,Lifecycle:nil,TerminationMessagePath:/dev/termination-log,ImagePullPolicy:IfNotPresent,SecurityContext:&SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,},Stdin:false,StdinOnce:false,TTY:false,EnvFrom:[]EnvFromSource{},TerminationMessagePolicy:File,VolumeDevices:[]VolumeDevice{},StartupProbe:nil,},},RestartPolicy:Always,TerminationGracePeriodSeconds:*0,ActiveDeadlineSeconds:nil,DNSPolicy:ClusterFirst,NodeSelector:map[string]string{},ServiceAccountName:default,DeprecatedServiceAccount:default,NodeName:,HostNetwork:false,HostPID:false,HostIPC:false,SecurityContext:&PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,},ImagePullSecrets:[]LocalObjectReference{},Hostname:,Subdomain:,Affinity:nil,SchedulerName:default-scheduler,InitContainers:[]Container{},AutomountServiceAccountToken:nil,Tolerations:[]Toleration{Toleration{Key:node.kubernetes.io/not-ready,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},Toleration{Key:node.kubernetes.io/unreachable,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},},HostAliases:[]HostAlias{},PriorityClassName:,Priority:*0,DNSConfig:nil,ShareProcessNamespace:nil,ReadinessGates:[]PodReadinessGate{},RuntimeClassName:nil,EnableServiceLinks:*true,PreemptionPolicy:*PreemptLowerPriority,Overhead:ResourceList{},TopologySpreadConstraints:[]TopologySpreadConstraint{},EphemeralContainers:[]EphemeralContainer{},SetHostnameAsFQDN:nil,},Status:PodStatus{Phase:Pending,Conditions:[]PodCondition{},Message:,Reason:,HostIP:,PodIP:,StartTime:<nil>,ContainerStatuses:[]ContainerStatus{},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{},EphemeralContainerStatuses:[]ContainerStatus{},},}
    Sep  3 09:41:07.392: INFO: Pod "webserver-deployment-847dcfb7fb-2bbzg" is available:
    &Pod{ObjectMeta:{webserver-deployment-847dcfb7fb-2bbzg webserver-deployment-847dcfb7fb- deployment-703  5cc6cfaa-f871-4e6c-a518-23e91b52b780 12721 0 2022-09-03 09:41:01 +0000 UTC <nil> <nil> map[name:httpd pod-template-hash:847dcfb7fb] map[] [{apps/v1 ReplicaSet webserver-deployment-847dcfb7fb 7896d98a-3123-4b2c-83f0-b3988bdd1f2c 0xc002fee7c7 0xc002fee7c8}] []  [{kube-controller-manager Update v1 2022-09-03 09:41:01 +0000 UTC FieldsV1 {"f:metadata":{"f:generateName":{},"f:labels":{".":{},"f:name":{},"f:pod-template-hash":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"7896d98a-3123-4b2c-83f0-b3988bdd1f2c\"}":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"httpd\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:securityContext":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}} } {kubelet Update v1 2022-09-03 09:41:03 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"ContainersReady\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Initialized\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:status":{},"f:type":{}},"k:{\"type\":\"Ready\"}":{".":{},"f:lastProbeTime":{},"f:lastTransitionTime":{},"f:status":{},"f:type":{}}},"f:containerStatuses":{},"f:hostIP":{},"f:phase":{},"f:podIP":{},"f:podIPs":{".":{},"k:{\"ip\":\"192.168.6.57\"}":{".":{},"f:ip":{}}},"f:startTime":{}}} status}]},Spec:PodSpec{Volumes:[]Volume{Volume{Name:kube-api-access-q5r5x,VolumeSource:VolumeSource{HostPath:nil,EmptyDir:nil,GCEPersistentDisk:nil,AWSElasticBlockStore:nil,GitRepo:nil,Secret:nil,NFS:nil,ISCSI:nil,Glusterfs:nil,PersistentVolumeClaim:nil,RBD:nil,FlexVolume:nil,Cinder:nil,CephFS:nil,Flocker:nil,DownwardAPI:nil,FC:nil,AzureFile:nil,ConfigMap:nil,VsphereVolume:nil,Quobyte:nil,AzureDisk:nil,PhotonPersistentDisk:nil,PortworxVolume:nil,ScaleIO:nil,Projected:&ProjectedVolumeSource{Sources:[]VolumeProjection{VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:nil,ServiceAccountToken:&ServiceAccountTokenProjection{Audience:,ExpirationSeconds:*3607,Path:token,},},VolumeProjection{Secret:nil,DownwardAPI:nil,ConfigMap:&ConfigMapProjection{LocalObjectReference:LocalObjectReference{Name:kube-root-ca.crt,},Items:[]KeyToPath{KeyToPath{Key:ca.crt,Path:ca.crt,Mode:nil,},},Optional:nil,},ServiceAccountToken:nil,},VolumeProjection{Secret:nil,DownwardAPI:&DownwardAPIProjection{Items:[]DownwardAPIVolumeFile{DownwardAPIVolumeFile{Path:namespace,FieldRef:&ObjectFieldSelector{APIVersion:v1,FieldPath:metadata.namespace,},ResourceFieldRef:nil,Mode:nil,},},},ConfigMap:nil,ServiceAccountToken:nil,},},DefaultMode:*420,},StorageOS:nil,CSI:nil,Ephemeral:nil,},},},Containers:[]Container{Container{Name:httpd,Image:k8s.gcr.io/e2e-test-images/httpd:2.4.38-1,Command:[],Args:[],WorkingDir:,Ports:[]ContainerPort{},Env:[]EnvVar{},Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},},VolumeMounts:[]VolumeMount{VolumeMount{Name:kube-api-access-q5r5x,ReadOnly:true,MountPath:/var/run/secrets/kubernetes.io/serviceaccount,SubPath:,MountPropagation:nil,SubPathExpr:,},},LivenessProbe:nil,ReadinessProbe:nil,Lifecycle:nil,TerminationMessagePath:/dev/termination-log,ImagePullPolicy:IfNotPresent,SecurityContext:&SecurityContext{Capabilities:nil,Privileged:nil,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,},Stdin:false,StdinOnce:false,TTY:false,EnvFrom:[]EnvFromSource{},TerminationMessagePolicy:File,VolumeDevices:[]VolumeDevice{},StartupProbe:nil,},},RestartPolicy:Always,TerminationGracePeriodSeconds:*0,ActiveDeadlineSeconds:nil,DNSPolicy:ClusterFirst,NodeSelector:map[string]string{},ServiceAccountName:default,DeprecatedServiceAccount:default,NodeName:k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1,HostNetwork:false,HostPID:false,HostIPC:false,SecurityContext:&PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,RunAsGroup:nil,Sysctls:[]Sysctl{},WindowsOptions:nil,FSGroupChangePolicy:nil,SeccompProfile:nil,},ImagePullSecrets:[]LocalObjectReference{},Hostname:,Subdomain:,Affinity:nil,SchedulerName:default-scheduler,InitContainers:[]Container{},AutomountServiceAccountToken:nil,Tolerations:[]Toleration{Toleration{Key:node.kubernetes.io/not-ready,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},Toleration{Key:node.kubernetes.io/unreachable,Operator:Exists,Value:,Effect:NoExecute,TolerationSeconds:*300,},},HostAliases:[]HostAlias{},PriorityClassName:,Priority:*0,DNSConfig:nil,ShareProcessNamespace:nil,ReadinessGates:[]PodReadinessGate{},RuntimeClassName:nil,EnableServiceLinks:*true,PreemptionPolicy:*PreemptLowerPriority,Overhead:ResourceList{},TopologySpreadConstraints:[]TopologySpreadConstraint{},EphemeralContainers:[]EphemeralContainer{},SetHostnameAsFQDN:nil,},Status:PodStatus{Phase:Running,Conditions:[]PodCondition{PodCondition{Type:Initialized,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:01 +0000 UTC,Reason:,Message:,},PodCondition{Type:Ready,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:03 +0000 UTC,Reason:,Message:,},PodCondition{Type:ContainersReady,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:03 +0000 UTC,Reason:,Message:,},PodCondition{Type:PodScheduled,Status:True,LastProbeTime:0001-01-01 00:00:00 +0000 UTC,LastTransitionTime:2022-09-03 09:41:01 +0000 UTC,Reason:,Message:,},},Message:,Reason:,HostIP:172.18.0.5,PodIP:192.168.6.57,StartTime:2022-09-03 09:41:01 +0000 UTC,ContainerStatuses:[]ContainerStatus{ContainerStatus{Name:httpd,State:ContainerState{Waiting:nil,Running:&ContainerStateRunning{StartedAt:2022-09-03 09:41:02 +0000 UTC,},Terminated:nil,},LastTerminationState:ContainerState{Waiting:nil,Running:nil,Terminated:nil,},Ready:true,RestartCount:0,Image:k8s.gcr.io/e2e-test-images/httpd:2.4.38-1,ImageID:k8s.gcr.io/e2e-test-images/httpd@sha256:b913fa234cc3473cfe16e937d106b455a7609f927f59031c81aca791e2689b50,ContainerID:containerd://a3ec014cc8e73473247b1b72f8cc9f81e2d73da58af819353ef103bc130dd21e,Started:*true,},},QOSClass:BestEffort,InitContainerStatuses:[]ContainerStatus{},NominatedNodeName:,PodIPs:[]PodIP{PodIP{IP:192.168.6.57,},},EphemeralContainerStatuses:[]ContainerStatus{},},}
... skipping 29 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:41:07.397: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "deployment-703" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] Deployment deployment should support proportional scaling [Conformance]","total":-1,"completed":79,"skipped":1741,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSS
    ------------------------------
    {"msg":"FAILED [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","total":-1,"completed":45,"skipped":746,"failed":2,"failures":["[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]"]}

    [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
    Sep  3 09:35:29.875: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename pod-network-test
    STEP: Waiting for a default service account to be provisioned in namespace
... skipping 274 lines ...
      ----    ------     ----  ----               -------
      Normal  Scheduled  22s   default-scheduler  Successfully assigned pod-network-test-6274/netserver-3 to k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1
      Normal  Pulled     21s   kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.39" already present on machine
      Normal  Created    21s   kubelet            Created container webserver
      Normal  Started    21s   kubelet            Started container webserver
    
    Sep  3 09:35:51.538: INFO: encountered error during dial (did not find expected responses... 

    Tries 1
    Command curl -g -q -s 'http://192.168.0.75:9080/dial?request=hostname&protocol=http&host=192.168.2.25&port=8083&tries=1'
    retrieved map[]
    expected map[netserver-2:{}])
    Sep  3 09:35:51.538: INFO: ...failed...will try again in next pass

    Sep  3 09:35:51.538: INFO: Breadth first check of 192.168.6.44 on host 172.18.0.5...
    Sep  3 09:35:51.542: INFO: ExecWithOptions {Command:[/bin/sh -c curl -g -q -s 'http://192.168.0.75:9080/dial?request=hostname&protocol=http&host=192.168.6.44&port=8083&tries=1'] Namespace:pod-network-test-6274 PodName:test-container-pod ContainerName:webserver Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
    Sep  3 09:35:51.542: INFO: >>> kubeConfig: /tmp/kubeconfig
    Sep  3 09:35:51.636: INFO: Waiting for responses: map[]
    Sep  3 09:35:51.636: INFO: reached 192.168.6.44 after 0/1 tries
    Sep  3 09:35:51.636: INFO: Going to retry 1 out of 4 pods....
... skipping 382 lines ...
      ----    ------     ----   ----               -------
      Normal  Scheduled  5m49s  default-scheduler  Successfully assigned pod-network-test-6274/netserver-3 to k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1
      Normal  Pulled     5m48s  kubelet            Container image "k8s.gcr.io/e2e-test-images/agnhost:2.39" already present on machine
      Normal  Created    5m48s  kubelet            Created container webserver
      Normal  Started    5m48s  kubelet            Started container webserver
    
    Sep  3 09:41:18.044: INFO: encountered error during dial (did not find expected responses... 

    Tries 46
    Command curl -g -q -s 'http://192.168.0.75:9080/dial?request=hostname&protocol=http&host=192.168.2.25&port=8083&tries=1'
    retrieved map[]
    expected map[netserver-2:{}])
    Sep  3 09:41:18.044: INFO: ... Done probing pod [[[ 192.168.2.25 ]]]
    Sep  3 09:41:18.044: INFO: succeeded at polling 3 out of 4 connections
    Sep  3 09:41:18.044: INFO: pod polling failure summary:
    Sep  3 09:41:18.044: INFO: Collected error: did not find expected responses... 

    Tries 46
    Command curl -g -q -s 'http://192.168.0.75:9080/dial?request=hostname&protocol=http&host=192.168.2.25&port=8083&tries=1'
    retrieved map[]
    expected map[netserver-2:{}]
    Sep  3 09:41:18.044: FAIL: failed,  1 out of 4 connections failed

    
    Full Stack Trace
    k8s.io/kubernetes/test/e2e/common/network.glob..func1.1.2()
    	/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/network/networking.go:82 +0x69
    k8s.io/kubernetes/test/e2e.RunE2ETests(0xc000c68a80)
    	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c
... skipping 14 lines ...
    /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/network/framework.go:23
      Granular Checks: Pods
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/network/networking.go:30
        should function for intra-pod communication: http [NodeConformance] [Conformance] [It]
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    
        Sep  3 09:41:18.044: failed,  1 out of 4 connections failed

    
        /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/network/networking.go:82
    ------------------------------
    {"msg":"FAILED [sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","total":-1,"completed":45,"skipped":746,"failed":3,"failures":["[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSS
    ------------------------------
    [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 secret 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-secret-zkp8
    STEP: Creating a pod to test atomic-volume-subpath
    Sep  3 09:41:18.112: INFO: Waiting up to 5m0s for pod "pod-subpath-test-secret-zkp8" in namespace "subpath-3013" to be "Succeeded or Failed"

    Sep  3 09:41:18.115: INFO: Pod "pod-subpath-test-secret-zkp8": Phase="Pending", Reason="", readiness=false. Elapsed: 2.826765ms
    Sep  3 09:41:20.120: INFO: Pod "pod-subpath-test-secret-zkp8": Phase="Running", Reason="", readiness=true. Elapsed: 2.007205479s
    Sep  3 09:41:22.124: INFO: Pod "pod-subpath-test-secret-zkp8": Phase="Running", Reason="", readiness=true. Elapsed: 4.011358765s
    Sep  3 09:41:24.128: INFO: Pod "pod-subpath-test-secret-zkp8": Phase="Running", Reason="", readiness=true. Elapsed: 6.015480925s
    Sep  3 09:41:26.132: INFO: Pod "pod-subpath-test-secret-zkp8": Phase="Running", Reason="", readiness=true. Elapsed: 8.019550441s
    Sep  3 09:41:28.137: INFO: Pod "pod-subpath-test-secret-zkp8": Phase="Running", Reason="", readiness=true. Elapsed: 10.024151941s
... skipping 2 lines ...
    Sep  3 09:41:34.149: INFO: Pod "pod-subpath-test-secret-zkp8": Phase="Running", Reason="", readiness=true. Elapsed: 16.036781958s
    Sep  3 09:41:36.154: INFO: Pod "pod-subpath-test-secret-zkp8": Phase="Running", Reason="", readiness=true. Elapsed: 18.041200417s
    Sep  3 09:41:38.159: INFO: Pod "pod-subpath-test-secret-zkp8": Phase="Running", Reason="", readiness=true. Elapsed: 20.04673832s
    Sep  3 09:41:40.164: INFO: Pod "pod-subpath-test-secret-zkp8": Phase="Running", Reason="", readiness=false. Elapsed: 22.051195117s
    Sep  3 09:41:42.168: INFO: Pod "pod-subpath-test-secret-zkp8": Phase="Succeeded", Reason="", readiness=false. Elapsed: 24.055732231s
    STEP: Saw pod success
    Sep  3 09:41:42.168: INFO: Pod "pod-subpath-test-secret-zkp8" satisfied condition "Succeeded or Failed"

    Sep  3 09:41:42.171: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-worker-zvk8j1 pod pod-subpath-test-secret-zkp8 container test-container-subpath-secret-zkp8: <nil>
    STEP: delete the pod
    Sep  3 09:41:42.197: INFO: Waiting for pod pod-subpath-test-secret-zkp8 to disappear
    Sep  3 09:41:42.199: INFO: Pod pod-subpath-test-secret-zkp8 no longer exists
    STEP: Deleting pod pod-subpath-test-secret-zkp8
    Sep  3 09:41:42.199: INFO: Deleting pod "pod-subpath-test-secret-zkp8" in namespace "subpath-3013"
    [AfterEach] [sig-storage] Subpath
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:41:42.203: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "subpath-3013" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Subpath Atomic writer volumes should support subpaths with secret pod [LinuxOnly] [Conformance]","total":-1,"completed":46,"skipped":759,"failed":3,"failures":["[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]"]}

    
    SSSSS
    ------------------------------
    [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-8166" for this suite.
    [AfterEach] [sig-network] Services
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:756
    
    •
    ------------------------------
    {"msg":"PASSED [sig-network] Services should provide secure master service  [Conformance]","total":-1,"completed":47,"skipped":764,"failed":3,"failures":["[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:41:58.485: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "resourcequota-354" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] ResourceQuota should verify ResourceQuota with best effort scope. [Conformance]","total":-1,"completed":48,"skipped":820,"failed":3,"failures":["[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]"]}

    
    SSS
    ------------------------------
    [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
    Sep  3 09:41:58.507: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename configmap
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume with mappings as non-root [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating configMap with name configmap-test-volume-map-091af8d2-7ad1-4341-94d9-41f2b68c9a78
    STEP: Creating a pod to test consume configMaps
    Sep  3 09:41:58.567: INFO: Waiting up to 5m0s for pod "pod-configmaps-34fe5817-1a4d-49fc-b047-565991e3d07e" in namespace "configmap-426" to be "Succeeded or Failed"

    Sep  3 09:41:58.570: INFO: Pod "pod-configmaps-34fe5817-1a4d-49fc-b047-565991e3d07e": Phase="Pending", Reason="", readiness=false. Elapsed: 2.354488ms
    Sep  3 09:42:00.576: INFO: Pod "pod-configmaps-34fe5817-1a4d-49fc-b047-565991e3d07e": Phase="Running", Reason="", readiness=false. Elapsed: 2.008234369s
    Sep  3 09:42:02.581: INFO: Pod "pod-configmaps-34fe5817-1a4d-49fc-b047-565991e3d07e": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.013843128s
    STEP: Saw pod success
    Sep  3 09:42:02.581: INFO: Pod "pod-configmaps-34fe5817-1a4d-49fc-b047-565991e3d07e" satisfied condition "Succeeded or Failed"

    Sep  3 09:42:02.585: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-configmaps-34fe5817-1a4d-49fc-b047-565991e3d07e container agnhost-container: <nil>
    STEP: delete the pod
    Sep  3 09:42:02.614: INFO: Waiting for pod pod-configmaps-34fe5817-1a4d-49fc-b047-565991e3d07e to disappear
    Sep  3 09:42:02.618: INFO: Pod pod-configmaps-34fe5817-1a4d-49fc-b047-565991e3d07e 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
    Sep  3 09:42:02.618: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "configmap-426" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with mappings as non-root [NodeConformance] [Conformance]","total":-1,"completed":49,"skipped":823,"failed":3,"failures":["[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]"]}

    
    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 23 lines ...
    STEP: Destroying namespace "crd-webhook-7277" 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":50,"skipped":829,"failed":3,"failures":["[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]","[sig-network] Networking Granular Checks: Pods should function for intra-pod communication: http [NodeConformance] [Conformance]"]}

    
    SSSSSSSSSSSSS
    ------------------------------
    [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 51 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:42:38.667: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "statefulset-8270" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-apps] StatefulSet Basic StatefulSet functionality [StatefulSetBasic] should perform rolling updates and roll backs of template modifications [Conformance]","total":-1,"completed":80,"skipped":1761,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SS
    ------------------------------
    [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
    Sep  3 09:42:38.694: INFO: >>> kubeConfig: /tmp/kubeconfig
    STEP: Building a namespace api object, basename projected
    STEP: Waiting for a default service account to be provisioned in namespace
    [It] should be consumable from pods in volume as non-root with defaultMode and fsGroup set [LinuxOnly] [NodeConformance] [Conformance]
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
    STEP: Creating projection with secret that has name projected-secret-test-f69a6c8d-a67c-472d-b785-65d32ca04989
    STEP: Creating a pod to test consume secrets
    Sep  3 09:42:38.753: INFO: Waiting up to 5m0s for pod "pod-projected-secrets-661b9dc2-997a-4e5c-a63c-2c5b8292c064" in namespace "projected-4099" to be "Succeeded or Failed"

    Sep  3 09:42:38.758: INFO: Pod "pod-projected-secrets-661b9dc2-997a-4e5c-a63c-2c5b8292c064": Phase="Pending", Reason="", readiness=false. Elapsed: 4.6643ms
    Sep  3 09:42:40.763: INFO: Pod "pod-projected-secrets-661b9dc2-997a-4e5c-a63c-2c5b8292c064": Phase="Running", Reason="", readiness=false. Elapsed: 2.010198035s
    Sep  3 09:42:42.769: INFO: Pod "pod-projected-secrets-661b9dc2-997a-4e5c-a63c-2c5b8292c064": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.016094729s
    STEP: Saw pod success
    Sep  3 09:42:42.769: INFO: Pod "pod-projected-secrets-661b9dc2-997a-4e5c-a63c-2c5b8292c064" satisfied condition "Succeeded or Failed"

    Sep  3 09:42:42.775: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-twzvl pod pod-projected-secrets-661b9dc2-997a-4e5c-a63c-2c5b8292c064 container projected-secret-volume-test: <nil>
    STEP: delete the pod
    Sep  3 09:42:42.800: INFO: Waiting for pod pod-projected-secrets-661b9dc2-997a-4e5c-a63c-2c5b8292c064 to disappear
    Sep  3 09:42:42.805: INFO: Pod pod-projected-secrets-661b9dc2-997a-4e5c-a63c-2c5b8292c064 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
    Sep  3 09:42:42.805: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "projected-4099" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-storage] Projected secret should be consumable from pods in volume as non-root with defaultMode and fsGroup set [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":81,"skipped":1763,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    [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
    Sep  3 09:42:42.818: 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
    Sep  3 09:44:43.417: INFO: Successfully updated pod "var-expansion-c5dea6dd-2ebf-407e-b239-7e0650db976c"
    STEP: waiting for pod running
    STEP: deleting the pod gracefully
    Sep  3 09:44:45.435: INFO: Deleting pod "var-expansion-c5dea6dd-2ebf-407e-b239-7e0650db976c" in namespace "var-expansion-9552"
    Sep  3 09:44:45.443: INFO: Wait up to 5m0s for pod "var-expansion-c5dea6dd-2ebf-407e-b239-7e0650db976c" to be fully deleted
... skipping 6 lines ...
    • [SLOW TEST:154.653 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":82,"skipped":1763,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    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 21 lines ...
    STEP: Destroying namespace "webhook-4191-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":83,"skipped":1765,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SS
    ------------------------------
    [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 35 lines ...
      /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:186
    Sep  3 09:45:23.069: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "gc-2066" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-api-machinery] Garbage collector should orphan RS created by deployment when deleteOptions.PropagationPolicy is Orphan [Conformance]","total":-1,"completed":84,"skipped":1767,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
    ------------------------------
    [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
    Sep  3 09:45:23.212: 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
    Sep  3 09:45:23.267: INFO: Waiting up to 5m0s for pod "downward-api-6f50918d-152a-471a-9f70-1c4a52e98274" in namespace "downward-api-7318" to be "Succeeded or Failed"

    Sep  3 09:45:23.271: INFO: Pod "downward-api-6f50918d-152a-471a-9f70-1c4a52e98274": Phase="Pending", Reason="", readiness=false. Elapsed: 3.417468ms
    Sep  3 09:45:25.278: INFO: Pod "downward-api-6f50918d-152a-471a-9f70-1c4a52e98274": Phase="Pending", Reason="", readiness=false. Elapsed: 2.01025487s
    Sep  3 09:45:27.285: INFO: Pod "downward-api-6f50918d-152a-471a-9f70-1c4a52e98274": Phase="Succeeded", Reason="", readiness=false. Elapsed: 4.018156897s
    STEP: Saw pod success
    Sep  3 09:45:27.286: INFO: Pod "downward-api-6f50918d-152a-471a-9f70-1c4a52e98274" satisfied condition "Succeeded or Failed"

    Sep  3 09:45:27.290: INFO: Trying to get logs from node k8s-upgrade-and-conformance-z5d79l-md-0-2lbb5-b695c987c-jh8sn pod downward-api-6f50918d-152a-471a-9f70-1c4a52e98274 container dapi-container: <nil>
    STEP: delete the pod
    Sep  3 09:45:27.326: INFO: Waiting for pod downward-api-6f50918d-152a-471a-9f70-1c4a52e98274 to disappear
    Sep  3 09:45:27.330: INFO: Pod downward-api-6f50918d-152a-471a-9f70-1c4a52e98274 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
    Sep  3 09:45:27.330: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
    STEP: Destroying namespace "downward-api-7318" for this suite.
    
    •
    ------------------------------
    {"msg":"PASSED [sig-node] Downward API should provide pod UID as env vars [NodeConformance] [Conformance]","total":-1,"completed":85,"skipped":1823,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller  [Conformance]"]}

    
    SSSSSSSSS
    ------------------------------
    {"msg":"FAILED [sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]","total":-1,"completed":8,"skipped":237,"failed":2,"failures":["[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
    Sep  3 09:35:31.741: 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 ...
    Sep  3 09:35:33.891: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:33.896: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:33.900: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:33.902: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:33.905: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:33.909: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:33.909: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3803 wheezy_tcp@dns-test-service.dns-3803 wheezy_udp@dns-test-service.dns-3803.svc wheezy_tcp@dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3803 jessie_tcp@dns-test-service.dns-3803 jessie_udp@dns-test-service.dns-3803.svc jessie_tcp@dns-test-service.dns-3803.svc jessie_udp@_http._tcp.dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_udp@_http._tcp.test-service-2.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:35:38.913: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:38.916: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:38.919: INFO: Unable to read wheezy_udp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:38.921: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:38.924: INFO: Unable to read wheezy_udp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 17 lines ...
    Sep  3 09:35:38.965: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:38.967: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:38.969: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:38.971: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:38.974: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:38.976: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:38.976: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-3803 wheezy_tcp@dns-test-service.dns-3803 wheezy_udp@dns-test-service.dns-3803.svc wheezy_tcp@dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-3803 jessie_tcp@dns-test-service.dns-3803 jessie_udp@dns-test-service.dns-3803.svc jessie_tcp@dns-test-service.dns-3803.svc jessie_udp@_http._tcp.dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_udp@_http._tcp.test-service-2.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:35:43.913: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:43.916: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:43.921: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:43.924: INFO: Unable to read wheezy_udp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:43.926: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 15 lines ...
    Sep  3 09:35:43.968: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:43.970: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:43.973: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:43.976: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:43.980: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:43.983: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:43.983: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3803 wheezy_udp@dns-test-service.dns-3803.svc wheezy_tcp@dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3803 jessie_udp@dns-test-service.dns-3803.svc jessie_tcp@dns-test-service.dns-3803.svc jessie_udp@_http._tcp.dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_udp@_http._tcp.test-service-2.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:35:48.913: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:48.916: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:48.921: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:48.923: INFO: Unable to read wheezy_udp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:48.926: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 15 lines ...
    Sep  3 09:35:48.967: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:48.970: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:48.972: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:48.975: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:48.978: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:48.980: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:48.980: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3803 wheezy_udp@dns-test-service.dns-3803.svc wheezy_tcp@dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3803 jessie_udp@dns-test-service.dns-3803.svc jessie_tcp@dns-test-service.dns-3803.svc jessie_udp@_http._tcp.dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_udp@_http._tcp.test-service-2.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:35:53.913: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:53.916: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:53.921: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:53.923: INFO: Unable to read wheezy_udp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:53.925: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 14 lines ...
    Sep  3 09:35:53.965: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:53.968: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:53.970: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:53.972: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:53.974: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:53.977: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:53.977: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3803 wheezy_udp@dns-test-service.dns-3803.svc wheezy_tcp@dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3803 jessie_tcp@dns-test-service.dns-3803.svc jessie_udp@_http._tcp.dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_udp@_http._tcp.test-service-2.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:35:58.913: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:58.916: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:58.923: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:58.925: INFO: Unable to read wheezy_udp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:58.927: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 14 lines ...
    Sep  3 09:35:58.972: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:58.975: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:58.979: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:58.982: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:58.985: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:58.987: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:35:58.987: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3803 wheezy_udp@dns-test-service.dns-3803.svc wheezy_tcp@dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3803 jessie_tcp@dns-test-service.dns-3803.svc jessie_udp@_http._tcp.dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_udp@_http._tcp.test-service-2.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:36:03.917: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:03.922: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:03.929: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:03.933: INFO: Unable to read wheezy_udp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:03.937: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 14 lines ...
    Sep  3 09:36:04.016: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:04.019: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:04.023: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:04.028: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:04.032: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:04.035: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:04.035: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3803 wheezy_udp@dns-test-service.dns-3803.svc wheezy_tcp@dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3803 jessie_tcp@dns-test-service.dns-3803.svc jessie_udp@_http._tcp.dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_udp@_http._tcp.test-service-2.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:36:08.912: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:08.915: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:08.921: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:08.923: INFO: Unable to read wheezy_udp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:08.926: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 14 lines ...
    Sep  3 09:36:08.969: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:08.971: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:08.981: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:08.984: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:08.986: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:08.989: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:08.989: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3803 wheezy_udp@dns-test-service.dns-3803.svc wheezy_tcp@dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3803 jessie_tcp@dns-test-service.dns-3803.svc jessie_udp@_http._tcp.dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_udp@_http._tcp.test-service-2.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:36:13.915: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:13.918: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:13.924: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:13.932: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:13.935: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 13 lines ...
    Sep  3 09:36:13.976: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:13.979: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:13.982: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:13.984: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:13.986: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:13.989: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:13.989: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3803 wheezy_tcp@dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3803 jessie_tcp@dns-test-service.dns-3803.svc jessie_udp@_http._tcp.dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_udp@_http._tcp.test-service-2.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:36:18.913: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:18.916: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:18.921: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:18.924: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:18.927: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 13 lines ...
    Sep  3 09:36:18.988: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:18.990: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:18.993: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:18.996: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:18.998: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:19.001: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:19.001: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3803 wheezy_tcp@dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3803 jessie_tcp@dns-test-service.dns-3803.svc jessie_udp@_http._tcp.dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_udp@_http._tcp.test-service-2.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:36:23.912: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:23.915: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:23.919: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:23.924: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:23.926: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 12 lines ...
    Sep  3 09:36:23.961: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:23.963: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:23.965: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:23.967: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:23.970: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:23.972: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:23.972: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3803 wheezy_tcp@dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3803 jessie_tcp@dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_udp@_http._tcp.test-service-2.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:36:28.914: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:28.917: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:28.923: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:28.931: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:28.934: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 12 lines ...
    Sep  3 09:36:28.979: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:28.981: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:28.984: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:28.987: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:28.989: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:28.991: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:28.991: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3803 wheezy_tcp@dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.dns-test-service.dns-3803.svc wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3803 jessie_tcp@dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_udp@_http._tcp.test-service-2.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:36:33.913: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:33.917: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:33.922: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:33.932: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:33.935: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 9 lines ...
    Sep  3 09:36:33.966: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:33.971: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:33.973: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:33.976: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:33.979: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:33.981: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:33.981: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3803 wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3803 jessie_tcp@dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:36:38.914: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:38.917: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:38.923: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:38.934: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:38.937: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 9 lines ...
    Sep  3 09:36:38.968: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:38.973: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:38.975: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:38.977: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:38.980: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:38.982: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:38.982: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3803 wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3803 jessie_tcp@dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:36:43.913: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:43.917: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:43.925: INFO: Unable to read wheezy_tcp@dns-test-service.dns-3803 from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:43.940: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:43.943: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
... skipping 9 lines ...
    Sep  3 09:36:43.987: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:43.995: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-3803.svc from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:43.999: INFO: Unable to read jessie_udp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:44.004: INFO: Unable to read jessie_tcp@PodARecord from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:44.008: INFO: Unable to read 10.137.117.5_udp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:44.012: INFO: Unable to read 10.137.117.5_tcp@PTR from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not find the requested resource (get pods dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7)
    Sep  3 09:36:44.012: INFO: Lookups using dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-3803 wheezy_tcp@_http._tcp.dns-test-service.dns-3803.svc wheezy_udp@_http._tcp.test-service-2.dns-3803.svc wheezy_tcp@_http._tcp.test-service-2.dns-3803.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-3803 jessie_tcp@dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.dns-test-service.dns-3803.svc jessie_tcp@_http._tcp.test-service-2.dns-3803.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.137.117.5_udp@PTR 10.137.117.5_tcp@PTR]

    
    Sep  3 09:36:48.914: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-3803/dns-test-ee7ba41f-d567-45f6-b253-782a441ca0a7: the server could not