On Thu, Oct 27, 2016 at 01:43:05PM -0000, Ryan Harper wrote: > without resolved in 16.04 though the change isn't strictly needed but to > keep the backported branch closer to trunk, I would expect those to come > in.
Except it's not correct that we don't have resolved in 16.04. We're not using resolved in the *desktop or server* in 16.04. Ubuntu Core 16 has explicitly seeded libnss-resolve in their image, you can see it configured in /etc/nsswitch.conf; for some reason the symlink that libnss-resolve sets up for /etc/systemd/system/multi-user.target.wants/systemd-resolved.service → /lib/systemd/system/systemd-resolved.service is absent, but this may be a bug related to the bind mounts over /etc/systemd and maybe shouldn't be relied on. I certainly don't know what to expect from the current resolved setup in Ubuntu Core 16, combined with the cloud-init systemd changes from zesty. (Martin, I don't suppose the snappy team talked to you before seeding libnss-resolve, which is a universe package in xenial, in their images...?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
