For the time being until we figure out what is going on you can override
/ downgrade cloud-init during deployments using the following preseed
file:
#cloud-config
debconf_selections:
maas: |
{{for line in str(curtin_preseed).splitlines()}}
{{line}}
{{endfor}}
late_commands:
maas: [wget, '--no-proxy', {{node_disable_pxe_url|escape.json}},
'--post-data', {{node_disable_pxe_data|escape.json}}, '-O', '/dev/null']
cloud_init: ["apt-get", "install", "-y", "--allow-downgrades",
"cloud-init=23.1.2-0ubuntu0~22.04.1"]
Save this under /var/snap/maas/current/preseeds/curtin_userdata (snap)
or /etc/maas/preseeds (deb) on ALL Region (OR Region+Rack) Controllers.
Please test this workaround and let us know if it resolves your issue.
--
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
