Comment 12 for bug 1472711

It looks like the use of the deployment_status API is currently restricted to bootstrap, which is synchronous. Thus when the bootstrap node is started, the deployment status is polled until it becomes Deployed or Failed Deployment.

With StartInstance() however, this is an async call to the provder. Thus a node is acquired and started and the call returns; the node status stays Pending until the node's machine agent starts and updates the status. This has always been Juju behaviour. There's no mechanism in Juju currently to recognise that StartInstance() may not immediately return an error. So for all providers, including MAAS, if StartInstance() initially returns OK, but then subsequently fails, the Juju status will stay Pending. The status only goes to error if the StartInstance() call itself fails.

To address this issue, it may be necessary to scope the work as part of the current Observability initiative, as it's not as far as I can see a MAAS specific issue but rather a fundamental Juju limitation.