[ovirt-users] Re: oVirt hosted-engine-setup issues with getting host facts

Ok, removed the manual created ovirtmgmt network. Now it's complaining about missing ovirtmgmt network when installing host: 2018-06-05 13:21:32,091+02 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [2ed0af08] Connecting to host01.recacted/1.2.3.42 2018-06-05 13:21:32,250+02 INFO [org.ovirt.engine.core.bll.host.HostConnectivityChecker] (EE-ManagedThreadFactory-engine-Thread-1) [33333924] Engine managed to communicate with VDSM agent on host 'host01.recacted' with address 'host01.recacted' ('9956cebf-59ab-426b-ace6-25342705445e') 2018-06-05 13:22:09,007+02 INFO [org.ovirt.engine.core. bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [2b3212b5] Lock Acquired to object 'EngineLock:{exclusiveLocks='[ 5eb1152b-e9fb-4e2a-abea-f2d9823b724a=PROVIDER]', sharedLocks=''}' 2018-06-05 13:22:09,024+02 INFO [org.ovirt.engine.core. bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [2b3212b5] Running command: SyncNetworkProviderCommand internal: true. 2018-06-05 13:22:09,254+02 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-64) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2018-06-05 13:22:09,526+02 INFO [org.ovirt.engine.core. bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [2b3212b5] Lock freed to object 'EngineLock:{exclusiveLocks='[ 5eb1152b-e9fb-4e2a-abea-f2d9823b724a=PROVIDER]', sharedLocks=''}' 2018-06-05 13:24:32,603+02 ERROR [org.ovirt.engine.core.dal. dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [33333924] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM host01.recacted command CollectVdsNetworkDataAfterInstallationVDS failed: Message timeout which can be caused by communication issues 2018-06-05 13:24:32,603+02 INFO [org.ovirt.engine.core. vdsbroker.vdsbroker.CollectVdsNetworkDataAfterInstallationVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [33333924] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker.CollectVdsNetworkDataAfterInstallationVDSCommand' return value 'org.ovirt.engine.core.vdsbroker.vdsbroker. VDSInfoReturn@7b51b9cb' 2018-06-05 13:24:32,603+02 INFO [org.ovirt.engine.core. vdsbroker.vdsbroker.CollectVdsNetworkDataAfterInstallationVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [33333924] HostName = host01.recacted 2018-06-05 13:24:32,616+02 ERROR [org.ovirt.engine.core. vdsbroker.vdsbroker.CollectVdsNetworkDataAfterInstallationVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [33333924] Command ' CollectVdsNetworkDataAfterInstallationVDSCommand(HostName = host01.recacted, CollectHostNetworkDataVdsCommandParameters:{hostId=' 9956cebf-59ab-426b-ace6-25342705445e', vds='Host[host01.recacted, 9956cebf-59ab-426b-ace6-25342705445e]'})' execution failed: VDSGenericException: VDSNetworkException: Message timeout which can be caused by communication issues 2018-06-05 13:24:32,616+02 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedThreadFactory-engine-Thread-3) [33333924] Host 'host01.recacted' is not responding. 2018-06-05 13:24:32,622+02 WARN [org.ovirt.engine.core. dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-3) [33333924] EVENT_ID: VDS_HOST_NOT_RESPONDING(9,027), Host host01.recacted is not responding. Host cannot be fenced automatically because power management for the host is disabled. 2018-06-05 13:24:32,616+02 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1) [33333924] Exception: org.ovirt.engine.core.common.errors.EngineException: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetworkException: Message timeout which can be caused by communication issues (Failed with error VDS_NETWORK_ERROR and code 5022) 2018-06-05 13:24:32,628+02 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1) [33333924] Host installation failed for host '9956cebf-59ab-426b-ace6-25342705445e', 'host01.redacted': Failed to configure management network on the host 2018-06-05 13:24:32,633+02 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [33333924] START, SetVdsStatusVDSCommand(HostName = host01.redacted, SetVdsStatusVDSCommandParameters:{hostId='9956cebf-59ab-426b-ace6-25342705445e', status='NonOperational', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 2fa6c4ab 2018-06-05 13:26:19,101+02 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-45) [374e0c] START, SetVdsStatusVDSCommand(HostName = host01.redacted, SetVdsStatusVDSCommandParameters:{hostId='9956cebf-59ab-426b-ace6-25342705445e', status='NonOperational', nonOperationalReason='NETWORK_UNREACHABLE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 460b0642 2018-06-05 13:26:19,106+02 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-45) [374e0c] FINISH, SetVdsStatusVDSCommand, log id: 460b0642 2018-06-05 13:26:19,161+02 ERROR [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-45) [374e0c] Host 'host01.redacted' is set to Non-Operational, it is missing the following networks: 'ovirtmgmt' 2018-06-05 13:26:19,196+02 WARN [org.ovirt.engine.core. dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-45) [374e0c] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519), Host host01.redacted does not comply with the cluster Default networks, the following networks are missing on host: 'ovirtmgmt' 2018-06-05 13:26:19,235+02 INFO [org.ovirt.engine.core.bll. HandleVdsCpuFlagsOrClusterChangedCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-45) [647a0b6c] Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : ID: 9956cebf-59ab-426b-ace6-25342705445e Type: VDS Answers used for ansible deploy: OVEHOSTED_NETWORK/bridgeIf=str:br0.1111 > OVEHOSTED_NETWORK/bridgeName=str:ovirtmgmt > Do you have idea why the ovirtmgmt wasn't created during deploy? Or should we use other settings for network for deploy script?

On Tue, 2018-06-05 at 11:03 +0200, Simone Tiraboschi wrote: On Tue, Jun 5, 2018 at 10:16 AM, Mariusz Kozakowski <mariusz.kozakowski@ sallinggroup.com> wrote: On Tue, 2018-06-05 at 10:09 +0200, Simone Tiraboschi wrote: But did you manually created the bridge or did the engine created it for you triggered by hosted-engine-setup? Manually. Before we had br0.1111. Should we go back with network configuration to br0.1111, and no ovritmgmt network created? Yes, I'm pretty sure that the issue is there, see also https://bugzilla.redhat.com/show_bug.cgi?id=1317125 It will work for sure if the management bridge has been created in the past by the engine but we had a lot of failure reports trying to consume management bridge manually created with wrong options. Letting the engine creating it with the right configuration is by far the safest option. Also, what we should use as anwers here? OVEHOSTED_NETWORK/bridgeIf=str:bond0.1111 OVEHOSTED_NETWORK/bridgeName=str:ovirtmgmt Yes, this should be fine. -- Best regards/Pozdrawiam/MfG *Mariusz Kozakowski* Site Reliability Engineer Dansk Supermarked Group Baltic Business Park ul. 1 Maja 38-39 71-627 Szczecin dansksupermarked.com -- Best regards/Pozdrawiam/MfG *Mariusz Kozakowski* Site Reliability Engineer Dansk Supermarked Group Baltic Business Park ul. 1 Maja 38-39 71-627 Szczecin dansksupermarked.com