Description of problem:

When two VLAN interfaces are defined on the same bond and one of those is marked for use by the ovirtmgmt bridge the other vlan interface gets disabled as soon as vdsm takes control of the network.
If this second vlan is used as backend network for storage this makes the hosted engine deploy fail, as the gluster volumes are no longer reachable.

Version-Release number of selected component (if applicable):
RHHI 2
RHVH 4.2.6


How reproducible:

Always.

Steps to Reproduce:
1. Install 3 hosts with RHVH 4.2.6
2. Set up networking as follow:

slave all interfaces to bond0
create bond0.1 and bond0.2 as two vlan interfaces. bond0.1 will be used for ovirtmgmt, bond0.2 is used for storage.
3. do the gluster part of the hosted engine deploy. Use the ips on bond0.2 for that. This should succeed.
4. do the hosted engine part of the deploy. This fails.
Actual results:


Expected results:

Hosted engine deploy should succeed.

Additional info:

vdsm does not appear to use NetworkManager for network configuration. What we observed is that when vdsm takes control of the network it moves the bond0, bond0.1 and all the slaves out of NM control and adds the ovirtmgmt bridge. As a side effect the bond0.2 vlan interface goes down, and is not brought up.

As a workaround we reenabled bond0.2 as a non network manager controlled interface using an ansible playbook, that we ran in between the two phases of the hosted engine deploy.