Bug 1757391 - No way of limiting AE Method type "Ansible Tower Job Template"
Summary: No way of limiting AE Method type "Ansible Tower Job Template"
Keywords:
Status: CLOSED DUPLICATE of bug 1757190
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.12.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.12.0
Assignee: Tina Fitzgerald
QA Contact: Nandini Chandra
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-01 11:44 UTC by mplesko
Modified: 2019-10-03 17:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-01 13:51:30 UTC
Category: Bug
Cloudforms Team: Ansible
Target Upstream Version:
Embargoed:
mfeifer: mirror+


Attachments (Terms of Use)
Screenshots (73.45 KB, application/zip)
2019-10-01 11:44 UTC, mplesko
no flags Details

Description mplesko 2019-10-01 11:44:35 UTC
Created attachment 1621379 [details]
Screenshots

Description of problem: I can create and use AE Method of type "Ansible Tower Job Template" but it'll always run against ENTIRE CloudForms inventory i.e. against all VMs of all providers.


Version-Release number of selected component (if applicable):
5.11.0.24

How reproducible:
Always

Steps to Reproduce:
1. In Automate > Explorer navigate to arbitrary AE Class and open tab "Methods"
2. Add a new method of type "Ansible Tower Job Template" (see screenshot 01 attached)
3. hook method to some AE instance
4. trigger instance

Actual results:
Job Template will run against entire CloudForms inventory!

Expected results:
User should be able to limit run to specific subset of the CloudForms inventory. It should be possible to specify the subset both:
- in a hard-coded way (sometimes you know your targets upfront)
- in a dynamic way. Subset of hosts should be read from state vars (because sometimes previous steps of the state machine create a new VM so the IP is not known upfront)

Additional info:

Comment 3 dmetzger 2019-10-01 13:51:30 UTC

*** This bug has been marked as a duplicate of bug 1757190 ***


Note You need to log in before you can comment on or make changes to this bug.