commit 6f250f2e05823d25db75287b921dc4f7a70ae542
Author: Alex Schultz <email address hidden>
Date: Tue Nov 28 12:15:14 2017 -0700
Fix neutron agent start order
In the baremetal deployment, we used to ensure that neutron-server was
started prior to starting up the various agents. In the containerized
deployment we need to ensure that we launch the agents after the server
has been started. We can do this by configuring a start_order for each
of the services.
It should be noted that the ovs agent was actually configured to start
in step5 on baremetal due to previous race conditions under HA
deployments. This change leaves it in step4 but configures the
start_order to be after the neutron-api service.
Reviewed: https:/ /review. openstack. org/524056 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=6f250f2e058 23d25db75287b92 1dc4f7a70ae542
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 6f250f2e05823d2 5db75287b921dc4 f7a70ae542
Author: Alex Schultz <email address hidden>
Date: Tue Nov 28 12:15:14 2017 -0700
Fix neutron agent start order
In the baremetal deployment, we used to ensure that neutron-server was
started prior to starting up the various agents. In the containerized
deployment we need to ensure that we launch the agents after the server
has been started. We can do this by configuring a start_order for each
of the services.
It should be noted that the ovs agent was actually configured to start
in step5 on baremetal due to previous race conditions under HA
deployments. This change leaves it in step4 but configures the
start_order to be after the neutron-api service.
Change-Id: I3794400ef5c8ae 620961914831ff8 5e3438b0399 8ee492caddaf47d 2ef5780f31)
Closes-Bug: #1734976
Related-Bug: #1663273
(cherry picked from commit c54c6222d8b517b