Description of problem: Setupnetworks can't handle vlan id 0 because it is not recognized as vlan interface. Vlan 0 is a useful id when user will like to treat the vlaned interface as un-tagged. This is fully supported in RHEL and RHEVM 3.0 there for this bug is actually a regression from 3.0 Setupnetworks display vlan 0 network as a regular network without vlan and cause few problems: 1. can't add multiple vlans over int/bond if one is vlan 0. 2. adding multiple vlans when one is vlan 0 via rest api (old api) will lead setupnetworks freezing when try to display this topology. Steps to Reproduce: 1. create logical network with vlan 0 2. add to cluster 3. add to host via setupnetworks Actual results: open setupnetworks and see that the networks doesn't assign as vlaned network Expected results: should treat vlan 0 as regular vlan. Additional info:
http://gerrit.ovirt.org/#/c/8358/
The same problem occurs when performing upgrade from Cluster 3.0 to Cluster 3.1 - After upgrade it's impossible to drag any network on interface with existing network with vlan 0 When performing verify to this bz, the above scenario should be tested as well
on SI21 setup networks works as expected