Ensure <service>_restart_bundle do not run concurrently
Now that paunch containers are run asynchronously, some
containers used for HA orchestration can run concurrently,
which triggers a deadlock and cause them to time out and
exit in error.
To overcome this concurrency deadlock, tweak the start_order
configuration of each HA service to make sure that no
<service>_restart_bundle container can be started at the same
time during a given step.
Reviewed: https:/ /review. opendev. org/722341 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=69012468272 8f56d36701e852a 899aaf8ee91940
Committed: https:/
Submitter: Zuul
Branch: master
commit 690124682728f56 d36701e852a899a af8ee91940
Author: Damien Ciabrini <email address hidden>
Date: Thu Apr 23 16:42:46 2020 +0200
Ensure <service> _restart_ bundle do not run concurrently
Now that paunch containers are run asynchronously, some _restart_ bundle container can be started at the same
containers used for HA orchestration can run concurrently,
which triggers a deadlock and cause them to time out and
exit in error.
To overcome this concurrency deadlock, tweak the start_order
configuration of each HA service to make sure that no
<service>
time during a given step.
Change-Id: I9ae55101945978 ea6c65d37eaa822 1ed3d96a7f5
Closes-Bug: #1873893