openstack-helm-infra/rabbitmq
Maik Catrinque a0206d9626 Add force_boot command to rabbit start template
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
2022-02-04 10:38:54 -03:00
..
templates Add force_boot command to rabbit start template 2022-02-04 10:38:54 -03:00
values_overrides rabbitmq: Set separate for HTTPS 2021-06-09 03:50:06 +00:00
.helmignore RabbitMQ: move RabbitMQ chart to OSH-Infra 2018-07-30 15:28:34 +00:00
Chart.yaml Add force_boot command to rabbit start template 2022-02-04 10:38:54 -03:00
requirements.yaml Update htk requirements 2021-10-06 01:02:28 +00:00
values.yaml Add force_boot command to rabbit start template 2022-02-04 10:38:54 -03:00