Bug 1705166

Summary:	[3.10] Pod are using the ip from the wrong interface i.e /etc/resolv.conf are getting wrong values
Product:	OpenShift Container Platform	Reporter:	rehan <rekhan>
Component:	Networking	Assignee:	Dan Mace <dmace>
Networking sub component:	DNS	QA Contact:	Hongan Li <hongli>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	aos-bugs, bbennett, dmace, vjaypurk
Version:	3.10.0
Target Milestone:	---
Target Release:	3.11.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-11 01:46:12 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:
Embargoed:

Description rehan 2019-05-01 17:04:45 UTC

Description of problem:
The pods that are using the address from tun0 instead of ens192 in order to configure /etc/resolv.conf .  This results in pods logging no route to host/ unknown host since they are unable to query the local dnsmasq instance.

I checked with ps output 

The --cluster-dns parameter itself is taking the incorrect ip i.e from the tun0 as you can see below, 



Version-Release number of selected component (if applicable):

3.10
How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

The customers pod's /etc/resolv.conf files are being populated with incorrect nameserver IP. This is happening on multiple nodes. 
and some pods are referring to the correct nameserver. 
 
Expected results:
The pod should refer to the correct default nameserver ip. 


Additional info:

Comment 5 Dan Mace 2019-10-11 01:46:12 UTC


*** This bug has been marked as a duplicate of bug 1696394 ***