Comment 3 for bug 1365035

Sooo... I finally caught this bugger in action. It's as I was discussing with bigjools in #maas.

I bootstrap, but soon after a destroy-environment previously ran. Well, that gets juju thinking that the machine is ready to use (since it hasn't been shutdown yet). Juju is then waiting on the machine to finish starting jujud so it can contact mongo, but then the power off/power on comes along.

*Then*, the machine is ripped out from underneath it.

Questions

1) Why doesn't maas allocate the machine after power on is run?

2) Why is this power off/power on taking so long?

My theory on #2: I'm getting a ton of dhcp refreshes that are all taking 6+ seconds. I think they are clogging the rabbit queue. Perhaps that warrants a separate bug. Not sure, will need some guidance there.