Bug 1624316

Summary:	oc cluster up doesn't work with dnsmasq running locally
Product:	OpenShift Container Platform	Reporter:	Tomáš Nožička <tnozicka>
Component:	Networking	Assignee:	Dan Mace <dmace>
Networking sub component:	router	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	low	CC:	aos-bugs, sponnaga
Version:	3.11.0
Target Milestone:	---
Target Release:	3.11.z
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-26 09:07:51 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 Tomáš Nožička 2018-08-31 08:15:53 UTC

Description of problem:

With oc cluster up, if you are running a dnsmasq locally (e.g. if using VPN to call the VPN's DNS only for queries in its domain) your cat /etc/resolv.conf looks like this

 # Generated by NetworkManager
search redhat.com
nameserver 127.0.0.1
copying this into the kube-dns container running on "different localhost" is pretty much pointless as the dns is not running in there but on the actual host where oc cluster up was run.

As that record is effectively unusable, oc cluster up can do best effort work of replacing it with a public IP, the openshift cluster is configured with. User can specify --public-hostname flag to influence this and give us a hint.

Fix is here: https://github.com/openshift/origin/pull/20688

Comment 1 Sudha Ponnaganti 2019-04-05 14:53:04 UTC

Pl validate in 4.1

Comment 2 Dan Mace 2019-04-05 15:20:21 UTC

No objection to taking a patch for 4.1, but I don't think this is a blocker. I adjusted the priority/severity to low to try and indicate that — if I should have changed just one or the other, please feel free to fix!

Comment 3 Tomáš Nožička 2019-04-08 13:27:35 UTC

there is no `oc cluster up` in 4.1 anymore, this was reported and fixed for 3.11

  https://github.com/openshift/origin/pull/20688/commits/ce1a39d36db8efac6e033620bafffab8ecc4dfed

Comment 5 errata-xmlrpc 2019-06-26 09:07:51 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:1605