Bug 1804925 - Monitoring Dashboards: Charts use poor y-axis ticks when data points are all 0
Summary: Monitoring Dashboards: Charts use poor y-axis ticks when data points are all 0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.4.0
Assignee: Andrew Pickering
QA Contact: shahan
URL:
Whiteboard:
Depends On: 1801395
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-19 21:54 UTC by bpeterse
Modified: 2020-05-04 11:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1801395
Environment:
Version: 4.4.0-0.ci-2020-02-09-194845 Cluster ID: 4144534a-f7b0-4e96-9f04-45e179e26601 Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:72.0) Gecko/20100101 Firefox/72.0
Last Closed: 2020-05-04 11:38:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 4536 0 None closed [release-4.4] Bug 1804925: Monitoring Dashboards: Fix stack chart Y axis when all values are zero 2020-04-22 08:42:58 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:38:30 UTC

Description bpeterse 2020-02-19 21:54:17 UTC 
+++ This bug was initially created as a clone of Bug #1801395 +++

See screenshot. The charts pick y-axis values with scientific notation when all data points are 0.

--- Additional comment from Samuel Padgett on 2020-02-10 19:11:01 UTC ---
Comment 3 shahan 2020-03-03 09:06:22 UTC 
The stack chart Y axis have the range [-1, 1] when all values are zero.
The tick of y axis are [-1,-0.5,0,0.5,1].
4.4.0-0.nightly-2020-03-02-231151
Comment 5 errata-xmlrpc 2020-05-04 11:38:10 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:0581
Note You need to log in before you can comment on or make changes to this bug.