Red Hat Bugzilla – Bug 849971
[RHEVM] [backend] [Host Networking] DC/CL 3.0 cannot create bond when one interface has network already attached
Last modified: 2016-02-10 14:48:12 EST
Description of problem:
DC/CL 3.0 cannot create bond when one interface has network already attached (configured with static IP) (see screenshot)
Following error appears:
Previous network name is required.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version: '3.1.0-12.el6ev'
Steps to Reproduce:
1. add host with 3 NICs into 3.0 cluster
2. create required logical network and assign it to one host NIC
3. try to bond NIC from step 2 with another NIC
Error message appears
Bond is created
2012-08-21 13:33:13,275 WARN [org.ovirt.engine.core.bll.UpdateNetworkToVdsInterfaceCommand] (ajp-/127.0.0.1:8009-2) [88ac678] CanDoAction of action UpdateNetworkToVdsInterface failed. Reasons:NETWROK_OLD_NETWORK_NOT_SPECIFIED
Created attachment 605915 [details]
vdsm.log + engine.log
Created attachment 605916 [details]
problem appears if you try to bond unassigned NIC with NIC which has VLAN assigned
The bug resides on UpdateNetworkToVdsInterfaceCommand.canDoAction()
The parameters class contains the list of slave-interfaces and the bond name (in case and the use-case is bonding of nics which one of them has network attached to it).
A new validation should be added to verify no more than one network is attached to any of the provided interfaces.
The attached network name should be referred as the 'old-network-name' to be sent to VDSM for removal.