** Description changed: [ Impact ] On Digital Ocean and some bare metal instances, changes introduced in e30549e8 are causing older instances to fail to boot. While the cloud- init team cannot reproduce the exact scenario, we have received enough reports that we believe it prudent revert this change as it was a boot- time optimization only change. No functionality should be affected by this change. [ Test Plan ] - - Launch an instance containing bootcmd user data was one way that e30549e8 triggered a start of systemd-network-wait-online. Ensure the instance boots with no errors. + - Launch an instance containing bootcmd user data as that was one way that e30549e8 triggered a start of systemd-network-wait-online. Ensure the instance boots with no errors. - Launch an instance containing no bootcmd user data. Ensure the instance boots with no errors. [ Where problems could occur ] This is a revert of a commit added this cycle, so it's possible we could bring back any other undiscovered bugs we didn't know about in the old code. [ Other Info ] Upstream bug: https://github.com/canonical/cloud-init/issues/5945
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2094149 Title: Changes to cloud-init's systemd-networkd-wait-online interactions causing boot failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2094149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
