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

2016-12-14 Thread 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:

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

2016-09-14 Thread 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

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

2016-09-06 Thread 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