Bug 1545850

Summary:	rhel-guest-image contains a resolv.conf with an address
Product:	Red Hat Enterprise Linux 7	Reporter:	Alex Schultz <aschultz>
Component:	rhel-guest-image	Assignee:	Nobody <nobody>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.5	CC:	aschultz, fdeutsch, gkadam, jgreguske, lkocman, msufiyan, sukulkar, wshi, yturgema
Target Milestone:	rc
Target Release:	---
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:	2018-10-18 11:18:00 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 Alex Schultz 2018-02-15 17:20:13 UTC

Description of problem:
While investigating BZ1545842 we found that a nameserver of 192.168.122.1 is being shipped in the guest images.  We noticed that with a recent change in to ifup-post[0] in 7.5 the provided nameserver is being kept after we configure the host.  This can lead to weird delays if the provided nameserver is not valid.  This is a different interaction then what was in 7.4.  Either way we probably shouldn't be shipping a resolv.conf with nameservers in the guest image. 


[0] https://github.com/fedora-sysv/initscripts/commit/4da9dbaffba4af74eb632d1a5d10e5c366475516#diff-0d62530925abcdd252ce22c42fdeff8c

Version-Release number of selected component (if applicable):
rhel-guest-image-7.5-106.x86_64.qcow2


How reproducible:


Steps to Reproduce:
1. download rhel-guest-image-7.5-106.x86_64.qcow2
2. inspect existing of /etc/resolv.conf with nameserver 192.168.122.1 defined
3.

Actual results:


Expected results:


Additional info:

Comment 4 Sandro Bonazzola 2018-03-30 13:14:54 UTC

Yuval, can you please check if this affects also rhvm-appliance?

Comment 7 Sandro Bonazzola 2018-03-30 15:04:21 UTC

Alex, 192.168.122.1 is the dns provided by libvirt, used during the image compose. Almost every existing cloud image contains an /etc/resolv.conv with that nameserver, including CentOS images for example.

I would suggest to revert the change in https://github.com/fedora-sysv/initscripts because I think almost everybody relies on the file being written by NetworkManager / ifup when the DHCP replies to network activation.

Moving to networking sst.

Comment 8 Alex Schultz 2018-04-02 16:22:03 UTC

We've updated the openstack image build process to remove these lines in the mean time. I do think we shouldn't be shipping any content in /etc/resolv.conf as it's something that should be specific to the deployed environment. I'd assume this would fall under similar categories as /etc/machine-id or other things that can be cleaned out by running virt-sysprep on the image.  One solution is to revert the initscript change, but I think the correct solution would be to ensure we properly clean images after building them.

Comment 9 sushil kulkarni 2018-04-30 14:56:08 UTC

Removing the sst_networking setting since it affects Bugzilla-Jira mirroring.. Need to move this to the correct group in networking.

-Sushil

Comment 17 Wei Shi 2018-10-18 11:18:00 UTC


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