periodic-cluster-api-e2e-workload-upgrade-1-19-1-20-release-1-1 #1612453963167174656
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| Result | SUCCESS |
| Tests | 15 failed / 288 succeeded |
| Started | |
| Elapsed | 1h22m |
| Revision | release-1.1 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-api\-machinery\]\sAdmissionWebhook\s\[Privileged\:ClusterAdmin\]\sshould\sunconditionally\sreject\soperations\son\sfail\sclosed\swebhook\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 Jan 9 15:20:59.476: waiting for webhook configuration to be ready Unexpected error: <*errors.errorString | 0xc0002761f0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:1274from junit.kubetest.02.xml
[BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 �[1mSTEP�[0m: Creating a kubernetes client Jan 9 15:20:05.794: INFO: >>> kubeConfig: /tmp/kubeconfig �[1mSTEP�[0m: Building a namespace api object, basename webhook �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:86 �[1mSTEP�[0m: Setting up server cert �[1mSTEP�[0m: Create role binding to let webhook read extension-apiserver-authentication �[1mSTEP�[0m: Deploying the webhook pod �[1mSTEP�[0m: Wait for the deployment to be ready Jan 9 15:20:06.105: INFO: deployment "sample-webhook-deployment" doesn't have the required revision set �[1mSTEP�[0m: Deploying the webhook service �[1mSTEP�[0m: Verifying the service has paired with the endpoint Jan 9 15:20:09.130: INFO: Waiting for amount of service:e2e-test-webhook endpoints to be 1 [It] should unconditionally reject operations on fail closed webhook [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 �[1mSTEP�[0m: Registering a webhook that server cannot talk to, with fail closed policy, via the AdmissionRegistration API Jan 9 15:20:19.152: INFO: Waiting for webhook configuration to be ready... Jan 9 15:20:29.266: INFO: Waiting for webhook configuration to be ready... Jan 9 15:20:39.362: INFO: Waiting for webhook configuration to be ready... Jan 9 15:20:49.465: INFO: Waiting for webhook configuration to be ready... Jan 9 15:20:59.475: INFO: Waiting for webhook configuration to be ready... Jan 9 15:20:59.476: FAIL: waiting for webhook configuration to be ready Unexpected error: <*errors.errorString | 0xc0002761f0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred Full Stack Trace k8s.io/kubernetes/test/e2e/apimachinery.registerFailClosedWebhook(0xc000b22b00, 0xc004c607e0, 0xc, 0xc0035a26e0, 0x20fb, 0xc0055a7228) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:1274 +0x8ca k8s.io/kubernetes/test/e2e/apimachinery.glob..func23.7() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:236 +0x69 k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c k8s.io/kubernetes/test/e2e.TestE2E(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b testing.tRunner(0xc0018abb00, 0x4fc9940) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 Jan 9 15:20:59.476: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready �[1mSTEP�[0m: Destroying namespace "webhook-7121" for this suite. �[1mSTEP�[0m: Destroying namespace "webhook-7121-markers" for this suite. [AfterEach] [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:101
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sclient\sUpdate\sDemo\sshould\screate\sand\sstop\sa\sreplication\scontroller\s\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 Jan 9 15:16:08.787: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:317from junit.kubetest.03.xml
{"msg":"FAILED [sig-cli] Kubectl client Update Demo should create and stop a replication controller [Conformance]","total":-1,"completed":49,"skipped":991,"failed":1,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller [Conformance]"]} [BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 �[1mSTEP�[0m: Creating a kubernetes client Jan 9 15:08:45.371: INFO: >>> kubeConfig: /tmp/kubeconfig �[1mSTEP�[0m: Building a namespace api object, basename kubectl �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:247 [BeforeEach] Update Demo /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:299 [It] should create and stop a replication controller [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 �[1mSTEP�[0m: creating a replication controller Jan 9 15:08:45.396: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 create -f -' Jan 9 15:08:46.073: INFO: stderr: "" Jan 9 15:08:46.073: INFO: stdout: "replicationcontroller/update-demo-nautilus created\n" �[1mSTEP�[0m: waiting for all containers in name=update-demo pods to come up. Jan 9 15:08:46.073: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo' Jan 9 15:08:46.169: INFO: stderr: "" Jan 9 15:08:46.169: INFO: stdout: "update-demo-nautilus-j6qbq update-demo-nautilus-sw89r " Jan 9 15:08:46.169: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 get pods update-demo-nautilus-j6qbq -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}' Jan 9 15:08:46.253: INFO: stderr: "" Jan 9 15:08:46.253: INFO: stdout: "" Jan 9 15:08:46.253: INFO: update-demo-nautilus-j6qbq is created but not running Jan 9 15:08:51.253: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo' Jan 9 15:08:51.342: INFO: stderr: "" Jan 9 15:08:51.342: INFO: stdout: "update-demo-nautilus-j6qbq update-demo-nautilus-sw89r " Jan 9 15:08:51.342: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 get pods update-demo-nautilus-j6qbq -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}' Jan 9 15:08:51.427: INFO: stderr: "" Jan 9 15:08:51.428: INFO: stdout: "true" Jan 9 15:08:51.428: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 get pods update-demo-nautilus-j6qbq -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}' Jan 9 15:08:51.513: INFO: stderr: "" Jan 9 15:08:51.513: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0" Jan 9 15:08:51.513: INFO: validating pod update-demo-nautilus-j6qbq Jan 9 15:12:24.650: INFO: update-demo-nautilus-j6qbq is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-j6qbq) Jan 9 15:12:29.650: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo' Jan 9 15:12:29.977: INFO: stderr: "" Jan 9 15:12:29.977: INFO: stdout: "update-demo-nautilus-j6qbq update-demo-nautilus-sw89r " Jan 9 15:12:29.977: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 get pods update-demo-nautilus-j6qbq -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}' Jan 9 15:12:30.068: INFO: stderr: "" Jan 9 15:12:30.068: INFO: stdout: "true" Jan 9 15:12:30.068: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 get pods update-demo-nautilus-j6qbq -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}' Jan 9 15:12:30.157: INFO: stderr: "" Jan 9 15:12:30.157: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0" Jan 9 15:12:30.157: INFO: validating pod update-demo-nautilus-j6qbq Jan 9 15:16:03.786: INFO: update-demo-nautilus-j6qbq is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-j6qbq) Jan 9 15:16:08.787: FAIL: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state Full Stack Trace k8s.io/kubernetes/test/e2e/kubectl.glob..func1.6.2() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:317 +0x29b k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0001d3e00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c k8s.io/kubernetes/test/e2e.TestE2E(0xc0001d3e00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b testing.tRunner(0xc0001d3e00, 0x4fc9940) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 �[1mSTEP�[0m: using delete to clean up resources Jan 9 15:16:08.787: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 delete --grace-period=0 --force -f -' Jan 9 15:16:08.874: INFO: stderr: "warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely.\n" Jan 9 15:16:08.874: INFO: stdout: "replicationcontroller \"update-demo-nautilus\" force deleted\n" Jan 9 15:16:08.874: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 get rc,svc -l name=update-demo --no-headers' Jan 9 15:16:08.966: INFO: stderr: "No resources found in kubectl-1504 namespace.\n" Jan 9 15:16:08.966: INFO: stdout: "" Jan 9 15:16:08.966: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 get pods -l name=update-demo -o go-template={{ range .items }}{{ if not .metadata.deletionTimestamp }}{{ .metadata.name }}{{ "\n" }}{{ end }}{{ end }}' Jan 9 15:16:09.054: INFO: stderr: "" Jan 9 15:16:09.054: INFO: stdout: "update-demo-nautilus-j6qbq\nupdate-demo-nautilus-sw89r\n" Jan 9 15:16:09.555: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 get rc,svc -l name=update-demo --no-headers' Jan 9 15:16:09.646: INFO: stderr: "No resources found in kubectl-1504 namespace.\n" Jan 9 15:16:09.646: INFO: stdout: "" Jan 9 15:16:09.646: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1504 get pods -l name=update-demo -o go-template={{ range .items }}{{ if not .metadata.deletionTimestamp }}{{ .metadata.name }}{{ "\n" }}{{ end }}{{ end }}' Jan 9 15:16:09.737: INFO: stderr: "" Jan 9 15:16:09.737: INFO: stdout: "" [AfterEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 Jan 9 15:16:09.737: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready �[1mSTEP�[0m: Destroying namespace "kubectl-1504" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sclient\sUpdate\sDemo\sshould\screate\sand\sstop\sa\sreplication\scontroller\s\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 Jan 9 15:23:33.206: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:317from junit.kubetest.03.xml
{"msg":"FAILED [sig-cli] Kubectl client Update Demo should create and stop a replication controller [Conformance]","total":-1,"completed":49,"skipped":991,"failed":2,"failures":["[sig-cli] Kubectl client Update Demo should create and stop a replication controller [Conformance]","[sig-cli] Kubectl client Update Demo should create and stop a replication controller [Conformance]"]} [BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 �[1mSTEP�[0m: Creating a kubernetes client Jan 9 15:16:09.749: INFO: >>> kubeConfig: /tmp/kubeconfig �[1mSTEP�[0m: Building a namespace api object, basename kubectl �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:247 [BeforeEach] Update Demo /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:299 [It] should create and stop a replication controller [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 �[1mSTEP�[0m: creating a replication controller Jan 9 15:16:09.773: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 create -f -' Jan 9 15:16:10.811: INFO: stderr: "" Jan 9 15:16:10.811: INFO: stdout: "replicationcontroller/update-demo-nautilus created\n" �[1mSTEP�[0m: waiting for all containers in name=update-demo pods to come up. Jan 9 15:16:10.811: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo' Jan 9 15:16:10.910: INFO: stderr: "" Jan 9 15:16:10.910: INFO: stdout: "update-demo-nautilus-cdzd7 update-demo-nautilus-fv9z4 " Jan 9 15:16:10.910: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 get pods update-demo-nautilus-cdzd7 -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}' Jan 9 15:16:10.998: INFO: stderr: "" Jan 9 15:16:10.998: INFO: stdout: "" Jan 9 15:16:10.998: INFO: update-demo-nautilus-cdzd7 is created but not running Jan 9 15:16:15.998: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo' Jan 9 15:16:16.084: INFO: stderr: "" Jan 9 15:16:16.084: INFO: stdout: "update-demo-nautilus-cdzd7 update-demo-nautilus-fv9z4 " Jan 9 15:16:16.084: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 get pods update-demo-nautilus-cdzd7 -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}' Jan 9 15:16:16.170: INFO: stderr: "" Jan 9 15:16:16.170: INFO: stdout: "true" Jan 9 15:16:16.170: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 get pods update-demo-nautilus-cdzd7 -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}' Jan 9 15:16:16.255: INFO: stderr: "" Jan 9 15:16:16.255: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0" Jan 9 15:16:16.255: INFO: validating pod update-demo-nautilus-cdzd7 Jan 9 15:19:49.070: INFO: update-demo-nautilus-cdzd7 is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-cdzd7) Jan 9 15:19:54.070: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo' Jan 9 15:19:54.157: INFO: stderr: "" Jan 9 15:19:54.157: INFO: stdout: "update-demo-nautilus-cdzd7 update-demo-nautilus-fv9z4 " Jan 9 15:19:54.158: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 get pods update-demo-nautilus-cdzd7 -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}' Jan 9 15:19:54.239: INFO: stderr: "" Jan 9 15:19:54.239: INFO: stdout: "true" Jan 9 15:19:54.239: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 get pods update-demo-nautilus-cdzd7 -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}' Jan 9 15:19:54.327: INFO: stderr: "" Jan 9 15:19:54.327: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0" Jan 9 15:19:54.327: INFO: validating pod update-demo-nautilus-cdzd7 Jan 9 15:23:28.206: INFO: update-demo-nautilus-cdzd7 is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-cdzd7) Jan 9 15:23:33.206: FAIL: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state Full Stack Trace k8s.io/kubernetes/test/e2e/kubectl.glob..func1.6.2() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:317 +0x29b k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0001d3e00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c k8s.io/kubernetes/test/e2e.TestE2E(0xc0001d3e00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b testing.tRunner(0xc0001d3e00, 0x4fc9940) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 �[1mSTEP�[0m: using delete to clean up resources Jan 9 15:23:33.207: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 delete --grace-period=0 --force -f -' Jan 9 15:23:33.482: INFO: stderr: "warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely.\n" Jan 9 15:23:33.482: INFO: stdout: "replicationcontroller \"update-demo-nautilus\" force deleted\n" Jan 9 15:23:33.482: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 get rc,svc -l name=update-demo --no-headers' Jan 9 15:23:33.575: INFO: stderr: "No resources found in kubectl-1197 namespace.\n" Jan 9 15:23:33.575: INFO: stdout: "" Jan 9 15:23:33.575: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 get pods -l name=update-demo -o go-template={{ range .items }}{{ if not .metadata.deletionTimestamp }}{{ .metadata.name }}{{ "\n" }}{{ end }}{{ end }}' Jan 9 15:23:33.656: INFO: stderr: "" Jan 9 15:23:33.656: INFO: stdout: "update-demo-nautilus-cdzd7\nupdate-demo-nautilus-fv9z4\n" Jan 9 15:23:34.156: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 get rc,svc -l name=update-demo --no-headers' Jan 9 15:23:34.276: INFO: stderr: "No resources found in kubectl-1197 namespace.\n" Jan 9 15:23:34.276: INFO: stdout: "" Jan 9 15:23:34.276: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-1197 get pods -l name=update-demo -o go-template={{ range .items }}{{ if not .metadata.deletionTimestamp }}{{ .metadata.name }}{{ "\n" }}{{ end }}{{ end }}' Jan 9 15:23:34.379: INFO: stderr: "" Jan 9 15:23:34.379: INFO: stdout: "" [AfterEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 Jan 9 15:23:34.379: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready �[1mSTEP�[0m: Destroying namespace "kubectl-1197" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sclient\sUpdate\sDemo\sshould\screate\sand\sstop\sa\sreplication\scontroller\s\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 Jan 9 15:08:44.370: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:317from junit.kubetest.03.xml
[BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 �[1mSTEP�[0m: Creating a kubernetes client Jan 9 15:01:20.067: INFO: >>> kubeConfig: /tmp/kubeconfig �[1mSTEP�[0m: Building a namespace api object, basename kubectl �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace [BeforeEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:247 [BeforeEach] Update Demo /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:299 [It] should create and stop a replication controller [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 �[1mSTEP�[0m: creating a replication controller Jan 9 15:01:20.097: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 create -f -' Jan 9 15:01:20.359: INFO: stderr: "" Jan 9 15:01:20.359: INFO: stdout: "replicationcontroller/update-demo-nautilus created\n" �[1mSTEP�[0m: waiting for all containers in name=update-demo pods to come up. Jan 9 15:01:20.359: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo' Jan 9 15:01:20.466: INFO: stderr: "" Jan 9 15:01:20.466: INFO: stdout: "update-demo-nautilus-gcq62 update-demo-nautilus-kvltz " Jan 9 15:01:20.466: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods update-demo-nautilus-gcq62 -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}' Jan 9 15:01:20.550: INFO: stderr: "" Jan 9 15:01:20.550: INFO: stdout: "" Jan 9 15:01:20.550: INFO: update-demo-nautilus-gcq62 is created but not running Jan 9 15:01:25.551: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo' Jan 9 15:01:25.778: INFO: stderr: "" Jan 9 15:01:25.778: INFO: stdout: "update-demo-nautilus-gcq62 update-demo-nautilus-kvltz " Jan 9 15:01:25.778: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods update-demo-nautilus-gcq62 -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}' Jan 9 15:01:25.864: INFO: stderr: "" Jan 9 15:01:25.865: INFO: stdout: "true" Jan 9 15:01:25.865: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods update-demo-nautilus-gcq62 -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}' Jan 9 15:01:25.945: INFO: stderr: "" Jan 9 15:01:25.945: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0" Jan 9 15:01:25.945: INFO: validating pod update-demo-nautilus-gcq62 Jan 9 15:01:25.949: INFO: got data: { "image": "nautilus.jpg" } Jan 9 15:01:25.949: INFO: Unmarshalled json jpg/img => {nautilus.jpg} , expecting nautilus.jpg . Jan 9 15:01:25.949: INFO: update-demo-nautilus-gcq62 is verified up and running Jan 9 15:01:25.949: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods update-demo-nautilus-kvltz -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}' Jan 9 15:01:26.035: INFO: stderr: "" Jan 9 15:01:26.035: INFO: stdout: "true" Jan 9 15:01:26.035: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods update-demo-nautilus-kvltz -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}' Jan 9 15:01:26.122: INFO: stderr: "" Jan 9 15:01:26.122: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0" Jan 9 15:01:26.122: INFO: validating pod update-demo-nautilus-kvltz Jan 9 15:05:00.238: INFO: update-demo-nautilus-kvltz is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-kvltz) Jan 9 15:05:05.238: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods -o template --template={{range.items}}{{.metadata.name}} {{end}} -l name=update-demo' Jan 9 15:05:05.360: INFO: stderr: "" Jan 9 15:05:05.360: INFO: stdout: "update-demo-nautilus-gcq62 update-demo-nautilus-kvltz " Jan 9 15:05:05.360: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods update-demo-nautilus-gcq62 -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}' Jan 9 15:05:05.472: INFO: stderr: "" Jan 9 15:05:05.472: INFO: stdout: "true" Jan 9 15:05:05.472: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods update-demo-nautilus-gcq62 -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}' Jan 9 15:05:05.561: INFO: stderr: "" Jan 9 15:05:05.561: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0" Jan 9 15:05:05.561: INFO: validating pod update-demo-nautilus-gcq62 Jan 9 15:05:05.565: INFO: got data: { "image": "nautilus.jpg" } Jan 9 15:05:05.565: INFO: Unmarshalled json jpg/img => {nautilus.jpg} , expecting nautilus.jpg . Jan 9 15:05:05.565: INFO: update-demo-nautilus-gcq62 is verified up and running Jan 9 15:05:05.565: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods update-demo-nautilus-kvltz -o template --template={{if (exists . "status" "containerStatuses")}}{{range .status.containerStatuses}}{{if (and (eq .name "update-demo") (exists . "state" "running"))}}true{{end}}{{end}}{{end}}' Jan 9 15:05:05.655: INFO: stderr: "" Jan 9 15:05:05.655: INFO: stdout: "true" Jan 9 15:05:05.655: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods update-demo-nautilus-kvltz -o template --template={{if (exists . "spec" "containers")}}{{range .spec.containers}}{{if eq .name "update-demo"}}{{.image}}{{end}}{{end}}{{end}}' Jan 9 15:05:05.738: INFO: stderr: "" Jan 9 15:05:05.739: INFO: stdout: "gcr.io/kubernetes-e2e-test-images/nautilus:1.0" Jan 9 15:05:05.739: INFO: validating pod update-demo-nautilus-kvltz Jan 9 15:08:39.370: INFO: update-demo-nautilus-kvltz is running right image but validator function failed: an error on the server ("unknown") has prevented the request from succeeding (get pods update-demo-nautilus-kvltz) Jan 9 15:08:44.370: FAIL: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state Full Stack Trace k8s.io/kubernetes/test/e2e/kubectl.glob..func1.6.2() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl/kubectl.go:317 +0x29b k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0001d3e00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c k8s.io/kubernetes/test/e2e.TestE2E(0xc0001d3e00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b testing.tRunner(0xc0001d3e00, 0x4fc9940) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 �[1mSTEP�[0m: using delete to clean up resources Jan 9 15:08:44.371: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 delete --grace-period=0 --force -f -' Jan 9 15:08:44.469: INFO: stderr: "warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely.\n" Jan 9 15:08:44.469: INFO: stdout: "replicationcontroller \"update-demo-nautilus\" force deleted\n" Jan 9 15:08:44.469: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get rc,svc -l name=update-demo --no-headers' Jan 9 15:08:44.558: INFO: stderr: "No resources found in kubectl-6168 namespace.\n" Jan 9 15:08:44.558: INFO: stdout: "" Jan 9 15:08:44.558: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods -l name=update-demo -o go-template={{ range .items }}{{ if not .metadata.deletionTimestamp }}{{ .metadata.name }}{{ "\n" }}{{ end }}{{ end }}' Jan 9 15:08:44.645: INFO: stderr: "" Jan 9 15:08:44.645: INFO: stdout: "update-demo-nautilus-gcq62\nupdate-demo-nautilus-kvltz\n" Jan 9 15:08:45.145: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get rc,svc -l name=update-demo --no-headers' Jan 9 15:08:45.261: INFO: stderr: "No resources found in kubectl-6168 namespace.\n" Jan 9 15:08:45.261: INFO: stdout: "" Jan 9 15:08:45.261: INFO: Running '/usr/local/bin/kubectl --kubeconfig=/tmp/kubeconfig --namespace=kubectl-6168 get pods -l name=update-demo -o go-template={{ range .items }}{{ if not .metadata.deletionTimestamp }}{{ .metadata.name }}{{ "\n" }}{{ end }}{{ end }}' Jan 9 15:08:45.358: INFO: stderr: "" Jan 9 15:08:45.360: INFO: stdout: "" [AfterEach] [sig-cli] Kubectl client /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 Jan 9 15:08:45.360: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready �[1mSTEP�[0m: Destroying namespace "kubectl-6168" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sDNS\sshould\sprovide\sDNS\sfor\sExternalName\sservices\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 Jan 9 14:51:37.546: Unable to read jessie_udp@dns-test-service-3.dns-5579.svc.cluster.local from pod dns-5579/dns-test-6bab9f9a-cec1-41e0-89f7-7121f6611c6a: Get "https://172.18.0.3:6443/api/v1/namespaces/dns-5579/pods/dns-test-6bab9f9a-cec1-41e0-89f7-7121f6611c6a/proxy/results/jessie_udp@dns-test-service-3.dns-5579.svc.cluster.local": context deadline exceeded /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:211from junit.kubetest.02.xml
{"msg":"FAILED [sig-network] DNS should provide DNS for ExternalName services [Conformance]","total":-1,"completed":2,"skipped":77,"failed":1,"failures":["[sig-network] DNS should provide DNS for ExternalName services [Conformance]"]} [BeforeEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 �[1mSTEP�[0m: Creating a kubernetes client Jan 9 14:46:35.488: INFO: >>> kubeConfig: /tmp/kubeconfig �[1mSTEP�[0m: Building a namespace api object, basename dns �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace [It] should provide DNS for ExternalName services [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 �[1mSTEP�[0m: Creating a test externalName service �[1mSTEP�[0m: Running these commands on wheezy: for i in `seq 1 30`; do dig +short dns-test-service-3.dns-5579.svc.cluster.local CNAME > /results/wheezy_udp@dns-test-service-3.dns-5579.svc.cluster.local; sleep 1; done �[1mSTEP�[0m: Running these commands on jessie: for i in `seq 1 30`; do dig +short dns-test-service-3.dns-5579.svc.cluster.local CNAME > /results/jessie_udp@dns-test-service-3.dns-5579.svc.cluster.local; sleep 1; done �[1mSTEP�[0m: creating a pod to probe DNS �[1mSTEP�[0m: submitting the pod to kubernetes �[1mSTEP�[0m: retrieving the pod �[1mSTEP�[0m: looking for the results for each expected name from probers Jan 9 14:50:11.402: INFO: Unable to read wheezy_udp@dns-test-service-3.dns-5579.svc.cluster.local from pod dns-5579/dns-test-6bab9f9a-cec1-41e0-89f7-7121f6611c6a: an error on the server ("unknown") has prevented the request from succeeding (get pods dns-test-6bab9f9a-cec1-41e0-89f7-7121f6611c6a) Jan 9 14:51:37.546: FAIL: Unable to read jessie_udp@dns-test-service-3.dns-5579.svc.cluster.local from pod dns-5579/dns-test-6bab9f9a-cec1-41e0-89f7-7121f6611c6a: Get "https://172.18.0.3:6443/api/v1/namespaces/dns-5579/pods/dns-test-6bab9f9a-cec1-41e0-89f7-7121f6611c6a/proxy/results/jessie_udp@dns-test-service-3.dns-5579.svc.cluster.local": context deadline exceeded Full Stack Trace k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtection(0xc000e0a628, 0xcb0200, 0x0, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:211 +0x69 k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.pollImmediateInternal(0xc000feec60, 0xc000e0a628, 0xc000feec60, 0xc000e0a628) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:445 +0x2f k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.PollImmediate(0x12a05f200, 0x8bb2c97000, 0xc000e0a628, 0x4a, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:441 +0x4d k8s.io/kubernetes/test/e2e/network.assertFilesContain(0xc000e0a918, 0x2, 0x2, 0x4dccbe5, 0x7, 0xc003032c00, 0x56112e0, 0xc0014ac9a0, 0x1, 0x4decde7, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464 +0x158 k8s.io/kubernetes/test/e2e/network.validateTargetedProbeOutput(0xc000f00420, 0xc003032c00, 0xc000e0a918, 0x2, 0x2, 0x4decde7, 0x10) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:549 +0x365 k8s.io/kubernetes/test/e2e/network.glob..func2.9() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns.go:353 +0x6fa k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c k8s.io/kubernetes/test/e2e.TestE2E(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b testing.tRunner(0xc0018abb00, 0x4fc9940) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 E0109 14:51:37.547389 15 runtime.go:78] Observed a panic: ginkgowrapper.FailurePanic{Message:"Jan 9 14:51:37.546: Unable to read jessie_udp@dns-test-service-3.dns-5579.svc.cluster.local from pod dns-5579/dns-test-6bab9f9a-cec1-41e0-89f7-7121f6611c6a: Get \"https://172.18.0.3:6443/api/v1/namespaces/dns-5579/pods/dns-test-6bab9f9a-cec1-41e0-89f7-7121f6611c6a/proxy/results/jessie_udp@dns-test-service-3.dns-5579.svc.cluster.local\": context deadline exceeded", Filename:"/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go", Line:211, FullStackTrace:"k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtection(0xc000e0a628, 0xcb0200, 0x0, 0x0)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:211 +0x69\nk8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.pollImmediateInternal(0xc000feec60, 0xc000e0a628, 0xc000feec60, 0xc000e0a628)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:445 +0x2f\nk8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.PollImmediate(0x12a05f200, 0x8bb2c97000, 0xc000e0a628, 0x4a, 0x0)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:441 +0x4d\nk8s.io/kubernetes/test/e2e/network.assertFilesContain(0xc000e0a918, 0x2, 0x2, 0x4dccbe5, 0x7, 0xc003032c00, 0x56112e0, 0xc0014ac9a0, 0x1, 0x4decde7, ...)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464 +0x158\nk8s.io/kubernetes/test/e2e/network.validateTargetedProbeOutput(0xc000f00420, 0xc003032c00, 0xc000e0a918, 0x2, 0x2, 0x4decde7, 0x10)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:549 +0x365\nk8s.io/kubernetes/test/e2e/network.glob..func2.9()\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns.go:353 +0x6fa\nk8s.io/kubernetes/test/e2e.RunE2ETests(0xc0018abb00)\n\t_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c\nk8s.io/kubernetes/test/e2e.TestE2E(0xc0018abb00)\n\t_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b\ntesting.tRunner(0xc0018abb00, 0x4fc9940)\n\t/usr/local/go/src/testing/testing.go:1123 +0xef\ncreated by testing.(*T).Run\n\t/usr/local/go/src/testing/testing.go:1168 +0x2b3"} ( Your test failed. Ginkgo panics to prevent subsequent assertions from running. Normally Ginkgo rescues this panic so you shouldn't see it. But, if you make an assertion in a goroutine, Ginkgo can't capture the panic. To circumvent this, you should call defer GinkgoRecover() at the top of the goroutine that caused this panic. ) goroutine 133 [running]: k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime.logPanic(0x499f1e0, 0xc0039ae100) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:74 +0x95 k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:48 +0x89 panic(0x499f1e0, 0xc0039ae100) /usr/local/go/src/runtime/panic.go:969 +0x1b9 k8s.io/kubernetes/test/e2e/framework/ginkgowrapper.Fail.func1(0xc001091200, 0x16b, 0x77a462c, 0x7d, 0xd3, 0xc002cba800, 0x771) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/ginkgowrapper/wrapper.go:63 +0xa5 panic(0x41905e0, 0x5431f10) /usr/local/go/src/runtime/panic.go:969 +0x1b9 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo.Fail(0xc001091200, 0x16b, 0xc000e0a0d0, 0x1, 0x1) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:267 +0xc8 k8s.io/kubernetes/test/e2e/framework/ginkgowrapper.Fail(0xc001091200, 0x16b, 0xc000e0a1b8, 0x1, 0x1) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/ginkgowrapper/wrapper.go:67 +0x1b5 k8s.io/kubernetes/test/e2e/framework.Failf(0x4e68bfb, 0x24, 0xc000e0a418, 0x4, 0x4) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/log.go:51 +0x219 k8s.io/kubernetes/test/e2e/network.assertFilesContain.func1(0x0, 0x0, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:481 +0xa6d k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtection(0xc000e0a628, 0xcb0200, 0x0, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:211 +0x69 k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.pollImmediateInternal(0xc000feec60, 0xc000e0a628, 0xc000feec60, 0xc000e0a628) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:445 +0x2f k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.PollImmediate(0x12a05f200, 0x8bb2c97000, 0xc000e0a628, 0x4a, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:441 +0x4d k8s.io/kubernetes/test/e2e/network.assertFilesContain(0xc000e0a918, 0x2, 0x2, 0x4dccbe5, 0x7, 0xc003032c00, 0x56112e0, 0xc0014ac9a0, 0x1, 0x4decde7, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464 +0x158 k8s.io/kubernetes/test/e2e/network.validateTargetedProbeOutput(0xc000f00420, 0xc003032c00, 0xc000e0a918, 0x2, 0x2, 0x4decde7, 0x10) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:549 +0x365 k8s.io/kubernetes/test/e2e/network.glob..func2.9() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns.go:353 +0x6fa k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc000f342a0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113 +0xa3 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).run(0xc000f342a0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:64 +0x15c k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*ItNode).Run(0xc000f2a3e0, 0x54fc2e0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/it_node.go:26 +0x87 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/spec.(*Spec).runSample(0xc00227f860, 0x0, 0x54fc2e0, 0xc000110900) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/spec/spec.go:215 +0x72f k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/spec.(*Spec).Run(0xc00227f860, 0x54fc2e0, 0xc000110900) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/spec/spec.go:138 +0xf2 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).runSpec(0xc000bcbb80, 0xc00227f860, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:200 +0x111 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).runSpecs(0xc000bcbb80, 0x1) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:170 +0x127 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).Run(0xc000bcbb80, 0xc00311aa60) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:66 +0x117 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/suite.(*Suite).Run(0xc000114280, 0x7f98d84f6c28, 0xc0018abb00, 0x4e003e0, 0x14, 0xc002236090, 0x3, 0x3, 0x55b68a0, 0xc000110900, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/suite/suite.go:62 +0x426 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo.RunSpecsWithCustomReporters(0x5500f20, 0xc0018abb00, 0x4e003e0, 0x14, 0xc0008bd8c0, 0x3, 0x4, 0x4) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:226 +0x238 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo.RunSpecsWithDefaultAndCustomReporters(0x5500f20, 0xc0018abb00, 0x4e003e0, 0x14, 0xc000fb8980, 0x2, 0x2, 0x25) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:214 +0xad k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c k8s.io/kubernetes/test/e2e.TestE2E(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b testing.tRunner(0xc0018abb00, 0x4fc9940) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 �[1mSTEP�[0m: deleting the pod �[1mSTEP�[0m: deleting the test externalName service [AfterEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 Jan 9 14:51:37.568: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready �[1mSTEP�[0m: Destroying namespace "dns-5579" for this suite.
Find dns-5579/dns-test-6bab9f9a-cec1-41e0-89f7-7121f6611c6a mentions in log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sDNS\sshould\sprovide\sDNS\sfor\sExternalName\sservices\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 Jan 9 14:56:41.632: Unable to read jessie_udp@dns-test-service-3.dns-6503.svc.cluster.local from pod dns-6503/dns-test-dd1bd544-9172-45c6-a491-93936736620e: Get "https://172.18.0.3:6443/api/v1/namespaces/dns-6503/pods/dns-test-dd1bd544-9172-45c6-a491-93936736620e/proxy/results/jessie_udp@dns-test-service-3.dns-6503.svc.cluster.local": context deadline exceeded /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:211from junit.kubetest.02.xml
{"msg":"FAILED [sig-network] DNS should provide DNS for ExternalName services [Conformance]","total":-1,"completed":2,"skipped":77,"failed":2,"failures":["[sig-network] DNS should provide DNS for ExternalName services [Conformance]","[sig-network] DNS should provide DNS for ExternalName services [Conformance]"]} [BeforeEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 �[1mSTEP�[0m: Creating a kubernetes client Jan 9 14:51:37.578: INFO: >>> kubeConfig: /tmp/kubeconfig �[1mSTEP�[0m: Building a namespace api object, basename dns �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace [It] should provide DNS for ExternalName services [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 �[1mSTEP�[0m: Creating a test externalName service �[1mSTEP�[0m: Running these commands on wheezy: for i in `seq 1 30`; do dig +short dns-test-service-3.dns-6503.svc.cluster.local CNAME > /results/wheezy_udp@dns-test-service-3.dns-6503.svc.cluster.local; sleep 1; done �[1mSTEP�[0m: Running these commands on jessie: for i in `seq 1 30`; do dig +short dns-test-service-3.dns-6503.svc.cluster.local CNAME > /results/jessie_udp@dns-test-service-3.dns-6503.svc.cluster.local; sleep 1; done �[1mSTEP�[0m: creating a pod to probe DNS �[1mSTEP�[0m: submitting the pod to kubernetes �[1mSTEP�[0m: retrieving the pod �[1mSTEP�[0m: looking for the results for each expected name from probers Jan 9 14:55:14.506: INFO: Unable to read wheezy_udp@dns-test-service-3.dns-6503.svc.cluster.local from pod dns-6503/dns-test-dd1bd544-9172-45c6-a491-93936736620e: an error on the server ("unknown") has prevented the request from succeeding (get pods dns-test-dd1bd544-9172-45c6-a491-93936736620e) Jan 9 14:56:41.632: FAIL: Unable to read jessie_udp@dns-test-service-3.dns-6503.svc.cluster.local from pod dns-6503/dns-test-dd1bd544-9172-45c6-a491-93936736620e: Get "https://172.18.0.3:6443/api/v1/namespaces/dns-6503/pods/dns-test-dd1bd544-9172-45c6-a491-93936736620e/proxy/results/jessie_udp@dns-test-service-3.dns-6503.svc.cluster.local": context deadline exceeded Full Stack Trace k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtection(0xc000e0a628, 0xcb0200, 0x0, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:211 +0x69 k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.pollImmediateInternal(0xc0038d8400, 0xc000e0a628, 0xc0038d8400, 0xc000e0a628) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:445 +0x2f k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.PollImmediate(0x12a05f200, 0x8bb2c97000, 0xc000e0a628, 0x4a, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:441 +0x4d k8s.io/kubernetes/test/e2e/network.assertFilesContain(0xc000e0a918, 0x2, 0x2, 0x4dccbe5, 0x7, 0xc0030d0000, 0x56112e0, 0xc0030ce9a0, 0x1, 0x4decde7, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464 +0x158 k8s.io/kubernetes/test/e2e/network.validateTargetedProbeOutput(0xc000f00420, 0xc0030d0000, 0xc000e0a918, 0x2, 0x2, 0x4decde7, 0x10) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:549 +0x365 k8s.io/kubernetes/test/e2e/network.glob..func2.9() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns.go:353 +0x6fa k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c k8s.io/kubernetes/test/e2e.TestE2E(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b testing.tRunner(0xc0018abb00, 0x4fc9940) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 E0109 14:56:41.633239 15 runtime.go:78] Observed a panic: ginkgowrapper.FailurePanic{Message:"Jan 9 14:56:41.632: Unable to read jessie_udp@dns-test-service-3.dns-6503.svc.cluster.local from pod dns-6503/dns-test-dd1bd544-9172-45c6-a491-93936736620e: Get \"https://172.18.0.3:6443/api/v1/namespaces/dns-6503/pods/dns-test-dd1bd544-9172-45c6-a491-93936736620e/proxy/results/jessie_udp@dns-test-service-3.dns-6503.svc.cluster.local\": context deadline exceeded", Filename:"/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go", Line:211, FullStackTrace:"k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtection(0xc000e0a628, 0xcb0200, 0x0, 0x0)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:211 +0x69\nk8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.pollImmediateInternal(0xc0038d8400, 0xc000e0a628, 0xc0038d8400, 0xc000e0a628)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:445 +0x2f\nk8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.PollImmediate(0x12a05f200, 0x8bb2c97000, 0xc000e0a628, 0x4a, 0x0)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:441 +0x4d\nk8s.io/kubernetes/test/e2e/network.assertFilesContain(0xc000e0a918, 0x2, 0x2, 0x4dccbe5, 0x7, 0xc0030d0000, 0x56112e0, 0xc0030ce9a0, 0x1, 0x4decde7, ...)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464 +0x158\nk8s.io/kubernetes/test/e2e/network.validateTargetedProbeOutput(0xc000f00420, 0xc0030d0000, 0xc000e0a918, 0x2, 0x2, 0x4decde7, 0x10)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:549 +0x365\nk8s.io/kubernetes/test/e2e/network.glob..func2.9()\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns.go:353 +0x6fa\nk8s.io/kubernetes/test/e2e.RunE2ETests(0xc0018abb00)\n\t_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c\nk8s.io/kubernetes/test/e2e.TestE2E(0xc0018abb00)\n\t_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b\ntesting.tRunner(0xc0018abb00, 0x4fc9940)\n\t/usr/local/go/src/testing/testing.go:1123 +0xef\ncreated by testing.(*T).Run\n\t/usr/local/go/src/testing/testing.go:1168 +0x2b3"} ( Your test failed. Ginkgo panics to prevent subsequent assertions from running. Normally Ginkgo rescues this panic so you shouldn't see it. But, if you make an assertion in a goroutine, Ginkgo can't capture the panic. To circumvent this, you should call defer GinkgoRecover() at the top of the goroutine that caused this panic. ) goroutine 133 [running]: k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime.logPanic(0x499f1e0, 0xc00323c240) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:74 +0x95 k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:48 +0x89 panic(0x499f1e0, 0xc00323c240) /usr/local/go/src/runtime/panic.go:969 +0x1b9 k8s.io/kubernetes/test/e2e/framework/ginkgowrapper.Fail.func1(0xc000b96300, 0x16b, 0x77a462c, 0x7d, 0xd3, 0xc002b2c000, 0x771) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/ginkgowrapper/wrapper.go:63 +0xa5 panic(0x41905e0, 0x5431f10) /usr/local/go/src/runtime/panic.go:969 +0x1b9 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo.Fail(0xc000b96300, 0x16b, 0xc000e0a0d0, 0x1, 0x1) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:267 +0xc8 k8s.io/kubernetes/test/e2e/framework/ginkgowrapper.Fail(0xc000b96300, 0x16b, 0xc000e0a1b8, 0x1, 0x1) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/ginkgowrapper/wrapper.go:67 +0x1b5 k8s.io/kubernetes/test/e2e/framework.Failf(0x4e68bfb, 0x24, 0xc000e0a418, 0x4, 0x4) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/log.go:51 +0x219 k8s.io/kubernetes/test/e2e/network.assertFilesContain.func1(0x0, 0x0, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:481 +0xa6d k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtection(0xc000e0a628, 0xcb0200, 0x0, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:211 +0x69 k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.pollImmediateInternal(0xc0038d8400, 0xc000e0a628, 0xc0038d8400, 0xc000e0a628) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:445 +0x2f k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.PollImmediate(0x12a05f200, 0x8bb2c97000, 0xc000e0a628, 0x4a, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:441 +0x4d k8s.io/kubernetes/test/e2e/network.assertFilesContain(0xc000e0a918, 0x2, 0x2, 0x4dccbe5, 0x7, 0xc0030d0000, 0x56112e0, 0xc0030ce9a0, 0x1, 0x4decde7, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464 +0x158 k8s.io/kubernetes/test/e2e/network.validateTargetedProbeOutput(0xc000f00420, 0xc0030d0000, 0xc000e0a918, 0x2, 0x2, 0x4decde7, 0x10) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:549 +0x365 k8s.io/kubernetes/test/e2e/network.glob..func2.9() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns.go:353 +0x6fa k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc000f342a0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113 +0xa3 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).run(0xc000f342a0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:64 +0x15c k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*ItNode).Run(0xc000f2a3e0, 0x54fc2e0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/it_node.go:26 +0x87 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/spec.(*Spec).runSample(0xc00227f860, 0x0, 0x54fc2e0, 0xc000110900) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/spec/spec.go:215 +0x72f k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/spec.(*Spec).Run(0xc00227f860, 0x54fc2e0, 0xc000110900) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/spec/spec.go:138 +0xf2 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).runSpec(0xc000bcbb80, 0xc00227f860, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:200 +0x111 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).runSpecs(0xc000bcbb80, 0x1) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:170 +0x127 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).Run(0xc000bcbb80, 0xc00311aa60) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:66 +0x117 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/suite.(*Suite).Run(0xc000114280, 0x7f98d84f6c28, 0xc0018abb00, 0x4e003e0, 0x14, 0xc002236090, 0x3, 0x3, 0x55b68a0, 0xc000110900, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/suite/suite.go:62 +0x426 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo.RunSpecsWithCustomReporters(0x5500f20, 0xc0018abb00, 0x4e003e0, 0x14, 0xc0008bd8c0, 0x3, 0x4, 0x4) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:226 +0x238 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo.RunSpecsWithDefaultAndCustomReporters(0x5500f20, 0xc0018abb00, 0x4e003e0, 0x14, 0xc000fb8980, 0x2, 0x2, 0x25) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:214 +0xad k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c k8s.io/kubernetes/test/e2e.TestE2E(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b testing.tRunner(0xc0018abb00, 0x4fc9940) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 �[1mSTEP�[0m: deleting the pod �[1mSTEP�[0m: deleting the test externalName service [AfterEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 Jan 9 14:56:41.654: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready �[1mSTEP�[0m: Destroying namespace "dns-6503" for this suite.
Find dns-6503/dns-test-dd1bd544-9172-45c6-a491-93936736620e mentions in log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sDNS\sshould\sprovide\sDNS\sfor\sExternalName\sservices\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 Jan 9 14:46:35.453: Unable to read jessie_udp@dns-test-service-3.dns-5647.svc.cluster.local from pod dns-5647/dns-test-b5b60887-db03-4410-965b-ce25499a5007: Get "https://172.18.0.3:6443/api/v1/namespaces/dns-5647/pods/dns-test-b5b60887-db03-4410-965b-ce25499a5007/proxy/results/jessie_udp@dns-test-service-3.dns-5647.svc.cluster.local": context deadline exceeded /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:211from junit.kubetest.02.xml
[BeforeEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 �[1mSTEP�[0m: Creating a kubernetes client Jan 9 14:41:23.362: INFO: >>> kubeConfig: /tmp/kubeconfig �[1mSTEP�[0m: Building a namespace api object, basename dns �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace [It] should provide DNS for ExternalName services [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 �[1mSTEP�[0m: Creating a test externalName service �[1mSTEP�[0m: Running these commands on wheezy: for i in `seq 1 30`; do dig +short dns-test-service-3.dns-5647.svc.cluster.local CNAME > /results/wheezy_udp@dns-test-service-3.dns-5647.svc.cluster.local; sleep 1; done �[1mSTEP�[0m: Running these commands on jessie: for i in `seq 1 30`; do dig +short dns-test-service-3.dns-5647.svc.cluster.local CNAME > /results/jessie_udp@dns-test-service-3.dns-5647.svc.cluster.local; sleep 1; done �[1mSTEP�[0m: creating a pod to probe DNS �[1mSTEP�[0m: submitting the pod to kubernetes �[1mSTEP�[0m: retrieving the pod �[1mSTEP�[0m: looking for the results for each expected name from probers Jan 9 14:45:08.298: INFO: Unable to read wheezy_udp@dns-test-service-3.dns-5647.svc.cluster.local from pod dns-5647/dns-test-b5b60887-db03-4410-965b-ce25499a5007: an error on the server ("unknown") has prevented the request from succeeding (get pods dns-test-b5b60887-db03-4410-965b-ce25499a5007) Jan 9 14:46:35.453: FAIL: Unable to read jessie_udp@dns-test-service-3.dns-5647.svc.cluster.local from pod dns-5647/dns-test-b5b60887-db03-4410-965b-ce25499a5007: Get "https://172.18.0.3:6443/api/v1/namespaces/dns-5647/pods/dns-test-b5b60887-db03-4410-965b-ce25499a5007/proxy/results/jessie_udp@dns-test-service-3.dns-5647.svc.cluster.local": context deadline exceeded Full Stack Trace k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtection(0xc0013b6628, 0xcb0200, 0x0, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:211 +0x69 k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.pollImmediateInternal(0xc0032305e0, 0xc0013b6628, 0xc0032305e0, 0xc0013b6628) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:445 +0x2f k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.PollImmediate(0x12a05f200, 0x8bb2c97000, 0xc0013b6628, 0x4a, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:441 +0x4d k8s.io/kubernetes/test/e2e/network.assertFilesContain(0xc0013b6918, 0x2, 0x2, 0x4dccbe5, 0x7, 0xc000581400, 0x56112e0, 0xc003bc06e0, 0x1, 0x4decde7, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464 +0x158 k8s.io/kubernetes/test/e2e/network.validateTargetedProbeOutput(0xc000f00420, 0xc000581400, 0xc0013b6918, 0x2, 0x2, 0x4decde7, 0x10) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:549 +0x365 k8s.io/kubernetes/test/e2e/network.glob..func2.9() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns.go:353 +0x6fa k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c k8s.io/kubernetes/test/e2e.TestE2E(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b testing.tRunner(0xc0018abb00, 0x4fc9940) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 E0109 14:46:35.454442 15 runtime.go:78] Observed a panic: ginkgowrapper.FailurePanic{Message:"Jan 9 14:46:35.453: Unable to read jessie_udp@dns-test-service-3.dns-5647.svc.cluster.local from pod dns-5647/dns-test-b5b60887-db03-4410-965b-ce25499a5007: Get \"https://172.18.0.3:6443/api/v1/namespaces/dns-5647/pods/dns-test-b5b60887-db03-4410-965b-ce25499a5007/proxy/results/jessie_udp@dns-test-service-3.dns-5647.svc.cluster.local\": context deadline exceeded", Filename:"/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go", Line:211, FullStackTrace:"k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtection(0xc0013b6628, 0xcb0200, 0x0, 0x0)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:211 +0x69\nk8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.pollImmediateInternal(0xc0032305e0, 0xc0013b6628, 0xc0032305e0, 0xc0013b6628)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:445 +0x2f\nk8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.PollImmediate(0x12a05f200, 0x8bb2c97000, 0xc0013b6628, 0x4a, 0x0)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:441 +0x4d\nk8s.io/kubernetes/test/e2e/network.assertFilesContain(0xc0013b6918, 0x2, 0x2, 0x4dccbe5, 0x7, 0xc000581400, 0x56112e0, 0xc003bc06e0, 0x1, 0x4decde7, ...)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464 +0x158\nk8s.io/kubernetes/test/e2e/network.validateTargetedProbeOutput(0xc000f00420, 0xc000581400, 0xc0013b6918, 0x2, 0x2, 0x4decde7, 0x10)\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:549 +0x365\nk8s.io/kubernetes/test/e2e/network.glob..func2.9()\n\t/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns.go:353 +0x6fa\nk8s.io/kubernetes/test/e2e.RunE2ETests(0xc0018abb00)\n\t_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c\nk8s.io/kubernetes/test/e2e.TestE2E(0xc0018abb00)\n\t_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b\ntesting.tRunner(0xc0018abb00, 0x4fc9940)\n\t/usr/local/go/src/testing/testing.go:1123 +0xef\ncreated by testing.(*T).Run\n\t/usr/local/go/src/testing/testing.go:1168 +0x2b3"} ( Your test failed. Ginkgo panics to prevent subsequent assertions from running. Normally Ginkgo rescues this panic so you shouldn't see it. But, if you make an assertion in a goroutine, Ginkgo can't capture the panic. To circumvent this, you should call defer GinkgoRecover() at the top of the goroutine that caused this panic. ) goroutine 133 [running]: k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime.logPanic(0x499f1e0, 0xc003a8e140) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:74 +0x95 k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:48 +0x89 panic(0x499f1e0, 0xc003a8e140) /usr/local/go/src/runtime/panic.go:969 +0x1b9 k8s.io/kubernetes/test/e2e/framework/ginkgowrapper.Fail.func1(0xc001091500, 0x16b, 0x77a462c, 0x7d, 0xd3, 0xc002b2d000, 0x771) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/ginkgowrapper/wrapper.go:63 +0xa5 panic(0x41905e0, 0x5431f10) /usr/local/go/src/runtime/panic.go:969 +0x1b9 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo.Fail(0xc001091500, 0x16b, 0xc0013b60d0, 0x1, 0x1) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:267 +0xc8 k8s.io/kubernetes/test/e2e/framework/ginkgowrapper.Fail(0xc001091500, 0x16b, 0xc0013b61b8, 0x1, 0x1) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/ginkgowrapper/wrapper.go:67 +0x1b5 k8s.io/kubernetes/test/e2e/framework.Failf(0x4e68bfb, 0x24, 0xc0013b6418, 0x4, 0x4) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/log.go:51 +0x219 k8s.io/kubernetes/test/e2e/network.assertFilesContain.func1(0x0, 0x0, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:481 +0xa6d k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtection(0xc0013b6628, 0xcb0200, 0x0, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:211 +0x69 k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.pollImmediateInternal(0xc0032305e0, 0xc0013b6628, 0xc0032305e0, 0xc0013b6628) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:445 +0x2f k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait.PollImmediate(0x12a05f200, 0x8bb2c97000, 0xc0013b6628, 0x4a, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:441 +0x4d k8s.io/kubernetes/test/e2e/network.assertFilesContain(0xc0013b6918, 0x2, 0x2, 0x4dccbe5, 0x7, 0xc000581400, 0x56112e0, 0xc003bc06e0, 0x1, 0x4decde7, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464 +0x158 k8s.io/kubernetes/test/e2e/network.validateTargetedProbeOutput(0xc000f00420, 0xc000581400, 0xc0013b6918, 0x2, 0x2, 0x4decde7, 0x10) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:549 +0x365 k8s.io/kubernetes/test/e2e/network.glob..func2.9() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns.go:353 +0x6fa k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc000f342a0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113 +0xa3 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).run(0xc000f342a0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:64 +0x15c k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*ItNode).Run(0xc000f2a3e0, 0x54fc2e0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/it_node.go:26 +0x87 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/spec.(*Spec).runSample(0xc00227f860, 0x0, 0x54fc2e0, 0xc000110900) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/spec/spec.go:215 +0x72f k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/spec.(*Spec).Run(0xc00227f860, 0x54fc2e0, 0xc000110900) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/spec/spec.go:138 +0xf2 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).runSpec(0xc000bcbb80, 0xc00227f860, 0x0) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:200 +0x111 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).runSpecs(0xc000bcbb80, 0x1) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:170 +0x127 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).Run(0xc000bcbb80, 0xc00311aa60) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:66 +0x117 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/suite.(*Suite).Run(0xc000114280, 0x7f98d84f6c28, 0xc0018abb00, 0x4e003e0, 0x14, 0xc002236090, 0x3, 0x3, 0x55b68a0, 0xc000110900, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/suite/suite.go:62 +0x426 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo.RunSpecsWithCustomReporters(0x5500f20, 0xc0018abb00, 0x4e003e0, 0x14, 0xc0008bd8c0, 0x3, 0x4, 0x4) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:226 +0x238 k8s.io/kubernetes/vendor/github.com/onsi/ginkgo.RunSpecsWithDefaultAndCustomReporters(0x5500f20, 0xc0018abb00, 0x4e003e0, 0x14, 0xc000fb8980, 0x2, 0x2, 0x25) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:214 +0xad k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c k8s.io/kubernetes/test/e2e.TestE2E(0xc0018abb00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b testing.tRunner(0xc0018abb00, 0x4fc9940) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 �[1mSTEP�[0m: deleting the pod �[1mSTEP�[0m: deleting the test externalName service [AfterEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 Jan 9 14:46:35.472: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready �[1mSTEP�[0m: Destroying namespace "dns-5647" for this suite.
Find dns-5647/dns-test-b5b60887-db03-4410-965b-ce25499a5007 mentions in log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sDNS\sshould\sprovide\sDNS\sfor\sthe\scluster\s\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 Jan 9 15:38:52.625: Unexpected error: <*errors.errorString | 0xc0001fc200>: { 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:464from junit.kubetest.03.xml
[BeforeEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 �[1mSTEP�[0m: Creating a kubernetes client Jan 9 15:28:50.512: INFO: >>> kubeConfig: /tmp/kubeconfig �[1mSTEP�[0m: Building a namespace api object, basename dns �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace [It] should provide DNS for the cluster [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 �[1mSTEP�[0m: Running these commands on wheezy: for i in `seq 1 600`; do check="$$(dig +notcp +noall +answer +search kubernetes.default.svc.cluster.local A)" && test -n "$$check" && echo OK > /results/wheezy_udp@kubernetes.default.svc.cluster.local;check="$$(dig +tcp +noall +answer +search kubernetes.default.svc.cluster.local A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@kubernetes.default.svc.cluster.local;podARec=$$(hostname -i| awk -F. '{print $$1"-"$$2"-"$$3"-"$$4".dns-2019.pod.cluster.local"}');check="$$(dig +notcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/wheezy_udp@PodARecord;check="$$(dig +tcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@PodARecord;sleep 1; done �[1mSTEP�[0m: Running these commands on jessie: for i in `seq 1 600`; do check="$$(dig +notcp +noall +answer +search kubernetes.default.svc.cluster.local A)" && test -n "$$check" && echo OK > /results/jessie_udp@kubernetes.default.svc.cluster.local;check="$$(dig +tcp +noall +answer +search kubernetes.default.svc.cluster.local A)" && test -n "$$check" && echo OK > /results/jessie_tcp@kubernetes.default.svc.cluster.local;podARec=$$(hostname -i| awk -F. '{print $$1"-"$$2"-"$$3"-"$$4".dns-2019.pod.cluster.local"}');check="$$(dig +notcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/jessie_udp@PodARecord;check="$$(dig +tcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/jessie_tcp@PodARecord;sleep 1; done �[1mSTEP�[0m: creating a pod to probe DNS �[1mSTEP�[0m: submitting the pod to kubernetes �[1mSTEP�[0m: retrieving the pod �[1mSTEP�[0m: looking for the results for each expected name from probers Jan 9 15:28:52.563: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:28:52.565: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:28:52.568: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:28:52.574: INFO: Unable to read jessie_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:28:52.578: INFO: Unable to read jessie_udp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:28:52.581: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:28:52.581: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@kubernetes.default.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord] Jan 9 15:28:57.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:28:57.590: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:28:57.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:28:57.598: INFO: Unable to read jessie_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:28:57.600: INFO: Unable to read jessie_udp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:28:57.602: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:28:57.602: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@kubernetes.default.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord] Jan 9 15:29:02.587: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:02.591: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:02.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:02.598: INFO: Unable to read jessie_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:02.600: INFO: Unable to read jessie_udp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:02.603: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:02.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@kubernetes.default.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord] Jan 9 15:29:07.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:07.591: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:07.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:07.599: INFO: Unable to read jessie_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:07.602: INFO: Unable to read jessie_udp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:07.604: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:07.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@kubernetes.default.svc.cluster.local jessie_udp@PodARecord jessie_tcp@PodARecord] Jan 9 15:29:12.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:12.590: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:12.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:12.604: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:12.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord] Jan 9 15:29:17.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:17.592: INFO: Unable to read wheezy_udp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:17.595: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:17.607: INFO: Unable to read jessie_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:17.607: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@PodARecord] Jan 9 15:29:22.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:22.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:22.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:29:27.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:27.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:27.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:29:32.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:32.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:32.606: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:29:37.587: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:37.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:37.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:29:42.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:42.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:42.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:29:47.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:47.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:47.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:29:52.593: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:52.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:52.608: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:29:57.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:57.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:29:57.607: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:30:02.593: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:02.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:02.609: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:30:07.587: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:07.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:07.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:30:12.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:12.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:12.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:30:17.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:17.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:17.606: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:30:22.587: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:22.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:22.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:30:27.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:27.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:27.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:30:32.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:32.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:32.610: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:30:37.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:37.592: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:37.602: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:30:42.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:42.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:42.607: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:30:47.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:47.595: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:47.608: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:30:52.589: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:52.595: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:52.608: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:30:57.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:57.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:30:57.606: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:31:02.589: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:02.596: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:02.608: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:31:07.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:07.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:07.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:31:12.586: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:12.592: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:12.611: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:31:17.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:17.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:17.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:31:22.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:22.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:22.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:31:27.587: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:27.592: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:27.601: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:31:32.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:32.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:32.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:31:37.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:37.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:37.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:31:42.587: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:42.592: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:42.602: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:31:47.589: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:47.595: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:47.607: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:31:52.589: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:52.600: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:52.612: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:31:57.587: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:57.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:31:57.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:32:02.588: INFO: Unable to read wheezy_tcp@kubernetes.default.svc.cluster.local from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:32:02.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:32:02.611: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@kubernetes.default.svc.cluster.local wheezy_tcp@PodARecord] Jan 9 15:32:07.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:32:07.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:32:12.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:32:12.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:32:17.592: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:32:17.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:32:22.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:32:22.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:32:27.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:32:27.606: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:32:32.595: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:32:32.609: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:32:37.592: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:32:37.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:32:42.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:32:42.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:32:47.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:32:47.607: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:32:52.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:32:52.611: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:32:57.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:32:57.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:33:02.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:33:02.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:33:07.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:33:07.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:33:12.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:33:12.618: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:33:17.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:33:17.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:33:22.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:33:22.609: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:33:27.595: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:33:27.607: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:33:32.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:33:32.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:33:37.596: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:33:37.610: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:33:42.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:33:42.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:33:47.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:33:47.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:33:52.596: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:33:52.614: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:33:57.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:33:57.606: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:34:02.596: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:34:02.613: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:34:07.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:34:07.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:34:12.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:34:12.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:34:17.595: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:34:17.606: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:34:22.754: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:34:22.867: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:34:27.709: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:34:27.810: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:34:32.595: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:34:32.607: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:34:37.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:34:37.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:34:42.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:34:42.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:34:47.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:34:47.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:34:52.595: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:34:52.606: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:34:57.592: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:34:57.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:35:02.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:35:02.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:35:07.595: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:35:07.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:35:12.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:35:12.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:35:17.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:35:17.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:35:22.595: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:35:22.607: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:35:27.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:35:27.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:35:32.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:35:32.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:35:37.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:35:37.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:35:42.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:35:42.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:35:47.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:35:47.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:35:52.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:35:52.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:35:57.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:35:57.606: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:36:02.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:36:02.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:36:07.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:36:07.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:36:12.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:36:12.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:36:17.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:36:17.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:36:22.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:36:22.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:36:27.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:36:27.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:36:32.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:36:32.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:36:37.592: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:36:37.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:36:42.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:36:42.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:36:47.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:36:47.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:36:52.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:36:52.606: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:36:57.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:36:57.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:37:02.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:37:02.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:37:07.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:37:07.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:37:12.592: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:37:12.602: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:37:17.595: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:37:17.606: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:37:22.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:37:22.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:37:27.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:37:27.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:37:32.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:37:32.607: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:37:37.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:37:37.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:37:42.592: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:37:42.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:37:47.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:37:47.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:37:52.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:37:52.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:37:57.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:37:57.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:02.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:38:02.623: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:07.596: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:38:07.609: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:12.592: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:38:12.601: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:17.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:38:17.605: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:22.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:38:22.609: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:27.594: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:38:27.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:32.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:38:32.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:37.598: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:38:37.609: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:42.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:38:42.607: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:47.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:38:47.603: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:52.593: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:38:52.604: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:52.615: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b: the server could not find the requested resource (get pods dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b) Jan 9 15:38:52.625: INFO: Lookups using dns-2019/dns-test-8cb451ef-8829-4f6a-acda-2bd6d08d5a2b failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:52.625: FAIL: Unexpected error: <*errors.errorString | 0xc0001fc200>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred Full Stack Trace k8s.io/kubernetes/test/e2e/network.assertFilesContain(0xc002e79180, 0x8, 0x8, 0x4dccbe5, 0x7, 0xc001a34000, 0x56112e0, 0xc0011d3a20, 0x0, 0x0, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464 +0x18a k8s.io/kubernetes/test/e2e/network.assertFilesExist(...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:458 k8s.io/kubernetes/test/e2e/network.validateDNSResults(0xc000e38b00, 0xc001a34000, 0xc002e79180, 0x8, 0x8) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:521 +0x34e k8s.io/kubernetes/test/e2e/network.glob..func2.1() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns.go:63 +0x58a k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0001d3e00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c k8s.io/kubernetes/test/e2e.TestE2E(0xc0001d3e00) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b testing.tRunner(0xc0001d3e00, 0x4fc9940) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 �[1mSTEP�[0m: deleting the pod [AfterEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 Jan 9 15:38:52.637: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready �[1mSTEP�[0m: Destroying namespace "dns-2019" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sDNS\sshould\sresolve\sDNS\sof\spartial\squalified\snames\sfor\sservices\s\[LinuxOnly\]\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 Jan 9 15:38:37.320: Unexpected error: <*errors.errorString | 0xc00027a200>: { 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:464from junit.kubetest.04.xml
{"msg":"FAILED [sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]","total":-1,"completed":99,"skipped":1895,"failed":3,"failures":["[sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]","[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]","[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]"]} [BeforeEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 �[1mSTEP�[0m: Creating a kubernetes client Jan 9 15:28:34.862: INFO: >>> kubeConfig: /tmp/kubeconfig �[1mSTEP�[0m: Building a namespace api object, basename dns �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace [It] should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 �[1mSTEP�[0m: Creating a test headless service �[1mSTEP�[0m: Running these commands on wheezy: for i in `seq 1 600`; do check="$$(dig +notcp +noall +answer +search dns-test-service A)" && test -n "$$check" && echo OK > /results/wheezy_udp@dns-test-service;check="$$(dig +tcp +noall +answer +search dns-test-service A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@dns-test-service;check="$$(dig +notcp +noall +answer +search dns-test-service.dns-9356 A)" && test -n "$$check" && echo OK > /results/wheezy_udp@dns-test-service.dns-9356;check="$$(dig +tcp +noall +answer +search dns-test-service.dns-9356 A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@dns-test-service.dns-9356;check="$$(dig +notcp +noall +answer +search dns-test-service.dns-9356.svc A)" && test -n "$$check" && echo OK > /results/wheezy_udp@dns-test-service.dns-9356.svc;check="$$(dig +tcp +noall +answer +search dns-test-service.dns-9356.svc A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@dns-test-service.dns-9356.svc;check="$$(dig +notcp +noall +answer +search _http._tcp.dns-test-service.dns-9356.svc SRV)" && test -n "$$check" && echo OK > /results/wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc;check="$$(dig +tcp +noall +answer +search _http._tcp.dns-test-service.dns-9356.svc SRV)" && test -n "$$check" && echo OK > /results/wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc;check="$$(dig +notcp +noall +answer +search _http._tcp.test-service-2.dns-9356.svc SRV)" && test -n "$$check" && echo OK > /results/wheezy_udp@_http._tcp.test-service-2.dns-9356.svc;check="$$(dig +tcp +noall +answer +search _http._tcp.test-service-2.dns-9356.svc SRV)" && test -n "$$check" && echo OK > /results/wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc;podARec=$$(hostname -i| awk -F. '{print $$1"-"$$2"-"$$3"-"$$4".dns-9356.pod.cluster.local"}');check="$$(dig +notcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/wheezy_udp@PodARecord;check="$$(dig +tcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@PodARecord;check="$$(dig +notcp +noall +answer +search 166.52.134.10.in-addr.arpa. PTR)" && test -n "$$check" && echo OK > /results/10.134.52.166_udp@PTR;check="$$(dig +tcp +noall +answer +search 166.52.134.10.in-addr.arpa. PTR)" && test -n "$$check" && echo OK > /results/10.134.52.166_tcp@PTR;sleep 1; done �[1mSTEP�[0m: Running these commands on jessie: for i in `seq 1 600`; do check="$$(dig +notcp +noall +answer +search dns-test-service A)" && test -n "$$check" && echo OK > /results/jessie_udp@dns-test-service;check="$$(dig +tcp +noall +answer +search dns-test-service A)" && test -n "$$check" && echo OK > /results/jessie_tcp@dns-test-service;check="$$(dig +notcp +noall +answer +search dns-test-service.dns-9356 A)" && test -n "$$check" && echo OK > /results/jessie_udp@dns-test-service.dns-9356;check="$$(dig +tcp +noall +answer +search dns-test-service.dns-9356 A)" && test -n "$$check" && echo OK > /results/jessie_tcp@dns-test-service.dns-9356;check="$$(dig +notcp +noall +answer +search dns-test-service.dns-9356.svc A)" && test -n "$$check" && echo OK > /results/jessie_udp@dns-test-service.dns-9356.svc;check="$$(dig +tcp +noall +answer +search dns-test-service.dns-9356.svc A)" && test -n "$$check" && echo OK > /results/jessie_tcp@dns-test-service.dns-9356.svc;check="$$(dig +notcp +noall +answer +search _http._tcp.dns-test-service.dns-9356.svc SRV)" && test -n "$$check" && echo OK > /results/jessie_udp@_http._tcp.dns-test-service.dns-9356.svc;check="$$(dig +tcp +noall +answer +search _http._tcp.dns-test-service.dns-9356.svc SRV)" && test -n "$$check" && echo OK > /results/jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc;check="$$(dig +notcp +noall +answer +search _http._tcp.test-service-2.dns-9356.svc SRV)" && test -n "$$check" && echo OK > /results/jessie_udp@_http._tcp.test-service-2.dns-9356.svc;check="$$(dig +tcp +noall +answer +search _http._tcp.test-service-2.dns-9356.svc SRV)" && test -n "$$check" && echo OK > /results/jessie_tcp@_http._tcp.test-service-2.dns-9356.svc;podARec=$$(hostname -i| awk -F. '{print $$1"-"$$2"-"$$3"-"$$4".dns-9356.pod.cluster.local"}');check="$$(dig +notcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/jessie_udp@PodARecord;check="$$(dig +tcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/jessie_tcp@PodARecord;check="$$(dig +notcp +noall +answer +search 166.52.134.10.in-addr.arpa. PTR)" && test -n "$$check" && echo OK > /results/10.134.52.166_udp@PTR;check="$$(dig +tcp +noall +answer +search 166.52.134.10.in-addr.arpa. PTR)" && test -n "$$check" && echo OK > /results/10.134.52.166_tcp@PTR;sleep 1; done �[1mSTEP�[0m: creating a pod to probe DNS �[1mSTEP�[0m: submitting the pod to kubernetes �[1mSTEP�[0m: retrieving the pod �[1mSTEP�[0m: looking for the results for each expected name from probers Jan 9 15:28:36.937: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.940: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.944: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.947: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.950: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.953: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.956: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.959: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.962: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.966: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.969: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.972: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.975: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.978: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.981: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.983: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.986: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.989: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.991: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.994: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.996: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:36.999: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:37.002: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:37.004: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:37.007: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:37.010: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:37.013: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:37.015: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:37.015: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9356 wheezy_tcp@dns-test-service.dns-9356 wheezy_udp@dns-test-service.dns-9356.svc wheezy_tcp@dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_udp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_udp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:28:42.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.022: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.025: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.028: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.031: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.034: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.036: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.042: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.045: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.047: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.050: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.053: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.056: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.059: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.061: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.065: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.067: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.070: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.073: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.076: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.078: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.081: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.084: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.087: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.089: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.092: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.095: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:42.095: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9356 wheezy_tcp@dns-test-service.dns-9356 wheezy_udp@dns-test-service.dns-9356.svc wheezy_tcp@dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_udp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_udp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:28:47.020: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.023: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.026: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.029: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.032: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.034: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.037: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.042: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.045: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.048: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.050: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.053: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.056: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.058: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.060: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.063: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.065: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.071: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.074: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.076: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.079: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.081: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.084: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.086: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.088: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.091: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.094: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:47.094: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9356 wheezy_tcp@dns-test-service.dns-9356 wheezy_udp@dns-test-service.dns-9356.svc wheezy_tcp@dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_udp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_udp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:28:52.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.023: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.025: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.028: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.031: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.034: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.036: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.041: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.043: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.046: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.051: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.053: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.056: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.058: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.060: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.063: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.066: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.069: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.072: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.078: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.080: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.082: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.085: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.087: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.089: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:52.089: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9356 wheezy_tcp@dns-test-service.dns-9356 wheezy_udp@dns-test-service.dns-9356.svc wheezy_tcp@dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_udp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_udp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:28:57.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.022: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.025: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.027: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.030: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.033: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.036: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.041: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.044: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.046: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.051: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.055: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.057: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.059: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.062: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.065: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.067: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.069: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.071: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.074: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.076: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.079: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.081: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.083: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.085: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.087: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:28:57.087: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9356 wheezy_tcp@dns-test-service.dns-9356 wheezy_udp@dns-test-service.dns-9356.svc wheezy_tcp@dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_udp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_udp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:29:02.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.022: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.025: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.028: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.030: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.033: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.035: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.040: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.043: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.045: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.050: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.052: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.055: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.057: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.059: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.062: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.064: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.067: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.070: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.077: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.080: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.082: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.085: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.087: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.089: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:02.089: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9356 wheezy_tcp@dns-test-service.dns-9356 wheezy_udp@dns-test-service.dns-9356.svc wheezy_tcp@dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_udp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_udp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:29:07.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.022: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.027: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.030: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.032: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.035: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.037: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.039: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.041: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.043: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.049: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.051: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.054: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.056: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.059: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.061: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.064: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.066: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.071: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.073: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.075: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.078: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.081: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.083: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.086: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:07.086: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9356 wheezy_udp@dns-test-service.dns-9356.svc wheezy_tcp@dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_udp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:29:12.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.023: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.028: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.030: INFO: Unable to read wheezy_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.033: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.036: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.041: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.044: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.047: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.050: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.053: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.056: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.059: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.061: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.064: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.067: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.071: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.074: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.081: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.083: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.085: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.087: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.090: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.092: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.095: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:12.095: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@dns-test-service.dns-9356 wheezy_udp@dns-test-service.dns-9356.svc wheezy_tcp@dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_udp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:29:17.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.023: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.040: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.042: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.045: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.048: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.050: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.053: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.055: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.059: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.061: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.064: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.066: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.069: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.071: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.076: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.078: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.081: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.083: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.086: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.092: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.094: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:17.094: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_udp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:29:22.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.022: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.040: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.044: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.047: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.050: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.062: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.065: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.069: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.072: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.075: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.078: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.080: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.083: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.086: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.091: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.093: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.095: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.099: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.102: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.104: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.106: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:22.106: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_udp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:29:27.020: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.023: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.041: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.043: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.046: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.049: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.052: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.055: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.058: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.061: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.064: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.067: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.070: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.072: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.075: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.084: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.087: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.090: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.093: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.096: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.099: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.101: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:27.101: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_udp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:29:32.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.023: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.041: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.043: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.045: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.050: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.052: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.054: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.057: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.059: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.061: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.063: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.066: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.072: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.075: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.078: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.081: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.083: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.086: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.095: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:32.095: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_udp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:29:37.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.022: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.041: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.043: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.046: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.051: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.054: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.056: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.059: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.061: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.063: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.066: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.070: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.081: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.084: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.086: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.090: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.093: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:37.093: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:29:42.044: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.049: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.082: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.087: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.091: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.095: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.102: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.107: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.111: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.115: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.120: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.124: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.128: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.130: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.134: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.140: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.146: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.149: INFO: Unable to read jessie_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.151: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.154: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.156: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:42.156: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_udp@_http._tcp.test-service-2.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:29:47.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.022: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.036: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.040: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.043: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.045: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.047: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.049: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.052: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.054: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.058: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.063: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.066: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.070: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.077: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.082: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.086: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.088: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.092: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:47.092: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:29:52.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.022: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.035: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.040: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.042: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.045: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.047: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.050: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.052: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.055: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.057: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.060: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.062: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.065: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.070: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.076: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.081: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.084: INFO: Unable to read 10.134.52.166_udp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.086: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:52.086: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@_http._tcp.test-service-2.dns-9356.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc jessie_tcp@PodARecord 10.134.52.166_udp@PTR 10.134.52.166_tcp@PTR] Jan 9 15:29:57.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.023: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.053: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.056: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.060: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.063: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.065: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.068: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.070: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.079: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.089: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:29:57.089: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc 10.134.52.166_tcp@PTR] Jan 9 15:30:02.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.022: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.041: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.057: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.063: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.065: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.068: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.071: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.076: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.079: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.082: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.088: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.093: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.104: INFO: Unable to read 10.134.52.166_tcp@PTR from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:02.104: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord 10.134.52.166_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc 10.134.52.166_tcp@PTR] Jan 9 15:30:07.020: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:07.023: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:07.044: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:07.054: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:07.061: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:07.064: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:07.067: INFO: Unable to read jessie_udp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:07.069: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:07.072: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:07.074: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:07.079: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:07.084: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:07.094: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:30:12.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:12.023: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:12.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:12.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:12.063: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:12.065: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:12.068: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:12.074: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:12.080: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:12.090: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:30:17.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:17.022: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:17.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:17.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:17.063: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:17.065: INFO: Unable to read jessie_udp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:17.067: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:17.072: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:17.077: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:17.087: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_udp@dns-test-service.dns-9356.svc jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:30:22.019: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:22.022: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:22.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:22.049: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:22.064: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:22.069: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:22.076: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:22.083: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:22.094: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:30:27.049: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:27.066: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:27.087: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:27.092: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:27.100: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:27.104: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:27.114: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:30:32.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:32.052: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:32.071: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:32.080: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:32.085: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:32.090: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:32.100: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:30:37.042: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:37.063: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:37.082: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:37.088: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:37.093: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:37.098: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:37.107: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:30:42.043: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:42.058: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:42.075: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:42.082: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:42.088: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:42.093: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:42.103: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:30:47.040: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:47.051: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:47.067: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:47.072: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:47.077: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:47.082: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:47.092: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:30:52.043: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:52.053: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:52.069: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:52.075: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:52.086: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:52.092: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:52.103: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:30:57.043: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:57.054: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:57.070: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:57.074: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:57.080: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:57.087: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:30:57.100: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:31:02.062: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:02.101: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:02.125: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:02.130: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:02.137: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:02.145: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:02.156: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:31:07.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:07.049: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:07.065: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:07.070: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:07.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:07.080: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:07.090: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:31:12.037: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:12.045: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:12.060: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:12.064: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:12.071: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:12.077: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:12.090: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:31:17.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:17.049: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:17.067: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:17.071: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:17.077: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:17.083: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:17.092: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:31:22.042: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:22.053: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:22.069: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:22.078: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:22.088: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:22.094: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:22.106: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:31:27.041: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:27.052: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:27.067: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:27.072: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:27.078: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:27.083: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:27.093: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:31:32.064: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:32.075: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:32.093: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:32.099: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:32.104: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:32.109: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:32.119: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:31:37.037: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:37.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:37.062: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:37.067: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:37.072: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:37.077: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:37.086: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:31:42.050: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:42.062: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:42.080: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:42.086: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:42.092: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:42.097: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:42.108: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:31:47.045: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:47.058: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:47.076: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356 from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:47.081: INFO: Unable to read jessie_tcp@dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:47.086: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:47.091: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:47.100: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9356 jessie_tcp@dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:31:52.040: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:52.051: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:52.076: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:52.082: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:52.092: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:31:57.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:57.053: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:57.079: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:57.084: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:31:57.094: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:32:02.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:02.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:02.077: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:02.084: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:02.096: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:32:07.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:07.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:07.073: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:07.078: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:07.088: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:32:12.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:12.049: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:12.076: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:12.083: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:12.097: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:32:17.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:17.051: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:17.078: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:17.082: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:17.091: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc jessie_tcp@_http._tcp.test-service-2.dns-9356.svc] Jan 9 15:32:22.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:22.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:22.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:22.092: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:32:27.040: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:27.051: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:27.080: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:27.094: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:32:32.040: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:32.057: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:32.089: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:32.108: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:32:37.049: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:37.065: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:37.101: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:37.119: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:32:42.051: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:42.063: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:42.095: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:42.114: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:32:47.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:47.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:47.074: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:47.092: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:32:52.040: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:52.050: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:52.077: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:52.093: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:32:57.043: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:57.055: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:57.093: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:32:57.110: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:33:02.040: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:02.053: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:02.089: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:02.114: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:33:07.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:07.050: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:07.080: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:07.094: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:33:12.058: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:12.073: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:12.120: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:12.151: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:33:17.040: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:17.051: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:17.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:17.089: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:33:22.041: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:22.053: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:22.081: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:22.099: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:33:27.041: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:27.052: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:27.078: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:27.092: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:33:32.040: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:32.052: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:32.078: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:32.101: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:33:37.041: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:37.052: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:37.081: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:37.097: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:33:42.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:42.052: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:42.083: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:42.103: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:33:47.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:47.052: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:47.079: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:47.094: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:33:52.046: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:52.061: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:52.092: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:52.110: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:33:57.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:57.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:57.076: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:33:57.091: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:34:02.043: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:02.056: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:02.088: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:02.107: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:34:07.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:07.049: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:07.078: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:07.094: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:34:12.041: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:12.051: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:12.077: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:12.095: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:34:17.037: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:17.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:17.078: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:17.095: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:34:22.070: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:22.135: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:22.662: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:22.869: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:34:27.173: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:27.259: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:27.444: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:27.630: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:34:32.040: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:32.051: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:32.078: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:32.098: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:34:37.037: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:37.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:37.073: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:37.088: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:34:42.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:42.050: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:42.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:42.092: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:34:47.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:47.049: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:47.076: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:47.095: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:34:52.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:52.049: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:52.073: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:52.089: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:34:57.039: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:57.051: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:57.103: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:34:57.124: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:35:02.037: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:02.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:02.073: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:02.088: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:35:07.040: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:07.051: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:07.077: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:07.094: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:35:12.038: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:12.050: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:12.074: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:12.089: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:35:17.043: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:17.062: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:17.099: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:17.115: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-9356.svc wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:35:22.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:22.080: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:22.103: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:35:27.050: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:27.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:27.090: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:35:32.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:32.074: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:32.089: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:35:37.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:37.072: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:37.086: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:35:42.050: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:42.086: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:42.103: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:35:47.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:47.072: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:47.086: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:35:52.049: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:52.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:52.091: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:35:57.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:57.072: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:35:57.087: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:36:02.052: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:02.077: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:02.093: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:36:07.049: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:07.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:07.090: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:36:12.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:12.072: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:12.088: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:36:17.049: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:17.074: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:17.089: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:36:22.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:22.073: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:22.087: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:36:27.053: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:27.078: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:27.092: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:36:32.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:32.074: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:32.088: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:36:37.049: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:37.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:37.089: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:36:42.051: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:42.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:42.090: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:36:47.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:47.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:47.090: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:36:52.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:52.072: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:52.088: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:36:57.052: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:57.079: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:36:57.095: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:37:02.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:02.079: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:02.094: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:37:07.046: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:07.072: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:07.087: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:37:12.047: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:12.071: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:12.086: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:37:17.052: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:17.080: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:17.095: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:37:22.046: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:22.071: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:22.084: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:37:27.049: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:27.075: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:27.091: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:37:32.051: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:32.077: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:32.092: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:37:37.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:37.074: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:37.088: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:37:42.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:42.083: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:42.100: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:37:47.050: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:47.088: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:47.106: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:37:52.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:52.072: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:52.088: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:37:57.051: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:57.077: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:37:57.095: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:38:02.053: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:38:02.080: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:38:02.094: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9356.svc] Jan 9 15:38:07.049: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:38:07.087: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:12.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:38:12.089: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:17.046: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:38:17.088: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:22.046: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:38:22.085: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:27.051: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:38:27.092: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:32.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:38:32.087: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:37.048: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:38:37.091: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:37.123: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4: the server could not find the requested resource (get pods dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4) Jan 9 15:38:37.319: INFO: Lookups using dns-9356/dns-test-60458ff8-4271-4582-b5a4-5b8cc4a1abb4 failed for: [wheezy_tcp@PodARecord] Jan 9 15:38:37.320: FAIL: Unexpected error: <*errors.errorString | 0xc00027a200>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred Full Stack Trace k8s.io/kubernetes/test/e2e/network.assertFilesContain(0xc0000dcc80, 0x1c, 0x28, 0x4dccbe5, 0x7, 0xc00058cc00, 0x56112e0, 0xc0018ebe40, 0x0, 0x0, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464 +0x18a k8s.io/kubernetes/test/e2e/network.assertFilesExist(...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:458 k8s.io/kubernetes/test/e2e/network.validateDNSResults(0xc0004d3760, 0xc00058cc00, 0xc0000dcc80, 0x1c, 0x28) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:521 +0x34e k8s.io/kubernetes/test/e2e/network.glob..func2.6() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns.go:236 +0xee5 k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0008d0600) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c k8s.io/kubernetes/test/e2e.TestE2E(0xc0008d0600) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b testing.tRunner(0xc0008d0600, 0x4fc9940) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 �[1mSTEP�[0m: deleting the pod �[1mSTEP�[0m: deleting the test service �[1mSTEP�[0m: deleting the test headless service [AfterEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 Jan 9 15:38:37.482: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready �[1mSTEP�[0m: Destroying namespace "dns-9356" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sDNS\sshould\sresolve\sDNS\sof\spartial\squalified\snames\sfor\sservices\s\[LinuxOnly\]\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 Jan 9 15:28:34.602: Unexpected error: <*errors.errorString | 0xc00027a200>: { 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:464from junit.kubetest.04.xml
{"msg":"FAILED [sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]","total":-1,"completed":99,"skipped":1895,"failed":2,"failures":["[sig-network] Services should be able to switch session affinity for NodePort service [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:174 �[1mSTEP�[0m: Creating a kubernetes client Jan 9 15:18:32.132: INFO: >>> kubeConfig: /tmp/kubeconfig �[1mSTEP�[0m: Building a namespace api object, basename dns �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace [It] should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 �[1mSTEP�[0m: Creating a test headless service �[1mSTEP�[0m: Running these commands on wheezy: for i in `seq 1 600`; do check="$$(dig +notcp +noall +answer +search dns-test-service A)" && test -n "$$check" && echo OK > /results/wheezy_udp@dns-test-service;check="$$(dig +tcp +noall +answer +search dns-test-service A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@dns-test-service;check="$$(dig +notcp +noall +answer +search dns-test-service.dns-1926 A)" && test -n "$$check" && echo OK > /results/wheezy_udp@dns-test-service.dns-1926;check="$$(dig +tcp +noall +answer +search dns-test-service.dns-1926 A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@dns-test-service.dns-1926;check="$$(dig +notcp +noall +answer +search dns-test-service.dns-1926.svc A)" && test -n "$$check" && echo OK > /results/wheezy_udp@dns-test-service.dns-1926.svc;check="$$(dig +tcp +noall +answer +search dns-test-service.dns-1926.svc A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@dns-test-service.dns-1926.svc;check="$$(dig +notcp +noall +answer +search _http._tcp.dns-test-service.dns-1926.svc SRV)" && test -n "$$check" && echo OK > /results/wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc;check="$$(dig +tcp +noall +answer +search _http._tcp.dns-test-service.dns-1926.svc SRV)" && test -n "$$check" && echo OK > /results/wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc;check="$$(dig +notcp +noall +answer +search _http._tcp.test-service-2.dns-1926.svc SRV)" && test -n "$$check" && echo OK > /results/wheezy_udp@_http._tcp.test-service-2.dns-1926.svc;check="$$(dig +tcp +noall +answer +search _http._tcp.test-service-2.dns-1926.svc SRV)" && test -n "$$check" && echo OK > /results/wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc;podARec=$$(hostname -i| awk -F. '{print $$1"-"$$2"-"$$3"-"$$4".dns-1926.pod.cluster.local"}');check="$$(dig +notcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/wheezy_udp@PodARecord;check="$$(dig +tcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@PodARecord;check="$$(dig +notcp +noall +answer +search 147.195.140.10.in-addr.arpa. PTR)" && test -n "$$check" && echo OK > /results/10.140.195.147_udp@PTR;check="$$(dig +tcp +noall +answer +search 147.195.140.10.in-addr.arpa. PTR)" && test -n "$$check" && echo OK > /results/10.140.195.147_tcp@PTR;sleep 1; done �[1mSTEP�[0m: Running these commands on jessie: for i in `seq 1 600`; do check="$$(dig +notcp +noall +answer +search dns-test-service A)" && test -n "$$check" && echo OK > /results/jessie_udp@dns-test-service;check="$$(dig +tcp +noall +answer +search dns-test-service A)" && test -n "$$check" && echo OK > /results/jessie_tcp@dns-test-service;check="$$(dig +notcp +noall +answer +search dns-test-service.dns-1926 A)" && test -n "$$check" && echo OK > /results/jessie_udp@dns-test-service.dns-1926;check="$$(dig +tcp +noall +answer +search dns-test-service.dns-1926 A)" && test -n "$$check" && echo OK > /results/jessie_tcp@dns-test-service.dns-1926;check="$$(dig +notcp +noall +answer +search dns-test-service.dns-1926.svc A)" && test -n "$$check" && echo OK > /results/jessie_udp@dns-test-service.dns-1926.svc;check="$$(dig +tcp +noall +answer +search dns-test-service.dns-1926.svc A)" && test -n "$$check" && echo OK > /results/jessie_tcp@dns-test-service.dns-1926.svc;check="$$(dig +notcp +noall +answer +search _http._tcp.dns-test-service.dns-1926.svc SRV)" && test -n "$$check" && echo OK > /results/jessie_udp@_http._tcp.dns-test-service.dns-1926.svc;check="$$(dig +tcp +noall +answer +search _http._tcp.dns-test-service.dns-1926.svc SRV)" && test -n "$$check" && echo OK > /results/jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc;check="$$(dig +notcp +noall +answer +search _http._tcp.test-service-2.dns-1926.svc SRV)" && test -n "$$check" && echo OK > /results/jessie_udp@_http._tcp.test-service-2.dns-1926.svc;check="$$(dig +tcp +noall +answer +search _http._tcp.test-service-2.dns-1926.svc SRV)" && test -n "$$check" && echo OK > /results/jessie_tcp@_http._tcp.test-service-2.dns-1926.svc;podARec=$$(hostname -i| awk -F. '{print $$1"-"$$2"-"$$3"-"$$4".dns-1926.pod.cluster.local"}');check="$$(dig +notcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/jessie_udp@PodARecord;check="$$(dig +tcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/jessie_tcp@PodARecord;check="$$(dig +notcp +noall +answer +search 147.195.140.10.in-addr.arpa. PTR)" && test -n "$$check" && echo OK > /results/10.140.195.147_udp@PTR;check="$$(dig +tcp +noall +answer +search 147.195.140.10.in-addr.arpa. PTR)" && test -n "$$check" && echo OK > /results/10.140.195.147_tcp@PTR;sleep 1; done �[1mSTEP�[0m: creating a pod to probe DNS �[1mSTEP�[0m: submitting the pod to kubernetes �[1mSTEP�[0m: retrieving the pod �[1mSTEP�[0m: looking for the results for each expected name from probers Jan 9 15:18:34.199: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.203: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.209: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.212: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.216: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.220: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.224: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.227: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.232: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.236: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.241: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.244: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.247: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.251: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.254: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.259: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.264: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.267: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.270: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.274: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.277: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.280: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.283: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.285: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.288: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.291: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.294: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.297: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:34.297: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_udp@dns-test-service.dns-1926.svc wheezy_tcp@dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_udp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:18:39.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.305: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.308: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.311: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.314: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.316: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.319: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.322: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.325: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.328: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.335: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.338: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.340: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.343: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.345: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.347: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.352: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.357: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.360: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.362: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.365: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.367: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.369: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.372: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.374: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.376: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.379: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:39.379: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_udp@dns-test-service.dns-1926.svc wheezy_tcp@dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_udp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:18:44.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.313: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.315: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.318: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.322: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.327: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.332: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.334: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.336: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.339: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.342: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.345: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.347: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.352: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.355: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.357: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.359: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.362: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.364: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.367: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.369: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:44.369: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_udp@dns-test-service.dns-1926.svc wheezy_tcp@dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_udp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:18:49.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.313: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.316: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.319: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.324: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.326: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.328: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.333: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.336: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.338: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.341: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.344: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.349: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.354: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.357: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.359: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.362: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.364: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.367: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.369: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.372: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:49.372: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_udp@dns-test-service.dns-1926.svc wheezy_tcp@dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_udp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:18:54.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.305: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.313: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.315: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.318: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.323: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.328: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.333: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.335: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.337: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.339: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.341: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.343: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.346: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.355: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.358: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.361: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.363: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.366: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.369: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.371: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.374: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:54.374: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_udp@dns-test-service.dns-1926.svc wheezy_tcp@dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_udp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:18:59.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.311: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.314: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.317: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.319: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.322: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.324: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.326: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.329: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.333: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.335: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.339: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.341: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.344: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.347: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.350: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.355: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.358: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.360: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.362: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.365: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.367: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.370: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.372: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:18:59.372: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_udp@dns-test-service.dns-1926.svc wheezy_tcp@dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_udp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:19:04.303: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.309: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.312: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.318: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.326: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.330: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.334: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.338: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.342: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.346: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.350: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.354: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.357: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.361: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.378: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.384: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.388: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.395: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.399: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.403: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.406: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.411: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.414: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.417: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.420: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.422: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.425: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.428: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:04.428: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_udp@dns-test-service.dns-1926.svc wheezy_tcp@dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_udp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:19:09.300: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.303: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.306: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.309: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.312: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.314: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.317: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.323: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.327: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.333: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.342: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.347: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.352: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.355: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.358: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.362: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.365: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.368: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.371: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.374: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.376: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.379: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.381: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.384: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.387: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:09.387: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_udp@dns-test-service.dns-1926.svc wheezy_tcp@dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_udp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:19:14.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.312: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.315: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.317: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.322: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.324: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.327: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.332: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.334: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.337: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.340: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.342: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.345: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.348: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.357: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.360: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.363: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.366: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.369: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.372: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.375: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:14.375: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_udp@dns-test-service.dns-1926.svc wheezy_tcp@dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:19:19.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.313: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.315: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.319: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.326: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.329: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.332: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.335: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.337: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.340: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.343: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.346: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.350: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.355: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.361: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.366: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.369: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.371: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.374: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.376: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.379: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.382: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:19.382: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_udp@dns-test-service.dns-1926.svc wheezy_tcp@dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:19:24.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.313: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.316: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.319: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.324: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.326: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.329: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.332: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.334: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.336: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.339: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.342: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.345: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.347: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.349: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.357: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.359: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.362: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.364: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.367: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.369: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.372: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:24.372: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_udp@dns-test-service.dns-1926.svc wheezy_tcp@dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:19:29.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.308: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.313: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.316: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.318: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.323: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.326: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.329: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.333: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.336: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.338: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.341: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.343: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.349: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.357: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.359: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.362: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.364: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.367: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.369: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.371: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:29.371: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_udp@dns-test-service.dns-1926.svc wheezy_tcp@dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:19:34.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.305: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.310: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.313: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.324: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.327: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.329: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.331: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.334: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.336: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.338: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.340: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.343: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.346: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.354: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.358: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.363: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.365: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.368: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.371: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.375: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.377: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.380: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:34.380: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:19:39.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.309: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.323: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.327: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.331: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.334: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.336: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.339: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.341: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.343: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.346: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.353: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.355: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.358: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.360: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.365: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.368: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.370: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:39.370: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_udp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:19:44.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.311: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.323: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.328: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.333: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.335: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.338: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.341: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.343: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.349: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.356: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.362: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.364: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.367: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.369: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.372: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:44.372: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:19:49.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.323: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.326: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.329: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.334: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.336: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.339: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.342: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.344: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.349: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.356: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.361: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.363: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.366: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.368: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.370: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:49.370: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:19:54.302: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.305: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.309: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.311: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.324: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.327: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.330: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.332: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.334: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.337: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.339: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.342: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.344: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.347: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.352: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.359: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.363: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.366: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.368: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.370: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.373: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:54.373: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:19:59.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.323: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.327: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.331: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.333: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.335: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.338: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.340: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.343: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.345: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.353: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.358: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.360: INFO: Unable to read jessie_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.363: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.365: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.367: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:19:59.367: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_udp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:20:04.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.306: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.309: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.312: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.325: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.331: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.333: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.336: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.338: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.341: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.343: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.349: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.353: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.356: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.361: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.365: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.372: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.380: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.387: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.390: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.393: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:04.393: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:20:09.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.309: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.326: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.329: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.332: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.334: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.337: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.339: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.342: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.345: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.347: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.350: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.358: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.366: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.372: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.374: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.377: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:09.377: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:20:14.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.308: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.311: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.314: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.324: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.330: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.332: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.335: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.337: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.339: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.342: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.344: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.347: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.352: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.359: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.364: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.370: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.372: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.375: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:14.375: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:20:19.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.305: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.308: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.311: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.323: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.328: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.331: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.335: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.338: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.341: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.344: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.346: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.349: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.353: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.356: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.361: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.367: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.372: INFO: Unable to read jessie_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.383: INFO: Unable to read 10.140.195.147_udp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.386: INFO: Unable to read 10.140.195.147_tcp@PTR from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:19.386: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc jessie_tcp@PodARecord 10.140.195.147_udp@PTR 10.140.195.147_tcp@PTR] Jan 9 15:20:24.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.309: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.324: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.326: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.336: INFO: Unable to read jessie_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.339: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.341: INFO: Unable to read jessie_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.343: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.346: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.352: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.357: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:24.367: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:20:29.302: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:29.305: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:29.308: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:29.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:29.329: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:29.336: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:29.339: INFO: Unable to read wheezy_udp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:29.342: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:29.359: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:29.362: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:29.364: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:29.370: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:29.375: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:29.385: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:20:34.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:34.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:34.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:34.309: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:34.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:34.326: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:34.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:34.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:34.348: INFO: Unable to read jessie_udp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:34.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:34.356: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:34.361: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:34.372: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_udp@dns-test-service.dns-1926.svc jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:20:39.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:39.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:39.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:39.312: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:39.323: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:39.328: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:39.333: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:39.347: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:39.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:39.357: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:39.363: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:39.373: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:20:44.302: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:44.305: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:44.308: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:44.311: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:44.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:44.328: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:44.334: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:44.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:44.356: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:44.360: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:44.366: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:44.375: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:20:49.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:49.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:49.306: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:49.309: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:49.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:49.323: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:49.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:49.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:49.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:49.359: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:49.365: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:49.374: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:20:54.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:54.305: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:54.308: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:54.311: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:54.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:54.327: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:54.332: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:54.347: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:54.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:54.357: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:54.362: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:54.372: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:20:59.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:59.305: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:59.308: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:59.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:59.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:59.326: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:59.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:59.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:59.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:59.355: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:59.360: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:20:59.369: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:21:04.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:04.305: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:04.309: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:04.314: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:04.330: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:04.339: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:04.348: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:04.369: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:04.375: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:04.381: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:04.386: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:04.397: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:21:09.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:09.303: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:09.306: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:09.309: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:09.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:09.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:09.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:09.344: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:09.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:09.354: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:09.358: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:09.368: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:21:14.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:14.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:14.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:14.309: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:14.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:14.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:14.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:14.344: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:14.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:14.354: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:14.359: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:14.367: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:21:19.301: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:19.304: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:19.307: INFO: Unable to read wheezy_udp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:19.309: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:19.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:19.324: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:19.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:19.344: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:19.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:19.352: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:19.356: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:19.365: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-1926 wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:21:24.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:24.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:24.326: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:24.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:24.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:24.358: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:24.367: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:24.373: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:24.386: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:21:29.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:29.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:29.324: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:29.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:29.342: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:29.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:29.354: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:29.359: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:29.368: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:21:34.309: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:34.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:34.324: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:34.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:34.342: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:34.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:34.351: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:34.356: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:34.365: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:21:39.311: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:39.322: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:39.328: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:39.333: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:39.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:39.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:39.358: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:39.364: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:39.375: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:21:44.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:44.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:44.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:44.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:44.345: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:44.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:44.354: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:44.359: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:44.369: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:21:49.312: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:49.322: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:49.327: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:49.333: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:49.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:49.356: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:49.362: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:49.368: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:49.379: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:21:54.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:54.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:54.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:54.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:54.344: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:54.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:54.354: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:54.359: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:54.368: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:21:59.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:59.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:59.326: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:59.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:59.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:59.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:59.356: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:59.361: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:21:59.370: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:22:04.309: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:04.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:04.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:04.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:04.345: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:04.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:04.355: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:04.360: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:04.369: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:22:09.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:09.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:09.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:09.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:09.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:09.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:09.356: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:09.361: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:09.371: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:22:14.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:14.324: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:14.329: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:14.335: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:14.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:14.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:14.359: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:14.365: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:14.378: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:22:19.312: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:19.325: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:19.330: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:19.336: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:19.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:19.355: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:19.360: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:19.365: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:19.374: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:22:24.311: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:24.323: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:24.328: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:24.335: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:24.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:24.359: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:24.365: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:24.370: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:24.381: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:22:29.313: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:29.325: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:29.331: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:29.336: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:29.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:29.355: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:29.361: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:29.365: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:29.375: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:22:34.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:34.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:34.323: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:34.328: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:34.342: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:34.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:34.351: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:34.356: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:34.365: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:22:39.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:39.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:39.327: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:39.332: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:39.347: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:39.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:39.357: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:39.362: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:39.372: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:22:44.322: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:44.338: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:44.343: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:44.350: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:44.368: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:44.374: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:44.379: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:44.384: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:44.397: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:22:49.309: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:49.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:49.324: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:49.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:49.343: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:49.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:49.352: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:49.357: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:49.366: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:22:54.311: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:54.322: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:54.327: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:54.332: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:54.347: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:54.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:54.357: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:54.363: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:54.379: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:22:59.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:59.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:59.324: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:59.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:59.342: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:59.347: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:59.351: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:59.356: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:22:59.366: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:23:04.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:04.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:04.327: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:04.335: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:04.360: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:04.367: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:04.375: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:04.383: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:04.397: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:23:09.311: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:09.322: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:09.329: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:09.335: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:09.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:09.359: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:09.366: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:09.372: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:09.383: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:23:14.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:14.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:14.329: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:14.335: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:14.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:14.357: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:14.362: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:14.367: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:14.378: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:23:19.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:19.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:19.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:19.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:19.345: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:19.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:19.354: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:19.359: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:19.369: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:23:24.310: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:24.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:24.326: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:24.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:24.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:24.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:24.356: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:24.361: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:24.374: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:23:29.309: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:29.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:29.324: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:29.328: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:29.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:29.358: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:29.362: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:29.367: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:29.378: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:23:34.314: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:34.324: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:34.329: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:34.334: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:34.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:34.356: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:34.362: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:34.367: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:34.378: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:23:39.315: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:39.325: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:39.329: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:39.333: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:39.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:39.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:39.358: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:39.364: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:39.374: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:23:44.321: INFO: Unable to read wheezy_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:44.335: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:44.346: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:44.353: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:44.374: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:44.380: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:44.387: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:44.395: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:44.419: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@dns-test-service.dns-1926 wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:23:49.336: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:49.343: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:49.350: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:49.370: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:49.375: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:49.382: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:49.388: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:49.397: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:23:54.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:54.323: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:54.327: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:54.342: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:54.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:54.356: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:54.363: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:54.383: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:23:59.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:59.324: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:59.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:59.344: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:59.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:59.354: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:59.358: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:23:59.368: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:24:04.323: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:04.328: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:04.333: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:04.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:04.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:04.358: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:04.362: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:04.373: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:24:09.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:09.325: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:09.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:09.345: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:09.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:09.355: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:09.360: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:09.370: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:24:14.318: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:14.323: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:14.327: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:14.342: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:14.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:14.351: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:14.356: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:14.364: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:24:19.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:19.323: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:19.328: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:19.344: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:19.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:19.354: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:19.358: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:19.368: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:24:24.322: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:24.329: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:24.335: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:24.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:24.358: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:24.363: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:24.368: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:24.382: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:24:29.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:29.328: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:29.333: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:29.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:29.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:29.358: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:29.362: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:29.372: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:24:34.326: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:34.334: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:34.340: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:34.358: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:34.364: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:34.369: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:34.374: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:34.395: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:24:39.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:39.327: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:39.332: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:39.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:39.355: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:39.361: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:39.365: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:39.376: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:24:44.326: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:44.332: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:44.337: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:44.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:44.358: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:44.364: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:44.369: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:44.380: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:24:49.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:49.326: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:49.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:49.344: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:49.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:49.359: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:49.369: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:24:54.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:54.324: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:54.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:54.344: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:54.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:54.360: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:54.370: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@_http._tcp.test-service-2.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:24:59.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:59.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:59.345: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:59.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:59.360: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:24:59.369: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:25:04.318: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:04.328: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:04.343: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:04.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:04.361: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:04.375: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:25:09.324: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:09.334: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:09.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:09.355: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:09.365: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:09.374: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:25:14.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:14.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:14.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:14.359: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:14.376: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:14.388: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:25:19.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:19.332: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:19.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:19.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:19.364: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:19.375: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:25:24.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:24.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:24.343: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:24.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:24.358: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:24.368: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:25:29.327: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:29.341: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:29.358: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:29.364: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:29.374: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:29.385: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:25:34.324: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:34.337: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:34.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:34.359: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:34.372: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:34.384: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:25:39.332: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:39.342: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:39.360: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:39.364: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:39.375: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:39.384: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:25:44.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:44.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:44.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:44.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:44.365: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:44.385: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:25:49.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:49.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:49.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:49.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:49.363: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:49.373: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:25:54.324: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:54.337: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:54.356: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:54.362: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:54.376: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:54.391: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:25:59.322: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:59.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:59.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:59.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:59.366: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:25:59.377: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:26:04.322: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:04.333: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:04.347: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:04.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:04.361: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:04.372: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:26:09.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:09.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:09.347: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:09.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:09.365: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:09.379: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:26:14.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:14.332: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:14.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:14.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:14.362: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:14.372: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:26:19.323: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:19.334: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:19.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:19.355: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:19.366: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:19.379: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:26:24.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:24.328: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:24.345: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:24.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:24.360: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:24.370: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:26:29.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:29.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:29.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:29.353: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:29.363: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:29.377: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:26:34.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:34.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:34.343: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:34.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:34.357: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:34.366: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:26:39.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:39.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:39.347: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:39.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:39.364: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:39.375: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:26:44.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:44.332: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:44.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:44.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:44.360: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:44.371: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:26:49.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:49.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:49.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:49.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:49.366: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:49.377: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:26:54.318: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:54.327: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:54.340: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:54.345: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:54.355: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:54.365: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:26:59.369: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:59.389: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:59.418: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:59.434: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:59.458: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:26:59.478: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:27:04.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:04.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:04.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:04.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:04.361: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:04.371: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:27:09.322: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:09.334: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:09.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:09.355: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:09.364: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:09.374: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:27:14.326: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:14.338: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:14.355: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:14.360: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:14.372: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:14.391: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:27:19.324: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:19.335: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:19.350: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:19.356: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:19.366: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:19.384: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:27:24.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:24.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:24.345: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:24.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:24.363: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:24.373: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:27:29.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:29.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:29.344: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:29.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:29.359: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:29.369: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:27:34.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:34.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:34.344: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:34.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:34.359: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:34.367: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:27:39.333: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:39.346: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:39.363: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:39.369: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:39.381: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:39.392: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:27:44.325: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:44.335: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:44.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:44.357: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:44.367: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:44.377: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:27:49.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:49.332: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:49.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:49.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:49.365: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:49.375: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:27:54.324: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:54.336: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:54.354: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:54.361: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:54.380: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:54.392: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:27:59.321: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:59.331: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:59.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:59.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:59.362: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:27:59.370: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:28:04.327: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:04.340: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:04.364: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:04.370: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:04.383: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:04.395: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:28:09.319: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:09.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:09.345: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:09.351: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:09.361: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:09.375: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:28:14.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:14.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:14.346: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:14.352: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:14.362: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:14.374: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:28:19.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:19.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:19.343: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:19.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:19.358: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:19.368: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:28:24.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:24.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:24.344: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:24.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:24.357: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:24.367: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:28:29.318: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:29.329: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:29.342: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:29.348: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:29.361: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:29.373: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:28:34.320: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:34.330: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:34.345: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:34.349: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:34.358: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:34.368: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:28:34.388: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:34.397: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:34.411: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926 from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:34.416: INFO: Unable to read jessie_tcp@dns-test-service.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:34.427: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-1926.svc from pod dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324: the server could not find the requested resource (get pods dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324) Jan 9 15:28:34.602: INFO: Lookups using dns-1926/dns-test-bd3f9f4d-a758-47a3-b662-d4b5a1c5d324 failed for: [wheezy_tcp@_http._tcp.dns-test-service.dns-1926.svc wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-1926 jessie_tcp@dns-test-service.dns-1926.svc jessie_tcp@_http._tcp.test-service-2.dns-1926.svc] Jan 9 15:28:34.602: FAIL: Unexpected error: <*errors.errorString | 0xc00027a200>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred Full Stack Trace k8s.io/kubernetes/test/e2e/network.assertFilesContain(0xc000d48280, 0x1c, 0x28, 0x4dccbe5, 0x7, 0xc003386c00, 0x56112e0, 0xc001879080, 0x0, 0x0, ...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:464 +0x18a k8s.io/kubernetes/test/e2e/network.assertFilesExist(...) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:458 k8s.io/kubernetes/test/e2e/network.validateDNSResults(0xc0004d3760, 0xc003386c00, 0xc000d48280, 0x1c, 0x28) /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:521 +0x34e k8s.io/kubernetes/test/e2e/network.glob..func2.6() /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns.go:236 +0xee5 k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0008d0600) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:130 +0x36c k8s.io/kubernetes/test/e2e.TestE2E(0xc0008d0600) _output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:144 +0x2b testing.tRunner(0xc0008d0600, 0x4fc9940) /usr/local/go/src/testing/testing.go:1123 +0xef created by testing.(*T).Run /usr/local/go/src/testing/testing.go:1168 +0x2b3 �[1mSTEP�[0m: deleting the pod �[1mSTEP�[0m: deleting the test service �[1mSTEP�[0m: deleting the test headless service [AfterEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:175 Jan 9 15:28:34.764: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready �[1mSTEP�[0m: Destroying namespace "dns-1926" for this suite.
Filter through log files
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sDNS\sshould\sresolve\sDNS\sof\spartial\squalified\snames\sfor\sservices\s\[LinuxOnly\]\s\[Conformance\]$'
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 Jan 9 15:18:31.870: Unexpected error: <*errors.errorString | 0xc00027a200>: { 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:464
[BeforeEach] [sig-network] DNS /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:174 �[1mSTEP�[0m: Creating a kubernetes client Jan 9 15:08:25.424: INFO: >>> kubeConfig: /tmp/kubeconfig �[1mSTEP�[0m: Building a namespace api object, basename dns �[1mSTEP�[0m: Waiting for a default service account to be provisioned in namespace [It] should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance] /workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:629 �[1mSTEP�[0m: Creating a test headless service �[1mSTEP�[0m: Running these commands on wheezy: for i in `seq 1 600`; do check="$$(dig +notcp +noall +answer +search dns-test-service A)" && test -n "$$check" && echo OK > /results/wheezy_udp@dns-test-service;check="$$(dig +tcp +noall +answer +search dns-test-service A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@dns-test-service;check="$$(dig +notcp +noall +answer +search dns-test-service.dns-9109 A)" && test -n "$$check" && echo OK > /results/wheezy_udp@dns-test-service.dns-9109;check="$$(dig +tcp +noall +answer +search dns-test-service.dns-9109 A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@dns-test-service.dns-9109;check="$$(dig +notcp +noall +answer +search dns-test-service.dns-9109.svc A)" && test -n "$$check" && echo OK > /results/wheezy_udp@dns-test-service.dns-9109.svc;check="$$(dig +tcp +noall +answer +search dns-test-service.dns-9109.svc A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@dns-test-service.dns-9109.svc;check="$$(dig +notcp +noall +answer +search _http._tcp.dns-test-service.dns-9109.svc SRV)" && test -n "$$check" && echo OK > /results/wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc;check="$$(dig +tcp +noall +answer +search _http._tcp.dns-test-service.dns-9109.svc SRV)" && test -n "$$check" && echo OK > /results/wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc;check="$$(dig +notcp +noall +answer +search _http._tcp.test-service-2.dns-9109.svc SRV)" && test -n "$$check" && echo OK > /results/wheezy_udp@_http._tcp.test-service-2.dns-9109.svc;check="$$(dig +tcp +noall +answer +search _http._tcp.test-service-2.dns-9109.svc SRV)" && test -n "$$check" && echo OK > /results/wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc;podARec=$$(hostname -i| awk -F. '{print $$1"-"$$2"-"$$3"-"$$4".dns-9109.pod.cluster.local"}');check="$$(dig +notcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/wheezy_udp@PodARecord;check="$$(dig +tcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/wheezy_tcp@PodARecord;check="$$(dig +notcp +noall +answer +search 174.52.135.10.in-addr.arpa. PTR)" && test -n "$$check" && echo OK > /results/10.135.52.174_udp@PTR;check="$$(dig +tcp +noall +answer +search 174.52.135.10.in-addr.arpa. PTR)" && test -n "$$check" && echo OK > /results/10.135.52.174_tcp@PTR;sleep 1; done �[1mSTEP�[0m: Running these commands on jessie: for i in `seq 1 600`; do check="$$(dig +notcp +noall +answer +search dns-test-service A)" && test -n "$$check" && echo OK > /results/jessie_udp@dns-test-service;check="$$(dig +tcp +noall +answer +search dns-test-service A)" && test -n "$$check" && echo OK > /results/jessie_tcp@dns-test-service;check="$$(dig +notcp +noall +answer +search dns-test-service.dns-9109 A)" && test -n "$$check" && echo OK > /results/jessie_udp@dns-test-service.dns-9109;check="$$(dig +tcp +noall +answer +search dns-test-service.dns-9109 A)" && test -n "$$check" && echo OK > /results/jessie_tcp@dns-test-service.dns-9109;check="$$(dig +notcp +noall +answer +search dns-test-service.dns-9109.svc A)" && test -n "$$check" && echo OK > /results/jessie_udp@dns-test-service.dns-9109.svc;check="$$(dig +tcp +noall +answer +search dns-test-service.dns-9109.svc A)" && test -n "$$check" && echo OK > /results/jessie_tcp@dns-test-service.dns-9109.svc;check="$$(dig +notcp +noall +answer +search _http._tcp.dns-test-service.dns-9109.svc SRV)" && test -n "$$check" && echo OK > /results/jessie_udp@_http._tcp.dns-test-service.dns-9109.svc;check="$$(dig +tcp +noall +answer +search _http._tcp.dns-test-service.dns-9109.svc SRV)" && test -n "$$check" && echo OK > /results/jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc;check="$$(dig +notcp +noall +answer +search _http._tcp.test-service-2.dns-9109.svc SRV)" && test -n "$$check" && echo OK > /results/jessie_udp@_http._tcp.test-service-2.dns-9109.svc;check="$$(dig +tcp +noall +answer +search _http._tcp.test-service-2.dns-9109.svc SRV)" && test -n "$$check" && echo OK > /results/jessie_tcp@_http._tcp.test-service-2.dns-9109.svc;podARec=$$(hostname -i| awk -F. '{print $$1"-"$$2"-"$$3"-"$$4".dns-9109.pod.cluster.local"}');check="$$(dig +notcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/jessie_udp@PodARecord;check="$$(dig +tcp +noall +answer +search $${podARec} A)" && test -n "$$check" && echo OK > /results/jessie_tcp@PodARecord;check="$$(dig +notcp +noall +answer +search 174.52.135.10.in-addr.arpa. PTR)" && test -n "$$check" && echo OK > /results/10.135.52.174_udp@PTR;check="$$(dig +tcp +noall +answer +search 174.52.135.10.in-addr.arpa. PTR)" && test -n "$$check" && echo OK > /results/10.135.52.174_tcp@PTR;sleep 1; done �[1mSTEP�[0m: creating a pod to probe DNS �[1mSTEP�[0m: submitting the pod to kubernetes �[1mSTEP�[0m: retrieving the pod �[1mSTEP�[0m: looking for the results for each expected name from probers Jan 9 15:08:31.493: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.496: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.500: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.503: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.505: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.508: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.511: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.513: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.516: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.519: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.521: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.524: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.526: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.529: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.532: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.534: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.536: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.539: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.541: INFO: Unable to read jessie_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.545: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.547: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.549: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.552: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.555: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.557: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.560: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.562: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.565: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:31.565: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_udp@dns-test-service.dns-9109.svc wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_udp@dns-test-service.dns-9109.svc jessie_tcp@dns-test-service.dns-9109.svc jessie_udp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_udp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:08:36.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.580: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.582: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.585: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.587: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.590: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.592: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.595: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.600: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.603: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.606: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.608: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.610: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.613: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.615: INFO: Unable to read jessie_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.618: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.620: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.622: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.624: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.627: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.629: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.631: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.634: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.636: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:36.636: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_udp@dns-test-service.dns-9109.svc wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_udp@dns-test-service.dns-9109.svc jessie_tcp@dns-test-service.dns-9109.svc jessie_udp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_udp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:08:41.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.577: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.579: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.582: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.584: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.587: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.589: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.591: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.593: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.596: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.598: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.600: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.602: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.605: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.607: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.610: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.612: INFO: Unable to read jessie_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.614: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.617: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.620: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.622: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.625: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.627: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.630: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.632: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.635: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:41.635: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_udp@dns-test-service.dns-9109.svc wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_udp@dns-test-service.dns-9109.svc jessie_tcp@dns-test-service.dns-9109.svc jessie_udp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_udp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:08:46.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.573: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.576: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.580: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.583: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.586: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.591: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.594: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.597: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.600: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.603: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.606: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.613: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.616: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.619: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.622: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.625: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.629: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.635: INFO: Unable to read jessie_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.639: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.643: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.648: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.651: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.655: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.658: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.661: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.663: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.666: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:46.666: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_udp@dns-test-service.dns-9109.svc wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_udp@dns-test-service.dns-9109.svc jessie_tcp@dns-test-service.dns-9109.svc jessie_udp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_udp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:08:51.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.571: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.574: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.576: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.579: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.581: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.584: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.586: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.588: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.590: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.593: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.596: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.598: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.601: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.604: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.606: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.609: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.611: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.613: INFO: Unable to read jessie_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.615: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.618: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.620: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.623: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.626: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.628: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.630: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.633: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.635: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:51.635: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_udp@dns-test-service.dns-9109.svc wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_udp@dns-test-service.dns-9109.svc jessie_tcp@dns-test-service.dns-9109.svc jessie_udp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_udp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:08:56.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.581: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.584: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.587: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.589: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.592: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.594: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.596: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.601: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.604: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.606: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.608: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.611: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.613: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.616: INFO: Unable to read jessie_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.618: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.621: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.623: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.626: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.629: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.632: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.634: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.637: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.639: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:08:56.639: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_udp@dns-test-service.dns-9109.svc wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_udp@dns-test-service.dns-9109.svc jessie_tcp@dns-test-service.dns-9109.svc jessie_udp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_udp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:09:01.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.577: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.580: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.582: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.584: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.587: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.589: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.592: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.594: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.596: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.599: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.602: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.604: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.606: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.609: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.611: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.615: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.618: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.620: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.623: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.626: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.628: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.630: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.633: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.635: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:01.635: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_udp@dns-test-service.dns-9109.svc wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_udp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_udp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:09:06.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.581: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.583: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.588: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.591: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.593: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.598: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.602: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.605: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.607: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.609: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.612: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.614: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.616: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.618: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.623: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.625: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.628: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.630: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.632: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.634: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.637: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.639: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.641: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:06.641: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_udp@dns-test-service.dns-9109.svc wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_udp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_udp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:09:11.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.573: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.581: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.584: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.587: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.590: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.592: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.594: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.597: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.602: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.604: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.607: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.610: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.612: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.615: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.620: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.622: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.625: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.627: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.630: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.632: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.634: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.637: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.639: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:11.639: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_udp@dns-test-service.dns-9109.svc wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_udp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_udp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:09:16.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.573: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.576: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.581: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.583: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.590: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.592: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.596: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.599: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.602: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.605: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.608: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.611: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.614: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.616: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.619: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.622: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.626: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.629: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.631: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.634: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.636: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.638: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.641: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.643: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.646: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:16.646: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_udp@dns-test-service.dns-9109.svc wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_udp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_udp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:09:21.568: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.571: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.574: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.577: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.579: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.582: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.584: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.587: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.590: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.594: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.598: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.600: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.602: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.605: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.608: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.611: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.613: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.626: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.635: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.641: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.647: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.653: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.658: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.664: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.679: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:21.679: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_udp@dns-test-service.dns-9109.svc wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_udp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:09:26.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.573: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.576: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.579: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.585: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.587: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.590: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.593: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.595: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.597: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.600: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.602: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.604: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.606: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.609: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.611: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.613: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.619: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.624: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.627: INFO: Unable to read jessie_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.629: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.631: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.634: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.636: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.638: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:26.638: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_udp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:09:31.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.583: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.585: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.588: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.590: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.593: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.595: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.599: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.604: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.606: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.609: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.611: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.614: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.618: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.623: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.628: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.631: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.633: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.635: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.637: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:31.637: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:09:36.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.583: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.586: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.589: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.592: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.594: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.597: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.602: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.604: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.607: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.609: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.611: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.614: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.618: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.623: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.629: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.631: INFO: Unable to read jessie_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.633: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.636: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.638: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:36.638: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_udp@PodARecord jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:09:41.570: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.583: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.586: INFO: Unable to read wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.588: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.590: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.593: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.596: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.598: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.601: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.604: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.606: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.609: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.611: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.613: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.618: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.623: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.629: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.634: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.637: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.639: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:41.639: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.dns-test-service.dns-9109.svc wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:09:46.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.577: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.580: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.589: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.592: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.594: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.596: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.601: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.604: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.606: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.608: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.610: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.613: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.618: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.622: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.627: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.632: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.635: INFO: Unable to read 10.135.52.174_udp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.637: INFO: Unable to read 10.135.52.174_tcp@PTR from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:46.637: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc jessie_tcp@PodARecord 10.135.52.174_udp@PTR 10.135.52.174_tcp@PTR] Jan 9 15:09:51.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.577: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.587: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.589: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.592: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.594: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.596: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.604: INFO: Unable to read jessie_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.607: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.609: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.612: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.621: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.627: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:51.637: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:09:56.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.573: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.578: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.581: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.592: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.594: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.596: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.599: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.601: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.611: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.613: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.615: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.620: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.625: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.630: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:09:56.639: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:10:01.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.576: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.579: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.590: INFO: Unable to read wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.592: INFO: Unable to read wheezy_udp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.595: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.597: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.600: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.611: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.613: INFO: Unable to read jessie_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.616: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.622: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.628: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.634: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:01.644: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@_http._tcp.dns-test-service.dns-9109.svc wheezy_udp@_http._tcp.test-service-2.dns-9109.svc wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_udp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:10:06.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:06.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:06.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:06.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:06.592: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:06.595: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:06.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:06.608: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:06.614: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:06.619: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:06.624: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:06.629: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:06.639: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:10:11.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:11.573: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:11.576: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:11.579: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:11.594: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:11.597: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:11.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:11.611: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:11.616: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:11.622: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:11.627: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:11.632: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:11.643: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:10:16.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:16.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:16.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:16.577: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:16.595: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:16.601: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:16.603: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:16.614: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:16.619: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:16.624: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:16.629: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:16.634: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:16.643: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:10:21.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:21.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:21.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:21.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:21.594: INFO: Unable to read wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:21.596: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:21.598: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:21.608: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:21.613: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:21.618: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:21.623: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:21.628: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:21.637: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@_http._tcp.test-service-2.dns-9109.svc wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:10:26.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:26.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:26.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:26.577: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:26.596: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:26.615: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:26.625: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:26.640: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:26.646: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:26.652: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:26.664: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:10:31.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:31.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:31.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:31.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:31.598: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:31.609: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:31.614: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:31.619: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:31.624: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:31.630: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:31.639: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:10:36.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:36.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:36.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:36.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:36.598: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:36.607: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:36.612: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:36.618: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:36.623: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:36.629: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:36.638: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:10:41.570: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:41.573: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:41.576: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:41.579: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:41.600: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:41.610: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:41.615: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:41.619: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:41.624: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:41.629: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:41.638: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:10:46.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:46.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:46.574: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:46.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:46.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:46.607: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:46.613: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:46.618: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:46.623: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:46.628: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:46.637: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:10:51.571: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:51.575: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:51.578: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:51.581: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:51.604: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:51.614: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:51.619: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:51.624: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:51.628: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:51.633: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:51.643: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:10:56.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:56.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:56.576: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:56.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:56.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:56.612: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:56.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:56.622: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:56.628: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:56.632: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:10:56.643: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:11:01.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:01.572: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:01.575: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:01.578: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:01.598: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:01.608: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:01.612: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:01.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:01.625: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:01.635: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:01.654: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:11:06.569: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:06.573: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:06.576: INFO: Unable to read wheezy_udp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:06.579: INFO: Unable to read wheezy_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:06.600: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:06.617: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:06.624: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:06.630: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:06.635: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:06.640: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:06.650: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.dns-9109 wheezy_tcp@dns-test-service.dns-9109 wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:11:11.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:11.606: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:11.611: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:11.616: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:11.621: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:11.626: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:11.637: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:11:16.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:16.609: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:16.615: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:16.620: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:16.625: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:16.629: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:16.639: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:11:21.600: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:21.615: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:21.619: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:21.624: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:21.630: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:21.634: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:21.645: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:11:26.606: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:26.616: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:26.621: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:26.626: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:26.631: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:26.637: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:26.647: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:11:31.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:31.610: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:31.616: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:31.621: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:31.627: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:31.633: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:31.643: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:11:36.603: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:36.613: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:36.619: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:36.624: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:36.629: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:36.634: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:36.643: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:11:41.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:41.608: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:41.613: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109 from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:41.618: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:41.624: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:41.629: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:41.638: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service jessie_tcp@dns-test-service.dns-9109 jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:11:46.598: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:46.619: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:46.625: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:46.631: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:46.641: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:11:51.608: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:51.630: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:51.634: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:51.639: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:51.649: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:11:56.598: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:56.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:56.622: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:56.627: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:11:56.636: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:12:01.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:01.621: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:01.627: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:01.632: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:01.642: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:12:06.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:06.619: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:06.623: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:06.628: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:06.638: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:12:11.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:11.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:11.623: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:11.628: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:11.641: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:12:16.602: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:16.626: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:16.632: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:16.638: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:16.648: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:12:21.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:21.619: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:21.624: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:21.629: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:21.639: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:12:26.603: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:26.640: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:26.645: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:26.651: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:26.662: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:12:31.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:31.624: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:31.631: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:31.636: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:31.646: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:12:36.607: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:36.630: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:36.635: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:36.641: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:36.654: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:12:41.598: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:41.616: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:41.621: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:41.626: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:41.635: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:12:46.598: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:46.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:46.622: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:46.627: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:46.636: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:12:51.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:51.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:51.622: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:51.626: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:51.638: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:12:56.606: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:56.632: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:56.638: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:56.644: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:12:56.655: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:13:01.602: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:01.627: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:01.633: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:01.639: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:01.650: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:13:06.600: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:06.622: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:06.627: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:06.633: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:06.643: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:13:11.603: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:11.627: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:11.632: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:11.638: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:11.649: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:13:16.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:16.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:16.621: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:16.626: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:16.636: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:13:21.625: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:21.654: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:21.660: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:21.665: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:21.676: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:13:26.605: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:26.625: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:26.630: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:26.635: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:26.645: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:13:31.596: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:31.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:31.622: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:31.626: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:31.635: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:13:36.605: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:36.624: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:36.629: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:36.634: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:36.643: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:13:41.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:41.619: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:41.625: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:41.630: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:41.640: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:13:46.603: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:46.631: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:46.637: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:46.643: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:46.654: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:13:51.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:51.619: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:51.624: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:51.629: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:51.639: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:13:56.602: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:56.621: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:56.627: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:56.632: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:13:56.642: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:14:01.596: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:01.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:01.622: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:01.627: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:01.638: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:14:06.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:06.625: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:06.630: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:06.635: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:06.646: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:14:11.598: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:11.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:11.623: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:11.627: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:11.637: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:14:16.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:16.617: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:16.622: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:16.628: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:16.638: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:14:21.599: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:21.621: INFO: Unable to read jessie_tcp@dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:21.633: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:21.638: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:21.649: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:14:26.600: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:26.627: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:26.633: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:26.644: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:14:31.601: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:31.626: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:31.631: INFO: Unable to read jessie_tcp@_http._tcp.test-service-2.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:31.641: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc jessie_tcp@_http._tcp.test-service-2.dns-9109.svc] Jan 9 15:14:36.597: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:36.620: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the server could not find the requested resource (get pods dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829) Jan 9 15:14:36.646: INFO: Lookups using dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829 failed for: [wheezy_tcp@PodARecord jessie_tcp@_http._tcp.dns-test-service.dns-9109.svc] Jan 9 15:14:41.598: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9109/dns-test-25ac087b-4fd5-42ea-b21a-85e5ce522829: the serve