Bug 1650209

Summary: [Ceph-Dashboard] Latency by Server report appears to be calculating the latency incorrectly.
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: jquinn <jquinn>
Component: Ceph-MetricsAssignee: Zack Cerza <zcerza>
Status: CLOSED ERRATA QA Contact: Sunil Angadi <sangadi>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.3CC: anharris, bniver, ceph-eng-bugs, gmeno, jquinn, kdreyer, kiran.factocert, pasik, sangadi, sostapov, teresa32yon, tserlin
Target Milestone: ---   
Target Release: 3.3z7   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: cephmetrics-ansible-2.0.10-1.el7cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-06 18:32:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 5 Giridhar Ramaraju 2019-08-05 13:09:47 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 6 Giridhar Ramaraju 2019-08-05 13:11:00 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 8 Scott Ostapovicz 2020-04-24 15:38:56 UTC
This is not a regression issue, and has not blocked 3.0, z1, z2, z3, or z4.  Thus I am kicking it to z6.  However, this issue has never been properly evaluated since it was introduced in 2018.  If this is a real issue, does it still happen in 4.x and 5.x?

Comment 9 Yaniv Kaul 2020-04-27 15:37:50 UTC
(In reply to Scott Ostapovicz from comment #8)
> This is not a regression issue, and has not blocked 3.0, z1, z2, z3, or z4. 
> Thus I am kicking it to z6.  However, this issue has never been properly
> evaluated since it was introduced in 2018.  If this is a real issue, does it
> still happen in 4.x and 5.x?

- It's unclear who should answer it? (No NEEDINFO set on anyone)
- Note that it has a customer case (and a strategic customer) attached.
- If we do not reach a conclusion, please close - let's not continue to drag it over releases.

Comment 10 Christina Meno 2020-04-27 20:00:11 UTC
We made some progress in the last hack-a-thon to fix this, updating status with that PR

Comment 24 errata-xmlrpc 2021-05-06 18:32:04 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 Ceph Storage 3.3 Security and 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-2021:1518

Comment 25 isoconsulattion 2022-01-04 10:47:43 UTC Comment hidden (spam)
Comment 26 teresa32yon 2025-01-24 10:56:55 UTC
Thanks for bringing this up! Bug 1650209 in the Ceph Dashboard seems to be related to incorrect latency calculations in the "Latency by Server" report. This can be quite a critical issue if accurate latency measurements are essential for your operations https://www.floridablue-fl.com