openstack/openstack-ansible-os_trove
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: Iacbddd8bc0c5f7d38ca85a3ef4df536ea4f66782
This commit is contained in:
Dmitriy Rabotyagov 2024-07-22 16:25:13 +02:00
parent 5b668b373c
commit 9a73e4a0b8
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
vars/main.yml
View File

@ -16,12 +16,12 @@
_trove_is_first_play_host: >-
{{
(trove_services['trove-api']['group'] in group_names and
inventory_hostname == (groups[trove_services['trove-api']['group']] | intersect(ansible_play_hosts)) | first) | bool
inventory_hostname == (groups[trove_services['trove-api']['group']] | select('in', ansible_play_hosts)) | first) | bool
}}
_trove_conductor_is_first_play_host: >-
{{
(trove_services['trove-conductor']['group'] in group_names and
inventory_hostname == (groups[trove_services['trove-conductor']['group']] | intersect(ansible_play_hosts)) | first) | bool
inventory_hostname == (groups[trove_services['trove-conductor']['group']] | select('in', ansible_play_hosts)) | first) | bool
}}
_trove_oslomsg_rpc_vhost_conf: >-