Bug 2022356

Summary: Range value is not properly displayed for performance card
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Bipin Kunal <bkunal>
Component: management-consoleAssignee: Debjyoti Pandit <dpandit>
Status: CLOSED CURRENTRELEASE QA Contact: avdhoot <asagare>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.9CC: badhikar, dpandit, jefbrown, muagarwa, nthomas, ocs-bugs, odf-bz-bot, skatiyar
Target Milestone: ---   
Target Release: ODF 4.12.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.12.0-80 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-08 14:06:28 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: 2138273    
Bug Blocks:    
Attachments:
Description Flags
NooBaa Only deployment none

Description Bipin Kunal 2021-11-11 12:51:34 UTC 
Created attachment 1841197 [details]
NooBaa Only deployment

Description of problem:

Range value for performance card.

I faced issues in 2 deployments:
  1. OCP-4.9 + OCS-4.8 being upgraded to OCP-4.9 + ODF-4.9, range value intermittently shows the rance of 00001 - 99999. Looks like there are even some additional zero at the start of the range and get not properly being displayed.

      From a user perspective, I don't think this is an appropriate range despite that there are no metrics yet to display.

  2. In the second instance, A weird range value was displayed for NooBaa only deployed with OCP-4.9 + ODF-4.9 It displays a range of 2e-10 - 1e-10.

   

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

1. 
   OCP Version: 4.9.0
   ODF Version: 4.8.3

   being upgraded to 

   OCP Version: 4.9.0
   ODF Version: quay.io/rhceph-dev/ocs-registry:4.9.0-233.ci

2. 

   OCP Version: 4.9.0
   ODF Version: quay.io/rhceph-dev/ocs-registry:4.9.0-233.ci
Comment 6 Mudit Agarwal 2022-02-23 14:57:39 UTC 
Can't be fixed before dev freeze and not a blocker, moving it out.
Comment 7 Bipul Adhikari 2022-03-07 02:49:59 UTC 
I think this bug can be replicated mostly during the initialization phases where the data nears very near to 0. So we need to either be on loading state or handle those data points properly. Maybe we are aggressively trying to round up values to certain units.