[Bug 1620559] Re: /etc/resolv.conf is empty on snappy

Andy Whitcroft apw at canonical.com
Wed Sep 7 09:13:26 UTC 2016


Hello Oliver, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu8
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Xenial)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
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 Committed

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



More information about the foundations-bugs mailing list