+++ This bug was initially created as a clone of Bug #2284090 +++

Description of problem (please be detailed as possible and provide log
snippests):
Happens for both internal & external mode "Block & file" dashboard -
"Requested capacity" & "Utilization" (Used capacity) Cards only display data for default StorageClasses created by OCS operator (as part of StorageSystem creation). It do not include any custom StorageClasses (Ceph provisioned) which could be created by users as a day-2 operation. 

Version of all relevant components (if applicable): ODF 4.15 & ODF 4.15


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No (but dashboard should display complete information)


Is there any workaround available to the best of your knowledge?
No


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Yes (ODF Block & file dashboards)

If this is a regression, please provide more details to justify this:
Yes (AFAIK earlier dashboards use to incorporate all ODF/OCS StorageClasses, default and custom).


Steps to Reproduce:
1. Deploy internal mode and external mode clusters (you can also deploy both on a same OCP, as ODF now supports multiple StorageClusters as well. Either is fine). 
2. Create some custom StorageClasses using ceph-rbd & ceph-fs provisioners.
3. Create PVC/PV using these custom and some default OCS StorageClasses.
4. Create some Pods and make sure these PVC/PV are attached/mounted to these "Running" pods (example: say we have 4 OCS StorageClasses/PVCs/PVs, we can create 4 Pods and mount each PVC to a separate Pod).
It's better if Pod can push some data to each PV, though not a hard requirement but good to do it before testing. Only hard requirement is that PVCs should be mounted, PVs should be bound and corresponding Pod should be running, otherwise "kubelet" metrics will not report this data at all.
5. Go to "Block & file" dashboard.
6. Check "Requested capacity" & "Utilization" (Used capacity) card, try different options from the dropdown.


Actual results: These cards only report capacity for the default OCS StorageClasses.


Expected results: It should report capacity for both default and custom created StorageClasses.


Additional info: PFA in the comments, this cluster had:
2 default & 1 custom "internal" PVs + PVCs, mounted to an active Pod.
1 default & 1 custom "external" PVs + PVCs, mounted to an active Pod.

1 default & 1 custom "internal" PVs + PVCs, not mounted to an active Pod.
1 default "external" PVs + PVCs, not mounted to an active Pod.

In attached screenshots we can see that,
for internal mode: Cards are only reporting 2 StorageClasses (default mounted ones), whereas it should report 3 ("2 default & 1 custom") in total.
for external mode: Cards are only reporting 1 StorageClass (default mounted), whereas it should report 2 ("1 default & 1 custom") in total.

--- Additional comment from INVALID USER on 2024-05-31 06:12:10 UTC ---

This bug having no release flag set previously, is now set with release flag 'odf‑4.16.0' to '?', and so is being proposed to be fixed at the ODF 4.16.0 release. Note that the 3 Acks (pm_ack, devel_ack, qa_ack), if any previously set while release flag was missing, have now been reset since the Acks are to be set against a release flag.

--- Additional comment from INVALID USER on 2024-05-31 06:12:10 UTC ---

The 'Target Release' is not to be set manually at the Red Hat OpenShift Data Foundation product.

The 'Target Release' will be auto set appropriately, after the 3 Acks (pm,devel,qa) are set to "+" for a specific release flag and that release flag gets auto set to "+".

--- Additional comment from Sanjal Katiyar on 2024-05-31 06:13:24 UTC ---

Internal mode cluster dashboard.

--- Additional comment from Sanjal Katiyar on 2024-05-31 06:14:26 UTC ---

External mode cluster dashboard.

--- Additional comment from INVALID USER on 2024-05-31 06:25:15 UTC ---

This BZ is being approved for ODF 4.16.0 release, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'odf‑4.16.0

--- Additional comment from INVALID USER on 2024-05-31 06:25:15 UTC ---

Since this bug has been approved for ODF 4.16.0 release, through release flag 'odf-4.16.0+', the Target Release is being set to 'ODF 4.16.0