Activity log for bug #1620559

Date Who What changed Old value New value Message
2016-09-06 10:26:02 Oliver Grawert bug added bug
2016-09-06 10:27:48 Oliver Grawert bug task added snappy
2016-09-06 10:27:58 Oliver Grawert snappy: importance Undecided Critical
2016-09-06 10:28:01 Oliver Grawert systemd (Ubuntu): importance Undecided Critical
2016-09-06 11:13:45 Martin Pitt nominated for series Ubuntu Xenial
2016-09-06 11:13:45 Martin Pitt bug task added systemd (Ubuntu Xenial)
2016-09-06 11:15:53 Martin Pitt systemd (Ubuntu): status New Fix Released
2016-09-06 11:16:02 Martin Pitt systemd (Ubuntu Xenial): status New In Progress
2016-09-06 11:16:06 Martin Pitt systemd (Ubuntu Xenial): importance Undecided High
2016-09-06 11:16:09 Martin Pitt systemd (Ubuntu): importance Critical Undecided
2016-09-06 11:16:11 Martin Pitt systemd (Ubuntu Xenial): assignee Martin Pitt (pitti)
2016-09-06 12:05:44 Martin Pitt tags hw-specific
2016-09-06 12:10:57 Martin Pitt 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:~$ 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 =============== 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.
2016-09-06 12:16:18 Martin Pitt 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 =============== 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. 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.
2016-09-07 09:13:16 Andy Whitcroft systemd (Ubuntu Xenial): status In Progress Fix Committed
2016-09-07 09:13:18 Andy Whitcroft bug added subscriber Ubuntu Stable Release Updates Team
2016-09-07 09:13:20 Andy Whitcroft bug added subscriber SRU Verification
2016-09-07 09:13:25 Andy Whitcroft tags hw-specific hw-specific verification-needed
2016-09-08 08:31:38 Oliver Grawert tags hw-specific verification-needed hw-specific verification-done
2016-09-14 11:56:44 Martin Pitt removed subscriber Ubuntu Stable Release Updates Team
2016-09-14 12:01:19 Launchpad Janitor systemd (Ubuntu Xenial): status Fix Committed Fix Released
2016-12-14 14:48:24 Oliver Grawert snappy: status New Incomplete
2016-12-14 14:48:28 Oliver Grawert snappy: status Incomplete Fix Released