Bug 1593661

Summary:	with main.rc-manager=file, follow dangling symlink instead of replacing symlink with file
Product:	Red Hat Enterprise Linux 7	Reporter:	Thomas Haller <thaller>
Component:	NetworkManager	Assignee:	Thomas Haller <thaller>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.6	CC:	atragler, bgalvani, fgiudici, fpokryvk, lrintel, rkhan, sukulkar, thaller, vbenes
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-30 11:14:18 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 Thomas Haller 2018-06-21 10:40:47 UTC

Upstream fixed behavior for NetworkManager.conf setting main.rc-manager=file.

See https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=644aa42f68d9d6f30144dba243f95690226a777c


With the rebase of NetworkManager for rhel-7.6 (bug #1592311), this change should be reverted downstream to preserve the previous behavior.

Comment 2 Thomas Haller 2018-06-21 13:22:56 UTC

After discussion, the team agreed that the upstream fix is a bugfix and desired behaviour also suitable for RHEL.

It's unlikely that the user relies on the old behaviour.

- if there is an existing RHEL installation that once had a dangling symlink, rc-manager=file would have already replaced it with a file.

- if there is a buggy script that creates dangling symlinks, with the new behavior NM would follow the symlink and write the file. That seems desired.

- Only if the dangling symlink points to a directory that doesn't exist or is read-only, the new approach would result in a failure to write to resolv.conf. But such a setup is broken, and should be fixed.



Re-purpose this bug, from not reverting to previous behavior, but just documenting the bugfix.

Comment 5 errata-xmlrpc 2018-10-30 11:14:18 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-2018:3207