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
20 lines
810 B
YAML
20 lines
810 B
YAML
---
|
|
rabbitmq:
|
|
- 0.1.0 Initial Chart
|
|
- 0.1.1 Change helm-toolkit dependency version to ">= 0.1.0"
|
|
- 0.1.2 changes rmq-exporter secret src
|
|
- 0.1.4 Add configurable RABBIT_TIMEOUT parameter
|
|
- 0.1.5 Update Rabbitmq exporter version
|
|
- 0.1.6 Disallow privilege escalation in rabbitmq server container
|
|
- 0.1.7 Adding TLS logic to rabbitmq
|
|
- 0.1.8 Make helm test work with TLS
|
|
- 0.1.9 Use full image ref for docker official images
|
|
- 0.1.10 Set separate for HTTPS
|
|
- 0.1.11 Add TLS support for helm test
|
|
- 0.1.12 Added helm hook post-install and post-upgrade for rabbitmq wait cluster job
|
|
- 0.1.13 Add prestop action and version 3.8.x upgrade prep
|
|
- 0.1.14 Update readiness and liveness probes
|
|
- 0.1.15 Update htk requirements
|
|
- 0.1.16 Add force_boot command to rabbit start template
|
|
...
|