The test plan is correctly testing a fresh install (by doing purge, and then install from proposed). Please also test the upgrade scenario, for those systems that have already installed the bad cloud-init.
I'm thinking something like this: - purge old cloud-init - install cloud-init from updates (bug) - confirm the services are not enabled - upgrade to cloud-init from proposed - confirm services are enabled now I know the bug manifests itself in a fresh install of cloud-init from updates, and the scenario we have for that so far is in image building, but I would like to be sure the above simple steps do not cause anything bad as well, or at least know what happens then. Let me know if you think this scenario in the test steps above makes no sense. ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2113797 Title: cloud-init 25.1.2 on Jammy not running on VM boot, systemd services disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2113797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
