From 9a73e4a0b854a07b308d17a795e24afd79d0dff8 Mon Sep 17 00:00:00 2001 From: Dmitriy Rabotyagov Date: Mon, 22 Jul 2024 16:25:13 +0200 Subject: [PATCH] Ensure that first/last host detection is deterministic 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 --- vars/main.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/vars/main.yml b/vars/main.yml index d27d1b2..a2099cf 100644 --- a/vars/main.yml +++ b/vars/main.yml @@ -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: >-