Comment 1 for bug 2039210

Just an addendum -- it also seems like once these extraneous instances are created,
neither Juju or MAAS are aware of the VMs in their respective databases, but these VMs still show up in lxc list output as shown in the bug description.

It almost seems like MAAS is sending LXC the go ahead to spin up the VMs, gives up on it and doesn't check with the hypervisor that LXC went ahead and created these instances (albeit in a stopped state).