Workflow limit does not limit on AWX 21.6.0
Please confirm the following
- I agree to follow this project's code of conduct.
- I have checked the current issues for duplicates.
- I understand that AWX is open source software provided for free and that I might not receive a timely response.
Bug Summary
Hi, I'm not really sure if this is a bug or if it's the normal behavior, but I can't really find what is the expected behavior in the documentation.
I'm creating a Workflow Job Template with a limit set on a specific host, calling a job template which has a limit set on a group. The job template is then applied to the all group (which is very surprising as you have defined a more restricted set just before when launching the workflow).
This behavior does not occur when the job template has the checkbox “prompt on launch” checked. I guess it's the same problem as #11967 which was closed as being marked as a duplicate of #11284 . I guess the explanation which is the best according to my case is the one on this comment : https://github.com/ansible/awx/issues/11284#issuecomment-961913484 .
AWX version
21.6.0
Select the relevant components
- UI
- API
- Docs
- Collection
- CLI
- Other
Installation method
minikube
Modifications
no
Ansible version
2.15.5
Operating system
Debian 11
Web browser
No response
Steps to reproduce
In case it's not the same, I will explain the steps I did to face this issue :
Create a group in an inventory with various hosts

Create a job template with a limit on the group with the prompt on launch checkbox unchecked

Launch the job template

Create a workflow job template with a limit set to whichever host you want

Set a node calling the job template

Actual results
Looks like it's limited to localhost

- This is where it's beginning to be strange to me and does not really make sense : the job template was applied to the limit defined in the job template, and not the one in the workflow template

Expected results
Whereas if on step 2 I check the prompt on launch checkbox and follow step 3/4/5 the workflow was launched on the limit defined on the workflow template job (which is what I want).


I except to have this result whether the checkbox is checked or not, or at least a warning telling me it will not limit to what I wrote in the limit text.
Additional information
I have found the following comment on another issue which says
As noted in the docs, the workflow limit "provide[s] a host pattern to further constrain the list of hosts that will be managed or affected by the workflow. This limit is applied to all job template nodes that prompt for a limit."
I've read the documentation on https://docs.ansible.com/ansible-tower/3.8.0/html/userguide/workflow_templates.html and I can't find this information. Where is it located?
This strange behavior lead us to delete half of our application instance when we wanted to delete only one (which was defined in limit text on workflob template job). Maybe a clear part on the documentation, or a warning (or something else? I have no idea what) telling when creating the workflow job template that the limit will not be applied would be best.
I'm not really sure this is really clear, let me know if you need some more information.
Source: ansible/awx