With regard to the other questions mentioned:
Pre-release Questions: ---------------------- azure-noble ----------- > 1) FAILED > tests/integration_tests/modules/test_ubuntu_pro.py::TestUbuntuAdvantagePro::test_custom_services > - AssertionError: Unexpected warnings or errors found This appears to be an image provisioning error in auto-attach pro images in Azure and not a cloud-init issue per-se. I don't believe my account has proper permissions to view this contract on custom images. I will sort this behavior with the proclient/ua-contracts team separately to ensure we have the right permissions to continue to use Pro images directly in integration tests. The error returned from ubuntu pro backend is "contract not found" 2026-10-16 21:04:54,314 - http[DEBUG]: URL [POST] response: https://contracts.canonical.com/v1/clouds/azure/token, headers: {'cache- control': 'no-store, max-age=0', 'connection': 'close', 'content- length': '119', 'content-type': 'application/json', 'date': 'Fri, 16 Oct 2026 21:04:54 GMT', 'server': 'nginx/1.18.0 (Ubuntu)', 'strict- transport-security': 'max-age=15724800; includeSubDomains', 'x-trace- id': '019aa7a9-7d9a-4815-b3a4-26aed289819e'}, data: {'code': 'contract not found', 'message': 'missing instance information', 'traceId': '019aa7a9-7d9a-4815-b3a4-26aed289819e'}. I have filed an upstream ubuntu pro bug to sort why snapshot-based Pro VMs do not appear to be authorized to auto-attach. https://github.com/canonical/ubuntu-pro-client/issues/3636 Nothing has changed in cloud-init related to ubuntu-pro interaction between 26.1 and 26.2. So, I don't believe this is a cloud-init problem, but possibly an integration test setup or some constraints on Azure platform preventing auto-attach in derivative Pro images. > So, this was noticed during 26.1, and claimed to be fixed by https://github.com/canonical/cloud-init/pull/6872, so why is this still happening in 26.2? I see it was merged and the commit is tagged 26.2, so it should be fixed? 6872 was fixing a test problem during instance teardown that was caused by cloud-init's integration tests attempting to peform cleanup on instances that were already destroyed. This error we now see in 26.2 is permissions and contract related from the pro backend services and most likely related to permissions of a derivative Pro image on azure. 2) FAILED tests/integration_tests/modules/test_users_groups.py::test_default_user_settings_override - AssertionError: Shell setting overridden even though user already exists Testing issues resolved in upstream test here: https://github.com/canonical/cloud-init/pull/7167 This is an issue in 26.2 because pycloudlib (our integration test library) runs `waagent -deprovision+user` on Azure machines during test image snapshot creation which removes the default user in the image when creating a snapshot. The cloud-init integration test incorrectly assumed that Azure snapshot images will contain the ubuntu user, this is incorrect for all Azure tests based on how the test image is created. Nic has just fixed this today in tests. lxd_vm-resolute: ---------------- Any additional details on these? 1) FAILED tests/integration_tests/bugs/test_lp1912844.py::test_get_interfaces_by_mac_doesnt_traceback - pycloudlib.errors.PycloudlibTimeoutError: Unable to determine IP address af... The test appears to fail in both stock canonical cloudimages with 26.1 and 26.2. It appears to be an integration test setup issue where the user.network-config does not seem to be passed to the integration-test instance. I have filed an upstream test bug for this case. This fix may ultimately be in pycloudlib (our test library) or cloud-init integration test setup, but it is not a behavior change in cloud-init 26.2. Upstream issue https://github.com/canonical/cloud-init/issues/7168 2) FAILED tests/integration_tests/modules/test_lxd.py::test_storage_preseed_zfs - AssertionError: Unexpected warning count != 0. Found: ["WARNING]: Running m... Successful retry locally, we have historically hit intermittent errors on GH vms that introduce certain flakiness of testing. I have attached the LXD_VM resolute successful retry to this message/. 3) FAILED tests/integration_tests/test_kernel_command_line_match.py::test_lxd_datasource_kernel_override_nocloud_net[ds=nocloud-net;s=https://raw.githubusercontent.com/canonical/cloud-init/main/tests/data/kernel_cmdline_match/] - AssertionError: assert False Successful retry locally, results attached maas-resolute ------------- >> I note the maas validation log is present only for noble. Has a resolute run >> been attempted? Does it succeed? mentioned in comment #8. Generally cloud-init does only exercises the test backends define for MAAS and solutions QA as they are supplemental tests beyond cloud-init's own integration test suite. ** Bug watch added: github.com/canonical/ubuntu-pro-client/issues #3636 https://github.com/canonical/ubuntu-pro-client/issues/3636 ** Bug watch added: github.com/canonical/cloud-init/issues #7168 https://github.com/canonical/cloud-init/issues/7168 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2164685 Title: src cloud-init 26.2:noble, resolute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2164685/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
