openstack/openstack-ansible-os_masakari
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: If2331f6c92e30613c67d2b320ff493ba48c7ce4a
This commit is contained in:
Dmitriy Rabotyagov 2024-07-22 15:53:33 +02:00
parent 25c002ed7d
commit f872fe8a7d
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 @@
_masakari_is_first_play_host: >-
{{
(masakari_services['masakari-api']['group'] in group_names and
inventory_hostname == (groups[masakari_services['masakari-api']['group']] | intersect(ansible_play_hosts)) | first) | bool
inventory_hostname == (groups[masakari_services['masakari-api']['group']] | select('in', ansible_play_hosts)) | first) | bool
}}
_masakari_oslomsg_rpc_vhost_conf: >-
{{