Description of problem (please be detailed as possible and provide log snippests): Error creating storageclass claim in a test namespace on consumer. The PHASE of the storage class claim is empty. Storage class is not created. $ oc get storageclassclaim -n test-project NAME STORAGETYPE PHASE test-storageclassclaim-rbd sharedfilesystem test-storageclassclaim-rbd1 blockpool $ oc get sc -n test-project NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE gp2 (default) kubernetes.io/aws-ebs Delete WaitForFirstConsumer true 5h14m gp2-csi ebs.csi.aws.com Delete WaitForFirstConsumer true 5h14m gp3-csi ebs.csi.aws.com Delete WaitForFirstConsumer true 5h14m ocs-storagecluster-ceph-rbd openshift-storage.rbd.csi.ceph.com Delete Immediate true 4h46m ocs-storagecluster-cephfs openshift-storage.cephfs.csi.ceph.com Delete Immediate true 4h46m Error in ocs-operator logs: {"level":"info","ts":1654072118.198573,"logger":"controller.storageclassclaim","msg":"Reconciling StorageClassClaim.","reconciler group":"ocs.openshift.io","reconciler kind":"StorageClassClaim","name":"test-storageclassclaim-rbd","namespace":"test-project","StorageClassClaim":"test-project/test-storageclassclaim-rbd"} {"level":"error","ts":1654072118.1986465,"logger":"controller.storageclassclaim","msg":"Reconciler error","reconciler group":"ocs.openshift.io","reconciler kind":"StorageClassClaim","name":"test-storageclassclaim-rbd","namespace":"test-project","error":"no StorageCluster found","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:266\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:227"} must-gather logs - http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/jijoy-j1-c1/jijoy-j1-c1_20220601T043509/logs/testcases_1654079214/ ============================================================== Version of all relevant components (if applicable): $ oc get csv NAME DISPLAY VERSION REPLACES PHASE mcg-operator.v4.11.0 NooBaa Operator 4.11.0 mcg-operator.v4.10.2 Succeeded ocs-operator.v4.11.0 OpenShift Container Storage 4.11.0 ocs-operator.v4.10.2 Succeeded ocs-osd-deployer.v2.0.2 OCS OSD Deployer 2.0.2 ocs-osd-deployer.v2.0.1 Succeeded odf-csi-addons-operator.v4.11.0 CSI Addons 4.11.0 odf-csi-addons-operator.v4.10.2 Succeeded odf-operator.v4.11.0 OpenShift Data Foundation 4.11.0 odf-operator.v4.10.2 Succeeded ose-prometheus-operator.4.10.0 Prometheus Operator 4.10.0 ose-prometheus-operator.4.8.0 Succeeded route-monitor-operator.v0.1.418-6459408 Route Monitor Operator 0.1.418-6459408 route-monitor-operator.v0.1.408-c2256a2 Succeeded $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.10.15 True False 6h1m Cluster version is 4.10.15 $ oc get csv odf-operator.v4.11.0 -o yaml | grep full_version full_version: 4.11.0-85 ============================================================= Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Yes. Cannot create StorageClassClaim. Is there any workaround available to the best of your knowledge? 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? Yes Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Create a namespace "test-project" on consumer cluster. 2. Create StorageClassClaim on consumer cluster namespace "test-project". Example yaml: apiVersion: ocs.openshift.io/v1alpha1 kind: StorageClassClaim metadata: name: test-storageclassclaim-cephfs1 spec: type: sharedfilesystem 3. Verify the phase of the StorageClassClaim 4. Verify new storage class is created Actual results: The phase of the StorageClassClaim is empty. New StorageClass is not created. Expected results: Phase of the StorageClassClaim should be Ready. New StorageClass should be created. Additional info:
Will this be resolved with the fix for BZ #2092372?
Marking this as verified because the current issue in creating storageclassclaim is different from the issue initially reported in the bug. Creation of storageclassclaim is tested again as described in https://bugzilla.redhat.com/show_bug.cgi?id=2092372#c5 Storageclassclaims with type "sharedfilesystem" are reaching Ready phase. But there are errors in the ocs-operator logs which is different from the issue fixed in this bug. Storageclassclaims with type "blockpool" is not reaching Ready phase. There are errors in ocs-operator logs on both consumer and provider but it is different from the issue fixed in this bug. The error "no StorageCluster found" is no longer present. Test result is updated in the bug https://bugzilla.redhat.com/show_bug.cgi?id=2092372#c5 Tested in version: ocs-operator.v4.11.0 ocs-osd-deployer.v2.0.2 odf-csi-addons-operator.v4.11.0 odf-operator.v4.11.0 ODF full version 4.11.0-90 OCP 4.10.16
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