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

Bug 1133264

Summary: client side sorting for disk/storage size behaves incorrectly
Product: [Retired] oVirt Reporter: Daniel Erez <derez>
Component: ovirt-engine-webadminAssignee: Daniel Erez <derez>
Status: CLOSED CURRENTRELEASE QA Contact: Elad <ebenahar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.5CC: acanan, ecohen, gklein, iheim, mgoldboi, rbalakri, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: ovirt-3.5.0_rc2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-17 12:32:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
sort by size none

Description Daniel Erez 2014-08-24 06:41:02 UTC
Created attachment 930060 [details]
sort by size

Description of problem:
Currently, size columns are sorted using LexoNumericComparator,
which is fine for most cases except for '< 1 GB' value (a screenshot
is attached for illustration).

Version-Release number of selected component (if applicable):
3.5

How reproducible:
100%

Steps to Reproduce:
1. Navigate to any disks/storage sub-tab.
2. Sort by size.
3.

Actual results:
'<1 GB' value is incorrectly positioned.

Expected results:
Values are sorted properly.

Additional info:

Comment 1 Elad 2014-09-14 11:28:51 UTC
1GB > disks are positioned right when sorting the disks by size.

Verified using rhev3.5 vt3.1

Comment 2 Sandro Bonazzola 2014-10-17 12:32:05 UTC
oVirt 3.5 has been released and should include the fix for this issue.