On 06/12/2018 09:06 AM, Stefan Seyfried wrote:
On 11.06.2018 21:43, John Paul Adrian Glaubitz wrote:
Hmm, I would also agree to rather fix the actual bug instead of adding a hack. I don't quite understand what the original issue is that we don't use the proper symlink that upstream uses.
The problem is that, as openSUSE does not use systemd-networkd/resolved but wicked by default, this symlink leads to a non-working name resolution in default configuration.
Nothing unusual. Debian defaults to NetworkManager on desktop/laptops and to ifupdown on other systems by default.
tmpfiles.d/etc.conf, when resolved is enabled at systemd build, creates the symlink on boot, if /etc/resolv.conf does not exist.
I usually just follow the instructions from the Arch Wiki on Debian:
I haven't tried that on openSUSE yet.
Every "standard" SUSE installation has /etc/resolv.conf, created by yast/whatever.
The Live iso, created by kiwi has no resolv.conf. If resolved is *enabled* at boot, tmpfiles.d/etc.conf will create the symlink, but networkd/resolved will not be used. Life will be bad.
I see, thanks for summarizing the bug.
If the fix involves upstream work, I can help with that. I have contributed something like 10 patches to systemd upstream in the past.
I have just commented out the symlink creation in tmpfiles.d/etc.conf, allowing to build resolved without breaking name resolution for default setups.
I'm not arguing (anymore, as it will not be heard anyway) the crazy wicked default, but I would really like to have the option of using systemd-networkd.
I agree. systemd-networkd *should* be usable as customers certainly expect it to work, in particular in cloud instances or containers for which it was specifically designed.
And if "we" do not want to give that option to users, then at least be honest and remove systemd-networkd from sytemd pacakge, so that everone knows they just should go and use $SOME_OTHER_DISTRIBUTION_THAT_WORKS.
No, I think that should definitely get fixed.
My solution was not acceptable to (one of) the systemd maintainer(s), and a proper solution seems overly complicated (hack the tmpfiles.d code to first check if networkd/resolved is enabled) for upstream to accept it for no visible gain.
I have to admit, I have never used the tmpfiles.d mechanism and the machines where I used systemd-networkd don't have an /etc/tmpfiles.d/etc.conf which creates the symlink, so I had to create the symlink manually.
Another solution would be to fix image building to just create an empty(?) resolv.conf in the image.
That would probably work, too. Adrian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org