Comment 2 for bug 1574272

Yes, I'm able to reproduce this every time. I'm essentially stuck on this one as I can't add a single machine without the aforementioned happening.

If you can supply a debug juju, I'm happy to run it for you. Also if you need any extra information just ask.

It's a test install so there's also nothing that needs to be censored about the config or setup.

For the setup, I'm using three virtual machines running on KVM (manually created xml files to define the virtuals with virsh, nothing fancy on management).
One virtual for Maas (running juju commands from this machine ip: 10.180.0.1)
Two virtuals in Maas power controlled with virsh, juju controller gets 10.180.0.2 and the first added machine gets 10.180.0.3.

I've killed the controller quite a few times and bootstrapped it again and retried either only doing "add machine" or trying "deploy rabbitmq-server" or "deploy mysql" just to see if something works. Every time things go wrong while adding the machine. The agent uninstalls itself and juju sees the machine eternally pending.

Also I've not figured an easy way to clean the pending machine, but as it's the only one I can just kill controller. Which only works after I release both nodes from maas.

I've been running the juju bootstrap as root most of the time, could that be doing something wonky?