Bug 1744965 - [Metrics] Ascending and descending sorting (by Value) doesn't work correct.
Summary: [Metrics] Ascending and descending sorting (by Value) doesn't work correct.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.2.0
Hardware: other
OS: Linux
unspecified
medium
Target Milestone: ---
: 4.2.0
Assignee: Andrew Pickering
QA Contact: Viacheslav
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-23 11:39 UTC by Viacheslav
Modified: 2019-10-16 06:37 UTC (History)
8 users (show)

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

Attachments (Terms of Use)
Example1 (98.02 KB, image/png)
2019-08-23 11:39 UTC, Viacheslav 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 2475 0 None None None 2019-08-24 09:43:27 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:37:45 UTC

Description Viacheslav 2019-08-23 11:39:15 UTC 
Created attachment 1607293 [details]
Example1

Description of problem:


Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-08-23-004712

Steps to Reproduce:

1. On the cluster web UI go to Monitoring
2. Click on the Metrics
3. Go to the input field set new metric for ex.:workqueue_adds_total
4. Click the button "Run Queries"
5. Click on the Value header field for sorting.
6. Scroll down several times for see digits  

Actual results:
 Sorting does not work properly by this field

Expected results:
 Sorting  should work correct

Additional info:
Comment 2 Viacheslav 2019-08-27 13:56:46 UTC 
Fixed now. 
was tested on: 4.2.0-0.nightly-2019-08-27-042756
Comment 3 errata-xmlrpc 2019-10-16 06:37:21 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.