Rundeck v5.7.0-20241021 does not process group_names correctly

[magnum31415]

1.- Executing from comand line a playbook that prints group_names for a host, in example de-web-95 it shows belogs to two groups: web & redhat (correct!!)

2.- Executing from rundeck the SAME playbook that prints group_names for de-web-95 it shows belogs to ONLY ONE groups: redhat

Playbook

- name: Host belongs to this ansible groups in the inventory
  debug:
    var: group_names

Inventory

all:
children:
web:
hosts:
de-web-95: {}
redhat:
hosts:
de-web-95 : {}

Can anybody exaplin how to solve this issue. If it is possible with an example...

[magnum31415]

There is any prevision to solve it?

[MegaDrive68k]

Hi, can you test setting gather facts = true in the Ansible model source? It works here in my environment.

thanks.

[jimr6007]

Hi @MegaDrive68k

I reported this here as well: https://groups.google.com/g/rundeck-discuss/c/gLWqF2uU5zo

It will work with gather_facts=True because that triggers the full playbook run (gather-hosts)

the awesome thing would be if groups are processed correctly when gather_facts=False and therefore, we can continue to take advantage of the HUGE cpu load/time savings we get by only running the ansible-inventory command to generate nodes instead of a full ansible-playbook run.

it looks like a List data structure is being used (does not allow duplicate items) and that is the cause of the problem.

any idea when a version of the plugin with the needed code changes might be ready?

[ibishop100]

I'd just like to confirm the issue with nested groups still occurs in Rundeck 5.14.1 with the included Ansible plugin 4.0.11-SNAPSHOT and the 4.0.10 release.

Changing gather facts to true 'fixes' it, however for our uses, we'd much rather not have gather facts on.

I notice there is at least one fork with a potential fix here: madsi1m@4a550f4

I haven't tried it yet, but might...

[jeroendev-one]

Yes, still bugged...