mirror of
https://github.com/optim-enterprises-bv/openstack-helm-infra.git
synced 2026-01-11 17:55:27 +00:00
a0206d9626
Currently, if a multi-node cluster is shut down unexpectedly, RabbitMQ is not able to boot and sync with the other nodes. The purpose of this change is to add the possibility to use the rabbitmqctl force_boot command to recover RabbitMQ cluster from an unexpected shut down. Test plan: PASS: Shutdown and start a multi-node RabbitMQ cluster Regression: PASS: OpenStack can be applied successfully PASS: RabbitMQ nodes can join the RabbitMQ cluster Story: 2009784 Task: 44290 Ref: [0] https://www.rabbitmq.com/rabbitmqctl.8.html#force_boot Signed-off-by: Maik Catrinque <maik.wandercatrinqueandrade@windriver.com> Co-authored-by: Andrew Martins Carletti <Andrew.MartinsCarletti@windriver.com> Change-Id: I56e966ea64e8881ba436213f0c9e1cbe547098e3
==================== Openstack-Helm-Infra ==================== Mission ------- The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm. For more information, please refer to the OpenStack-Helm repository_. .. _repository: https://github.com/openstack/openstack-helm Communication ------------- * Join us on `IRC <irc://chat.oftc.net/openstack-helm>`_: #openstack-helm on oftc * Community `IRC Meetings <http://eavesdrop.openstack.org/#OpenStack-Helm_Team_Meeting>`_: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on oftc * Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-helm-meeting-agenda>`_ * Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - #openstack-helm Contributing ------------ We welcome contributions. Check out `this <CONTRIBUTING.rst>`_ document if you would like to get involved.