gh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620559
Title:
/etc/resolv.conf is empty on snappy
To manage notifications about this bug go to:
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620559
Title:
/etc/resolv.conf
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
works fine now
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620559
Title:
/etc/resolv.conf is empty on snappy
To manage
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
** Description changed:
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
** Description changed:
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
** Tags added: hw-specific
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620559
Title:
/etc/resolv.conf is empty on snappy
To manage notifications about this bug go to:
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
