FWIW, even 'juju status --format=yaml' doesn't provide much information as to why it failed:
| "6": | juju-status: | current: down | message: agent is not communicating with the server | since: 12 Apr 2019 02:07:17Z | dns-name: 52.230.xxx.xxx | ip-addresses: | - 52.230.xxx.xxx | - 192.168.0.10 | instance-id: machine-6 | machine-status: | current: provisioning error | message: Failed | since: 12 Apr 2019 02:07:17Z | modification-status: | current: idle | since: 12 Apr 2019 02:06:40Z | series: xenial | constraints: instance-type=Standard_D2_v2 | hardware: arch=amd64 cores=2 mem=7168M root-disk=30720M
FWIW, even 'juju status --format=yaml' doesn't provide much information as to why it failed:
| "6": status: type=Standard_ D2_v2
| juju-status:
| current: down
| message: agent is not communicating with the server
| since: 12 Apr 2019 02:07:17Z
| dns-name: 52.230.xxx.xxx
| ip-addresses:
| - 52.230.xxx.xxx
| - 192.168.0.10
| instance-id: machine-6
| machine-status:
| current: provisioning error
| message: Failed
| since: 12 Apr 2019 02:07:17Z
| modification-
| current: idle
| since: 12 Apr 2019 02:06:40Z
| series: xenial
| constraints: instance-
| hardware: arch=amd64 cores=2 mem=7168M root-disk=30720M