[Bug 1620559] Update Released

[Martin Pitt]

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
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 at 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 at 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