Created attachment 824518 [details]
screenshot 1

Description of problem:
after upgrade of RHEV-M from 3.2 to 3.3 supported bond modes (2,4,5) are displayed as custom modes despite there is matching modes in RHEV-M 3.3 (see screenshot)


Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version: 3.3.0-0.33.beta1.el6ev 

How reproducible:
100%

Steps to Reproduce:
1. In RHEVM-M 3.2 create 4 bonds on host: 
bond in mode 1, 
bond in mode 2, 
bond in mode 4, 
bond in mode 5 
(if you do not have enough interfaces you can use script from additional info to  create dummy interfaces)

2. upgrade RHEV-M to 3.3

Actual results:
bonds in modes 2,4 and 5 are displayed as bonds with custom mode despite there is matching modes in RHEV-M 3.3 (see screenshot)


Expected results:
bonds are displayed with appropriate mode (Load-balance, dynamic link, adaptive transmit mode)

Additional info:
it is interesting that bond in mode 1 is displayed correctly after upgrade


#!/bin/bash

###CLEAN UP######
#make sure conf line is not present in vdsm.conf
sed -i '/^fake_nics/d' /etc/vdsm/vdsm.conf

#unload dummy driver (destroy existing dummies)
modprobe -r dummy

#delete existing ifcfg files
rm -f /etc/sysconfig/network-scripts/ifcfg-dummy*

####CREATE INTERFACES####
#create dummy interfaces named dummy[0-11]
modprobe dummy numdummies=12

#create ifcfg file for dummy interfaces
for i in {0..11} 
do 
    echo -e "DEVICE=dummy$i\nONBOOT=yes\nNM_CONTROLLED=no\nBOOTPROTO=none" > /etc/sysconfig/network-scripts/ifcfg-dummy$i
done

#####ADJUST CONF#######
#add fake nics to vdsm.conf do they get propagated to engine
#find on which line [vars] section begins
line=$(cat /etc/vdsm/vdsm.conf | grep -n vars | grep -o '^[0-9]*')
#increase by 1
line=$((line + 1))
#insert config line
sed -i ${line}'i\fake_nics = dummy*' /etc/vdsm/vdsm.conf


####restart vdmsd####
/etc/init.d/vdsmd stop && /etc/init.d/vdsmd start