Bug 1781037

Summary: Capacity breakdown card should show absolute values and not hourly averaged values
Product: OpenShift Container Platform Reporter: Anmol Sachan <asachan>
Component: Console Storage PluginAssignee: Anmol Sachan <asachan>
Status: CLOSED ERRATA QA Contact: aberner
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: afrahman, aos-bugs, asachan, ebenahar, nthomas, ratamir
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1779208 Environment:
Last Closed: 2020-01-23 11:18:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1779208    
Bug Blocks:    

Description Anmol Sachan 2019-12-09 06:55:07 UTC
+++ This bug was initially created as a clone of Bug #1779208 +++

Description of problem:

Currently, the storage usage in the Capacity breakdown card shown is the hourly average of the values. It should be an absolute value.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create an OCS setup.
2. Push data into the setup.
3. After pushing the data, compare the actual size of data-pushed and the shown( by project, storageclass or pods)

Actual results: The usage values shown are lesser than the actual consumption.


Expected results: The usage values should be the same as consumption.


Additional info:

--- Additional comment from Anmol Sachan on 2019-12-03 14:05:07 UTC ---

Comment 2 aberner 2019-12-23 16:21:22 UTC
verified on ocp version: 4.3.0-0.nightly-2019-12-23-071857 and ocs version: 4.2 rc3

created a pod with pvc and pushed data into the pvc, Capacity breakdown card shows absolute values.

Comment 4 errata-xmlrpc 2020-01-23 11:18:15 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, 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/RHBA-2020:0062