Current output message for oc adm top pvc -n xxxx 
"error: no persistentvolumeclaims found in xxxx namespace" even though there exists persistent volumes which could mislead the end user. 

4.19.0-0.nightly-2025-02-11-161912    

Always    

1. Create sc with Immediate VOLUMEBINDINGMODE, pvc which consume sc
2. Check the pvc. oc get pvc -n testropatil there exists persistent volume claims/volume 
3. Check the output message oc adm top pvc     
oc adm top pvc --insecure-skip-tls-verify=true -n testropatil
error: no persistentvolumeclaims found in testropatil namespace.

sc_pvc.yaml 
 allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: mysc
parameters:
  encrypted: "true"
  type: gp3
provisioner: ebs.csi.aws.com
reclaimPolicy: Delete
volumeBindingMode: Immediate
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: mypvc-fs
  namespace: testropatil
spec:
  accessModes:
    - ReadWriteOnce
  volumeMode: Filesystem
  storageClassName: mysc
  resources:
    requests:
      storage: 1Gi

oc get pvc
NAME           STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   VOLUMEATTRIBUTESCLASS   AGE
mypvc-fs       Bound    pvc-8257a331-c808-47c0-b127-53c817f090a7   1Gi        RWO            mysc           <unset>                 4s

oc get pv | grep "testropatil"
pvc-8257a331-c808-47c0-b127-53c817f090a7   1Gi        RWO            Delete           Bound    testropatil/mypvc-fs                        mysc           <unset>                          82s

error: no persistentvolumeclaims found in testropatil namespace

error: no persistentvolumeclaims found or mounted in xxxx namespace