Comment 8 for bug 1708676

I'm not sure how Juju works, but if it has access to the instance that it deploys, there are some user-facing tools that Juju could make use of.

Cloud-init surfaces status information via the command `cloud-init status --format json`.

Return codes:

0: means that cloud-init completed successfully.
1: means that cloud-init experienced a fatal error and was unable to complete.
2: means that cloud-init completed, but experienced an error.

Output contains the following keys:

extended_status: shows current cloud-init status
recoverable_errors: displays text describing errors seen by cloud-init