openshift-ansible: resolv.conf not updated configured properly
Description
After installing OpenShift Origin 3.6, resolv.conf does not contain the necessary ‘search svc.cluster.local cluster.local’
Version
Ansible version - 2.3.1.0
git describe - openshift-ansible-3.6.173.0.37-1-2-g5929b6c
Steps To Reproduce
- Clean install of RHEL 7.4
- Install Docker and configure storage
- ansible-playbook -i hosts openshift-ansible/playbooks/byo/config.yml
Expected Results
Installing OpenShift places a script (99-origin-dns.sh) in /etc/NetworkManager/dispatcher.d that should update /etc/resolv.conf with the appropriate values whenever the network status changes.
Observed Results
The script mentioned above is in fact created during the installation process. So far as I can tell, it also gets executed any time the network status changes. Something else, however, seems to come along right afterwards and clean out the changes that 99-origin-dns.sh made to resolv.conf, resulting in dns not working for the cluster.
Additional Information
This problem seems to be related to https://github.com/openshift/origin/issues/16097. Based on information in this issue and looking at the code mentioned when the issue was closed, it looks like this issue should be working, but for some reason is not being persisted.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 1
- Comments: 16 (4 by maintainers)
well I noticed the resolv.conf was not being changed properly but you can see 99-origin-dns.sh was being executed in logs, so you know that there is some kind of race going, I didn’t find the time to properly debug NetworkManager but as a quick fix waiting a second is good enough here - it’s just a test environment … 😃
@chris-str-cst /etc/NetworkManager/dispatcher.d/99-origin-dns.sh start of the script, inserted line and comment why I changed it above “cd /etc/sysconfig/network-scripts”