Comment 27 for bug 1954925

Reviewed: https://review.opendev.org/c/openstack/kolla-ansible/+/872863
Committed: https://opendev.org/openstack/kolla-ansible/commit/a87810db7e5bccdc863dd5cb5158ca5193eb5fd3
Submitter: "Zuul (22348)"
Branch: master

commit a87810db7e5bccdc863dd5cb5158ca5193eb5fd3
Author: Matt Crees <email address hidden>
Date: Tue Feb 7 09:56:43 2023 +0000

    Set RabbitMQ ha-promote-on-shutdown=always

    Changes the default value of `rabbitmq-ha-promote-on-shutdown` to
    `"always"`.

    We are seeing issues with RabbitMQ automatically recovering when nodes
    are restarted. https://www.rabbitmq.com/ha.html#cluster-shutdown

    Rather than waiting for operator interventions, it is better we allow
    recovery to happen, even if that means we may loose some messages.
    A few failed and timed out operations is better than a totaly broken
    cloud. This is achieved using ha-promote-on-shutdown=always.

    Note, when a node failure is detected, this is already the default
    behaviour from 3.7.5 onwards:
    https://www.rabbitmq.com/ha.html#promoting-unsynchronised-mirrors

    Related-Bug: #1954925
    Change-Id: I484a81163f703fa27112df22473d657e2a9ab964