I've just attached the output of our verification testing runs for each series.
Each series exhibits two test failures, neither of which is material to the change in question (and both of which reproduce against the cloud- init currently in the archive). `test_datasource_rbx_no_stacktrace` is testing a non-Azure datasource but doesn't include the appropriate marks to exclude it from an Azure test run. As such, it's an expected failure (which we will fix upstream: https://bugs.launchpad.net/cloud-init/+bug/1911230). `TestSeedRandomData.test_seed_random_data` is implemented incorrectly for Azure. `cc_seed_random` behaves differently on platforms which provide random data to cloud-init (such as Azure), and that is not taken into account in the test code (or described in the documentation). https://bugs.launchpad.net/cloud-init/+bug/1911227 captures addressing the documentation and test issue. Given that all other tests pass, including the one for this bug, I consider verification of these cloud-init SRUs to be complete. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-groovy verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910835 Title: Azure IMDS publicKeys contain \r\n which prevents ssh access to vms using cloud-generated ssh keys. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1910835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
