Bug 1474292 - Metrics beginning time points are unstable in value and alignment among mem/cpu/network charts
Summary: Metrics beginning time points are unstable in value and alignment among mem/c...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Samuel Padgett
QA Contact: XiaochuanWang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-24 10:29 UTC by Xingxing Xia
Modified: 2019-06-04 20:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-04 20:27:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
metrics-beginning-time-points-unstable-and-not-aligned (1.50 MB, application/octet-stream)
2017-07-24 10:29 UTC, Xingxing Xia
no flags Details

Description Xingxing Xia 2017-07-24 10:29:46 UTC
Created attachment 1303561 [details]
metrics-beginning-time-points-unstable-and-not-aligned

Description of problem:
Metrics beginning time points are unstable in value and alignment among mem/cpu/network charts

Version-Release number of selected component (if applicable):
openshift v3.6.153

How reproducible:
Always

Steps to Reproduce:
1. Create pod on env that deployed metrics (e.g. free-stg env. OCP env also reproduced)
2. Wait for pod running and has metrics charts in pod Metrics tab
3. Check the beginning time points of charts. Refresh and check again

Actual results:
3. Beginning time points are unstable among refreshes. See screen record:
Sometimes the begging time point is 17:13, 17:14, ..., or 17:16
Sometimes the beginning time point among mem/cpu/network is not same in some refresh

Expected results:
3. Should stable

Additional info:

Comment 1 Samuel Padgett 2019-06-04 20:27:56 UTC
This is no longer an issue in the new 4.1 console. We do not plan to change this behavior in the 3.x console.


Note You need to log in before you can comment on or make changes to this bug.