Context on the cloud-init failures: Cloud-init's newer version changed the key used in cloud config for the Pro client from ubuntu_advantage to ubuntu_pro. Because it is a "breaking" change, this works fine on Focal and Jammy, where both keys are accepted, but not on Noble.
On Noble, when you use ubuntu_advantage, the functionality itself works but you get a warning and cloud-init is left in a degraded state - breaking our test expectations that all is good on their side. We changed the key to `ubuntu_pro` in tests so cloud-init can work well on Noble, and it does. But the catch is: the support for the `ubuntu_pro` key is only implemented in THIS version of the Client, >=32, which is in -proposed. When we launch the machines for testing, we are not using the package from proposed yet - we boot with cloud-config being considered in the installed version, and install from proposed later. This leads to the following conclusion: - our test is meant to verify the Client's behavior with the new key, and what is breaking is the cloud-init integration. So those failures are not related to the proposed package at all, and should not block verification for the SRU. - this is and has been true for a while, and those tests are always executed, which carries the side effect of guaranteeing some extent of cloud-init integration, but only after released. - We have assured this particular integration works using builds from local / daily PPAs. So all is good to proceed here despite those failures. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060732 Title: [SRU] ubuntu-advantage-tools (31 -> 32) Xenial, Bionic, Focal, Jammy, Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2060732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
