Description of problem: When creating a service catalog item that first provisions either a vCenter or RHEV VM and then launches an Ansible playbook with extra vars, CloudForms does not pass the extra vars to Ansible Tower. Version-Release number of selected component (if applicable): CFME Version 5.6.0.9-rc2.20160531154046_b4e2f6d How reproducible: always Steps to Reproduce: 1. Create a service catalog item that provisions either a vCenter or RHEV VM using /Service/Provisioning/StateMachines/ServiceProvision_Template/CatalogItemInitialization as the provisioning entry point. 2. Modify the provisioning workflow in Infrastructure->Vm->Provisioning->StateMachines->VMProvision_VM->Provision_VM from Template by adding an "Ansible Job" post provisioning step that launches your specific Ansible Playbook. Example: /ConfigurationManagement/AnsibleTower/RunTemplates/STIG Actual results: CloudForms correctly provisions the vCenter or RHEV VM and Ansible Tower launches the correct playbook. However no extra vars are sent from CloudForms to Ansible Tower. Expected results: CloudForms provisions the vCenter or RHEV VM and the Ansible Tower job with all the extra vars sent from CloudForms is executed on the newly provisioned VM. Additional info: I spoke with Madhu Kanoor about this issue, so he is familiar with this bugzilla.
https://github.com/ManageIQ/manageiq/pull/9306
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/cdd9ab23185e42c2876769729027f3a409070499 commit cdd9ab23185e42c2876769729027f3a409070499 Author: Madhu Kanoor <mkanoor> AuthorDate: Mon Jun 20 15:35:18 2016 -0400 Commit: Madhu Kanoor <mkanoor> CommitDate: Mon Jun 20 15:35:18 2016 -0400 Use Ansbile extra vars defined in options hash https://bugzilla.redhat.com/show_bug.cgi?id=1348232 Users create service dialog to collect ansible extra vars these get stored in the options hash by CatalogItemInitialization. The Automate method wasn't looking at the options hash to get the ansible extra vars. .../Job.class/__methods__/launch_ansible_job.rb | 17 ++++++++-- .../method_validation/launch_ansible_job_spec.rb | 37 ++++++++++++++++++++++ 2 files changed, 51 insertions(+), 3 deletions(-)
https://github.com/ManageIQ/manageiq/pull/9426
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/b486f599834e576b4dbc5e8b2a010beb09303c12 commit b486f599834e576b4dbc5e8b2a010beb09303c12 Author: Madhu Kanoor <mkanoor> AuthorDate: Thu Jun 23 17:46:54 2016 -0400 Commit: Madhu Kanoor <mkanoor> CommitDate: Thu Jun 23 17:46:54 2016 -0400 Ansible extra variables missing when called from button https://bugzilla.redhat.com/show_bug.cgi?id=1348232 PR #9306 broke the passing in of variables from button. .../StateMachines/Job.class/__methods__/launch_ansible_job.rb | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
Fixed in PR https://github.com/ManageIQ/manageiq/pull/9426
Please provide more steps to recreate this issue .b
I think you want to follow the steps outlined in: Launch an Ansible Job Template from a button in ManageIQ http://talk.manageiq.org/t/launching-ansible-tower-job-templates-from-manageiq/1394
Assigning to Pavol for Ansible .
Hi Pavol, Do you still need info from me. Thanks, Madhu