+++ This bug was initially created as a clone of Bug #1845817 +++ Description of problem: on EtcdBackup creation form, 'AWS Secret' descriptor always shows a loading ... icon until user select one secret from dropdown Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-06-09-201617 How reproducible: Always Steps to Reproduce: 1. subscribe etcd operator and wait until successfully subscribed 2. create EtcdBackup instance via Operators -> Installed Operators -> etcd -> click on 'etcd Backup' -> click 'Create EtcdBackup' button Actual results: 2. the 'AWS Secret' dropdown always shows loading ... until user select one secret from dropdown - description: >- The name of the secret object that stores the AWS credential and config files. displayName: AWS Secret path: s3.awsSecret x-descriptors: - 'urn:alm:descriptor:io.kubernetes:Secret' Expected results: 2. If secrets are loaded completely, we should not show a loading icon ... any more Additional info: --- Additional comment from jhadvig on 2020-06-11 07:46:01 UTC --- The problem is that use the `<aws-secret>` placeholder as a selectedKey for the ListDropdown component, which doesn't exist. For the fix we should update the ListDropdown so when the key does not exist no item will be selected, to avoid loading icon.
*** Bug 1848383 has been marked as a duplicate of this bug. ***
PR pending
PR is open, awaiting cherry pick approval.
Tested on OCP 4.5 cluster with payload 4.5.0-0.nightly-2020-08-08-162221. 1. subscribe etcd operator and wait until successfully subscribed 2. create EtcdBackup instance via Operators -> Installed Operators -> etcd -> click on 'etcd Backup' -> click 'Create EtcdBackup' button. The 'AWS Secret' dropdown works well now. The bug is fixed.
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 (OpenShift Container Platform 4.5.6 bug fix update), 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:3330