Bug 2189551

Summary: StorageClassClaim created in a different namespace than fusion-storage is not working
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Filip Balák <fbalak>
Component: odf-managed-serviceAssignee: Ohad <omitrani>
Status: CLOSED NOTABUG QA Contact: Neha Berry <nberry>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.12CC: ocs-bugs, odf-bz-bot
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: 2023-04-25 15:37:44 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 Filip Balák 2023-04-25 15:02:30 UTC
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/

Comment 1 Ohad 2023-04-25 15:14:21 UTC
@fbalak 
StorageClassClaims are cluster-scoped resources, this bug does not make sense in that context. 
Could you please clarify?

Comment 2 Filip Balák 2023-04-25 15:35:24 UTC
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.

Comment 3 Ohad 2023-04-25 15:47:07 UTC
> 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