| Summary: | Pod metrics don't update graphs if scale needs to change | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Dan McPherson <dmcphers> | ||||||||||
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 3.3.0 | CC: | aos-bugs, jokerman, jupierce, mmccomas, tdawson, yanpzhan | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| 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 12:43:33 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Bug Depends On: | 1390502 | ||||||||||||
| Bug Blocks: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Dan McPherson
2016-10-19 13:42:53 UTC
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
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 |