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:
Created attachment 1212156 [details] Missing CPU
Created attachment 1212157 [details] CPU After Refresh
*** Bug 1386752 has been marked as a duplicate of this bug. ***
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.
Created attachment 1212729 [details] missing-memory
https://github.com/openshift/origin-web-console/pull/707
This has been merged into ose and is in OSE v3.4.0.16 or newer.
Will continue to verify the this bug after bug 1388833 fixed.
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.
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.
Created attachment 1217931 [details] cpu-graph
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.
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.
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