Created attachment 2028508 [details] average is higher than the total used capacity Description of problem (please be detailed as possible and provide log snippests): "Average" value is greater than the "Total used capacity", which should not be possible at any situation. I have been using this cluster since 5 days. Started filling high amount of data 450G on 4th day, 300G on 5th day. It looks like Average is defined as sum of all the day's consumption. Total: 860.6 GiB Average: 861.4 GiB Please refer snapshot for more details Version of all relevant components (if applicable): odf: 4.16.0-81.stable ocp: 4.16.0-0.nightly-2024-04-18-141003 ceph version 18.2.1-136.el9cp (e7edde2b655d0dd9f860dda675f9d7954f07e6e3) reef (stable) Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Yes 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)? 2 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. Deploy cluster. 2. Start creating files with larger size for 4 to 5 days. 3. Daily fill some amount of storage. 4. Average of storage consumption will be higher than the total used capacity. Actual results: Expected results: Additional info:
Until this issue is fixed, we cannot proceed with further testing. added Test Blocker.
Severity changed to 'urgent' as we cannot test this feature without accuracy in "Average" value.
like other BZs, this one too might be already fixed alongside https://bugzilla.redhat.com/show_bug.cgi?id=2275965 & https://bugzilla.redhat.com/show_bug.cgi?id=2272928, but good to cross-check once... thanks for the cluster...
Verified with 4.16.0-85 Issue not fixed. Please refer attached snapshots for more details. Average is 3 times of Total storage consumption.
the issue pops up after a manual failover, as you’ve mentioned in bz 2275965. this should not qualify as a testblocker. as @muagarwa has mentioned.
This feature is 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