RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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.

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