Please gather the logs as described in [1] and report back. Which image did this last succeed in?
I just linked the upstream bug and set the downstream bug to "invalid". [1] https://docs.cloud-init.io/en/latest/howto/bugs.html#collect-logs ** Bug watch added: github.com/canonical/cloud-init/issues #5849 https://github.com/canonical/cloud-init/issues/5849 ** Also affects: cloud-init via https://github.com/canonical/cloud-init/issues/5849 Importance: Unknown Status: Unknown ** Changed in: cloud-init (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/2089185 Title: Releasing fails with latest cloud-init on image 20241113 Status in cloud-init: Unknown Status in MAAS: Invalid Status in cloud-init package in Ubuntu: Invalid Bug description: Hello, It seems a bug was introduced in the `20241113` Jammy image and now when we release a server with disk erasing, after the wipe-disks script finishes successfully, cloud-init fails and causes the server to go into a release failed state. Searching the internet, this issue seems to align with what I'm seeing: https://github.com/canonical/cloud-init/issues/5849 See attached logs, where cloud-init fails with `failed stage modules- final`. I reviewed the cloud-config the server was getting and noticed the following: ``` power_state: condition: test ! -e /tmp/block-poweroff delay: now mode: poweroff timeout: 3600 ``` If my understanding is correct, basically cloud-init finishes running the user script then powers off. After sending the power off signal, it starts the modules-final section which then is cancelled by the shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2089185/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
