Description of problem:
For hosted client in 'Connected' status and storageclasses added, Storageclaims were stuck at 'Intializing' status until networkpolicy was added at provider side for the hcp cluster. And after adding the networkpolicy it got stuck at 'Configuring' status.

networkpolicy:
kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
name: openshift-storage-egress
namespace: clusters-hcp416-bm3-1a
uid: 6c338bce-cb27-47ff-a08f-566f9fa42e6c
resourceVersion: '3652923'
generation: 1
creationTimestamp: '2024-10-16T07:09:12Z'
managedFields:

• manager: Mozilla
  operation: Update
  apiVersion: networking.k8s.io/v1
  time: '2024-10-16T07:09:12Z'
  fieldsType: FieldsV1
  fieldsV1:
  'f:spec':
  'f:egress': {}
  'f:podSelector': {}
  'f:policyTypes': {}
  spec:
  podSelector:
  matchLabels:
  kubevirt.io: virt-launcher
  egress:
• to:
• namespaceSelector:
  matchLabels:
  kubernetes.io/metadata.name: openshift-storage
  policyTypes:
• Egress

On hcp cluster----

~ oc get storageclient
NAME PHASE CONSUMER
storage-client Connected 87cc4612-0afa-4f9a-94d3-b1a7b547c518

oc get storageclass
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
kubevirt-csi-infra-default (default) csi.kubevirt.io Delete Immediate false 23h
storage-client-ceph-rbd openshift-storage.rbd.csi.ceph.com Delete Immediate true 23h
storage-client-cephfs openshift-storage.cephfs.csi.ceph.com Delete Immediate true 23h

~ oc get storageclaim
NAME STORAGETYPE STORAGEPROFILE STORAGECLIENTNAME PHASE
storage-client-ceph-rbd block storage-client Configuring
storage-client-cephfs sharedfile storage-client Configuring

error log:
2024-10-16T07:04:56Z INFO Reconciling StorageClaim. {"controller": "storageclaim", "controllerGroup": "ocs.openshift.io", "controllerKind": "StorageClaim", "StorageClaim":

, "namespace": "", "name": "storage-client-cephfs", "reconcileID": "6887ab98-3d1a-43ab-b5bd-cc6a90b6b05b", "StorageClaim": {"name":"storage-client-cephfs"}}
2024-10-16T07:04:56Z ERROR Reconciler error {"controller": "storageclaim", "controllerGroup": "ocs.openshift.io", "controllerKind": "StorageClaim", "StorageClaim":

, "namespace": "", "name": "storage-client-cephfs", "reconcileID": "6887ab98-3d1a-43ab-b5bd-cc6a90b6b05b", "error": "failed to unmarshal StorageClaim configuration response: json: cannot unmarshal object into Go value of type string"}

Note: I am not very sure if this is related to upgrade of the provider cluster as there were 2 hcp clusters with client before upgrade and for only one I have faced the issue. And did not check the storageclaim status before upgrade so not very sure if it broke after upgrade.

Version-Release number of selected component (if applicable):
provider:
Before upgrade----
ocp: 4.16.15
ocs: 4.16.3-rhodf
After upgrade----
ocp: 4.17.0-0.nightly-2024-10-14-225948
ocs: 4.17.0-122.stable

hcp cluster: hcp416-bm3-1a
ocp: 4.16.15
OpenShift Data Foundation Client: 4.16.3-rhodf

How reproducible:
Have encountered this issue for the first time not sure if its easily reproducible.

Steps to Reproduce:
1. Create Provider cluster
2. Create hcp cluster
3. Check if the client cluster on hcp is in 'Connected' status and the storageclaims are in 'Ready' status

Actual results:
For hosted client in 'Connected' status and storageclasses added, Storageclaims were stuck at 'Intializing' status until networkpolicy was added at provider side for the hcp cluster. And after adding the networkpolicy it got stuck at 'Configuring' status.

Expected results:
Storageclaims should be in 'Ready' status.

Additional info: Logs will be uploaded shortly.