Bug 2284090 - Capacity & Utilization cards do not incorporate custom StorageClasses (Block & file dashboard)
Summary: Capacity & Utilization cards do not incorporate custom StorageClasses (Block ...
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.15
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.16.0
Assignee: Sanjal Katiyar
QA Contact: Elena Bondarenko
URL:
Whiteboard:
Depends On:
Blocks: 2260844 2290863
TreeView+ depends on / blocked
 
Reported: 2024-05-31 06:12 UTC by Sanjal Katiyar
Modified: 2024-07-03 08:43 UTC (History)
3 users (show)

Fixed In Version: 4.16.0-124
Doc Type: Bug Fix
Doc Text:
.Capacity and Utilization cards do not include custom storage classes Previously, the Requested capacity and Utilization cards displayed only data for the default storage classes created by the OCS operator as part of the storage system creation. The cards do not include any custom storage classes that were created later. This was due to the refactoring of the prometheus to support multiple storage clusters. With this fix, the queries are updated and the cards now show report capacity for both default and custom created storage classes.
Clone Of:
: 2290863 (view as bug list)
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-console pull 1409 0 None open Fix dashboard queries (Inventory + Capacity + Utilization cards) 2024-05-31 06:17:12 UTC
Github red-hat-storage odf-console pull 1428 0 None open Bug 2284090: [release-4.16] Fix dashboard queries (Inventory + Capacity + Utilization cards) 2024-06-07 11:44:06 UTC
Github red-hat-storage odf-console pull 1429 0 None open Bug 2284090: [release-4.16-compatibility] Fix dashboard queries (Inventory + Capacity + Utilization cards) 2024-06-07 11:44:15 UTC

Description Sanjal Katiyar 2024-05-31 06:12:00 UTC
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.

Comment 7 Sunil Kumar Acharya 2024-06-18 06:45:26 UTC
Please update the RDT flag/text appropriately.


Note You need to log in before you can comment on or make changes to this bug.