openstack/kolla-ansible.git/ansible/group_vars, branch stable/2026.1

cinder: Define backend variables in group_vars/all

2026-07-28T18:22:18+00:00

The iscsi role derives the cinder-volume/backup inventory groups from cinder_enabled_backends, but that variable (along with cinder_backends, cinder_ceph_backends and the cinder_backend_*_name variables) was only defined in the cinder role defaults. The iscsi play runs before the cinder play, so the variable is out of scope there and prechecks (and deploy/reconfigure) fail with: 'cinder_enabled_backends' is undefined when a Cinder iSCSI/LVM backend is enabled. Move these backend variable definitions to group_vars/all/cinder.yml so they are in scope for every play, including the iscsi role. This also keeps all cinder backend definitions - including the cinder-backup ceph backend (cinder_backup_backend_ceph_name, cinder_backup_ceph_backend) - in one place. All of their dependencies (the enable_cinder_backend_* flags, cinder_backend_ceph and the ceph_* variables) are already global, and globals.yml is applied as extra-vars, so operator overrides continue to take precedence. Partial-Bug: #2158120 Change-Id: I765f45814382377332ba9f01f1bc52bd4e046170 Signed-off-by: Kari Häkkinen (cherry picked from commit 2df2ee6e49d0fd58b1781c0b490b019e1936e96b)

rabbitmq: Bump default rabbit_qos_prefetch_count from 1 to 50

2026-07-23T16:44:21+00:00

rabbit_qos_prefetch_count was previously set to 1, the lowest value permitted by oslo.messaging when rabbit_stream_fanout is enabled (oslo.messaging requires prefetch_count > 0 for stream queues, since the stream protocol needs a positive credit window to make progress). However, non-zero is not the same as optimal. RabbitMQ's own quorum queue documentation recommends the opposite of what a prefetch of 1 provides: "Quorum queues also benefit from consumers using higher prefetch values to ensure consumers aren't starved whilst acknowledgements are flowing through the system and allowing messages to be delivered in a timely fashion." -- https://www.rabbitmq.com/docs/quorum-queues With rabbit_quorum_queue enabled by default alongside rabbit_stream_fanout, prefetch=1 forces every quorum-queue consumer (nova-conductor, neutron-server, cinder-volume, etc.) into fully serialized delivery: RabbitMQ will not deliver the next message to a channel until the previous one has been acked. Combined with a small worker count, this can turn a burst of RPC traffic into a queueing delay long enough to exceed rpc_response_timeout, surfacing as a false-positive MessagingTimeout with no actual broker outage. Bump the default to 50. This keeps the value legal for stream queues (still > 0), keeps a bound on how much a single consumer can hold in flight, but gives quorum-queue consumers enough headroom to avoid unnecessary serialization and consumer starvation under load. This is a shared value across all services using oslo_messaging_rabbit, so it is intentionally conservative rather than tuned per-service; operators with specific throughput requirements can still override om_rabbitmq_qos_prefetch_count. See [1]. [1]: I541f704bfa2e98068096331afbdb591659cbc40b Change-Id: Iea474a553cb8bd3920ef89c148f63b1c7b1b8dbc Signed-off-by: Michal Nasiadka (cherry picked from commit 1ccf97e6234dea12811f0a1270055015bd403079)

Fix typo in neutron group vars

2026-07-09T08:43:01+00:00

Closes-Bug: 2160035 Change-Id: I2f3ef4ef1085c93fd7e697c03fd530885795bcc4 Signed-off-by: alma.maillet-contoz (cherry picked from commit 4784eee7086043610c49c3f06d5e77eb816c9a2e)

Fix OVN SB relay port calculation for relay counts > 9

2026-06-17T08:07:30+00:00

The OVN SB relay port was generated using string concatenation between the port prefix and relay group ID. When the relay count exceeded 9, this resulted in invalid port numbers such as 166410. Update the port calculation to use numeric addition instead, ensuring ports remain within the expected and valid range. Closes-Bug: #2131191 Change-Id: I4738339431483c3d38fb322c18888fe61cae1a62 Signed-off-by: amir58118 Signed-off-by: Michal Nasiadka (cherry picked from commit 6c2b9225d52cf2470d7ed85fa5fde833d764bb3c)

Switch openstack_release to 2026.1

2026-05-11T09:31:22+00:00

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

haproxy: fix missing user in rabbitmq healthcheck

2026-04-28T15:26:40+00:00

RabbitMQ HAProxy config was missing user/auth in health checks, causing backend to be marked DOWN and HTTP 500 errors. Closes-Bug: #2150569 Change-Id: I1949210687bbe8f896e6b973950ddbea03c1f804 Signed-off-by: Piotr Milewski

Drop zun and kuryr

2026-04-27T05:18:03+00:00

Zun is broken in 2026.1, it has been released broken and there are no reviews on the patch to fix it [1]. [1]: https://review.opendev.org/c/openstack/zun/+/982362 Depends-On: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/986150 Change-Id: I8ced621754d03c44b7672dd94fc3d7d2173ac734 Signed-off-by: Michal Nasiadka

Merge "horizon: add Valkey session cache backend and prefer it"

2026-04-16T21:17:18+00:00

Merge "Add OpenStack Network Exporter for Prometheus"

2026-04-16T15:54:22+00:00

horizon: add Valkey session cache backend and prefer it

2026-04-16T10:18:30+00:00

Horizon may display "Something went wrong!" when a memcached node becomes unavailable. Add support for Valkey as a Horizon session cache backend using django-redis with Sentinel. Valkey is now preferred when enabled. If Valkey is not enabled, Memcached is used instead. This improves Horizon availability when cache nodes fail. Depends-On: https://review.opendev.org/c/openstack/kolla/+/980779 Closes-Bug: #2093414 Change-Id: I771754acc0febb466f4f921fdf29946d9e54f0c3 Signed-off-by: Piotr Milewski