Verified the BZ on AWS + RHCOS setup with following builds: OCP = 4.4.0-0.nightly-2020-03-19-075457 OCS = ocs-operator.v4.3.0-377.ci (4.30-rc2) Steps performed: 1. Ran deploy-with-olm.yaml to create 4.3 Operator 2. Installed subscription 3. Navigated to Installed Operator->StorageCluster and clicked on Create Storage Cluster 4. gp2 was selected as default SC, Size was 2TiB by default.( didnt change anything). I did not hit Bug 1812448 and default selection was honored. 5. Clicked on Create and Stotragecluster was created. YAML from UI ================== spec: storageDeviceSets: - config: {} count: 1 dataPVCTemplate: metadata: creationTimestamp: null spec: accessModes: - ReadWriteOnce resources: requests: storage: 2Ti storageClassName: gp2 <--- not NULL volumeMode: Block status: {} name: ocs-deviceset placement: {} portable: true replica: 3 resources: {} version: 4.3.0 Hence, moving this BZ to verified state in OCp 4.4. I did not encounter
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:0581