Description of problem: The user can try to deploy hosted-engine choosing a bond interface with invalid mode (0, 5, 6) and it will fail really late. Version-Release number of selected component (if applicable): 2.2.20 How reproducible: 100% Steps to Reproduce: 1. configure a bond in mode 0, 5 or 6 2. try to deploy hosted-engine choosing that bond 3. Actual results: The bond will be accepted but the host will be set as non operational by the engine due to: WARN [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (EE-ManagedThreadFactory-engine-Thread-1) [1408d11e] Validation of action 'HostSetupNetworks' failed for user admin@internal-authz. Reasons: VAR__ACTION__SETUP,VAR__TYPE__NETWORKS,INVALID_BOND_MODE_FOR_BOND_WITH_VM_NETWORK,$BondName bond0,$networkName ovirtmgmt Expected results: the user is not allowed to choose an invalid bond interface fro hosted-engine Additional info:
(In reply to Simone Tiraboschi from comment #0) > Additional info: The code checks for 802.3adq instead of 802.3ad
Severity...?
(In reply to Yaniv Kaul from comment #2) > Severity...?
Verified on - ovirt-hosted-engine-ha-2.2.13-1.el7ev.noarch ovirt-hosted-engine-setup-2.2.22-1.el7ev.noarch Cockpit - IF the host active connection is on top of a bond mode=0,5,6, the HE wizard won't be loaded and we failing with a very generic error: 'System data could not be retrieved!' Can't start the HE deploy in such scenario, but we must to handle this generic error, will report a fresh bug to handle this. CLI- If the host active connection is on top of a bond mode-0,5,6, the HE deploy is failed: [ ERROR ] Failed to execute stage 'Environment customization': A Network interface is required [ ERROR ] Hosted Engine deployment failed
Created new bug to handle the generic error on cockpit side - BZ 1585462
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.4 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.