Comment 2 for bug 1629113

Hey Mark,

Please see below:

cs:trusty/wordpress-4

sdn@ubuntu-openstack1:~$ juju status --format tabular
[Services]
NAME STATUS EXPOSED CHARM
juju-gui unknown true cs:trusty/juju-gui-135
wordpress unknown true cs:trusty/wordpress-4

[Units]
ID WORKLOAD-STATE AGENT-STATE VERSION MACHINE PORTS PUBLIC-ADDRESS MESSAGE
juju-gui/0 unknown idle 1.25.6.1 0 80/tcp,443/tcp soggy-temper.maas
wordpress/2 unknown allocating 3 tremendous-yarn.maas Waiting for agent initialization to finish

[Machines]
ID STATE VERSION DNS INS-ID SERIES HARDWARE
0 started 1.25.6.1 soggy-temper.maas /MAAS/api/1.0/nodes/node-6226861c-8404-11e6-8f32-0025903bdf32/ trusty arch=amd64 cpu-cores=4 mem=8192M availability-zone=default
3 pending tremendous-yarn.maas /MAAS/api/1.0/nodes/node-1a7c390a-8405-11e6-ae0e-0025903bdf32/ trusty arch=amd64 cpu-cores=4 mem=8192M availability-zone=default

sdn@ubuntu-openstack1:~$

It gets stuck in this state and finally after about 20-30 minutes in MaaS I see that the node failed commissioning. It looks like MaaS properly allocates the node and it goes through the install process but it seems like after executing late commands and finishing "curtin command install" it just sort of times out or the juju agent does not come up on the node where the charm was deployed to.

Thanks!