I think this is unlikely to be a bug in cloud-init, as the cloud-init failure is a consequence of the failure starting the juju-clean-shutdown service, as noted already. We could get better understanding on what happens on the cloud-init side from the logs tarball generated by running
cloud-init collect-logs
on the failed machine. For the moment I'm marking the cloud-init task as Incomplete.
Hi,
I think this is unlikely to be a bug in cloud-init, as the cloud-init failure is a consequence of the failure starting the juju-clean-shutdown service, as noted already. We could get better understanding on what happens on the cloud-init side from the logs tarball generated by running
cloud-init collect-logs
on the failed machine. For the moment I'm marking the cloud-init task as Incomplete.