Bug 1837860

Summary: The graph is not shown after clicking "Show Graph"
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: Management ConsoleAssignee: Andrew Pickering <anpicker>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: low Docs Contact:
Priority: medium    
Version: 4.5CC: anpicker, aos-bugs, jokerman, xiaocwan
Target Milestone: ---Keywords: Regression
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:40:02 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:
Embargoed:
Attachments:
Description Flags
The graph is not shown after clicking "Show Graph"
none
Verification screenshot none

Description Junqi Zhao 2020-05-20 07:09:59 UTC
Created attachment 1690085 [details]
The graph is not shown after clicking "Show Graph"

Description of problem:
Goto "Monitoring -> Metrics", search metrics, for example: cluster:container_cpu_usage:ratio
zoom in the graph, then click "Hide Graph", after a few seconds, click "Show Graph", the graph is not shown

Note: no such issue if select timespan from the timespan drop-down list

Version-Release number of selected component (if applicable):
4.5.0-0.nightly-2020-05-19-041951

How reproducible:
always

Steps to Reproduce:
1. See the description
2.
3.

Actual results:
the graph is not shown

Expected results:
no error

Additional info:

Comment 1 Robb Hamilton 2020-05-20 18:11:21 UTC
Lowering severity since the bug only occurs if the graph is first zoomed.

Comment 4 XiaochuanWang 2020-05-25 03:21:36 UTC
Created attachment 1691676 [details]
Verification screenshot

Comment 5 XiaochuanWang 2020-05-25 03:22:23 UTC
Attached the screen recording.
Verified on 4.5.0-0.nightly-2020-05-24-191212

Comment 6 errata-xmlrpc 2020-07-13 17:40:02 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-2020:2409