Created attachment 1082726 [details] engine, vdsm and supervdsm logs Description of problem: Using old SetupNetwork API when attaching network the BOND the operation fail with error "Interface name can't be found" Version-Release number of selected component (if applicable): rhevm-3.6.0-0.18.el6.noarch How reproducible: 100% Steps to Reproduce: 1. Create VLAN network on DC/Cluster 2. Attach the VLAN network the host NIC using old SetupNetworks API Additional info: In vdsm log: call setupNetworks with ({u'net1': {u'nic': u'bond0' , u'STP': u'no', u'bridged': u'true', u'mtu': u'1500'}}, {u'bond0': {u'remove': u'true'}}, {u'connectivityCheck': u'true', u'connectivityTimeout': 60}) {} seems like engine send {u'bond0': {u'remove': u'true'}} to the BOND that the network should attach to.
Steps to Reproduce: 1. Create network on DC/Cluster 2. Attach the network the host NIC using old SetupNetworks API Removed the VLAN network from Steps to Reproduce.
vdsm-4.17.8-1.el7ev.noarch
Smells like bug 1271524.
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag.
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.
Verified on 3.6.1.1-0.1.el6
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.