Comment 14 for bug 1649931

Ryan Harper (raharper) wrote :

Something isn't working here. I also typo'd the test-case, in particular, the change to the cloud-init.service unit didn't specify 'systemd-networkd-wait-online.service', the sed command missed the 'd' in networkd.

When I fix that, I find that systemd-networkd-resolvconf-update.service does NOT run. Manually adding that to /lib/systemd/system/resolvconf.service.wants fixes the networkd boot path, but of course breaks the ifupdown path.