On Mon, May 28, 2018 at 11:44 AM, Mariusz Kozakowski <
mariusz.kozakowski(a)dsg.dk> wrote:
On Fri, 2018-05-25 at 11:21 +0200, Simone Tiraboschi wrote:
On Fri, May 25, 2018 at 9:20 AM, Mariusz Kozakowski <
mariusz.kozakowski(a)dsg.dk> wrote:
On Thu, 2018-05-24 at 14:11 +0200, Simone Tiraboschi wrote:
To better understand what it's happening you have to check host-deploy
logs; they are available under /var/log/ovirt-engine/host-deploy/ on your
engine VM.
Unfortunately there is no logs under that directory. It's empty.
So it probably failed to reach the host due to a name resolution issue or
something like that.
Can you please double check it in /var/log/ovirt-engine/engine.log on the
engine VM ?
Thanks - it helped a bit. At least now we have logs for host-deploy, but
still no success.
Few parts I found in engine log:
2018-05-28 11:07:39,473+02 ERROR
[org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
(EE-ManagedThreadFactory-engine-Thread-1) [1a4cf85e] 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-05-28 11:07:39,485+02 ERROR
[org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
(EE-ManagedThreadFactory-engine-Thread-1) [1a4cf85e] Host installation
failed for host '098c3c99-921d-46f0-bdba-86370a2dc895',
'host01.redacted': Failed to configure management network on the host
The issue is on network configuration:
you have to check /var/log/vdsm/vdsm.log and /var/log/vdsm/supervdsm.log to
understand why it failed.
2018-05-28 11:20:04,705+02 INFO [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-37) [5ba0ae45] Running
command: SetNonOperationalVdsCommand internal: true. Entities affected
: ID: 098c3c99-921d-46f0-bdba-86370a2dc895 Type: VDS
2018-05-28 11:20:04,711+02 INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-37) [5ba0ae45] START,
SetVdsStatusVDSCommand(HostName = host01.redacted,
SetVdsStatusVDSCommandParameters:{hostId='098c3c99-921d-46f0-bdba-86370a2dc895',
status='NonOperational', nonOperationalReason='NETWORK_UNREACHABLE',
stopSpmFailureLogged='false', maintenanceReason='null'}), log id:
11ebbdeb
2018-05-28 11:20:04,715+02 INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-37) [5ba0ae45] FINISH,
SetVdsStatusVDSCommand, log id: 11ebbdeb
2018-05-28 11:20:04,769+02 ERROR [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-37) [5ba0ae45] Host
'host01.redacted' is set to Non-Operational, it is missing the following
networks: 'ovirtmgmt'
2018-05-28 11:20:04,786+02 WARN [org.ovirt.engine.core.
dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engineScheduled-Thread-37)
[5ba0ae45] 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-05-28 11:20:04,807+02 INFO [org.ovirt.engine.core.bll.
HandleVdsCpuFlagsOrClusterChangedCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-37)
[7937fb47] Running command: HandleVdsCpuFlagsOrClusterChangedCommand
internal: true. Entities affected : ID: 098c3c99-921d-46f0-bdba-86370a2dc895
Type: VDS
2018-05-28 11:20:04,814+02 INFO [org.ovirt.engine.core.
dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engineScheduled-Thread-37)
[7937fb47] EVENT_ID: VDS_DETECTED(13), Status of host host01.redacted was
set to NonOperational.
2018-05-28 11:20:04,833+02 INFO [org.ovirt.engine.core.bll.HandleVdsVersionCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-37) [4c10675c] Running
command: HandleVdsVersionCommand internal: true. Entities affected : ID:
098c3c99-921d-46f0-bdba-86370a2dc895 Type: VDS
2018-05-28 11:20:04,837+02 INFO [org.ovirt.engine.core.
vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-37)
[4c10675c] Host 'host01.redacted'(098c3c99-921d-46f0-bdba-86370a2dc895)
is already in NonOperational status for reason 'NETWORK_UNREACHABLE'.
SetNonOperationalVds command is skipped.
Full log as attachment.