Bug 1268974

Summary: systemd-tmpfiles is creating /etc/resolv.conf as a broken symlink, which breaks networking
Product: [Fedora] Fedora Reporter: David Shea <dshea>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: awilliam, johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-05 19:04:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journal none

Description David Shea 2015-10-05 18:56:35 UTC
Created attachment 1080025 [details]
journal

Description of problem:
This again!

/etc/resolv.conf is a broken symlink to /run/systemd/resolve/resolv.conf, which is breaking networking. If systemd-tmpfiles creates its files before NetworkManager starts up, NetworkManager will fail to write DNS information to /etc/resolv.conf, because /etc/resolv.conf is not a writeable file.




Version-Release number of selected component (if applicable):
systemd-226-3.fc24.x86_64

Attaching journalctl output, the "could not commit DNS changes: Could not stat /etc/resolv.conf: No such file or directory" is the part I would like not to have to see.

Comment 1 Adam Williamson 2015-10-05 19:04:07 UTC

*** This bug has been marked as a duplicate of bug 1264364 ***