Comment 4 for bug 1469077

Tested increasing memory, in case it was a factor. It was not, I increased memory by 50% and restarted the bootstrap node.

Tried a brand new deployment. A small deployment of percona-cluster and a few machines using add-machine was all working.

I then deploy an openstack bundle without relations and everything is working.
When I then add all the relations for the openstack bundle, that is when the leadership election starts and jujud spins for hours re-running config-changed on a lot of services, juju status tells me there are 27 services still running config-changed.
After leaving it overnight, juju API is no longer responsive and restarting only fixes it for a few minutes until the API fails again and is no longer responsive, although still listening on port 17070.