Hide Forgot
Description of problem: Duplicated nameserver is set in the pod when configuring dnsmasq on node Version-Release number of selected component (if applicable): https://github.com/sdodson/openshift-ansible -b cluster-dns How reproducible: always Steps to Reproduce: 1. install env with dnsmasq on node 2. create registry and check the resolv.conf in the pod #oc exec docker-registry-1-xsagy cat /etc/resolv.conf Actual results: search default.svc.cluster.local svc.cluster.local cluster.local openstacklocal lab.eng.nay.redhat.com nameserver 192.168.0.233 nameserver 192.168.0.233 options ndots:5 Set the duplicated nameserver Expected results: Delete the duplicated nameserver Additional info:
Unless this is observed to cause any problems I'd like to mark this UpcomingRelease. The first should return reasonable responses for all queries so there should be no need to move on to the second one. I'm also moving this to Kubernetes because I believe that when dnsIP is set then pod resolv.conf should contain only that value. I believe this is a diff between openshift and kube behavior and I'm not sure how we should address it.
I'm aware of no adverse conditions created by this. Closing this.