Bug 1013059 - Sort order for VM list in pool doesn't make sense [NEEDINFO]
Summary: Sort order for VM list in pool doesn't make sense
Keywords:
Status: CLOSED DUPLICATE of bug 892260
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Pavel Stehlik
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-27 17:53 UTC by mrao
Modified: 2014-07-13 23:25 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-08 12:14:17 UTC
oVirt Team: ---
Target Upstream Version:
iheim: needinfo? (mrao)


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.