Bug 1956511 - [ceph-dashbaord][grafana] Physical Device Performance graphs for OSDs do not display
Summary: [ceph-dashbaord][grafana] Physical Device Performance graphs for OSDs do not ...
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: Ceph-Dashboard
Version: 4.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 5.1
Assignee: Alfonso Martínez
QA Contact: Preethi
Anjana Suparna Sriram
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-03 20:03 UTC by Steve Baldwin
Modified: 2021-05-14 08:17 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 50686 0 None None None 2021-05-07 13:33:22 UTC
Github ceph ceph pull 41221 0 None open mgr/dashboard: fix OSDs Host details/overview grafana graphs 2021-05-07 13:42:58 UTC

Description Steve Baldwin 2021-05-03 20:03:14 UTC
Description of problem:
The Physical Device Performance graphs for OSDs > performance details do not display any data.  

Version-Release number of selected component (if applicable):
rhcs : 14.2.11-95 / 4.2

How reproducible:
Unable to reproduce in-house

Actual results:
All four Physical Device Performance graphs only show "No data points" 

Expected results:
Physical Device Performance graphs for OSDs > performance details should display data in the graphs.

Additional info:
- The customer provided json files for two of the graphs not displaying data and I compared with my json from the same graphs in my 4.2 lab and they are exactly the same.
- One difference compared to my lab is this customer is running all nvme for all OSDs.

Comment 1 RHEL Program Management 2021-05-03 20:03:18 UTC
Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.


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