Bug 2255036 - External storage system stats on data foundation page shows only zeros when multi storagecluster installed
Summary: External storage system stats on data foundation page shows only zeros when m...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ceph-monitoring
Version: 4.15
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ODF 4.15.0
Assignee: arun kumar mohan
QA Contact: Shay Rozen
URL:
Whiteboard:
: 2255261 2257817 2257819 (view as bug list)
Depends On: 2257674 2257694
Blocks: 2255261
TreeView+ depends on / blocked
 
Reported: 2023-12-18 17:06 UTC by Shay Rozen
Modified: 2024-03-19 15:25 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-03-19 15:25:37 UTC
Embargoed:


Attachments (Terms of Use)
storagesystem stats (336.35 KB, image/png)
2023-12-18 17:06 UTC, Shay Rozen
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2024:1383 0 None None None 2024-03-19 15:25:44 UTC

Description Shay Rozen 2023-12-18 17:06:34 UTC
Created attachment 2004854 [details]
storagesystem stats

Description of problem (please be detailed as possible and provide log
snippests):
When checking stats of Raw Capacity,Used capacity, IOPS, Throughput and latency in data foundation page under storagesystem all stats for the external storagesystem are zero


Version of all relevant components (if applicable):
ODF 4.15.0-88

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
User can't see storage stats


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)?
1

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:
No

Steps to Reproduce:
1. Install odf
2. Create an internal storagesystem
3. Create an external storagesystem
4. Navigate to: Storage->Data foundation-> storage systems and check stats

Actual results:
external storagesystem shows all the stats are zeros.

Expected results:
External storage system should show the exacts status of stats

Additional info:

Comment 11 Sanjal Katiyar 2023-12-19 07:13:10 UTC
Namespace is labelled correctly, exporter pod is running in the extended Namespace and StorageCluster/CephCluster are healthy, but we are missing "odf_system_" and "ceph_" metrics' info for the second cluster. Moving to monitoring side for further analysis.

Comment 13 Sanjal Katiyar 2023-12-20 05:01:45 UTC
BZ#2255036 and BZ#2255261 (https://bugzilla.redhat.com/show_bug.cgi?id=2255261) are related to one another.

Comment 14 umanga 2024-01-09 12:30:10 UTC
*** Bug 2255261 has been marked as a duplicate of this bug. ***

Comment 16 Sanjal Katiyar 2024-01-16 12:56:14 UTC
*** Bug 2257819 has been marked as a duplicate of this bug. ***

Comment 18 umanga 2024-01-16 13:03:49 UTC
*** Bug 2257817 has been marked as a duplicate of this bug. ***

Comment 22 arun kumar mohan 2024-02-08 09:23:11 UTC
As this is an umbrella bug and all the dependent BZs (BZ#2257694 and BZ#2257674) are ON_QA, this is no longer a blocker and could be moved to ON_QA. Once the dependent BZs are moved to verified, the state could be changed to verified.

Comment 23 Shay Rozen 2024-02-21 14:05:13 UTC
Verified on odf-operator.v4.15.0-147

Comment 25 errata-xmlrpc 2024-03-19 15:25:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.15.0 security, enhancement, & bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2024:1383


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