<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla-ansible.git/ansible/rabbitmq.yml, branch stable/2026.1</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.1</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.1'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/'/>
<updated>2026-03-19T12:17:03+00:00</updated>
<entry>
<title>ansible-lint: Fix fqcn[actions-core] in playbooks</title>
<updated>2026-03-19T12:17:03+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2025-12-12T08:37:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=21013949cdae545dbb797d149d7e4bcfa1378ea7'/>
<id>urn:sha1:21013949cdae545dbb797d149d7e4bcfa1378ea7</id>
<content type='text'>
Also add all failed roles into ignore and these will be removed in
subsequent patches

Change-Id: Ifa6f2725cfa93cb14d72daf27448bd58f186acfd
Signed-off-by: Michal Nasiadka &lt;mnasiadka@gmail.com&gt;
</content>
</entry>
<entry>
<title>ansible-lint: fix unnamed-task in rabbitmq.yml</title>
<updated>2025-12-09T22:01:47+00:00</updated>
<author>
<name>Bertrand Lanson</name>
<email>bertrand.lanson@protonmail.com</email>
</author>
<published>2025-12-09T22:01:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=d6038ef629266cd28d057c70ee27635e636fe430'/>
<id>urn:sha1:d6038ef629266cd28d057c70ee27635e636fe430</id>
<content type='text'>
Change-Id: Icd689a152ba17065c81cfecc5c7da51d686465cd
Signed-off-by: Bertrand Lanson &lt;bertrand.lanson@protonmail.com&gt;
</content>
</entry>
<entry>
<title>ansible-lint: Remove yaml[truthy] from excludes</title>
<updated>2025-11-28T09:06:26+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2025-11-12T14:24:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=78f3c2b5de0470c0b1d350d0865663bb6f17f49e'/>
<id>urn:sha1:78f3c2b5de0470c0b1d350d0865663bb6f17f49e</id>
<content type='text'>
Normalize quotes and some other easy fixes done by
ansible-lint --fix

Also drop etc from excludes and ignore comment check in
etc/kolla/globals.yml

Pinning to ansible-lint&lt;25.11.0 because 25.11.1 is breaking
without any messages

Change-Id: I7dee3866191cef84cd12b1816cdab0a02380ec7f
Signed-off-by: Michal Nasiadka &lt;mnasiadka@gmail.com&gt;
</content>
</entry>
<entry>
<title>RMQ: enable all stable feature flags at once</title>
<updated>2024-05-13T12:26:10+00:00</updated>
<author>
<name>Matt Crees</name>
<email>mattc@stackhpc.com</email>
</author>
<published>2024-03-27T16:15:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=223556e4e2efe35c77c4607408d47e67577a68f1'/>
<id>urn:sha1:223556e4e2efe35c77c4607408d47e67577a68f1</id>
<content type='text'>
Also enable these after an upgrade.

Partial-Bug: #2058512
Change-Id: Ib9bdae2e25c2b6cce30e4c8024015ab5875bc1ff
</content>
</entry>
<entry>
<title>Drop Murano</title>
<updated>2024-04-25T09:20:42+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2024-04-24T15:35:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=6c31bb676d372969d2489ecc7d39f04fa8ba4941'/>
<id>urn:sha1:6c31bb676d372969d2489ecc7d39f04fa8ba4941</id>
<content type='text'>
It's inactive and hasn't produced a 2024.1 release [1].
In addition to that, there's a CVE that hasn't really been patched [2].

Also drop outward_rabbitmq that was used only with Murano.

[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects
[2]: https://lists.openstack.org/archives/list/openstack-announce@lists.openstack.org/thread/4FYM6GSIM5WZSJQIG4TT5Q3UBKQIHLWX/

Change-Id: I691205730b0e10a42ce61f3340cc39ee51bd1010
</content>
</entry>
<entry>
<title>Support Ansible max_fail_percentage</title>
<updated>2023-12-05T10:49:42+00:00</updated>
<author>
<name>Mark Goddard</name>
<email>mark@stackhpc.com</email>
</author>
<published>2021-08-16T16:03:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=af6e1ca4fd3366c1ae936d225b2835e95a4191fc'/>
<id>urn:sha1:af6e1ca4fd3366c1ae936d225b2835e95a4191fc</id>
<content type='text'>
This allows us to continue execution until a certain proportion of hosts
to fail. This can be useful at scale, where failures are common, and
restarting a deployment is time-consuming.

The default max failure percentage is 100, keeping the default
behaviour. A global max failure percentage may be set via
kolla_max_fail_percentage, and individual services may define a max
failure percentage via &lt;service&gt;_max_fail_percentage.

Note that all hosts in the inventory must be reachable for fact
gathering, even those not included in a --limit.

Closes-Bug: #1833737
Change-Id: I808474a75c0f0e8b539dc0421374b06cea44be4f
</content>
</entry>
<entry>
<title>Refactor MariaDB and RabbitMQ restart procedure</title>
<updated>2023-06-17T21:02:49+00:00</updated>
<author>
<name>Mark Goddard</name>
<email>mark@stackhpc.com</email>
</author>
<published>2023-05-24T11:21:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=6c037790f2802d626902d377486ec2f8ce2c8cda'/>
<id>urn:sha1:6c037790f2802d626902d377486ec2f8ce2c8cda</id>
<content type='text'>
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] https://github.com/ansible/ansible/commit/65366f663de7d044f42ae6dd53368fd4c1f88b35
[2] https://github.com/ansible/ansible/issues/80848

Depends-On: https://review.opendev.org/c/openstack/kolla/+/884208

Change-Id: I5a12670d07077d24047aaff57ce8d33ccf7156ff
</content>
</entry>
</feed>
