Bug 1013059

Summary: Sort order for VM list in pool doesn't make sense
Product: Red Hat Enterprise Virtualization Manager Reporter: mrao
Component: ovirt-engine-webadmin-portalAssignee: Nobody <nobody>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acathrow, ecohen, iheim, michal.skrivanek, mrao, plightfoot, Rhev-m-bugs, yeylon
Target Milestone: ---Flags: iheim: needinfo? (mrao)
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-08 12:14:17 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:

Description mrao 2013-09-27 17:53:41 UTC 
Description of problem:

When 200 VMs are created in a pool, the names are automatically given and default sort order is crazy. Today, the sort goes something like – 1, 10, 100, 101, 11, 110, 111, 112, 113...119, 12, 120 etc.

Seems like in the past, the 0 padding was available but removed later but sorting was not fixed. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Itamar Heim 2013-09-28 13:12:00 UTC 
mailini - doesn't bug 892260 resolves this?
I'd "close duplicate" with it
Comment 3 Michal Skrivanek 2013-10-02 13:30:03 UTC 
yes, bug 892260 is supposed to be the solution exactly to this issue