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

[Oliver Grawert]

** Changed in: snappy
   Status: New => Incomplete

** Changed in: snappy
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1620559

Title:
  /etc/resolv.conf is empty on snappy

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1620559/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Launchpad Bug Tracker]

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   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 Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1620559

Title:
  /etc/resolv.conf is empty on snappy

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1620559/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Martin Pitt]

This is a bug in systemd-networkd-resolvconf-update.service, apparently
/run/systemd/netif/state does not always get the received DNS servers.
This does not affect yakkety any more as this hackish thing is gone
entirely and replaced by resolved.

But it is still relevant for xenial which snappy is based on, so we need
to SRU it there.

Quick fix for snappy image builds until this is SRUed:

   sed '/^ExecStart=/ s!netif/state!& /run/systemd/netif/leases/* | sort
-u!' /lib/systemd/system/systemd-networkd-resolvconf-update.service

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Fix Released

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

** Changed in: systemd (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: systemd (Ubuntu)
   Importance: Critical => Undecided

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Martin Pitt (pitti)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1620559

Title:
  /etc/resolv.conf is empty on snappy

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1620559/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs