Description of problem: Once a Ansible Playbook Service Dialog is built, it has default parameters, which can be overridden at "ordering" time. We are not honoring the parameters entered by the user at ordering time. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create an Ansible Playbook Service with extra vars 2. Order the Service and update one of the extra vars 3. When the playbook is executed in Embedded Ansible it should use the updated parameters. Actual results: Uses the original values Expected results: Should use the updated value Additional info: It seems this happens because of our mixing of symbols and strings. :extra_vars=>{:user=>"root", :pkg=>"httpd", :sleep=>"10", :host=>"localhost", "user"=>"root", "pkg"=>"abrt", "sleep"=>"97", "host"=>"localhost"}
https://github.com/ManageIQ/manageiq/pull/14824
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/228a0c6dbcef128d3762514ef52885b113f9eb0c commit 228a0c6dbcef128d3762514ef52885b113f9eb0c Author: Bill Wei <bilwei> AuthorDate: Thu Apr 20 11:50:12 2017 -0400 Commit: Bill Wei <bilwei> CommitDate: Thu Apr 20 14:08:32 2017 -0400 Use HashWithIndifferentAccess for job options https://bugzilla.redhat.com/show_bug.cgi?id=1444107 app/models/service_ansible_playbook.rb | 2 +- spec/models/service_ansible_playbook_spec.rb | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
Verified in 5.9.0.3.20171017182919_5f3a0ce. Parameters entered by the user at ordering time are used during a service provisioning.