I am setting the importance to low for the following reasons: - reverting the change would reintroduce a different bug[1] - a workaround has been provided - the change in behavior is minor - the change was introduced almost a year ago without any reports yet
[1] https://bugs.launchpad.net/cloud-init/+bug/1815990 ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Low ** Changed in: cloud-init (Ubuntu Focal) Importance: Undecided => Low ** Changed in: cloud-init (Ubuntu Jammy) Importance: Undecided => Low ** Description changed: + 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 ** Changed in: cloud-init (Ubuntu) Status: New => Triaged ** Changed in: cloud-init (Ubuntu Focal) Status: New => Triaged ** Changed in: cloud-init (Ubuntu Jammy) Status: New => Triaged -- 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
