Bug 915205 - Network names badly sorted in Setup Networks popup
Summary: Network names badly sorted in Setup Networks popup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 3.2.0
Assignee: Lior Vernia
QA Contact: Meni Yakove
URL:
Whiteboard: network
Depends On:
Blocks: 922807 948448
TreeView+ depends on / blocked
 
Reported: 2013-02-25 08:39 UTC by Lior Vernia
Modified: 2016-02-10 19:59 UTC (History)
11 users (show)

Fixed In Version: sf8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 12001 0 None None None Never

Description Lior Vernia 2013-02-25 08:39:54 UTC
Description of problem:

The network names are sorted purely lexicographically, thus mishandling numeric subsequences.


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


How reproducible:

Always.


Steps to Reproduce:
1. Create two networks named "net2" and "net10".
2. Go to host main tab, network interfaces subtab, and click setup network hosts button.
  
Actual results:

"net10" appears before "net2".


Expected results:

"net2" should appear before "net10".


Additional info:

Networks are also badly sorted when they have VLAN tags and appear as contained within a NIC, not only on the side panel as required or non-required networks.

Comment 1 Meni Yakove 2013-03-11 14:03:54 UTC
Verified on rhevm-3.2.0-10.14.beta1.el6ev.noarch

Comment 2 Itamar Heim 2013-06-11 08:41:47 UTC
3.2 has been released

Comment 3 Itamar Heim 2013-06-11 08:41:47 UTC
3.2 has been released

Comment 4 Itamar Heim 2013-06-11 08:41:57 UTC
3.2 has been released

Comment 5 Itamar Heim 2013-06-11 08:49:11 UTC
3.2 has been released


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