Bug 883269

Summary:	The order of NICs and Bonds is random in Network Interface tab and setupNetwork window
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	GenadiC <gcheresh>
Component:	ovirt-engine-webadmin-portal	Assignee:	Lior Vernia <lvernia>
Status:	CLOSED CURRENTRELEASE	QA Contact:	GenadiC <gcheresh>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.1.0	CC:	alkaplan, bazulay, dyasny, ecohen, iheim, lpeer, masayag, mavital, Rhev-m-bugs, sgrinber, ykaul
Target Milestone:	---
Target Release:	3.2.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	network
Fixed In Version:	sf10	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	922807, 948448

Description GenadiC 2012-12-04 08:15:23 UTC

Description of problem:
The order on NICs in the Network Interfaces window is randomly picked and changes every time you open this subtab.
The same issue we have in the setupNetwork window with NICs and bonds

How reproducible:
Always

Steps to Reproduce:
1. Open Network Interfaces tab to see the order of the NICs
2. Move to different tab/subtab and return to the Network Interfaces tab
3. Open setupNetworks, create bond and check the order of the NICs
4. Reopen setupNetworks
  
Actual results:
The order of the Nics/Bonds is random

Expected results:
There should be always the same order and it should start with eth0 till ethn, for the bond it should start with bond0 till bond5

Additional info:

Comment 1 lpeer 2012-12-05 06:44:38 UTC

Alona,
please take a look if the sorting should be done on the backend side and can benefit other usages of the queries (in the API for example).

Comment 2 Simon Grinberg 2012-12-19 19:01:25 UTC

(In reply to comment #0)

> Expected results:
> There should be always the same order and it should start with eth0 till
> ethn, for the bond it should start with bond0 till bond5

in newer OSs you'll find different interface naming conventions.

The sorting should be according to the following :
- Sort by type (ATM NIC and Bond)
Then withing type 
- Sort by alphabetical order 
Then within interfaces with same conventions but ending in number 
-sort by the number at the end 

The reason for the third is that if you just sort by alphabetical you often get
eth1
eth11
eth12
eth2
eth3 

Which is not what we want to have.

Comment 3 Lior Vernia 2013-02-13 10:17:20 UTC

Couldn't reproduce second half of the bug - the order of the interfaces in the setup networks window didn't look random at all to me. Could you elaborate?

Comment 4 GenadiC 2013-02-14 09:36:36 UTC

If the decision is to put bonds before the interfaces then the second half is working as expected

Comment 5 GenadiC 2013-03-11 14:57:46 UTC

Verified in rhevm-3.2.0-10.14.beta1.el6ev.noarch

Comment 6 Itamar Heim 2013-06-11 09:03:10 UTC

3.2 has been released

Comment 7 Itamar Heim 2013-06-11 09:03:10 UTC

3.2 has been released

Comment 8 Itamar Heim 2013-06-11 09:03:13 UTC

3.2 has been released

Comment 9 Itamar Heim 2013-06-11 09:04:00 UTC

3.2 has been released

Comment 10 Itamar Heim 2013-06-11 09:33:05 UTC

3.2 has been released