Comment 8 for bug 1543778

I am seeing similar behaviour. Every time I commit a change a whole bunch of new machines get created, about 9. They don't show up before the commit, only once you hit commit. They have no services assigned.

This happens just changing a configuration option on a charm, with no new charms, as well as if I try to scale a charm and add a new unit but manually place it onto an existing container. Once I force destroy them all and everything is steady, if I make a change again it happens again.. many times.

I destroyed and re-installed juju-gui and the same occurs. I have an openstack-base deployment on 3 machines using both root and extra lxc containers.

What debug information can I generate?

juju: 1.25.3 (xenial) and 1.25.4 (git branch head for 1.25)
provider: maas
juju host: xenial
all other vms including state server: trusty

juju-gui charm cs:trusty/juju-gui-47

from pip list on the juju-gui machine:
juju-deployer (0.6.2)
jujubundlelib (0.1.9)
jujuclient (0.50.1)
jujugui (2.0.2)