Created attachment 1422657[details]
ScreenShot retire
Description of problem:
If an ansible playbook is used to retire, a user cannot choose if he wants resources removed before or after the playbook runs. It always switches back to "NO" no matter what the user chooses. If retirement is done without the ansible playbook the correct value is saved in the UI.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Create a catalog item
2. Choose ansible playbook for retirement
3. Try to change the value for "Remove Resources" and save
4. The value will flip back to "NO"
Actual results:
Remove Resources flips back to NO
Expected results:
Should save the chosen value.
Additional info:
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:0212
Created attachment 1422657 [details] ScreenShot retire Description of problem: If an ansible playbook is used to retire, a user cannot choose if he wants resources removed before or after the playbook runs. It always switches back to "NO" no matter what the user chooses. If retirement is done without the ansible playbook the correct value is saved in the UI. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a catalog item 2. Choose ansible playbook for retirement 3. Try to change the value for "Remove Resources" and save 4. The value will flip back to "NO" Actual results: Remove Resources flips back to NO Expected results: Should save the chosen value. Additional info: