Bug 1701057

Summary: resolv.conf isn't properly populated on first boot
Product: OpenShift Container Platform Reporter: Alex Crawford <crawford>
Component: RHCOSAssignee: Ben Howard <behoward>
Status: CLOSED ERRATA QA Contact: Micah Abbott <miabbott>
Severity: medium Docs Contact:
Priority: high    
Version: 4.1.0CC: bbreard, behoward, dustymabe, imcleod, jerzhang, jligon, nstielau, smilner, sponnaga
Target Milestone: ---Flags: smilner: needinfo? (behoward)
Target Release: 4.1.0   
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-06-04 10:47:47 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 Alex Crawford 2019-04-17 21:51:13 UTC 
Description of problem:

When booting an RHCOS instance on Azure, /etc/resolv.conf is populated with information about the build environment. After a reboot, it is properly populated with information derived from Azure DHCP.


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


How reproducible:

Always


Steps to Reproduce:
1. Boot instance on Azure
2. Observe /etc/resolv.conf
3. Reboot the instance
4. Observe /etc/resolv.conf

Actual results:

$ cat /etc/resolv.conf 
# Generated by NetworkManager
search virt.pnr.lab.eng.rdu2.redhat.com
nameserver 10.0.2.3

<reboot>

$ cat /etc/resolv.conf
# Generated by NetworkManager
search p4lbnhjmffruzemjwvnywik2tf.xx.internal.cloudapp.net
nameserver 168.63.129.16


Expected results:

$ cat /etc/resolv.conf
# Generated by NetworkManager
search p4lbnhjmffruzemjwvnywik2tf.xx.internal.cloudapp.net
nameserver 168.63.129.16

<reboot>

$ cat /etc/resolv.conf
# Generated by NetworkManager
search p4lbnhjmffruzemjwvnywik2tf.xx.internal.cloudapp.net
nameserver 168.63.129.16


Additional info:
Comment 7 errata-xmlrpc 2019-06-04 10:47:47 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:0758