On Thu, Feb 15, 2018 at 6:42 PM, Kuko Armas <kuko@canarytek.com> wrote:

> Can you please attach vdsm and host-deploy logs?

This is what I saw in engine.log

2018-02-15 13:49:26,850Z INFO  [org.ovirt.engine.core.bll.host.HostConnectivityChecker] (EE-ManagedThreadFactory-engine-Thread-1) [15c7e33a] Engine managed to communicate wi
th VDSM agent on host 'ovirt1' with address 'ovirt1' ('06651b32-4ef8-4b5d-ab2d-c38e84c2d790')
2018-02-15 13:49:30,302Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [15c7e33a] EVENT_ID: VLAN_ID_
MISMATCH_FOR_MANAGEMENT_NETWORK_CONFIGURATION(1,119), Failed to configure management network on host ovirt1. Host ovirt1 has an interface bond0.1005 for the management netwo
rk configuration with VLAN-ID (1005), which is different from data-center definition (none).
2018-02-15 13:49:30,302Z ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1) [15c7e33a] Exception: org.ovirt.eng
ine.core.bll.network.NetworkConfigurator$NetworkConfiguratorException: Failed to configure management network

It seems that ovirtmgmt creation is skipper because inconsistency between datacenter setup and host setup. Of course we can not configure the vlan for mgmt network in datacenter because we are still deploying

Yes, you are absolutely right: the setup has to set the VLAN ID at datacenter level before adding the host as the old flow was doing.
 

Salu2!
--
Miguel Armas
CanaryTek Consultoria y Sistemas SL
http://www.canarytek.com/