Bug 1350450 - resolv.conf management
resolv.conf management
Status: NEW
Product: Fedora
Classification: Fedora
Component: systemd (Show other bugs)
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: systemd-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-06-27 08:58 EDT by DaveG
Modified: 2016-08-29 06:33 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description DaveG 2016-06-27 08:58:33 EDT
Description of problem:

Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1116999

BZ1116999 moved creation of the symlink /etc/resolv.conf from tmpfiles to systemd-resolved runtime to avoid treading on NM's toes (0999-resolved-create-etc-resolv.conf-symlink-at-runtime.patch).

Fedora 24 now runs systemd-resolved with ProtectSystem=full.

This means that the service CANNOT create the symlink since /etc will be mounted read-only.

Version-Release number of selected component (if applicable):


How reproducible:


Additional info:

I do not use NM. Used systemd-networkd since F22.

Changing to ProtectSystem=true side-steps the issue but defeats the added security.

The symlink needs to be manage by some other mechanism than a long-running service. systemd-networkd could be packaged as an alternative to NM and initscripts networking, with the symlink set on install. Could alternatives(8) handle it?

Move symlink creation to ExecStartPre?

The use of ProtectSystem=full in F24 may uncover similar issues elsewhere (mounton AVC?).


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