Comment 2 for bug 1534757

machine-0.log, which is rather large. Note that this is the same environment as Bug #1532130 , which had occurred a short while earlier. There is a chance that the weirdness here is fallout from this earlier failure.

Also amusingly, lxc shows the machine aparently active with an IP address. Alas, processes kicked in and it got shutdown before I could investigate further or rescue the unit log from it.

$ lxc list
+------------------------------------------------------+---------+-------------------+------+-----------+-----------+
| NAME | STATE | IPV4 | IPV6 | EPHEMERAL | SNAPSHOTS |
+------------------------------------------------------+---------+-------------------+------+-----------+-----------+
| juju-5f65e7eb-5d0b-4c6e-8fde-143ad97856fc-machine-0 | RUNNING | 10.0.3.145 (eth0) | | NO | 0 |
+------------------------------------------------------+---------+-------------------+------+-----------+-----------+
| juju-5f65e7eb-5d0b-4c6e-8fde-143ad97856fc-machine-26 | RUNNING | 10.0.3.36 (eth0) | | NO | 0 |
+------------------------------------------------------+---------+-------------------+------+-----------+-----------+
| juju-81816a86-9dd3-445a-8bc0-99ff62d179c9-machine-0 | RUNNING | 10.0.3.144 (eth0) | | NO | 0 |
+------------------------------------------------------+---------+-------------------+------+-----------+-----------+

(Hmm... and a second controller node that didn't get cleaned up last teardown)