Created attachment 2027139 [details] dashboard Description of problem (please be detailed as possible and provide log snippests): Deployed a cluster and filled almost half of the storage within 1day. Expecting "Estimated days to fill" values '1' on 2nd day. I had observed that the graph shows wrong data and all the values for 'average' and "Estimated days to fill" went wrong. Looks like active mgr failover happened and calculations went wrong after that. Version of all relevant components (if applicable): Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? 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? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. 2. 3. Actual results: 'average' and "Estimated days to fill" displayed wrong values. Expected results: Graph, 'average' and "Estimated days to fill" should be displayed correctly after mgr failover. Additional info:
Nagendra, if you still have this cluster can you plz share it with Divyansh ? (It will be helpful to debug these bugs on a live cluster).
Issue here is due to mgr exporting 2 metrics, both under the job name ocs-storagecluster. workaround is to add the values up for both the metrics
This feature moved to 4.17
Please evaluate and provide qa_ack.
Please update the RDT flag/text appropriately.
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.17.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:8676
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days