Bug 1748799

Summary:	Ordering in Usage Report table will re-send getting report requests
Product:	OpenShift Container Platform	Reporter:	Yadan Pei <yapei>
Component:	Management Console	Assignee:	David Taylor <dtaylor>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4.2.0	CC:	aos-bugs, jokerman, yapei
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-16 06:40:12 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:

Description Yadan Pei 2019-09-04 08:12:45 UTC

Description of problem:
The first time we click on ordering arrow in Usage Report table it will send report requests again, it looks like other resource pages will not resend the request when clicking on ordering 

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-09-03-102130

How reproducible:
Always

Steps to Reproduce:
1. cluster admin enable Metering 
2. Visit Administration -> Chargeback, click 'Create Report' using example YAML
3. After report is generated, check Usage Report table
4. Clicking on ordering arrow

Actual results:
3. The first time we click ordering arrow, it will re-send requests to get report data

Expected results:
3. After report data is loaded, it's unnecessary to send the request again when ordering

Additional info:

Comment 2 Yadan Pei 2019-09-09 05:38:41 UTC

Clicking on reordering will not send another report request

Verified on 4.2.0-0.nightly-2019-09-08-180038

Comment 3 errata-xmlrpc 2019-10-16 06:40:12 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