Remove RabbitMQ ha-all policy when not required
With the addition of the variable `om_enable_rabbitmq_high_availability`, this feature in the upgrade task should be brought back. It is also now used in the deploy task. The `ha-all` policy is cleared only when `om_enable_rabbitmq_high_availability` is set to `false`. Change-Id: Ia056aa40e996b1f0fed43c0f672466c7e4a2f547 (cherry picked from commit c85b64d1589a515da2f3cf2dcc082d15df1d6edd)
This commit is contained in:
parent
fb71fbf928
commit
14482acb5f
@ -1,6 +1,8 @@
|
||||
---
|
||||
- include_tasks: remove-ha-all-policy.yml
|
||||
when: rabbitmq_remove_ha_all_policy | bool
|
||||
when:
|
||||
- not om_enable_rabbitmq_high_availability | bool
|
||||
- rabbitmq_remove_ha_all_policy | bool
|
||||
|
||||
- import_tasks: config.yml
|
||||
|
||||
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
When upgrading or deploying RabbitMQ, the policy `ha-all` is cleared if
|
||||
`om_enable_rabbitmq_high_availability` is set to `false`.
|
Loading…
x
Reference in New Issue
Block a user