Bug 1841581

Summary:	Changes to prepender result in no resolv.conf
Product:	OpenShift Container Platform	Reporter:	Stephen Benjamin <stbenjam>
Component:	Installer	Assignee:	Beth White <beth.white>
Installer sub component:	OpenShift on Bare Metal IPI	QA Contact:	Victor Voronkov <vvoronko>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	urgent	CC:	augol, vvoronko
Version:	4.5	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.5.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:	2020-07-13 17:42:41 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 Stephen Benjamin 2020-05-29 13:52:14 UTC

In BZ1841260 we refactored the NetworkManager prepender to be atomic, but also enabled `set -e`. 

We used to get a resolv.conf because the podman command in the  prepender failed and fell through to the cp of /var/run/NetworkManager/resolv.conf. This no longer happens as podman results in the script bailing, and now we never get a resolv.conf.

Comment 4 errata-xmlrpc 2020-07-13 17:42:41 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-2020:2409