Hide Forgot
Description of problem: The "resolv.conf" is recovered in 'the openshift_node' roles, 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 Actual results: The 'openshift_node' role will recover the 'resolv.conf' file, the dnsmasq will not work on individual nodes after installation Expected results: The dnsmasq should work on all node Additional info: the content of '/etc/resolv.conf' file after configuring dnsmasq # cat /etc/resolv.conf search openstacklocal lab.sjc.redhat.com nameserver 192.168.1.53 # nameserver updated by /etc/NetworkManager/dispatcher.d/99-origin-dns.sh the content of '/etc/resolv.conf' after configuring openshift_node roles # cat /etc/resolv.conf search openstacklocal lab.sjc.redhat.com nameserver 10.11.5.19
Ma, Can you clarify the steps you're taking? Are you re-running the playbooks after the install is completed?
In the install process, I read the the resolve.conf file. I find out that the dns works fine after configuring dnsmasq. the next playbook is configuring the openshift node. When the ansible configure the openshift node, I found that the resolv.conf file is recovered only on the independent node and the dns on the master works fine. so I guess the ansible recover the file when it configuring the openshift node. I did not re-run the playbook.
Ma, Ok, I suspect you have an interface that's coming up and configuring the dns server but isn't the default route's interface. Can you give me the output of `ip addr show` and `nmcli config show` and the contents of all the files in /var/lib/dhclient ?
Can not reproduce it again.