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
21 lines
706 B
YAML
21 lines
706 B
YAML
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
|
|
---
|
|
apiVersion: v1
|
|
appVersion: v3.7.26
|
|
description: OpenStack-Helm RabbitMQ
|
|
name: rabbitmq
|
|
version: 0.1.16
|
|
home: https://github.com/rabbitmq/rabbitmq-server
|
|
...
|