Description of problem (please be detailed as possible and provide log snippests): After upgrading to OCS 4.8, ocs-external-storagecluster-ceph-rbd-thick SC doesn't exist in external cluster. oc get csv NAME DISPLAY VERSION REPLACES PHASE ocs-operator.v4.8.0-433.ci OpenShift Container Storage 4.8.0-433.ci ocs-operator.v4.7.2 Succeeded $ Version of all relevant components (if applicable): cluster upgraded to 4.8.0-433.ci Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? NA Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? 1/1 Can this issue reproduce from the UI? not tried If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. upgrade OCS from 4.7.2 to 4.8.0-433.ci ( external mode ) 2. after upgrade succeeded, check ocs-external-storagecluster-ceph-rbd-thick sc exists Actual results: ocs-external-storagecluster-ceph-rbd-thick storageclass doesn't exist oc get sc NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE ocs-external-storagecluster-ceph-rbd openshift-storage.rbd.csi.ceph.com Delete Immediate true 19h ocs-external-storagecluster-ceph-rgw openshift-storage.ceph.rook.io/bucket Delete Immediate false 19h ocs-external-storagecluster-cephfs openshift-storage.cephfs.csi.ceph.com Delete Immediate true 19h openshift-storage.noobaa.io openshift-storage.noobaa.io/obc Delete Immediate false 19h thin kubernetes.io/vsphere-volume Delete Immediate false 20h Expected results: ocs-external-storagecluster-ceph-rbd-thick SC should exist Additional info: Job: https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/1278/consoleFull must gather logs: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j023vu1ce33-ua/j023vu1ce33-ua_20210701T090317/logs/failed_testcase_ocs_logs_1625137095/test_upgrade_ocs_logs/
@mudit rbd thick is dev preview in 4.8 so do we really want to continue creating the SC as part of deployment of OCS storagecluster?
As discussed, I am moving this out of 4.8 https://chat.google.com/room/AAAAREGEba8/iSnDygYVmKY
Thick provisioning is out of 4.9
It looks like this BZ is directly related to the thick provisioning Epic, which has made it into ODF 4.10: https://issues.redhat.com/browse/RHSTOR-2068 Reading the epic tells me that the absence of the thick provisioned StorageClass is absolutely intentional. As such, closing this as NOTABUG.