search

openshift / origin

Conformance test suite for OpenShift
http://www.openshift.org
Apache License 2.0
8.49k stars 4.7k forks source link

Exteded.[k8s.io] DNS should provide DNS for pods for Hostname and Subdomain Annotation #15631

Closed ingvagabund closed 6 years ago

ingvagabund commented 7 years ago

The test is failing when running e2e extended conformance tests over system container based deployment. The Jenkins Job producing the failures at https://ci.openshift.redhat.com/jenkins/job/test_pull_request_openshift_ansible_extended_conformance_install_system_containers/31/consoleFull (the job will get deleted eventually):

[k8s.io] DNS 
  should provide DNS for pods for Hostname and Subdomain Annotation
  /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/dns.go:424

[BeforeEach] [Top Level]
  /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/util/test.go:52
[BeforeEach] [k8s.io] DNS
  /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:130
STEP: Creating a kubernetes client
Aug  3 04:19:36.396: INFO: >>> kubeConfig: /etc/origin/master/admin.kubeconfig
STEP: Building a namespace api object
Aug  3 04:19:36.442: INFO: About to run a Kube e2e test, ensuring namespace is privileged
STEP: Waiting for a default service account to be provisioned in namespace
[It] should provide DNS for pods for Hostname and Subdomain Annotation
  /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/dns.go:424
STEP: Creating a test headless service
STEP: Running these commands on wheezy: for i in `seq 1 600`; do test -n "$$(dig +notcp +noall +answer +search dns-querier-2.dns-test-service-2.e2e-tests-dns-6sxwf.svc.cluster.local A)" && echo OK > /results/wheezy_udp@dns-querier-2.dns-test-service-2.e2e-tests-dns-6sxwf.svc.cluster.local;test -n "$$(dig +tcp +noall +answer +search dns-querier-2.dns-test-service-2.e2e-tests-dns-6sxwf.svc.cluster.local A)" && echo OK > /results/wheezy_tcp@dns-querier-2.dns-test-service-2.e2e-tests-dns-6sxwf.svc.cluster.local;test -n "$$(getent hosts dns-querier-2.dns-test-service-2.e2e-tests-dns-6sxwf.svc.cluster.local)" && echo OK > /results/wheezy_hosts@dns-querier-2.dns-test-service-2.e2e-tests-dns-6sxwf.svc.cluster.local;test -n "$$(getent hosts dns-querier-2)" && echo OK > /results/wheezy_hosts@dns-querier-2;podARec=$$(hostname -i| awk -F. '{print $$1"-"$$2"-"$$3"-"$$4".e2e-tests-dns-6sxwf.pod.cluster.local"}');test -n "$$(dig +notcp +noall +answer +search $${podARec} A)" && echo OK > /results/wheezy_udp@PodARecord;test -n "$$(dig +tcp +noall +answer +search $${podARec} A)" && echo OK > /results/wheezy_tcp@PodARecord;sleep 1; done

STEP: Running these commands on jessie: for i in `seq 1 600`; do test -n "$$(dig +notcp +noall +answer +search dns-querier-2.dns-test-service-2.e2e-tests-dns-6sxwf.svc.cluster.local A)" && echo OK > /results/jessie_udp@dns-querier-2.dns-test-service-2.e2e-tests-dns-6sxwf.svc.cluster.local;test -n "$$(dig +tcp +noall +answer +search dns-querier-2.dns-test-service-2.e2e-tests-dns-6sxwf.svc.cluster.local A)" && echo OK > /results/jessie_tcp@dns-querier-2.dns-test-service-2.e2e-tests-dns-6sxwf.svc.cluster.local;test -n "$$(getent hosts dns-querier-2.dns-test-service-2.e2e-tests-dns-6sxwf.svc.cluster.local)" && echo OK > /results/jessie_hosts@dns-querier-2.dns-test-service-2.e2e-tests-dns-6sxwf.svc.cluster.local;test -n "$$(getent hosts dns-querier-2)" && echo OK > /results/jessie_hosts@dns-querier-2;podARec=$$(hostname -i| awk -F. '{print $$1"-"$$2"-"$$3"-"$$4".e2e-tests-dns-6sxwf.pod.cluster.local"}');test -n "$$(dig +notcp +noall +answer +search $${podARec} A)" && echo OK > /results/jessie_udp@PodARecord;test -n "$$(dig +tcp +noall +answer +search $${podARec} A)" && echo OK > /results/jessie_tcp@PodARecord;sleep 1; done

STEP: creating a pod to probe DNS
STEP: submitting the pod to kubernetes
STEP: retrieving the pod
STEP: looking for the results for each expected name from probers
Aug  3 04:20:12.570: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:20:12.584: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:20:12.584: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:20:22.571: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:20:22.588: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:20:22.588: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:20:32.564: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:20:32.576: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:20:32.576: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:20:42.564: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:20:42.576: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:20:42.576: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:20:52.564: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:20:52.576: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:20:52.576: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:21:02.576: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:21:02.593: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:21:02.593: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:21:12.578: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:21:12.600: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:21:12.600: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:21:22.574: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:21:22.592: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:21:22.592: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:21:32.565: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:21:32.577: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:21:32.577: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:21:42.625: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:21:42.655: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:21:42.655: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:21:52.562: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:21:52.574: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:21:52.574: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:22:02.564: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:22:02.577: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:22:02.577: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:22:12.568: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:22:12.581: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:22:12.581: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:22:22.563: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:22:22.574: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:22:22.574: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:22:32.624: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:22:32.656: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:22:32.656: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:22:42.591: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:22:42.613: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:22:42.613: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:22:52.563: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:22:52.574: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:22:52.574: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:23:02.608: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:23:02.621: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:23:02.621: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:23:12.564: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:23:12.576: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:23:12.576: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:23:22.581: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:23:22.599: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:23:22.599: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:23:32.566: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:23:32.579: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:23:32.579: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:23:42.567: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:23:42.580: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:23:42.580: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:23:52.567: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:23:52.610: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:23:52.610: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:24:02.567: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:24:02.581: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:24:02.581: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:24:12.564: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:24:12.576: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:24:12.576: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:24:22.564: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:24:22.576: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:24:22.576: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:24:32.563: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:24:32.575: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:24:32.575: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:24:42.576: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:24:42.598: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:24:42.598: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:24:52.565: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:24:52.578: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:24:52.578: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:25:02.585: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:25:02.600: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:25:02.600: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:25:12.563: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:25:12.575: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:25:12.575: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:25:22.562: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:25:22.573: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:25:22.573: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:25:32.562: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:25:32.575: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:25:32.575: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:25:42.567: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:25:42.581: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:25:42.581: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:25:52.565: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:25:52.580: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:25:52.580: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:26:02.568: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:26:02.581: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:26:02.581: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:26:12.567: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:26:12.583: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:26:12.583: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:26:22.564: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:26:22.576: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:26:22.576: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:26:32.566: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:26:32.580: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:26:32.580: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:26:42.564: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:26:42.576: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:26:42.576: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:26:52.570: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:26:52.582: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:26:52.582: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:27:02.565: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:27:02.578: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:27:02.578: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:27:12.567: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:27:12.581: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:27:12.581: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:27:22.566: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:27:22.579: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:27:22.579: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:27:32.563: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:27:32.574: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:27:32.574: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:27:42.563: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:27:42.576: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:27:42.576: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:27:52.564: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:27:52.575: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:27:52.575: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:28:02.563: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:28:02.575: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:28:02.575: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:28:12.563: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:28:12.575: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:28:12.575: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:28:22.606: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:28:22.646: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:28:22.646: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:28:32.563: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:28:32.575: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:28:32.575: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:28:42.582: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:28:42.599: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:28:42.599: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:28:52.565: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:28:52.576: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:28:52.576: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:29:02.565: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:29:02.578: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:29:02.578: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:29:12.563: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:29:12.576: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:29:12.576: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:29:22.569: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:29:22.587: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:29:22.587: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:29:32.563: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:29:32.575: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:29:32.575: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:29:42.565: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:29:42.578: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:29:42.578: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:29:52.567: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:29:52.607: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:29:52.607: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:30:02.581: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:30:02.594: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:30:02.594: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:30:02.606: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:30:02.625: INFO: Unable to read jessie_tcp@PodARecord from pod dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: the server could not find the requested resource (get pods dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932)
Aug  3 04:30:02.625: INFO: Lookups using dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 failed for: [wheezy_tcp@PodARecord jessie_tcp@PodARecord]

Aug  3 04:30:02.625: INFO: Unexpected error occurred: timed out waiting for the condition
STEP: deleting the pod
STEP: deleting the test headless service
[AfterEach] [k8s.io] DNS
  /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:131
STEP: Collecting events from namespace "e2e-tests-dns-6sxwf".
STEP: Found 15 events.
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:19:36 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {default-scheduler } Scheduled: Successfully assigned dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932 to ip-172-18-2-135.ec2.internal
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:19:37 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} SuccessfulMountVolume: MountVolume.SetUp succeeded for volume "results" 
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:19:37 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} SuccessfulMountVolume: MountVolume.SetUp succeeded for volume "default-token-nt26x" 
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:19:39 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} Pulling: pulling image "gcr.io/google_containers/test-webserver:e2e"
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:19:41 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} Pulled: Successfully pulled image "gcr.io/google_containers/test-webserver:e2e"
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:19:42 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} Created: Created container
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:19:42 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} Started: Started container
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:19:42 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} Pulling: pulling image "gcr.io/google_containers/dnsutils:e2e"
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:19:45 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} Pulled: Successfully pulled image "gcr.io/google_containers/dnsutils:e2e"
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:19:46 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} Created: Created container
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:19:46 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} Started: Started container
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:19:46 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} Pulling: pulling image "gcr.io/google_containers/jessie-dnsutils:e2e"
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:19:59 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} Pulled: Successfully pulled image "gcr.io/google_containers/jessie-dnsutils:e2e"
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:20:00 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} Created: Created container
Aug  3 04:30:02.668: INFO: At 2017-08-03 04:20:00 -0400 EDT - event for dns-test-7cc04317-7824-11e7-98b3-0e3e3be55932: {kubelet ip-172-18-2-135.ec2.internal} Started: Started container
Aug  3 04:30:02.685: INFO: POD                                            NODE                          PHASE    GRACE  CONDITIONS
Aug  3 04:30:02.686: INFO: docker-registry-1-d3t61                        ip-172-18-2-135.ec2.internal  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:10:06 -0400 EDT  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:17:05 -0400 EDT  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:10:06 -0400 EDT  }]
Aug  3 04:30:02.686: INFO: registry-console-1-52065                       ip-172-18-2-135.ec2.internal  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:10:27 -0400 EDT  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:17:00 -0400 EDT  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:10:27 -0400 EDT  }]
Aug  3 04:30:02.686: INFO: router-1-sc0jx                                 ip-172-18-2-135.ec2.internal  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:09:22 -0400 EDT  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:17:09 -0400 EDT  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:09:22 -0400 EDT  }]
Aug  3 04:30:02.686: INFO: liveness-http                                  ip-172-18-2-135.ec2.internal  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:28:40 -0400 EDT  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:28:43 -0400 EDT  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:28:40 -0400 EDT  }]
Aug  3 04:30:02.686: INFO: dns-test-bef9d643-7825-11e7-9b7c-0e3e3be55932  ip-172-18-2-135.ec2.internal  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:28:37 -0400 EDT  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:28:42 -0400 EDT  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:28:37 -0400 EDT  }]
Aug  3 04:30:02.686: INFO: deployment-simple-1-8h946                      ip-172-18-2-135.ec2.internal  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:29:47 -0400 EDT  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:29:55 -0400 EDT  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:29:47 -0400 EDT  }]
Aug  3 04:30:02.686: INFO: deployment-simple-1-sf8vr                      ip-172-18-2-135.ec2.internal  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:29:47 -0400 EDT  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:29:55 -0400 EDT  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:29:47 -0400 EDT  }]
Aug  3 04:30:02.686: INFO: deployment-simple-2-80724                      ip-172-18-2-135.ec2.internal  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:30:01 -0400 EDT  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:30:01 -0400 EDT ContainersNotReady containers with unready status: [myapp]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:30:01 -0400 EDT  }]
Aug  3 04:30:02.686: INFO: deployment-simple-2-deploy                     ip-172-18-2-135.ec2.internal  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:29:56 -0400 EDT  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:30:00 -0400 EDT  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-08-03 04:29:56 -0400 EDT  }]
Aug  3 04:30:02.686: INFO: 
Aug  3 04:30:02.692: INFO: 
Logging node info for node ip-172-18-2-135.ec2.internal
Aug  3 04:30:02.695: INFO: Node Info: &Node{ObjectMeta:k8s_io_apimachinery_pkg_apis_meta_v1.ObjectMeta{Name:ip-172-18-2-135.ec2.internal,GenerateName:,Namespace:,SelfLink:/api/v1/nodes/ip-172-18-2-135.ec2.internal,UID:c0973c6c-7822-11e7-8b36-0e3e3be55932,ResourceVersion:11592,Generation:0,CreationTimestamp:2017-08-03 04:07:11 -0400 EDT,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{beta.kubernetes.io/arch: amd64,beta.kubernetes.io/os: linux,kubernetes.io/hostname: ip-172-18-2-135.ec2.internal,region: infra,zone: default,},Annotations:map[string]string{volumes.kubernetes.io/controller-managed-attach-detach: true,},OwnerReferences:[],Finalizers:[],ClusterName:,Initializers:nil,},Spec:NodeSpec{PodCIDR:,ExternalID:ip-172-18-2-135.ec2.internal,ProviderID:aws:////i-0762c70264ba973bb,Unschedulable:false,Taints:[],},Status:NodeStatus{Capacity:ResourceList{cpu: {{4 0} {<nil>} 4 DecimalSI},memory: {{16388919296 0} {<nil>} 16004804Ki BinarySI},pods: {{40 0} {<nil>} 40 DecimalSI},},Allocatable:ResourceList{cpu: {{4 0} {<nil>} 4 DecimalSI},memory: {{16284061696 0} {<nil>} 15902404Ki BinarySI},pods: {{40 0} {<nil>} 40 DecimalSI},},Phase:,Conditions:[{OutOfDisk False 2017-08-03 04:30:01 -0400 EDT 2017-08-03 04:07:11 -0400 EDT KubeletHasSufficientDisk kubelet has sufficient disk space available} {MemoryPressure False 2017-08-03 04:30:01 -0400 EDT 2017-08-03 04:07:11 -0400 EDT KubeletHasSufficientMemory kubelet has sufficient memory available} {DiskPressure False 2017-08-03 04:30:01 -0400 EDT 2017-08-03 04:07:11 -0400 EDT KubeletHasNoDiskPressure kubelet has no disk pressure} {Ready True 2017-08-03 04:30:01 -0400 EDT 2017-08-03 04:17:05 -0400 EDT KubeletReady kubelet is posting ready status}],Addresses:[{InternalIP 172.18.2.135} {Hostname ip-172-18-2-135.ec2.internal}],DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:f9370ed252a14f73b014c1301a9b6d1b,SystemUUID:EC2F4FBB-3BAF-A110-30DE-33DED71B4EDD,BootID:8cf24619-f718-4393-9f04-020003d2a5e4,KernelVersion:3.10.0-514.26.2.el7.x86_64,OSImage:CentOS Linux 7 (Core),ContainerRuntimeVersion:docker://1.12.6,KubeletVersion:v1.7.0+695f48a16f,KubeProxyVersion:v1.7.0+695f48a16f,OperatingSystem:linux,Architecture:amd64,},Images:[{[openshift/origin-federation:latest openshift/origin-federation:v3.6.0-rc.0] 1269982240} {[openshift/openvswitch:latest openshift/openvswitch:v3.6.0-rc.0] 1232140489} {[openshift/node:latest openshift/node:v3.6.0-rc.0] 1230458678} {[openshift/origin-docker-registry:latest openshift/origin-docker-registry:v3.6.0-rc.0] 1132989947} {[openshift/origin-gitserver:latest openshift/origin-gitserver:v3.6.0-rc.0] 1119865414} {[openshift/origin-keepalived-ipfailover:latest openshift/origin-keepalived-ipfailover:v3.6.0-rc.0] 1075578822} {[openshift/origin-haproxy-router:latest openshift/origin-haproxy-router:v3.6.0-rc.0] 1069814043} {[openshift/origin-service-catalog:latest openshift/origin-service-catalog:v3.6.0-rc.0] 1062742565} {[openshift/origin-f5-router:latest openshift/origin-f5-router:v3.6.0-rc.0] 1048789100} {[openshift/origin-recycler:latest openshift/origin-recycler:v3.6.0-rc.0] 1048789100} {[openshift/origin-deployer:latest openshift/origin-deployer:v3.6.0-rc.0] 1048789100} {[openshift/origin:latest openshift/origin:v3.6.0-rc.0] 1048789100} {[openshift/origin-sti-builder:latest openshift/origin-sti-builder:v3.6.0-rc.0] 1048789100} {[openshift/origin-docker-builder:latest openshift/origin-docker-builder:v3.6.0-rc.0] 1048789100} {[openshift/origin-cluster-capacity:latest openshift/origin-cluster-capacity:v3.6.0-rc.0] 1002533207} {[docker.io/openshift/origin@sha256:fe7d5b3244f0e7fe83b8742947fa6dc091dd278c248fe1db87a6508a3861f00e docker.io/openshift/origin:v3.6.0-rc.0] 974057765} {[docker.io/openshift/origin-release@sha256:d03fa29a86385176442f712e8f1e85763f930e076657cf285586fadf62249d7a docker.io/openshift/origin-release:golang-1.8] 889401157} {[docker.io/openshift/origin-release@sha256:e7830c1917b24cd07897d69044d0a831d32563daeed2e5ef8260e080e841ba63] 888265752} {[docker.io/openshift/origin-release@sha256:28ba70dba48e007062d84740596478a34db8ba933955cd7fbd2fe4cb631fb8fe docker.io/openshift/origin-release:golang-1.7] 861320249} {[docker.io/openshift/origin-gce@sha256:409e2746c9e376c304ebe64928926f916e8d2b54e9c63630bbb598a9bc9857fb docker.io/openshift/origin-gce:latest] 779683339} {[docker-registry.default.svc:5000/extended-test-build-valuefrom-ps6f9-9sls9/test@sha256:de4b0b829aff3938dba69aa278da49ae08c04645bb12582e664c889218f17871 docker-registry.default.svc:5000/extended-test-build-valuefrom-ps6f9-9sls9/test:latest] 557783534} {[docker.io/centos/php-70-centos7@sha256:6031273626136d92e348ec38b1e6605e9b87cc7f7b7f072939409eb408d217af docker.io/centos/php-70-centos7:latest] 539245846} {[docker-registry.default.svc:5000/extended-test-build-valuefrom-j74nq-g6qtg/test@sha256:e5ef6dc87227dd06631d823925ede3d56671478152f504a9f5577cd532c1388b docker-registry.default.svc:5000/extended-test-build-valuefrom-j74nq-g6qtg/test:latest] 539238390} {[docker.io/centos/ruby-23-centos7@sha256:e8b4f68b4313f41c582a3727c29a3cf762a04cca13f2cdf6bb1bba833be4b90f] 506420289} {[docker.io/centos/ruby-22-centos7@sha256:758c185615fbebe02d7e9bdea9e9e7509af4d95ea964dae3a0d5b180ce6c5410 docker.io/centos/ruby-22-centos7:latest] 491762969} {[docker.io/centos/s2i-base-centos7@sha256:78383cd807c6f700bc0c1310d06acd986d15288c80ffa735eecff346d85d4423 docker.io/centos/s2i-base-centos7:latest] 429895545} {[docker.io/cockpit/kubernetes@sha256:c5f076d8317ff1f9c77352f1b4e128662b9567dbf29941df3093e876b06f5d07 docker.io/cockpit/kubernetes:latest] 407281755} {[openshift/origin-egress-http-proxy:latest openshift/origin-egress-http-proxy:v3.6.0-rc.0] 395971365} {[openshift/origin-egress-router:latest openshift/origin-egress-router:v3.6.0-rc.0] 364719653} {[openshift/origin-base:8ef052d openshift/origin-base:latest] 363043407} {[docker.io/openshift/origin-base@sha256:3848ab52436662e4193f34063bbfd259c0c09cbe91562acec7dd6eb510ca2e94 docker.io/openshift/origin-base:latest] 363024868} {[openshift/origin-pod:latest openshift/origin-pod:v3.6.0-rc.0] 213205928} {[openshift/origin-source:8ef052d openshift/origin-source:latest] 192530021} {[docker.io/centos@sha256:c1010e2fe2b635822d99a096b1f4184becf5d1c98707cbccae00be663a9b9131 docker.io/centos:7 docker.io/centos:centos7] 192529651} {[gcr.io/google_containers/jessie-dnsutils@sha256:2460d596912244b5f8973573f7150e7264b570015f4becc2d0096f0bd1d17e36 gcr.io/google_containers/jessie-dnsutils:e2e] 190122856} {[gcr.io/google_containers/nginx-slim@sha256:8b4501fe0fe221df663c22e16539f399e89594552f400408303c42f3dd8d0e52 gcr.io/google_containers/nginx-slim:0.8] 110461313} {[gcr.io/google_containers/nginx-slim@sha256:dd4efd4c13bec2c6f3fe855deeab9524efe434505568421d4f31820485b3a795 gcr.io/google_containers/nginx-slim:0.7] 86838142} {[gcr.io/google_containers/nettest@sha256:8af3a0e8b8ab906b0648dd575e8785e04c19113531f8ffbaab9e149aa1a60763 gcr.io/google_containers/nettest:1.7] 24051275} {[gcr.io/google_containers/hostexec@sha256:cab8d4e2526f8f767c64febe4ce9e0f0e58cd35fdff81b3aadba4dd041ba9f00 gcr.io/google_containers/hostexec:1.2] 13185747} {[gcr.io/google_containers/dnsutils@sha256:cd9182f6d74e616942db1cef6f25e1e54b49ba0330c2e19d3ec061f027666cc0 gcr.io/google_containers/dnsutils:e2e] 8893907} {[gcr.io/google_containers/netexec@sha256:56c53846f44ea214e4aa5df37c9c50331f0b09e64a32cc7cf17c7e1808d38eef gcr.io/google_containers/netexec:1.7] 8016035} {[gcr.io/google_containers/serve_hostname@sha256:a49737ee84a3b94f0b977f32e60c5daf11f0b5636f1f7503a2981524f351c57a gcr.io/google_containers/serve_hostname:v1.4] 6222101} {[gcr.io/k8s-testimages/redis@sha256:2c3f1112c32a23ad0f14a0a6ff8ac8006e23b5c27de89a4b5287467eb4844dad gcr.io/k8s-testimages/redis:e2e] 5857995} {[openshift/hello-openshift:latest openshift/hello-openshift:v3.6.0-rc.0] 5840109} {[docker.io/openshift/hello-openshift@sha256:a6b8e48ec0d1c06ccd3d3176aac271af0e4ab92139a6658b3af5fcb9c3a2b77c docker.io/openshift/hello-openshift:latest] 5840109} {[gcr.io/google_containers/update-demo@sha256:89ac104fa7c43880d2324f377b79be95b0b2b3fb32e4bd03b8d1e6d91a41f009 gcr.io/google_containers/update-demo:nautilus] 4555533} {[gcr.io/google_containers/test-webserver@sha256:f804e8837490d1dfdb5002e073f715fd0a08115de74e5a4847ca952315739372 gcr.io/google_containers/test-webserver:e2e] 4534272} {[gcr.io/google_containers/liveness@sha256:90994881062c7de7bb1761f2f3d020fe9aa3d332a90e00ebd3ca9dcc1ed74f1c gcr.io/google_containers/liveness:e2e] 4387474} {[docker.io/alpine@sha256:1072e499f3f655a032e88542330cf75b02e7bdf673278f701d7ba61629ee3ebe docker.io/alpine:3.6] 3961627} {[gcr.io/google_containers/eptest@sha256:bb088b26ed78613cce171420168db9a6c62a8dbea17d7be13077e7010bae162f gcr.io/google_containers/eptest:0.1] 2970692}],VolumesInUse:[],VolumesAttached:[],},}
Aug  3 04:30:02.695: INFO: 
Logging kubelet events for node ip-172-18-2-135.ec2.internal
Aug  3 04:30:02.699: INFO: 
Logging pods the kubelet thinks is on node ip-172-18-2-135.ec2.internal
Aug  3 04:30:02.722: INFO: deployment-simple-2-80724 started at 2017-08-03 04:30:01 -0400 EDT (0+1 container statuses recorded)
Aug  3 04:30:02.722: INFO:  Container myapp ready: false, restart count 0
Aug  3 04:30:02.722: INFO: liveness-http started at 2017-08-03 04:28:40 -0400 EDT (0+1 container statuses recorded)
Aug  3 04:30:02.722: INFO:  Container liveness ready: true, restart count 0
Aug  3 04:30:02.722: INFO: deployment-simple-1-8h946 started at 2017-08-03 04:29:47 -0400 EDT (0+1 container statuses recorded)
Aug  3 04:30:02.722: INFO:  Container myapp ready: true, restart count 0
Aug  3 04:30:02.722: INFO: deployment-simple-1-sf8vr started at 2017-08-03 04:29:47 -0400 EDT (0+1 container statuses recorded)
Aug  3 04:30:02.722: INFO:  Container myapp ready: true, restart count 0
Aug  3 04:30:02.722: INFO: deployment-simple-2-deploy started at 2017-08-03 04:29:56 -0400 EDT (0+1 container statuses recorded)
Aug  3 04:30:02.722: INFO:  Container deployment ready: true, restart count 0
Aug  3 04:30:02.722: INFO: registry-console-1-52065 started at 2017-08-03 04:10:27 -0400 EDT (0+1 container statuses recorded)
Aug  3 04:30:02.722: INFO:  Container registry-console ready: true, restart count 0
Aug  3 04:30:02.722: INFO: dns-test-bef9d643-7825-11e7-9b7c-0e3e3be55932 started at 2017-08-03 04:28:37 -0400 EDT (0+3 container statuses recorded)
Aug  3 04:30:02.722: INFO:  Container jessie-querier ready: true, restart count 0
Aug  3 04:30:02.722: INFO:  Container querier ready: true, restart count 0
Aug  3 04:30:02.722: INFO:  Container webserver ready: true, restart count 0
Aug  3 04:30:02.722: INFO: router-1-sc0jx started at 2017-08-03 04:09:22 -0400 EDT (0+1 container statuses recorded)
Aug  3 04:30:02.722: INFO:  Container router ready: true, restart count 0
Aug  3 04:30:02.722: INFO: docker-registry-1-d3t61 started at 2017-08-03 04:10:06 -0400 EDT (0+1 container statuses recorded)
Aug  3 04:30:02.722: INFO:  Container registry ready: true, restart count 0
W0803 04:30:02.724754   18664 metrics_grabber.go:74] Master node is not registered. Grabbing metrics from Scheduler and ControllerManager is disabled.
Aug  3 04:30:02.754: INFO: 
Latency metrics for node ip-172-18-2-135.ec2.internal
Aug  3 04:30:02.754: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:30.143292s}
Aug  3 04:30:02.754: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:26.472003s}
Aug  3 04:30:02.754: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.9 Latency:26.297801s}
Aug  3 04:30:02.754: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.5 Latency:21.849847s}
Aug  3 04:30:02.754: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:12.020623s}
Aug  3 04:30:02.754: INFO: {Operation:create_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:11.822238s}
STEP: Dumping a list of prepulled images on each node...
Aug  3 04:30:02.757: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "e2e-tests-dns-6sxwf" for this suite.
Aug  3 04:30:08.822: INFO: namespace: e2e-tests-dns-6sxwf, resource: bindings, ignored listing per whitelist
Aug  3 04:30:08.891: INFO: namespace e2e-tests-dns-6sxwf deletion completed in 6.129803267s

• Failure [632.495 seconds]
[k8s.io] DNS
/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:619
  should provide DNS for pods for Hostname and Subdomain Annotation [It]
  /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/dns.go:424

  Expected error:
      <*errors.errorString | 0xc420171b40>: {
          s: "timed out waiting for the condition",
      }
      timed out waiting for the condition
  not to have occurred

  /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/dns.go:223
0xmichalis commented 6 years ago

Still an issue: https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/18176/test_pull_request_origin_extended_conformance_gce/14788/

/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/dns.go:448
Expected error:
    <*errors.errorString | 0xc4201b7380>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
not to have occurred
/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/dns.go:230
smarterclayton commented 6 years ago

What known issues exist on 3.6 for informers?

tnozicka commented 6 years ago

@smarterclayton watch cache is broken on 3.6 for sure (breaking informers) but I had to close that PR (https://github.com/openshift/origin/pull/18248) as steve said he won't fix 3.6 CI in origin anymore

openshift-bot commented 6 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 6 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 6 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close