6c037790f2
Ansible 2.14.3 introduced a change that broke the method used for
restarting MariaDB and RabbitMQ serially [1][2]. In
I57425680a4cdbf0daeb9b2cc35920f1b933aa4a8 we limited to 2.14.2 to work
around this. Ansible upstream claim this behaviour was unintentional,
and will not fix it.
This change moves to a different approach where we use separate plays
with a 'serial' keyword to execute the restart.
This change also removes the restriction on the maximum supported
version of 2.14.2 on ansible-core - any 2.14 release is now supported.
[1] 65366f663d
[2] https://github.com/ansible/ansible/issues/80848
Depends-On: https://review.opendev.org/c/openstack/kolla/+/884208
Change-Id: I5a12670d07077d24047aaff57ce8d33ccf7156ff
11 lines
368 B
YAML
11 lines
368 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
Removes the restriction on the maximum supported version of 2.14.2 for
|
|
``ansible-core``. Any 2.14 series release is now supported.
|
|
other:
|
|
- |
|
|
Refactors the MariaDB and RabbitMQ restart procedures to be compatible with
|
|
Ansible 2.14.3+. See `Ansible issue 80848
|
|
<https://github.com/ansible/ansible/issues/80848>`__ for details.
|