Is the update really required step to reproduce? In other words does this work on 5.10.3 without the update?
As far as I know, this is NOT update related, just something we broke in 5.10.3
Hi Tina , I tried to recreate this BZ on https://10.8.199.40/. Created a dynamic dialog with textarea (shveta_survey) On ordering service catalog the parameter passed in text area does not show in ansible tower. Please check the appliance once .
Hi Shveta, The dialog is working properly. If you look at the service -> requests page, and select a request, you'll see the dialog values are present, The dialog values were missing when this issue was initially reported. It looks like the error is caused "PROMPT ON LAUNCH" not being set as shown below: r/share/ruby/drb/drb.rb:1664:in `block in main_loop' [----] E, [2019-06-06T14:38:56.120760 #18784:a8a2528] ERROR -- : Q-task_id([r4_service_template_provision_task_4]) <AEMethod provision> Template shveta-survey launching failed. Reason: 'PROMPT ON LAUNCH' is required for the following fields: limit (MiqException::MiqOrchestrationProvisionError) [----] I, [2019-06-06T14:38:56.177173 #18784:622f50] INFO -- : Q-task_id([r4_service_template_provision_task_4]) <AEMethod [/ManageIQ/AutomationManagement/AnsibleTower/Service/Provisioning/StateMachines/Provision/provision]> Endin Let me know if you have any questions. Thanks, Tina
I can see the parameters passed in service request page . Thanks. Do I also need to Verify it from ansible tower UI ? I don't see it in Ansible tower job playbook .
Hi Shveta, As we discussed, the prompt on launch checkbox needed to be set for the limit setting. Also, the limit field needs to contain an ip address of a machine in the inventory. The service provisioned successfully once we fixed those 2 settings. Let me know if you have any questions. Thanks, Tina
Created attachment 1578079 [details] In CFME
Created attachment 1578080 [details] In ansible tower Parameters are passed. Verified in 5.10.5.1.20190528153822_0501085
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/RHSA-2019:1429