@shirshfe I am unable to reproduce this bug. Can you please provide the steps to reproduce it?
(In reply to ialmeida from comment #1) > @shirshfe > > I am unable to reproduce this bug. Can you please provide the steps to > reproduce it? U will not see rgw StorageClass on AWS cluster... either u can use QE's setup or for quick testing u can create vSphere cluster using ClusterBot on Slack. use command: launch <OCP VERSION> vsphere ex: launch 4.12.0-0.nightly-2023-03-06-151602 vsphere
FIXED OC version: Client Version: 4.12.0-202208031327 Kustomize Version: v4.5.4 Server Version: 4.13.0-0.nightly-2023-03-23-204038 Kubernetes Version: v1.26.2+dc93b13 OCS verison: ocs-operator.v4.13.0-110.stable OpenShift Container Storage 4.13.0-110.stable Succeeded Cluster version NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.13.0-0.nightly-2023-03-23-204038 True False 2d Cluster version is 4.13.0-0.nightly-2023-03-23-204038 Rook version: rook: v4.13.0-0.8eff918ef2611ffdedd08f9bceeab8b1423bee38 go: go1.19.6 Ceph version: ceph version 17.2.5-75.el9cp (52c8ab07f1bc5423199eeb6ab5714bc30a930955) quincy (stable) Video recording: https://url.corp.redhat.com/rgw-obc-fix-recording
RDT not needed as this was introduced and fixed on 4.13 itself...
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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement and 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-2023:3742
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days