Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1386708 - Pod metrics don't update graphs if scale needs to change
Pod metrics don't update graphs if scale needs to change
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console (Show other bugs)
3.3.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Samuel Padgett
Yadan Pei
:
: 1386752 (view as bug list)
Depends On: 1390502
Blocks:
  Show dependency tree / graph
 
Reported: 2016-10-19 09:42 EDT by Dan McPherson
Modified: 2017-03-08 13 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In some cases, the Y-axis values would not adjust to fit the data when while looking at metrics for a pod. The Y-axis now will scale appropriately to fit the data as usage increases.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-18 07:43:33 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Missing CPU (58.34 KB, image/png)
2016-10-19 09:57 EDT, Dan McPherson 		no flags Details
CPU After Refresh (58.73 KB, image/png)
2016-10-19 09:57 EDT, Dan McPherson 		no flags Details
missing-memory (207.78 KB, image/png)
2016-10-21 04:05 EDT, Yanping Zhang 		no flags Details
cpu-graph (145.44 KB, image/png)
2016-11-07 04:26 EST, Yanping Zhang 		no flags Details
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0066 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 12:23:26 EST

  None (edit)
Description Dan McPherson 2016-10-19 09:42:53 EDT 
Description of problem:

If the CPU graph needs to change the scale to show the top of the new data, it doesn't show anything for those data points.  Meaning the scale on the graph doesn't change and the line isn't drawn.


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

3.3.0

How reproducible:

Not sure.  Probably 100%.


Steps to Reproduce:
1. Create the ruby 2.3 app (or whatever)
2. Go to the pod metrics page
3. Run a small scale test.  Ex: ab -n 100 -c 10 http://<app-url>/lobster
4. Let the metrics page refresh
5. Run a larger scale test. Ex: ab -n 1000 -c 100 http://<app-url>/lobster

Actual results:

The CPU won't refresh after the second test but the other graphs will

Expected results:

The scale should reset and the new line should be drawn

Additional info:
Comment 1 Dan McPherson 2016-10-19 09:57 EDT 
Created attachment 1212156 [details]
Missing CPU
Comment 2 Dan McPherson 2016-10-19 09:57 EDT 
Created attachment 1212157 [details]
CPU After Refresh
Comment 3 Dan McPherson 2016-10-19 14:43:25 EDT 
*** Bug 1386752 has been marked as a duplicate of this bug. ***
Comment 4 Yanping Zhang 2016-10-21 04:03:37 EDT 
openshift v3.3.1.3
kubernetes v1.3.0+52492b4
etcd 2.3.0+git
Checked on OCP 3.3.1.3, after increase load, observe the pod metrics, found the memory graph doesn't update in time, has the same issue as the bug description, pls refter to the attachment. After a while, refresh page, check the pod metrics, new graphs for memory/cpu/network are all shown up.
Comment 5 Yanping Zhang 2016-10-21 04:05 EDT 
Created attachment 1212729 [details]
missing-memory
Comment 7 Troy Dawson 2016-10-27 12:01:37 EDT 
This has been merged into ose and is in OSE v3.4.0.16 or newer.
Comment 9 Yanping Zhang 2016-10-28 06:03:05 EDT 
Will continue to verify the this bug after bug 1388833 fixed.
Comment 10 Yanping Zhang 2016-11-01 05:31:35 EDT 
Checked on OCP v3.4.0.18.  after increase load, observe the pod metrics, found the memory and network graph update in time. Could not check cpu graph due to bug 1390502. Will continue check after cpu value is available.
Comment 11 Yanping Zhang 2016-11-07 04:25:12 EST 
Tested again on OCP 3.4.0.22, followed the steps in the bug description, after increase load, the cpu graph still doesn't show up, but move mouse could see the use cpu value. Attach the screenshot. Pls have a check.
Comment 12 Yanping Zhang 2016-11-07 04:26 EST 
Created attachment 1217931 [details]
cpu-graph
Comment 13 Samuel Padgett 2016-11-07 08:11:15 EST 
It looks correct to me. 4m is within the y-axis range. It looks like you might only have one data point because your app is using no CPU before that time. Please wait a few minutes after increasing CPU usage so that there is more than one data point to see a line between them.
Comment 14 Yanping Zhang 2016-11-08 02:22:08 EST 
Checked on OCP 3.4.0.23 again, after increase load, wait for minutes, then could see the cpu graph updated.
The bug is fixed, so move it to Verified.
Comment 16 errata-xmlrpc 2017-01-18 07:43:33 EST 
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-2017:0066
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.