Description of problem: Vlan devices reported by VDSM aren't being reused by the UI, instead a new interface is created to represent the vlan device which causes the action to fail due to providing the same interface twice. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. [UI] setupNetworks for network "red" over bond2 {eth1, eth2} with vlan 3 2. ssh to the host 3. ip link set dev red down 4. brctl delbr red 5. go to the UI 6. put the host in maintenance and activate again (to make the engine/ui realize that "red" is not over the vlanned bond anymore. 7. Open setup host networks dialog. and do: vlanned (3) network red over bond2 {eth1, eth2, eth3}. Actual results: Operation is block by can-do-action and the following message appears in the log: 2013-02-12 12:58:58,722 WARN [org.ovirt.engine.core.bll.network.host.SetupNetworksCommand] (ajp--127.0.0.1-8702-10) [d0ee46d] CanDoAction of action SetupNetworks failed. Reasons:VAR__ACTION__SETUP,VAR__TYPE__NETWORKS,NETWORK_INTERFACES_ALREADY_SPECIFIED,$NETWORK_INTERFACES_ALREADY_SPECIFIED_LIST bond2.3 Expected results: Operation should succeed and bond2.3 should be reused instead creating new interface by the UI. Additional info:
(In reply to comment #0) > 3. ip link set dev red down > 4. brctl delbr red doing this is a recipe to vdsm/libvirt inconsistency (to be solved only on beta2 build by virtue of bug 861701. to avoid that, please delete the network from libvirt, too: 4.1 virsh -c qemu+tcp://localhost/system net-destroy red 4.2 virsh -c qemu+tcp://localhost/system net-undefine red
Verified on: vdsm-4.10.2-14.0.el6ev.x86_64 rhevm-3.2.0-10.19.beta2.el6ev.noarch
3.2 has been released