Bug 1731322 - time range is not changed after dragging mouse in blank area of the graph
Summary: time range is not changed after dragging mouse in blank area of the graph
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.2.0
Assignee: Andrew Pickering
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-19 06:11 UTC by Junqi Zhao
Modified: 2019-10-16 06:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:30:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 2197 0 None None None 2019-07-29 10:27:38 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:30:17 UTC

Description Junqi Zhao 2019-07-19 06:11:03 UTC
Description of problem:
login cluster console as cluster-admin and go to Query Browser page, search one metrics and drag mouse in blank area of the graph(don't accross the line),
the time range is not changed, if t 

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-07-18-120653

How reproducible:
Always

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

Actual results:
the time range is not changed 

Expected results:


Additional info:
If we think this is not a bug, please close it as NOTABUG

Comment 2 Junqi Zhao 2019-08-01 08:40:26 UTC
we can not drag mouse in blank area of the graph now,the rectangle will be selected from top to bottom of the graph
payload: 4.2.0-0.nightly-2019-07-31-162901

Comment 3 errata-xmlrpc 2019-10-16 06:30:08 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-2019:2922


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