openstack/openstack-ansible-os_octavia
Code Issues Proposed changes

Ensure that first/last host detection is deterministic

Browse Source 
With ansible-core 2.16 a breaking changes landed [1] to some filters
making their result returned in arbitrary order. With that, we were
relying on them to always return exactly same ordered lists.

With that we need to ensure that we still have determenistic behaviour
where this is important.

[1] https://github.com/ansible/ansible/issues/82554

Change-Id: I6c14dc2d153995b4045e34318e5e857ddad42019
This commit is contained in:
Dmitriy Rabotyagov 2024-07-22 16:11:20 +02:00
parent 92e069f148
commit 56a41ab760
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
vars/main.yml
View File

@ -16,7 +16,7 @@
_octavia_is_first_play_host: >- _octavia_is_first_play_host: >-
{{ {{
(octavia_services['octavia-api']['group'] in group_names and (octavia_services['octavia-api']['group'] in group_names and
inventory_hostname == (groups[octavia_services['octavia-api']['group']] | intersect(ansible_play_hosts)) | first) | bool inventory_hostname == (groups[octavia_services['octavia-api']['group']] | select('in', ansible_play_hosts)) | first) | bool
}} }}
_octavia_oslomsg_rpc_vhost_conf: >- _octavia_oslomsg_rpc_vhost_conf: >-