[Bug 1018387] New: Please build and ship systemd-resolved related files
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 Bug ID: 1018387 Summary: Please build and ship systemd-resolved related files 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: mchandras@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Right now, systemd in Tumbleweed builds with --disable-resolved which means that files such as /usr/bin/systemd-resolve and systemd-resolved.service are not being shipped at all. There is probably not a good reason to do that. The systemd unit file can always be disabled by default if it conflicts with other components but there are cases where users may want to use these systemd utilities. I believe it makes sense to always build and ship these files. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c3 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |dimstar@opensuse.org Depends on| |1024897 Resolution|FIXED |--- --- Comment #3 from Dominique Leuenberger <dimstar@opensuse.org> --- Caused a regression, discovered by openQA: bug 1024897 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c6 Niels Abspoel <aboe76@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aboe76@gmail.com --- Comment #6 from Niels Abspoel <aboe76@gmail.com> --- Hi Franck, Can you update the status of this bug report? Is enabling systemd-resolved still a problem? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c7 --- Comment #7 from Franck Bui <fbui@suse.com> --- Hi Niels, (In reply to Niels Abspoel from comment #6)
Can you update the status of this bug report? Is enabling systemd-resolved still a problem?
Yeah, we still need to find a way to prevent bug #1024897 from resurrecting if we want to enable resolved. I unfortunately haven't time to look at this, so feel free to look at it ;) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c8 --- Comment #8 from Niels Abspoel <aboe76@gmail.com> --- Hi Franck, Can't open the urls anymore too see if I can help.. 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 Can these be recreated? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c9 --- Comment #9 from Franck Bui <fbui@suse.com> --- Isn't the description of the problem given in comment #0 enough ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c10 --- Comment #10 from Niels Abspoel <aboe76@gmail.com> --- Hi Franck, I have read https://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c0 if resolved is enabled there will be an extra entry in /usr/lib/tmpfiles.d/etc.conf to produce a symlink: L! /etc/resolv.conf - - - - ../usr/lib/systemd/resolv.conf and with future versions: L! /etc/resolv.conf - - - - ../run/systemd/resolve/stub-resolv.conf I don't really see the issue, the exclamation mark means this is only safe for execution during boot. and only if /etc/resolv.conf isn't present. That's why I'm intrested in the error reports, what is going on..and why is /etc/resolv.conf apparently missing or are we testing to which resolvers the QA builds point? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c11 --- Comment #11 from Markos Chandras <markos.chandras@suse.com> --- (In reply to Niels Abspoel from comment #10)
Hi Franck,
I have read https://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c0
if resolved is enabled there will be an extra entry in /usr/lib/tmpfiles.d/etc.conf to produce a symlink:
L! /etc/resolv.conf - - - - ../usr/lib/systemd/resolv.conf
and with future versions:
L! /etc/resolv.conf - - - - ../run/systemd/resolve/stub-resolv.conf
I don't really see the issue, the exclamation mark means this is only safe for execution during boot. and only if /etc/resolv.conf isn't present.
That's why I'm intrested in the error reports, what is going on..and why is /etc/resolv.conf apparently missing or are we testing to which resolvers the QA builds point?
The bug that Franck pointed before contains the explanation "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" so like you said, the problem is reproducible when the system does not have an /etc/resolv.conf file. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c12 Franck Bui <fbui@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(dimstar@opensuse. | |org) --- Comment #12 from Franck Bui <fbui@suse.com> --- (In reply to Niels Abspoel from comment #10)
That's why I'm intrested in the error reports, what is going on..and why is /etc/resolv.conf apparently missing or are we testing to which resolvers the QA builds point?
Dominique, can you remember the details ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c13 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dimstar@opensuse. | |org) | --- Comment #13 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to Franck Bui from comment #12)
(In reply to Niels Abspoel from comment #10)
That's why I'm intrested in the error reports, what is going on..and why is /etc/resolv.conf apparently missing or are we testing to which resolvers the QA builds point?
Dominique, can you remember the details ?
Vaguely: There is nothing putting a /etc/resolv.conf on the live ISO (regular installation gets one written by yast, the creation of the live image happens with kiwi and is booted directly) So when the user first boots up the live medium, system created that symlink to 'manage resolv.conf', but then did not start resolvd to actuall DO the management. Resulting in a Live image without network access IMHO: the resolv.d specific parts of etc.conf need to go to a resolvd.conf and be packaged together with resolvd; you get the tmpfiles configuration together with the package; not installing resolv won't mess up the system. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c14 --- Comment #14 from Niels Abspoel <aboe76@gmail.com> --- So Dominique, I see three solutions: -1- Ship a default /etc/resolv.conf file so tmpfiles.d/etc.conf doesn't overwrite it. -2- use systemd-resolved as default and enabled to have /run/systemd/system/resolv.conf filled. -3- hack etc.conf in systemd package with some kind of logic if resolved enabled is true and if package is installed to overwrite etc.conf which is shipped with systemd package... Solution 1 could be easier and leaves the work with the sysadmin, is he installes systemd-resolved, he should also know that a symlink is required. Solution 2 is a political question for opensuse/suse if they want to use systemd-resolved as a resolver in general. solution 3 is a potential debug hazard and I think to complicated... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c15 --- Comment #15 from Niels Abspoel <aboe76@gmail.com> --- I have found some more information about this issue, with some fedora devs: https://bugzilla.redhat.com/show_bug.cgi?id=1313085 They have created the following patch: http://pkgs.fedoraproject.org/cgit/rpms/systemd.git/tree/0998-resolved-creat... Which is already merged upstream with version 236 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c16 --- Comment #16 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to Niels Abspoel from comment #14)
solution 3 is a potential debug hazard and I think to complicated...
solution 3a: split etc.conf it two parts; resolvd related stuff and normal stuff. there is absolutely no reason to have all this logic in one conf file; systemd-tmpfiles is going to parse all present conf files anyway. This is non-introsive and not disrupting to anything a dummy resolv.conf is the wrong solution, just to accommodate some other program which is not shipped/enabled by default. NetworkManager for example does not touch a resolv.conf file if it's not pre-managed by NetworkManager. You just can't assume everything will keep on doing as expected. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c17 --- Comment #17 from Franck Bui <fbui@suse.com> --- (In reply to Niels Abspoel from comment #15)
They have created the following patch: http://pkgs.fedoraproject.org/cgit/rpms/systemd.git/tree/0998-resolved- create-etc-resolv.conf-symlink-at-runtime.patch
Which is already merged upstream with version 236
Are you sure about that ? I can't find it in the upstream repo. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c18 --- Comment #18 from Franck Bui <fbui@suse.com> --- (In reply to Dominique Leuenberger from comment #13)
IMHO: the resolv.d specific parts of etc.conf need to go to a resolvd.conf and be packaged together with resolvd; you get the tmpfiles configuration together with the package; not installing resolv won't mess up the system.
That's what the patch pointed out by Niels in comment #15 seems to achieve. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c19 --- Comment #19 from Markos Chandras <markos.chandras@suse.com> --- *** Bug 1084080 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c20 --- Comment #20 from Markos Chandras <markos.chandras@suse.com> --- The patch doesn't seem to have made it upstream but this is the updated link https://src.fedoraproject.org/rpms/systemd/blob/master/f/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=1018387 Markos Chandras <markos.chandras@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://github.com/systemd/ | |systemd/issues/8373 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c21 Stefan Seyfried <seife@novell.slipkontur.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife@novell.slipkontur.de --- Comment #21 from Stefan Seyfried <seife@novell.slipkontur.de> --- can we for now please just enable systemd-resolved build in Leap 15, Factory and SLES15 again? without systemd-resolved, systemd-networkd is "mostly useless™" Let's just remove the symlink-creating-line in etc.conf. Users wanting to use systemd-networkd need to do manual steps anyway to get rid of wicked and friends, so creating a symlink should be possible for them. I'll prepare a SR... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 Oliver Kurz <okurz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |okurz@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 Bruno Friedmann <bruno@ioda-net.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno@ioda-net.ch -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c22 --- Comment #22 from Stefan Seyfried <seife@novell.slipkontur.de> --- SR to Base:System/systemd: https://build.opensuse.org/request/show/616099 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 http://bugzilla.opensuse.org/show_bug.cgi?id=1018387#c23 --- Comment #23 from Franck Bui <fbui@suse.com> --- (In reply to Stefan Seyfried from comment #22)
SR to Base:System/systemd: https://build.opensuse.org/request/show/616099
Declined. There's still bug #1024897 that needs to be addressed *properly* first. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 Bug 1018387 depends on bug 1024897, which changed state. Bug 1024897 Summary: systemd: no DNS Resolving possible on live images with latest systemd submission http://bugzilla.opensuse.org/show_bug.cgi?id=1024897 What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 Bug 1018387 depends on bug 1024897, which changed state. Bug 1024897 Summary: systemd: no DNS Resolving possible on live images with latest systemd submission http://bugzilla.opensuse.org/show_bug.cgi?id=1024897 What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 Bug 1018387 depends on bug 1024897, which changed state. Bug 1024897 Summary: systemd: no DNS Resolving possible on live images with latest systemd submission http://bugzilla.opensuse.org/show_bug.cgi?id=1024897 What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX |--- -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018387 Bug 1018387 depends on bug 1024897, which changed state. Bug 1024897 Summary: systemd: no DNS Resolving possible on live images with latest systemd submission http://bugzilla.opensuse.org/show_bug.cgi?id=1024897 What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com