Thank you TimBishop for the request for logs in comment #39. I can
confirm that latest image manifest[1] contains cloud-init v.
24.4.1-0ubuntu0~22.04.2 which should have the expected fix for the
original traceback seen:
TypeError: OauthUrlHelper._exception_cb() missing 1 required
positional argument: 'exception'
I think we'd need cloud-init logs from the failing instances to
determine what the symptom is that is causing an issue on latest jammy
images.
references:
[1] maas image manifest:
http://images.maas.io/ephemeral-v3/candidate/jammy/amd64/20250401/squashfs.manifest
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100963
Title:
cloud-init fails with MAAS since Feb 4 update
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2100963/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs