commit 0cd5b027c985a8f6d3368ae0dc08b65f67f67fe0
Author: Mark Goddard <email address hidden>
Date: Mon Jun 7 12:56:36 2021 +0100
Fix RabbitMQ restart ordering
The host list order seen during Ansible handlers may differ to the usual
play host list order, due to race conditions in notifying handlers. This
means that restart_services.yml for RabbitMQ may be included in a
different order than the rabbitmq group, resulting in a node other than
the 'first' being restarted first. This can cause some nodes to fail to
join the cluster. The include_tasks loop was introduced in [1].
This change fixes the issue by splitting the handler into two tasks, and
restarting the first node before all others.
Reviewed: https:/ /review. opendev. org/c/openstack /kolla- ansible/ +/795091 /opendev. org/openstack/ kolla-ansible/ commit/ 0cd5b027c985a8f 6d3368ae0dc08b6 5f67f67fe0
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 0cd5b027c985a8f 6d3368ae0dc08b6 5f67f67fe0
Author: Mark Goddard <email address hidden>
Date: Mon Jun 7 12:56:36 2021 +0100
Fix RabbitMQ restart ordering
The host list order seen during Ansible handlers may differ to the usual services. yml for RabbitMQ may be included in a
play host list order, due to race conditions in notifying handlers. This
means that restart_
different order than the rabbitmq group, resulting in a node other than
the 'first' being restarted first. This can cause some nodes to fail to
join the cluster. The include_tasks loop was introduced in [1].
This change fixes the issue by splitting the handler into two tasks, and
restarting the first node before all others.
[1] https:/ /review. opendev. org/c/openstack /kolla- ansible/ +/763137
Change-Id: I1823301d588958 9bfd48326ed7de0 3c6061ea5ba
Closes-Bug: #1930293