Bug 1807291

Summary: Wrong sort criteria for capacity on console
Product: OpenShift Container Platform Reporter: shahan <hasha>
Component: Management ConsoleAssignee: Joe Caiani <jcaiani>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.zCC: aos-bugs, jcaiani, jokerman, rhamilto, xiaocwan, yapei
Target Milestone: ---   
Target Release: 4.3.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1806875 Environment:
Last Closed: 2020-03-24 14:33:46 UTC Type: ---
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: 1807293    
Bug Blocks: 1807294    
Attachments:
Description Flags
capacity order correct none

Description shahan 2020-02-26 02:09:12 UTC 
+++ This bug was initially created as a clone of Bug #1806875 +++

Description of problem:
Wrong sort criteria for capacity on console. sort criteria for pvc capacity should be numeric sort not the dictionary order

Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-02-24-105333

How reproducible:
Always

Steps to Reproduce:
1. create several PVCs with 1Gi/10Gi/4GI size
2. The goto storage->pvc page and select all-project 
3. try to sort item by capacity

Actual results:
The items sorted based on dictionary order

Expected results:
sort criteria for pvc capacity should be numeric sort

Additional info:
Comment 3 XiaochuanWang 2020-03-09 08:45:03 UTC 
Created attachment 1668609 [details]
capacity order correct
Comment 4 XiaochuanWang 2020-03-09 08:46:55 UTC 
Capacities ordered correctly when selecting all-projects. Refer to the screenshot.
Verified on 4.3.0-0.nightly-2020-03-06-003558
Comment 6 errata-xmlrpc 2020-03-24 14:33:46 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:0858