Description of problem: After attaching a non-VM, vlanned network to a network device, VDSM reports the new vlan device (As usual) and the engine displays the new vlan device in the different GUI elements. Subsequent setupNetworks will fail with a 'network sent twice' error. In other words, if a non-VM, vlanned network is placed on a host, the host's networking will no longer be able to be managed by the engine, until the network is manually removed from the host. How reproducible: 100% Steps to Reproduce: 1. Create a new, non-VM, vlanned network 2. Attach it to a bond / nic Actual results: Following a successful operation, the new VLAN device will be visible in the GUI Expected results: The VLAN device should not be visible in the GUI Additional info: I reproduced the issue with a dummy nic. However, I suspect the bug has nothing to do with dummy nics.
Moti, I think this has to do with the fix we discussed a couple of months ago for Bug 1011486.
After Moti debugged it for a bit he discovered that this indeed only happens with dummy nics, and it's a VDSM bug. As it turns out in vdsCaps, the dummy nic and vlan device are both reported under the nics section (Which is wrong, and different than with real / non-dummy devices).
ovirt-engine-3.4.0-0.5.beta1.el6.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0504.html