Public bug reported: Originally reported on Github[1], cloud-init released a change in the cli[2] that broke former cloud-init cli commands.
Previously `cloud-init -f <file> init` was allowed, but after the 24.1 SRU release to Jammy, this broke and now the following invocation is required to accomplish the same thing: `cloud-init init -f foo.cfg`. There is apparently no syntax that is compatible with both versions. This is a change in behavior that was released under SRU back to stable releases. [1] https://github.com/canonical/cloud-init/pull/4559#issuecomment-2084860007 [2] https://github.com/canonical/cloud-init/pull/4559 ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu Focal) Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Mantic) 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/2064300 Title: cli behavior changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
