Public bug reported: Originally filed on Github[1]
In 612b4de (23.2) cloud-init switched the ds= kernel key from optionally matching on nocloud-net to forcibly selecting nocloud-net. This means that anyone that previously had a matching `ds=nocloud*` in their kernel commandline that _did not_ want to use the NoCloud datasource may experience broken behavior as a result of this change. Workarounds include updating the kernel commandline and optionally configuring a datasource_list in /etc/cloud/cloud.cfg.d/*.cfg. [1] https://github.com/canonical/cloud-init/issues/4977 ** Affects: cloud-init (Ubuntu) Importance: Low Status: New ** Affects: cloud-init (Ubuntu Focal) Importance: Low Status: New ** Affects: cloud-init (Ubuntu Jammy) Importance: Low Status: New ** Also affects: cloud-init (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056367 Title: kernel commandline change in behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
