Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri
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?
(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.
We made some progress in the last hack-a-thon to fix this, updating status with that PR
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
This comment was flagged a spam, view the edit history to see the original text if required.
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