Using --limit working on hosts with multiple tasks

Hi,

I have the following set-up:

[hosts]
am[201:205]
am[301:305]

[matcher:children]
hosts

[memcached:children]
hosts

I’m expecting to be able to use “–limit matcher” and have only the tasks associated with “matcher” executed on the hosts but the tasks associated with “memcached” are also being executed. If I’m not doing something incorrectly how do I get only the tasks associated with “matcher” to execute on the hosts associated with both “matcher” and “memcached”?

Thanks.

Groups select hosts not tasks, I see the group “hosts” in both groups so this is correct.

Consider tagging or splitting your playbooks.

– Michael

I even tried the following:

[matcher:children]

am[201:205]
am[301:305]

[memcached:children]

am[201:205]
am[301:305]

I called the playbook with “–limit matcher”.

Stuff for “- hosts: matcher_memcached” still executed.

No need to respond if this is expected. I will look into tags or splitting.

Thanks for the response, especially so quickly on the weekend.

Mike

Typo…

Stuff for “- hosts: memcached” still executed.

Still as designed…

– Michael

the group with children have to have child groups entries not hosts , not child hosts