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
Can't be fixed before dev freeze and not a blocker, moving it out.
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.