There is an interesting issue just filed against cloud-init for Ubuntu resolute images about network configuration (determined by cloud-init in init-local stage) not being applied to the system.
https://github.com/canonical/cloud-init/issues/6666 Given that it is an Ubuntu resolute bug related to netplan generation versus applying config, I thought it worth reflecting that content over here too as the context is highly suspicious. Cloud-init only runs netplan generate in init-local timeframe, and only opts to run `netplan apply` if initial network configuration is initially discovered during the init-network stage. We wonder if `netplan apply` should always be invoked or if systemd ordering is still not ideal in resolute to allow cloud-init to create /etc/netplan/50-cloud-init.yaml early enough in boot. ** Bug watch added: github.com/canonical/cloud-init/issues #6666 https://github.com/canonical/cloud-init/issues/6666 -- 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
