Bug 1268974 - systemd-tmpfiles is creating /etc/resolv.conf as a broken symlink, which breaks networking
Summary: systemd-tmpfiles is creating /etc/resolv.conf as a broken symlink, which brea...
Keywords:
Status: CLOSED DUPLICATE of bug 1264364
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-05 18:56 UTC by David Shea
Modified: 2016-02-29 22:31 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-05 19:04:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
journal (135.07 KB, text/x-vhdl)
2015-10-05 18:56 UTC, David Shea 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1313085 0 unspecified CLOSED Name resolution fails (resolv.conf is a broken systemd symlink) on livemedia-creator live image 2021-02-22 00:41:40 UTC

Internal Links: 1313085

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 ***
Note You need to log in before you can comment on or make changes to this bug.