Bug 1423490 - [dns] change behavior for rc-manager=symlink to keep /etc/resolv.conf as regular file instead of symlink
Summary: [dns] change behavior for rc-manager=symlink to keep /etc/resolv.conf as regu...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Desktop QE
Depends On: 1367551
TreeView+ depends on / blocked
Reported: 2017-02-17 12:42 UTC by Thomas Haller
Modified: 2017-08-01 09:24 UTC (History)
15 users (show)

Fixed In Version: NetworkManager-1.8.0-0.2.git20170215.1d40c5f4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1367551
Last Closed: 2017-08-01 09:24:38 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2299 normal SHIPPED_LIVE Moderate: NetworkManager and libnl3 security, bug fix and enhancement update 2017-08-01 12:40:28 UTC

Description Thomas Haller 2017-02-17 12:42:40 UTC
+++ This bug was initially created as a clone of Bug #1367551 +++

For bug 1367551, we changed behavior for rc-manager=symlink setting upstream: 

This change will also go to rhel-7.4.

This bug is only as a marker to fill a proper changelog, and possibly add some testing for it.

The change is suitable for rhel-7.4 because:

- the default on rhel7 is rc-manager=file. So, this likely does not affect many users.

- the new behavior makes much more sense, the difference comes into play when

  - if somebody has rc-manager=symlink
  - /etc/resolv.conf is a regular file or missing

Previously, NM would have replaced /etc/resolv.conf with a symlink to /var/run/NetworkManager/resolv.conf. Now, instead NM will write resolv.conf as a regular file. A user who intentionally chooses rc-manager=symlink likely already replaced /etc/resolv.conf with a symlink (which is the main use of this mode).

Comment 3 errata-xmlrpc 2017-08-01 09:24:38 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.


Note You need to log in before you can comment on or make changes to this bug.