Description of problem : ------------------------- After user enters the details to all the required parameters for creating a new backing store and click on create button , it directs to blank page and the new backing store was not created . [root@localhost recheck-11]# oc get backingstore -n openshift-storage NAME TYPE PHASE AGE noobaa-default-backing-store s3-compatible Ready 22h Version of all relevant components : ------------------------------------- OCP : 4.11.0-0.nightly-2022-05-10-045003 ODF : 4.11.0-67 Steps to Reproduce: -------------------- 1. Direct to Backing store dashboard. 2. Click on "create backing store" bucket. 3. Fill in the required parameters and click on create. Actual results: ------------------ A blank page is displayed when clicked on create button and a new backing store is not created. Expected results: ------------------ The page should direct to backing store dashboard and backing store should be created.
Validated the fix using cluster with the following versions :- OCP : [root@localhost bugs]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.0-0.nightly-2022-06-06-025509 True False 92m Cluster version is 4.11.0-0.nightly-2022-06-06-025509 ODF : [root@localhost bugs]# oc get csv odf-operator.v4.11.0 -o yaml -n openshift-storage| grep full_version full_version: 4.11.0-89 f:full_version: {} ----------------------------------------------------------- **Observations: (a) After clicked on the create button for new backing store , it didn't lead to a blank page but detail page of newly created backing store . (b) The newly created backing store stays in creating state for more than 20 minutes . Since this is a UI issue moving it to verified and will raise a bug (b) observation if a genuine issue is found . Thanks Mugdha
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 (Important: Red Hat OpenShift Data Foundation 4.11.0 security, enhancement, & bugfix 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/RHSA-2022:6156