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:
I changed the severity to high, since there is no workaround for this and this shows incorrect data.
Created attachment 1689930 [details] Logical vs Physical usage I verified the bug & it shows the correct legends now.
(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.
(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.
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