Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1758031

Summary:	Query Browser can flip between two different query results
Product:	OpenShift Container Platform	Reporter:	Andrew Pickering <anpicker>
Component:	Management Console	Assignee:	Andrew Pickering <anpicker>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	aos-bugs, hasha, jokerman, spadgett
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1758170 (view as bug list)		Environment:
Last Closed:	2020-05-13 21:26:35 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:
Bug Depends On:
Bug Blocks:	1758170

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