9847546fe1
At the moment rabbitmq_upgrade will temporary stop all nodes in the cluster, shortly disrupting operations. This behavior is now changed to perform a regular rolling upgrade [1] Community right now relying on the rabbitmq_upgrade variable to "recover" the cluster state by basically re-bootstrapping the cluster. Such behaviour should be implemented separately in a follow-up patch. [1] https://www.rabbitmq.com/docs/upgrade#rolling-upgrade Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/931801 Change-Id: Ibb3fae0d85dc31237ce169bb4cde9551dd5cabb6
10 lines
373 B
YAML
10 lines
373 B
YAML
---
|
|
prelude: >
|
|
Behavior of ``rabbitmq_upgrade`` variable has changed. It no longer can
|
|
be used to reset the cluster state. It now acts solely as a flag to perform
|
|
a rolling-upgrade of the existing cluster.
|
|
other:
|
|
- |
|
|
Supplying ``rabbitmq_upgrade=true`` no longer re-initialize cluster and
|
|
will perform regular rolling upgrade of the RabbitMQ cluster.
|