Bug 1024897

Summary:	systemd: no DNS Resolving possible on live images with latest systemd submission
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Dominique Leuenberger <dimstar>
Component:	Basesystem	Assignee:	systemd maintainers <systemd-maintainers>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	fbui, lnussel, mchandras, seife
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:
Bug Blocks:	1018387

Description Dominique Leuenberger 2017-02-11 00:20:08 UTC

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)

Comment 1 Bernhard Wiedemann 2017-02-11 01:01:34 UTC

This is an autogenerated message for OBS integration:
This bug (1024897) was mentioned in
https://build.opensuse.org/request/show/456350 Factory / systemd

Comment 2 Franck Bui 2017-03-03 09:45:56 UTC

I'm closing this bug as resolved has been (re)disabled.

But we still need to find a proper way to enable it (bsc#1018387).

Comment 3 Stefan Seyfried 2018-06-11 19:22:05 UTC

why not just touch /etc/resolv.conf in a kiwi config.sh script or similar?

Why keep systemd-networkd unusable  because of errors in the image build process?

Comment 5 Franck Bui 2018-06-12 12:29:51 UTC

(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

Comment 6 Stefan Seyfried 2018-06-12 17:31:21 UTC

not necessary, sorry for the hassle.

I fixed it for myself.

Comment 7 Markos Chandras 2018-06-12 18:26:03 UTC

(In reply to Stefan Seyfried from comment #6)
> 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

Comment 8 Markos Chandras 2018-06-12 18:28:57 UTC

(In reply to Franck Bui from comment #5)
> (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?

Comment 9 Stefan Seyfried 2018-06-12 18:39:33 UTC

(In reply to Markos Chandras from comment #7)
> 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.

Comment 10 Franck Bui 2018-06-13 06:35:47 UTC

(In reply to Markos Chandras from comment #8)
> 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.

Comment 11 Franck Bui 2018-06-14 12:47:23 UTC

Fedora's patch pushed to next update, closing.