Bug 1746546 - Dashboard: Pods By CPU Time is inaccurate and displays a bizarre unit
Summary: Dashboard: Pods By CPU Time is inaccurate and displays a bizarre unit
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.2.0
Assignee: Rastislav Wagner
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-28 18:06 UTC by Clayton Coleman
Modified: 2019-10-16 06:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:38:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 2528 0 None None None 2019-08-29 08:59:48 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:40:23 UTC

Description Clayton Coleman 2019-08-28 18:06:41 UTC 
https://www.dropbox.com/s/64wvs0kv743ytz0/Screenshot%202019-08-28%2013.56.08.png?dl=0

The dashboard "Pods by CPU Time" shows fractional ns for pods, which makes no sense.  These pods are using significant amounts of CPU time, so this metric is probably wrong.
Comment 2 Yanping Zhang 2019-09-03 08:32:21 UTC 
4.2.0-0.nightly-2019-09-02-172410
Checked on OCP 4.2 with above payload version. Now on the dashboard filter with "Pods by CPU" , the unit is "ms".
But filter with "Pods by Storage", the unit is still "ns", and the number are all "0".
Comment 3 Yanping Zhang 2019-09-03 08:39:04 UTC 
The filter with "Pods by Storage" could be traced by bug https://bugzilla.redhat.com/show_bug.cgi?id=1745865
So this bug could be verified now.
Comment 4 errata-xmlrpc 2019-10-16 06:38:14 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-2019:2922
Note You need to log in before you can comment on or make changes to this bug.