Bug 1758170 - Query Browser can flip between two different query results
Summary: Query Browser can flip between two different query results
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
unspecified
Target Milestone: ---
: 4.2.z
Assignee: Andrew Pickering
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On: 1758031
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-03 13:22 UTC by Samuel Padgett
Modified: 2019-10-30 04:45 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1758031
Environment:
Last Closed: 2019-10-30 04:44:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 2837 0 None None None 2019-10-18 13:07:54 UTC
Red Hat Product Errata RHBA-2019:3151 0 None None None 2019-10-30 04:45:07 UTC

Description Samuel Padgett 2019-10-03 13:22:47 UTC
+++ This bug was initially created as a clone of Bug #1758031 +++

Description of problem:
Query Browser can get stuck rapidly flipping between two different queries, causing the table results to change and lines in the graph to appear and disappear.

Version-Release number of selected component (if applicable):
4.2.0

How reproducible:
Always

Steps to Reproduce:
1. Enter two queries
2. Click the "Run Queries" button
3. Quickly toggle the first query off and on again using the query switch. You may need to repeat this several times until the bug is seen.

Actual results:
Graph and results table repeatedly switch between two different query results.

Expected results:
Graph and table show the results without changing other than when new data is fetched by the API polling.

Comment 1 Samuel Padgett 2019-10-09 15:29:18 UTC
https://github.com/openshift/console/pull/2837

Comment 6 errata-xmlrpc 2019-10-30 04:44:56 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:3151


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