Bug 1978542

Summary: [4.8] [External Mode] After upgrading to OCS 4.8, ocs-external-storagecluster-ceph-rbd-thick SC doesn't exist
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Vijay Avuthu <vavuthu>
Component: ocs-operatorAssignee: arun kumar mohan <amohan>
Status: CLOSED NOTABUG QA Contact: Elad <ebenahar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.8CC: bniver, etamir, jrivera, madam, muagarwa, nberry, ocs-bugs, odf-bz-bot, sostapov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-20 16:07:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vijay Avuthu 2021-07-02 06:24:27 UTC
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/

Comment 2 Neha Berry 2021-07-05 07:01:32 UTC
@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?

Comment 3 Mudit Agarwal 2021-07-05 10:35:02 UTC
As discussed, I am moving this out of 4.8 https://chat.google.com/room/AAAAREGEba8/iSnDygYVmKY

Comment 5 Mudit Agarwal 2021-09-24 16:48:56 UTC
Thick provisioning is out of 4.9

Comment 6 Jose A. Rivera 2022-01-20 16:07:58 UTC
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.