systemd-networkd-resolvconf-update.service uses default dependencies which will only run after sysinit.target, however cloud-init.service needs to run before sysinit.target; systemd apparently dropped running the service due to the inconsistent order. Adding a DefaultDependencies=no to systemd-networkd-resolvconf-update.{service,path} allows cloud-init.service to run early with DNS before sysinit.target.
I've marked verification failed for this bug since the current proposed packages do not resolv the issue without changes to systemd package (/lib/systemd/system/systemd-networkd-resolvconf-update.{service,path}.
systemd- networkd- resolvconf- update. service uses default dependencies which will only run after sysinit.target, however cloud-init.service needs to run before sysinit.target; systemd apparently dropped running the service due to the inconsistent order. Adding a DefaultDependen cies=no to systemd- networkd- resolvconf- update. {service, path} allows cloud-init.service to run early with DNS before sysinit.target.
I've marked verification failed for this bug since the current proposed packages do not resolv the issue without changes to systemd package (/lib/systemd/ system/ systemd- networkd- resolvconf- update. {service, path}.