Interestingly, dropping the /usr/lib/systemd/system/netplan-
configure.service.d/cloud-init.conf override [1] has the side-effect of
being unable to re-name network-interfaces at boot time ("netplan apply"
at runtime still works) in my original reproducer from the bug
descriptiong. E.g. booting a resolute cloud-image, modify interface name
("set-name") in /etc/netplan/50-cloud-init.yaml and reboot => Boot is
delayed by 2 min (systemd-networkd-wait-online.service timeout) as it's
waiting for the new interface name to come online, while it's not
actually renamed. – Other configuration, such as IP addresses, is still
applied at boot time.Using the drop-in config [1] solves the interface re-name during boot, but breaks other use-cases as explained in comment #7. Interestingly, the rename-via-udev usecase seems to be broken in cloud-images on netplan 1.1.2-8ubuntu1 as well, so should likely not be considered a regression. Still, it might be worthwhile to investigate the link and proper integration between netplan-configure.service and cloud-init- network.service. – I filed bug #2136392 for that. [1] """ [Unit] # This drop-in unit can be dropped, once cloud-init grew the # "Before=netplan-configure.service" dependency natively. # LP: #2133724 After=cloud-init-network.service """ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2133724 Title: Update to Netplan v1.2, to enable the split generator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2133724/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
