The above fixed patch has the recent change where the ordering of hosts in 'ansible/site.yml' has been changed to have neutron-server at the top of the list. With ansible 1.9.4 as recommended by kolla, delegate_to and run_once have some issues where the task to be run is attempted on the first host where the details are gathered and irrespective of the outcome of the task, it is only attempted once. The first host is apparently chosen from the ordering of the list of hosts in 'ansible/site.yml'. All the other plays have the respective servers at the top of the list and neutron did not. They made the neutron db creation and service registering task to always be attempted on the first compute node and gets skipped. This patch should be re-visited/reverted once we move a version of ansible where delegate_to issues are fixed to make sure that the code works as expected.
The above fixed patch has the recent change where the ordering of hosts in 'ansible/site.yml' has been changed to have neutron-server at the top of the list. With ansible 1.9.4 as recommended by kolla, delegate_to and run_once have some issues where the task to be run is attempted on the first host where the details are gathered and irrespective of the outcome of the task, it is only attempted once. The first host is apparently chosen from the ordering of the list of hosts in 'ansible/site.yml'. All the other plays have the respective servers at the top of the list and neutron did not. They made the neutron db creation and service registering task to always be attempted on the first compute node and gets skipped. This patch should be re-visited/reverted once we move a version of ansible where delegate_to issues are fixed to make sure that the code works as expected.