James Falcon

The original issue here was fixed in https://github.com/canonical/cloud-init/pull/4864 . Cloud-init no longer reports RUNNING but instead reports DONE. > Long term cloud-init status should return a fatal error code and...

@sshedi , thanks for the bug report, but I am unable to reproduce this. Would it be possible to attach the tarball resulting from `cloud-init collect-logs`? Based on the traceback,...

Thanks. I can reproduce this when there is no datasource list defined or datasource detected.

@sshedi , upstream, we have decided we're going to keep this as a breaking change given that the old argument placement did not make sense. Since the `--file` argument cannot...

This is a symptom of having no datasource found during cloud-init's earlier stages. Is cloud-init being run by systemd as part of boot? If so, do you see an "ERROR"...

@holmanb , I believe I answered all of your questions. Ready for re-review.

We'll want to patch this out of Mantic and below.

Thanks for the bug report @leezu . I put up a draft PR to address this at https://github.com/canonical/cloud-init/pull/5287

@leezu , fix has been merged upstream. Downstream Ubuntu can be tracked in https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2066979

@leezu , I unfortunately do not have a timeline, but we are trying to get this released ASAP.