Bug 1836763

Summary: Legends swapped in data consumption card for providers->logical vs physical usage
Product: OpenShift Container Platform Reporter: Afreen <afrahman>
Component: Console Storage PluginAssignee: Ankush Behl <anbehl>
Status: CLOSED ERRATA QA Contact: Raz Tamir <ratamir>
Severity: high Docs Contact:
Priority: urgent    
Version: 4.5CC: anbehl, aos-bugs, nthomas
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:39:31 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:
Bug Depends On:    
Bug Blocks: 1837550    
Attachments:
Description Flags
Logical vs Physical usage none

Description Afreen 2020-05-18 05:32:14 UTC 
Description of problem:
Legends swapped in data consumption card for providers->logical vs physical usage

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

How reproducible:


Steps to Reproduce:
1. Go to object service dashboard
2. Check logical vs physical usage on data consumption chart by providers


Actual results:
The total logical usage and total physical usage legends are reporting correct capacities but swapped

Expected results:
The legends should map to correct names

Additional info:
Comment 4 Afreen 2020-05-19 15:31:13 UTC 
I changed the severity to high, since there is no workaround for this and this shows incorrect data.
Comment 5 Ankush Behl 2020-05-19 16:00:01 UTC 
Created attachment 1689930 [details]
Logical vs Physical usage

I verified the bug & it shows the correct legends now.
Comment 6 Scott Dodson 2020-05-20 18:25:27 UTC 
(In reply to afrahman from comment #4)
> I changed the severity to high, since there is no workaround for this and
> this shows incorrect data.

Lack of a workaround alone is not sufficient justification for bumping this to high. There's 70 other changes waiting in the queue, many of which affect cluster availability. This seems like a very minor cosmetic issue.
Comment 7 Afreen 2020-05-20 20:26:36 UTC 
(In reply to Scott Dodson from comment #6)
> (In reply to afrahman from comment #4)
> > I changed the severity to high, since there is no workaround for this and
> > this shows incorrect data.
> 
> Lack of a workaround alone is not sufficient justification for bumping this
> to high. There's 70 other changes waiting in the queue, many of which affect
> cluster availability. This seems like a very minor cosmetic issue.

Might be my miss in explaining this properly but a user wont see the correct stats on chart.
When he want to see the logical usage, he would actually see physical usage and vice versa.
Other parts of dashboard also report the logical usage and this could confuse user in identifying the actual logical space he is having currently.
Comment 9 errata-xmlrpc 2020-07-13 17:39:31 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:2409