Description of problem: Storageclasslaim can be created in fusion-storage namespace but not in a custom namespace created for the storageclassclaim. Version-Release number of selected component (if applicable): rosa 4.11.37 ocs-client-operator.v4.13.0-168.stable How reproducible: 3/3 Steps to Reproduce: 1. Create a Fusion aaS consumer in fusion-storage namespace. 2. Create a new namespace test-namespace. 3. Create a storageclassclaim that uses test-namespace namespace: apiVersion: ocs.openshift.io/v1alpha1 kind: StorageClassClaim metadata: name: storageclassclaim-test-cephblockpool spec: storageClient: name: storageclient namespace: test-namespace type: blockpool Actual results: Storageclass is not created and claim has no Phase: $ oc get storageclassclaim NAME STORAGETYPE STORAGEPROFILE STORAGECLIENTNAME STORAGECLIENTNAMESPACE PHASE ocs-storagecluster-ceph-rbd blockpool storageclient fusion-storage Ready ocs-storagecluster-cephfs sharedfilesystem storageclient fusion-storage Ready storageclassclaim-test-cephblockpool-1 blockpool storageclient test-namespace storageclassclaim-test-cephblockpool-14d blockpool storageclient fusion-storage Ready storageclassclaim-test-cephblockpool-2 blockpool storageclient test-namespace2 Expected results: Claim should be created correctly. Additional info: ocp must gather: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/sgatfane-c2425/sgatfane-c2425_20230425T015755/logs/testcases_1682433492/ocp_must_gather/
@fbalak StorageClassClaims are cluster-scoped resources, this bug does not make sense in that context. Could you please clarify?
Right, what I am configuring in: storageClient: name: storageclient namespace: test-namespace is storage namespace of the provider, correct? In that case this can be closed as not a bug.
> is storage namespace of the provider, correct? In that case this can be closed as not a bug. No this is the namespace where the client operator was installed, no matter where you want to use the storage class. And yes this is not a bug