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
22 lines
518 B
YAML
22 lines
518 B
YAML
---
|
|
docker_version_min: '18.09'
|
|
docker_py_version_min: '3.4.1'
|
|
ansible_version_min: '2.13'
|
|
ansible_version_max: '2.14'
|
|
|
|
# Top level keys should match ansible_facts.distribution.
|
|
# These map to lists of supported releases (ansible_facts.distribution_release) or
|
|
# versions (ansible_facts.distribution_version or ansible_facts.distribution_major_version)
|
|
# for that distribution.
|
|
host_os_distributions:
|
|
CentOS:
|
|
- "9"
|
|
Debian:
|
|
- "bullseye"
|
|
openEuler:
|
|
- "22.03"
|
|
Rocky:
|
|
- "9"
|
|
Ubuntu:
|
|
- "jammy"
|