I have the same behavior when working with MAAS and Juju, installing many openstack services collapsed onto a single node. I agree that the hosts entry ( in my case "127.0.1.1 qpx6p.maas qpx6p") is the root of the problem.
It seems that making this sort of entry would be problematic for a number of potential cloud deployment strategies. Wouldn't it be better to assume that there is functional DNS, and/or put a real IP in this hosts entry? It seems that would solve all the mysql-related problems that currently exist in the Trusty openstack-related charms.
I have the same behavior when working with MAAS and Juju, installing many openstack services collapsed onto a single node. I agree that the hosts entry ( in my case "127.0.1.1 qpx6p.maas qpx6p") is the root of the problem.
It seems that making this sort of entry would be problematic for a number of potential cloud deployment strategies. Wouldn't it be better to assume that there is functional DNS, and/or put a real IP in this hosts entry? It seems that would solve all the mysql-related problems that currently exist in the Trusty openstack-related charms.