Comment 21 for bug 1649931

For yakkety resolvconf update; I've updated the SRU test-case to include a more general netplan config for bringing up ethernet devices; the previous version only worked on lxd (or instances with devices named eth0).

With the above change; it looks like yakkety/zesty (due to running systemd-resolved instead of resolvconf service) need an update to the systemd-resolved service the instance is configured to use networkd insteadof ifupdown to ensure that systemd-resolved runs *before* network-online.target.

# diff -u systemd-resolved.service.orig systemd-resolv
--- systemd-resolved.service.orig 2017-03-06 19:37:44.206692449 +0000
+++ systemd-resolved.service 2017-03-06 19:33:09.467080158 +0000
@@ -12,6 +12,7 @@
 Documentation=http://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
 Documentation=http://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
 After=systemd-networkd.service network.target
+Before=network-online.target

 # On kdbus systems we pull in the busname explicitly, because it
 # carries policy that allows the daemon to acquire its name.

This makes things more complicated for this SRU; yakkety/zesty will need an updated systemd; the resolvconf portion of this SRU (for yakkety) is still OK but it's not sufficient to achieve the goal of ensuring DNS is functional *before* we reach 'network-online.target'.