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: 2017-08-15 04:37 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?).

Comment 1 Fedora End Of Life 2017-07-25 17:21:12 EDT
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 2 Zbigniew Jędrzejewski-Szmek 2017-07-25 19:08:11 EDT
I'm not even sure what the state is here. I'll reassign to rawhide so this doesn't get lost.
Comment 3 Jan Kurik 2017-08-15 04:37:39 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

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