Description of problem: Some bond modes cause problems in VM networks, see bug 1094842. For hosted-engine this is especially important, because a bad bond mode can break PXE booting the VM (bug 1230638). he-setup should check the bond mode (if a bond is used) and warn the user in case that a bond mode is used, which is known to be unsafe.
Just for avoiding to dig into other bugs: interfaces using bonding modes 0, 5 and 6 must fail validation when selected for creating the bridge.
Marcin, any check done by VDSM when creating the bridge with setupNetworks?
Got appropriate warning message for bond type 0: [WARNING] Bond bond0 is on mode 0, modes ('0', '5', '6') are not supported Please indicate a nic to set ovirtmgmt bridge on: (enp3s0f1, eno1, eno2, enp3s0f0) [enp3s0f1]: for bond type 5: [WARNING] Bond bond0 is on mode 5, modes ('0', '5', '6') are not supported Please indicate a nic to set ovirtmgmt bridge on: (enp3s0f1, eno1, eno2, enp3s0f0) [enp3s0f1]: for bond type 6: [WARNING] Bond bond0 is on mode 6, modes ('0', '5', '6') are not supported Please indicate a nic to set ovirtmgmt bridge on: (enp3s0f1, eno1, eno2, enp3s0f0) [enp3s0f1]: Tested on ovirt-hosted-engine-setup-2.2.0-0.0.master.20170919052946.git896e399.el7.centos.noarch. Moving to verified.
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.