Description of problem: When launching a service dialog through a button utilizing ansible playbooks, none of the values that the user inputs utilizing the button are passed through. Only the defaults of the Service Catalog Item are passed through, overwriting anything the user might have changed. Opened as an offshoot of https://bugzilla.redhat.com/show_bug.cgi?id=1602883 The hotfix fixed the encryption problem, but seems to have resulted in this. Version-Release number of selected component (if applicable): 5.9.3.4-2 (hotfix build) How reproducible: Always Steps to Reproduce: 1. Launch playbook catalog item from button 2. 3. Actual results: No user input information goes through Expected results: Service Dialog passes vars through Additional info: An example of this is here: SSH password: PLAY [all] ********************************************************************* TASK [Gathering Facts] ********************************************************* ok: [localhost] TASK [debug] ******************************************************************* ok: [localhost] => { "msg": "This password is password" } PLAY RECAP ********************************************************************* localhost : ok=2 changed=0 unreachable=0 failed=0 The password should've been different and the host should've not been localhost, as I had it set to target machine.
On Reproducer environment, I re-created issue with simple button calling a playbook and dialog. The values that I entered were NOT honored and the default values were used. Building a 5.9.3.4 environment and will run the same tests. I want to determine if this works before the hot fix was applied.
I tested with 5.9.3.4 and user entered values are honored. The button is working without any hot fixes.
I can confirm that it worked before the hotifx was applied. I have another appliance that is on 5.9.3 without the hotfix, and it works as expected (barring the decryption that the hotfix addressed)
Please verify with released 5.9.4.
Hello Dennis, It seems that buttons are working again, but the bug that I originally opened this up for, https://bugzilla.redhat.com/show_bug.cgi?id=1602883 seems to have regressed. "msg": "This is a test for list variables ********." As you can see, the variable is now ******** again instead of if being decrypted like it was in that previously mentioned bug.
Hi David, Please re-open https://bugzilla.redhat.com/show_bug.cgi?id=1602883 if you feel the issue has not been resolved. If possible, please supply a reproducer environment. Thanks, Tina
Hi David, Are you okay if we close this ticket? Thanks, Tina
Sure