We were able to drive MAAS system-tests via MAAS-owned jenkins job and
include them in our integration test verification. Attached all all
successful runs (and retries).
Successes for lxd_vm, lxd_container, gce, ec2 and azure on the following
series
jammy, noble, questing
Known/expected failures with integration tests are in the following areas:
- already fixed upstream: ntp tests, not a regression. cloud-init to prefer
ntpsec instead of ntp meta package as preferred ntp client
- rust coreutils in questing has different output for some commands (double
quotes vs single quotes)
- test_cloud_id_file_symlink and test_wireguard[stat -c '%N'
/etc/wireguard/wg0.conf-'/etc/wireguard/wg0.conf']
- test_crlf_in_azure_metadata_ssh_keys: upstream PR for integration-test fixes
non-functional test change needed
- test_ubuntu_advantage, integration test teardown issue in pycloudlib.
test library fix needed
** Attachment added: "sru-25.3.tar"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2131604/+attachment/5945814/+files/sru-25.3.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2131604
Title:
sru cloud-init 25.3: Jammy, Noble, Plucky, Questing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2131604/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
