Red Hat Bugzilla – Bug 1350450
Last modified: 2016-08-29 06:33:28 EDT
Description of problem:
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):
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?).