[Bug 1024897] New: systemd: no DNS Resolving possible on live images with latest systemd submission
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897 Bug ID: 1024897 Summary: systemd: no DNS Resolving possible on live images with latest systemd submission Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: dimstar@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Issue was introduced with https://build.opensuse.org/request/show/455437 And detected by openQA in several tests: GNOME Live : https://openqa.opensuse.org/tests/352734 KDE Live : https://openqa.opensuse.org/tests/352732 Rescue CD : https://openqa.opensuse.org/tests/352726 The issue boils down to: /etc/resolv.conf is now a symlink to /usr/lib/systemd/resolv.conf This happens only on the live images (so far) because they do not have a 'pre-shipped' resolv.conf - and systemd contains instructions in /usr/lib/tmpfiles.d/etc.conf to produce that symlink This part of tmpfiles.d should also be moved to the systemd-resolv package, so that the absence of this package means no ill side-effects For the time being, I am reverting systemd to the previous revision in openSUSE:Factory *no Tumbleweed snapshot had been produced with this systemd package - openQA blocked it) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897#c3
Stefan Seyfried
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897
Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897#c5
--- Comment #5 from Franck Bui
why not just touch /etc/resolv.conf in a kiwi config.sh script or similar?
That seems what Lennart Poettering suggested here: https://github.com/systemd/systemd/issues/8373#issuecomment-374892148 OTOH, I don't see why the symlink understood by systemd-resolved only should be created if resolved is not running and used at all... So for the time being I think we should do the same as fedora does and apply the following patch: https://src.fedoraproject.org/cgit/rpms/systemd.git/tree/0998-resolved-creat... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897#c6
Stefan Seyfried
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897#c7
Markos Chandras
not necessary, sorry for the hassle.
I fixed it for myself.
You may have fixed it for yourself but the problem remains for the rest of us so please leave this bug open -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897#c8
--- Comment #8 from Markos Chandras
(In reply to Stefan Seyfried from comment #3)
why not just touch /etc/resolv.conf in a kiwi config.sh script or similar?
That seems what Lennart Poettering suggested here: https://github.com/systemd/systemd/issues/8373#issuecomment-374892148
OTOH, I don't see why the symlink understood by systemd-resolved only should be created if resolved is not running and used at all...
So for the time being I think we should do the same as fedora does and apply the following patch: https://src.fedoraproject.org/cgit/rpms/systemd.git/tree/0998-resolved- create-etc-resolv.conf-symlink-at-runtime.patch
Franck is there any chance you can apply the Fedora patch for the time being since upstream is not going to fix it for us? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897#c9
--- Comment #9 from Stefan Seyfried
You may have fixed it for yourself but the problem remains for the rest of us so please leave this bug open
It was closed for over a year, and I mistakenly reopened it, so I wanted to correct that mistake. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897#c10
--- Comment #10 from Franck Bui
Franck is there any chance you can apply the Fedora patch for the time being since upstream is not going to fix it for us?
I will, probably at the end of the week. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897
http://bugzilla.opensuse.org/show_bug.cgi?id=1024897#c11
Franck Bui
participants (1)
-
bugzilla_noreply＠novell.com