Bug 1677548

Summary: [RFE] Use Ansible Runner for Ansible Embedded Integration
Product: Red Hat CloudForms Management Engine Reporter: Loic Avenel <lavenel>
Component: AutomateAssignee: Nick LaMuro <nlamuro>
Status: CLOSED ERRATA QA Contact: Satyajit Bulage <sbulage>
Severity: high Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: high    
Version: unspecifiedCC: dmetzger, lavenel, mkanoor, obarenbo, simaishi, tfitzger
Target Milestone: GAKeywords: RFE
Target Release: 5.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-12 13:35:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Bug Depends On: 1734129, 1734902, 1739015    
Bug Blocks: 1672689, 1677575, 1678132, 1678135, 1692941, 1722197    

Description Loic Avenel 2019-02-15 08:34:45 UTC
[RFE] Use Ansible Runner for Ansible Embedded Integration

Comment 1 Dave Johnson 2019-02-15 09:01:10 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set the severity to Low.

Comment 4 Satyajit Bulage 2019-09-09 12:40:36 UTC
Able to see all of the BZ's(depends on and blockers) are verified.
The Ansible Runner functionality is also working fine, cross-checked with all of the "Credentials" options present.
By ordering playbook which accommodates respective credentials.

Able to see all required attributes are gathered which helps to execute Automate domain Ansible Methods.
Based on Ansible Runner functionality, I am verifying this BZ.

Verified Version: 5.11.0.23.20190904213640_d113674

Comment 6 errata-xmlrpc 2019-12-12 13:35:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:4199