Bug 1758031 - 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.3.0
Assignee: Andrew Pickering
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks: 1758170
TreeView+ depends on / blocked
 
Reported: 2019-10-03 04:58 UTC by Andrew Pickering
Modified: 2020-05-13 21:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1758170 (view as bug list)
Environment:
Last Closed: 2020-05-13 21:26:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 2828 0 None closed Query Browser: Fix UI rapidly flipping between two different queries 2020-03-20 05:54:08 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-05-13 21:26:38 UTC

Description Andrew Pickering 2019-10-03 04:58:28 UTC
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 3 shahan 2019-10-14 08:21:13 UTC
Query metrics with 'sum(sort_desc(sum_over_time(ALERTS{alertstate="firing"}[24h]))) by (alertname)' and 'sum(sort_desc(sum_over_time(ALERTS{alertstate!="firing"}[24h]))) by (alertname)' for several times. The line in Graph did not refresh and table results did not change.
4.3.0-0.ci-2019-10-14-031716

Comment 5 errata-xmlrpc 2020-05-13 21:26:35 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:0062


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