kubernetes: [Fail] [sig-network] DNS [It] should provide /etc/hosts entries for the cluster [LinuxOnly]

What happened: following instruction https://github.com/cncf/k8s-conformance/blob/master/instructions.md, with k8s v1.14.3, sonobuoy v0.15.0

Summarizing 1 Failure:

[Fail] [sig-network] DNS [It] should provide /etc/hosts entries for the cluster [LinuxOnly] [Conformance]
/workspace/anago-v1.14.3-beta.0.37+5e53fd6bc17c0d/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:508

Ran 204 of 3585 Specs in 5911.786 seconds
FAIL! -- 203 Passed | 1 Failed | 0 Pending | 3381 Skipped --- FAIL: TestE2E (5911.96s)

and i’ve read related issues #43264, and serveral others, but got little information to solve it. What you expected to happen: the test suite should pass. How to reproduce it (as minimally and precisely as possible): setup an AIO k8s cluster: https://github.com/easzlab/kubeasz/blob/master/docs/setup/quickStart.md do k8s-conformance test: https://github.com/cncf/k8s-conformance/blob/master/instructions.md Anything else we need to know?: Environment: local k8s setup with kvm vm hosts

  • Kubernetes version (use kubectl version): 1.14.3
  • Cloud provider or hardware configuration:
  • OS (e.g: cat /etc/os-release): Ubuntu 1604
  • Kernel (e.g. uname -a): 4.4.0-150
  • Install tools: kubeasz(github.com/easzlab/kubeasz, ansible automation for “Kubernetes The Hard Way” installation)
  • Network plugin and version (if this is a network-related bug): flannel v0.11.0-amd64
  • Others: sonobuoy logs
[sig-network] DNS
  should provide /etc/hosts entries for the cluster [LinuxOnly] [Conformance]
  /workspace/anago-v1.14.3-beta.0.37+5e53fd6bc17c0d/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:692
[BeforeEach] [sig-network] DNS
  /workspace/anago-v1.14.3-beta.0.37+5e53fd6bc17c0d/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:149
STEP: Creating a kubernetes client
Jul 16 04:07:06.986: INFO: >>> kubeConfig: /tmp/kubeconfig-103299968
STEP: Building a namespace api object, basename dns
STEP: Waiting for a default service account to be provisioned in namespace
[It] should provide /etc/hosts entries for the cluster [LinuxOnly] [Conformance]
  /workspace/anago-v1.14.3-beta.0.37+5e53fd6bc17c0d/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:692
STEP: Running these commands on wheezy: for i in `seq 1 600`; do test -n "$$(getent hosts dns-querier-1.dns-test-service.dns-5363.svc.cluster.local)" && echo OK > /results/wheezy_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local;test -n "$$(getent hosts dns-querier-1)" && echo OK > /results/wheezy_hosts@dns-querier-1;podARec=$$(hostname -i| awk -F. '{print $$1"-"$$2"-"$$3"-"$$4".dns-5363.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

STEP: Running these commands on jessie: for i in `seq 1 600`; do test -n "$$(getent hosts dns-querier-1.dns-test-service.dns-5363.svc.cluster.local)" && echo OK > /results/jessie_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local;test -n "$$(getent hosts dns-querier-1)" && echo OK > /results/jessie_hosts@dns-querier-1;podARec=$$(hostname -i| awk -F. '{print $$1"-"$$2"-"$$3"-"$$4".dns-5363.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

STEP: creating a pod to probe /etc/hosts
STEP: submitting the pod to kubernetes
STEP: retrieving the pod
STEP: looking for the results for each expected name from probers
Jul 16 04:07:09.080: INFO: Unable to read wheezy_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local from pod dns-5363/dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4: the server could not find the requested resource (get pods dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4)
Jul 16 04:07:09.093: INFO: Unable to read jessie_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local from pod dns-5363/dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4: the server could not find the requested resource (get pods dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4)
Jul 16 04:07:09.100: INFO: Lookups using dns-5363/dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4 failed for: [wheezy_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local jessie_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local]

Jul 16 04:07:14.104: INFO: Unable to read wheezy_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local from pod dns-5363/dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4: the server could not find the requested resource (get pods dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4)
Jul 16 04:07:14.112: INFO: Unable to read jessie_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local from pod dns-5363/dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4: the server could not find the requested resource (get pods dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4)
Jul 16 04:07:14.119: INFO: Lookups using dns-5363/dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4 failed for: [wheezy_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local jessie_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local]

Jul 16 04:07:19.104: INFO: Unable to read wheezy_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local from pod dns-5363/dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4: the server could not find the requested resource (get pods dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4)
Jul 16 04:07:19.112: INFO: Unable to read jessie_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local from pod dns-5363/dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4: the server could not find the requested resource (get pods dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4)
Jul 16 04:07:19.120: INFO: Lookups using dns-5363/dns-test-2d15a929-a77f-11e9-9ae9-da7161b169e4 failed for: [wheezy_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local jessie_hosts@dns-querier-1.dns-test-service.dns-5363.svc.cluster.local]

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 23 (11 by maintainers)

Most upvoted comments

I have the same issue on k8s 1.16.2 deployed with kubeadm. I’m trying to run the test suite and I get

STEP: looking for the results for each expected name from probers                                                                                                                                                                        
Oct 30 13:50:11.717: INFO: Unable to read wheezy_hosts@dns-querier-1.dns-test-service.dns-9783.svc.cluster.local from pod dns-9783/dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7: the server is currently unable to handle the request (g
et pods dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7)                                                                                                                                                                                   
                                                                                                                                                                                                                                         
Oct 30 13:50:41.729: INFO: Unable to read wheezy_hosts@dns-querier-1 from pod dns-9783/dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7: the server is currently unable to handle the request (get pods dns-test-1391a3bb-d1ed-4b82-95eb-b30
e3efe6da7)                                                                                                                                                                                                                               
Oct 30 13:51:11.734: INFO: Unable to read wheezy_udp@PodARecord from pod dns-9783/dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7: the server is currently unable to handle the request (get pods dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe
6da7)                                                 
Oct 30 13:51:41.740: INFO: Unable to read wheezy_tcp@PodARecord from pod dns-9783/dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7: the server is currently unable to handle the request (get pods dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe
6da7)     
Oct 30 13:52:11.753: INFO: Unable to read jessie_hosts@dns-querier-1.dns-test-service.dns-9783.svc.cluster.local from pod dns-9783/dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7: the server is currently unable to handle the request (g
et pods dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7)
Oct 30 13:52:41.759: INFO: Unable to read jessie_hosts@dns-querier-1 from pod dns-9783/dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7: the server is currently unable to handle the request (get pods dns-test-1391a3bb-d1ed-4b82-95eb-b30
e3efe6da7)
Oct 30 13:53:11.764: INFO: Unable to read jessie_udp@PodARecord from pod dns-9783/dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7: the server is currently unable to handle the request (get pods dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe
6da7)                                                 
Oct 30 13:53:41.782: INFO: Unable to read jessie_tcp@PodARecord from pod dns-9783/dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7: the server is currently unable to handle the request (get pods dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe
6da7)     
Oct 30 13:53:41.783: INFO: Lookups using dns-9783/dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7 failed for: [wheezy_hosts@dns-querier-1.dns-test-service.dns-9783.svc.cluster.local wheezy_hosts@dns-querier-1 wheezy_udp@PodARecord whee
zy_tcp@PodARecord jessie_hosts@dns-querier-1.dns-test-service.dns-9783.svc.cluster.local jessie_hosts@dns-querier-1 jessie_udp@PodARecord jessie_tcp@PodARecord]
                                                                                                                                                                                                                                         
Oct 30 13:54:16.788: INFO: Unable to read wheezy_hosts@dns-querier-1.dns-test-service.dns-9783.svc.cluster.local from pod dns-9783/dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7: the server is currently unable to handle the request (g
et pods dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7)                                                                                                                                                                                   
Oct 30 13:54:46.794: INFO: Unable to read wheezy_hosts@dns-querier-1 from pod dns-9783/dns-test-1391a3bb-d1ed-4b82-95eb-b30e3efe6da7: the server is currently unable to handle the request (get pods dns-test-1391a3bb-d1ed-4b82-95eb-b30
e3efe6da7)

When I exec the command manually in the container all the files are here and are OK