Created attachment 1656540 [details] Service account dropdown does not retain selection when toggling between Edit YAML and Edit Form Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: Create a new project if you don't have one 2. Navigate to Operators > OperatorHub 3. Make sure the project from step 1 is the currently active namespace 3. Filter by keyword "Prometheus" 4. Click the Prometheus Operator tile 5. Click 'Install' in the resulting modal 6. Make sure the following options are selected: - Installation Mode: A specific namespace on the cluster (make sure the project from step 1 is selected) - Update Channel: beta - Approval Strategy: Automatic 7. Click "Subscribe" 8. Navigate to Operators > Installed Operators 9. Click the "Prometheus Operator" link in the installed operators list 10. In the Provided APIs section, click "Create Instance" in the first card "Prometheus" 11. Click "Edit Form" in the top right 12. Scroll down to the "Service Account" field and select "default" from the dropdown 13. Click "Edit YAML" in the top right 14. Find the "serviceAccountName" field in the YAML editor and ensure it matches the selection from the form: "default" 16. Click "Edit Form" in the top right 17. Scroll down to the Service Account field Actual results: There is no selection in the service account field and it displays the placeholder text "Select ServiceAccount" Expected results: The Service Account field should retain the selected value when switching between Edit YAML and Edit Form modes.
Perform the steps according to comment #0 and then switching between Edit YAML and Edit Form modes, the Service Account field will retain the selected value "default". 4.5.0-0.ci-2020-03-03-032706
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/RHBA-2020:2409