Comment 16 for bug 1543778

I did not start from scratch, I think from my quick reading of the bug the issue is that the same service exists twice duplicate in the Mongo DB, and causes weirdness because the service effectively exists with the same name/details but twice? So since my DB is already broken (from before this fix) the upgrade hasn't fixed that root brokenness. And each time it wants to create machines for the unplaced services, but then doesn't find any to place due to the duplication. However I am totally naive on juju internals so I may be totally wrong.

All I did to get into this state was deploy the openstack-base bundle from the GUI. I did this 3 times and had the same issue each time, with a fresh bootstrap.

I destroyed and re-created my environment and the issue with the new GUI and the issue has not re-occurred. So it seems fixed from a new environment standpoint but given this release was out in the wild, some kind of upgrade logic to fix the root brokenness may be prudent.

Before re-creating my environment I dumped the Mongo DB, I am happy to upload it if you think that will help.