openstack/kolla-ansible.git/ansible/roles/rabbitmq, branch stable/2026.1

rabbitmq: fix precheck missing backend TLS cert fallback

2026-09-08T13:48:29+00:00

service-cert-copy falls back to kolla_tls_backend_cert/key when no rabbitmq-specific cert is found, but the precheck did not check for this path, causing a false failure when relying on the shared backend certificate. Closes-Bug: #2166283 Change-Id: I75d4b33fc893bcf0793c1280981574bcdf3f3002 Signed-off-by: fprzewozn (cherry picked from commit a54ad717f08a8258424004e6224a36ea561393d2)

Fix for overly restrictive permissions on ca-certificates directory

2026-05-12T05:56:37+00:00

Closes-Bug: #2112280 Change-Id: I52499bdf2b7fc70f91a4c2920749bfef83a79850 Signed-off-by: Rafal Lewandowski Signed-off-by: Michal Nasiadka (cherry picked from commit e302bab31f30296f7d6f41c3d46e19cf5668b97a)

rabbitmq: fix reset-state on RabbitMQ 4.x

2026-05-06T13:23:14+00:00

kolla-ansible rabbitmq-reset-state fails because rabbitmqctl force_reset is not supported with Khepri. Use rabbitmqctl reset instead. Closes-Bug: #2150536 Change-Id: Idc275dc830838519e40a519111ae0e5ca2b76edf Signed-off-by: Piotr Milewski

Merge "Make RabbitMQ stream retention policy configurable"

2026-04-27T09:23:16+00:00

Make RabbitMQ stream retention policy configurable

2026-04-24T08:21:14+00:00

When fanout queues are set to be RabbitMQ stream, number of ready messages in stream queues grow large. This is because retention policy of stream is only applied when stream segments hit the maximum size. This change make the maximum size of RabbitMQ stream segment and the retention time configurable by new variables ``rabbitmq_stream_max_segment_size_bytes`` and ``rabbitmq_stream_segment_max_age`` respectively. NOTE: These are only applied when ``om_enable_rabbitmq_stream_fanout`` is set to ``true``. Change-Id: Iade5e525f0de8981a0e03e3340ad7552c2f40121 Signed-off-by: Seunghun Lee

Standardize API health check endpoints

2026-04-12T13:02:28+00:00

Configure dedicated health check endpoints for Load Balancers Standardize health check paths in OpenStack and Grafana Ansible defaults to improve Load Balancer (HAProxy) reliability. The 'httpchk' configuration for the modified roles now uses dedicated health check endpoints (e.g., /healthcheck or /api/health) and enforces an HTTP 200 OK expectation. This ensures faster and more robust failure detection. Additionally, by moving health checks away from generic endpoints (such as OPTIONS /), application logs are now much cleaner. The log files will no longer be flooded every second with HAProxy probe entries like: "OPTIONS / HTTP/1.0" 200 94 0.000954 NOTE: The following services are exceptions to this standardization and still use the root endpoint (`/`) for health checks due to the lack of a dedicated health check middleware in their default API paste configuration: **cyborg_api**, **masakari**, **mistral_api**, **nova_api**, **octavia_api**, **placement**, **tacker**, **venus**, and **watcher**. Updated roles: * aodh * barbican * cinder * cloudkitty * cyborg * designate * etcd * glance * gnocchi * grafana * heat * horizon * influxdb * ironic * keystone * loadbalancer * magnum * manila * masakari * mistral * neutron * nova * nova-cell * octavia * opensearch * placement * rabbitmq * skyline * tacker * trove * venus * watcher * zun Change-Id: Ibbb9fda45a98565ab12e784bbef80be787bd6638 Signed-off-by: Piotr Milewski

kolla-ansible: Add RabbitMQ 4.2 support and dynamic upgrade paths

2026-03-27T14:00:46+00:00

The RabbitMQ version check currently hardcodes allowed version jumps. This makes supporting new major/minor releases (like 4.2) rigid and requires modifying the core task file. This commit introduces the `rabbitmq_allowed_upgrades` variable in the role's defaults. This allows operators to define explicit version jumps (e.g., 3.13 to 4.2) and makes the upgrade logic more flexible. The version validation logic now: 1. Checks for standard minor increments (e.g., 4.1 -> 4.2). 2. Checks for explicitly defined jumps in `rabbitmq_allowed_upgrades`. By moving these definitions to defaults, operators can easily override them in globals.yml if necessary. Depends-On: https://review.opendev.org/c/openstack/kolla/+/966017 Change-Id: I0e19cf109eb5665045806b7d925779e82164c2dc Signed-off-by: Piotr Milewski

ansible-lint: Fix fqcn[actions-core] for rabbitmq

2026-03-23T17:05:12+00:00

Change-Id: I1285f9c00829a7d64851c16a7222985eabdc06ef Signed-off-by: Michal Nasiadka

ansible-lint: fix yaml[line-length] in rabbitmq

2026-03-03T08:25:09+00:00

Change-Id: Ib4eef492268432343cf8e3e4bcf3c3bb16e08d95 Signed-off-by: Bertrand Lanson

Switch to pypi version of j2lint and fix linting errors

2025-12-30T16:31:17+00:00

Since ipwrap filter is getting moved another time inside ansible code - let's switch to j2lint that is actively maintained and it's rules will help in readability of jinja2 templates Change-Id: I6762b691b927de31fa1abd83c4c14e87226fe5e2 Signed-off-by: Michal Nasiadka