openstack/openstack-ansible-os_tacker
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: I93deb022cdd83003f92e54a523f6db833ce5bf97
This commit is contained in:
Dmitriy Rabotyagov 2024-07-22 16:19:17 +02:00
parent d35b74cc7c
commit 436089d596
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 @@
# limitations under the License. # limitations under the License.
_tacker_is_first_play_host: >- _tacker_is_first_play_host: >-
{{ ('tacker_all' in group_names and inventory_hostname == (groups['tacker_all'] | intersect(ansible_play_hosts)) | first) | bool }} {{ ('tacker_all' in group_names and inventory_hostname == (groups['tacker_all'] | select('in', ansible_play_hosts)) | first) | bool }}
_tacker_oslomsg_rpc_vhost_conf: >- _tacker_oslomsg_rpc_vhost_conf: >-
{{ {{