aboutsummaryrefslogtreecommitdiff
path: root/ansible/rabbitmq.yml
AgeCommit message (Collapse)AuthorFilesLines
2026-03-19ansible-lint: Fix fqcn[actions-core] in playbooksMichal Nasiadka1-3/+3
Also add all failed roles into ignore and these will be removed in subsequent patches Change-Id: Ifa6f2725cfa93cb14d72daf27448bd58f186acfd Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-12-09ansible-lint: fix unnamed-task in rabbitmq.ymlBertrand Lanson1-2/+4
Change-Id: Icd689a152ba17065c81cfecc5c7da51d686465cd Signed-off-by: Bertrand Lanson <bertrand.lanson@protonmail.com>
2025-11-28ansible-lint: Remove yaml[truthy] from excludesMichal Nasiadka1-15/+15
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<25.11.0 because 25.11.1 is breaking without any messages Change-Id: I7dee3866191cef84cd12b1816cdab0a02380ec7f Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2024-05-13RMQ: enable all stable feature flags at onceMatt Crees1-1/+1
Also enable these after an upgrade. Partial-Bug: #2058512 Change-Id: Ib9bdae2e25c2b6cce30e4c8024015ab5875bc1ff
2024-04-25Drop MuranoMichal Nasiadka1-69/+0
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
2023-12-05Support Ansible max_fail_percentageMark Goddard1-0/+24
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 <service>_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
2023-06-17Refactor MariaDB and RabbitMQ restart procedureMark Goddard1-0/+115
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
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-05 16:12:04 +0000