Comment 13 for bug 1930293

Reviewed: https://review.opendev.org/c/openstack/kolla-ansible/+/795284
Committed: https://opendev.org/openstack/kolla-ansible/commit/f11af96cc62106cb9ab95e1687a693fa2a6a6df7
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit f11af96cc62106cb9ab95e1687a693fa2a6a6df7
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.

    [1] https://review.opendev.org/c/openstack/kolla-ansible/+/763137

    Change-Id: I1823301d5889589bfd48326ed7de03c6061ea5ba
    Closes-Bug: #1930293
    (cherry picked from commit 0cd5b027c985a8f6d3368ae0dc08b65f67f67fe0)