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:
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days