Comment 7 for bug 1546789

How is this issue planned to be handled for Mitaka? Will there be ansible 1.9.x with fix of this?

Maybe technically it is not a valid bug against Kolla, but the other thing is that it hits Kolla's functionality significantly - deployment of multi-node configuration fails. Workaround mentioned above works, but requires manual actions, not simple to automatize. Also other workaround with changing service distribution across nodes is I think not much good.

Note that there is other workaround mentioned on Kolla's IRC channel
http://eavesdrop.openstack.org/irclogs/%23kolla/%23kolla.2016-03-11.log.html#t2016-03-11T19:56:39
which is working for me - tweak site.yml for neutron role - putting following services on section top in this order:
    - neutron-server
    - neutron-dhcp-agent
    - neutron-l3-agent
    - neutron-metadata-agent

in neutron section:
https://github.com/openstack/kolla/blob/906c13eb6148d0c48b5f5ae157cfb10113efe173/ansible/site.yml#L101

Would this be acceptable fix/workaround to include into kolla directly?