Bug 1325742

Summary:	The "resolv.conf" is recovered in 'the openshift_node' roles
Product:	OpenShift Container Platform	Reporter:	Ma xiaoqiang <xiama>
Component:	Installer	Assignee:	Scott Dodson <sdodson>
Status:	CLOSED WORKSFORME	QA Contact:	Ma xiaoqiang <xiama>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.2.0	CC:	aos-bugs, bleanhar, jokerman, mmccomas, xiama, xtian
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-18 05:01:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ma xiaoqiang 2016-04-11 04:55:44 UTC

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

Comment 1 Scott Dodson 2016-04-11 13:21:25 UTC

Ma,

Can you clarify the steps you're taking? Are you re-running the playbooks after the install is completed?

Comment 2 Ma xiaoqiang 2016-04-18 06:49:16 UTC

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.

Comment 3 Scott Dodson 2016-04-18 12:45:03 UTC

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 ?

Comment 4 Ma xiaoqiang 2016-04-21 04:57:54 UTC

Can not reproduce it again.