You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you have more than one deployment define in an inventory file, you can select the hosts to run the playbooks against with something like ipareplicas:&{{ run_here }}.
The problem is that when defining the server list for both ipareplica and ipaclient roles forces a query to the inventory file without the filter in place.
See the tasks from ipareplica:
- name: Install - Set ipareplica_serversansible.builtin.set_fact:
ipareplica_servers: "{{ groups['ipaservers'] | list }}"when: groups.ipaservers is defined and ipareplica_servers is not defined
- name: Install - Set ipareplica_servers from cluster inventoryansible.builtin.set_fact:
ipareplica_servers: "{{ groups['ipaserver'] | list }}"when: ipareplica_servers is not defined and groups.ipaserver is defined
The workaround for this issue is to have ipareplica_servers and ipaclient_servers set.
Today, it is not a huge issue as a single deployment is expected, but with IPA-to-IPA migration in place, we may face the same issue as multiple deployments in one inventory file may become more common.
The text was updated successfully, but these errors were encountered:
rjeffman
changed the title
ipareplica and ipaclient fail when there are more than on deployment set in an inventory file
ipareplica and ipaclient fail when there are more than one deployment set in an inventory file
Dec 30, 2024
When you have more than one deployment define in an inventory file, you can select the hosts to run the playbooks against with something like
ipareplicas:&{{ run_here }}
.The problem is that when defining the server list for both
ipareplica
andipaclient
roles forces a query to the inventory file without the filter in place.See the tasks from
ipareplica
:The workaround for this issue is to have
ipareplica_servers
andipaclient_servers
set.Today, it is not a huge issue as a single deployment is expected, but with IPA-to-IPA migration in place, we may face the same issue as multiple deployments in one inventory file may become more common.
The text was updated successfully, but these errors were encountered: