group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #07512
[Bug 1620559] Re: /etc/resolv.conf is empty on snappy
This bug was fixed in the package systemd - 229-4ubuntu8
---------------
systemd (229-4ubuntu8) xenial-proposed; urgency=medium
* Queue loading transient units after setting their properties. Fixes
starting VMs with libvirt. (LP: #1529079)
* Connect pid1's stdin/out/err fds to /dev/null also for containers. This
fixes generators which expect a valid stdout/err fd in some container
technologies. (LP: #1608953)
* 73-usb-net-by-mac.rules: Do not run readlink for *every* uevent, and
merely check if /etc/udev/rules.d/80-net-setup-link.rules exists.
A common way to disable an udev rule is to just "touch" it in
/etc/udev/rule.d/ (i. e. empty file), and if the rule is customized we
cannot really predict anyway if the user wants MAC-based USB net names or
not. (LP: #1615021)
* systemd-networkd-resolvconf-update.service: Also pick up DNS servers from
individual link leases, as they sometimes don't appear in the global
ifstate. (LP: #1620559)
-- Martin Pitt <martin.pitt@xxxxxxxxxx> Tue, 06 Sep 2016 14:16:29
+0200
** Changed in: systemd (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1620559
Title:
/etc/resolv.conf is empty on snappy
Status in Snappy:
New
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Released
Bug description:
we currently have no working resolver on snappy installs,
/etc/resolv.conf is the boilerplate one.
on the low level we seem to have DNS from the DHCP server though
ogra@localhost:~$ grep -r DNS= /run/systemd/netif
/run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205
/run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205
/run/systemd/netif/links/3:MDNS=no
ogra@localhost:~$
SRU INFORMATION
===============
Fix: https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=0a96feb1561
Test case:
I cannot reproduce this in a VM or normal laptop, this is somehow
specific to the reporter's hardware/DHCP server config.
* Configure systemd-networkd for an ethernet interface, either directly or via netplan; remove it from /etc/network/interfaces{,.d}
* Reboot.
* With current xenial's systemd, if /run/systemd/netif/state does not have "DNS=" then /etc/resolv.conf will not have any nameserver.
* With the proposed update, /etc/resolv.conf should have the DHCP-provided nameserver.
Regression potential: Low; in 16.04 LTS we do not configure networkd
by any Ubuntu tool, so networkd is not widely used there yet. For
systems which do use it it could happen that interface-specific DNS
servers now appear in resolv.conf that should not be global -- but we
do not have anything that would configure or obey this setup in 16.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1620559/+subscriptions