On Tue, May 14, 2019 at 11:10 AM <axel.thimm@01lgc.com> wrote:
Hi,
yes, the host seems to have been updated.
vdsm-api-4.30.13-1.el7ev.noarch vdsm-http-4.30.13-1.el7ev.noarch vdsm-hook-vmfex-dev-4.30.13-1.el7ev.noarch vdsm-network-4.30.13-1.el7ev.x86_64 vdsm-common-4.30.13-1.el7ev.noarch vdsm-yajsonrpc-4.30.13-1.el7ev.noarch vdsm-jsonrpc-4.30.13-1.el7ev.noarch vdsm-hook-ethtool-options-4.30.13-1.el7ev.noarch vdsm-hook-openstacknet-4.30.13-1.el7ev.noarch vdsm-hook-vhostmd-4.30.13-1.el7ev.noarch vdsm-client-4.30.13-1.el7ev.noarch vdsm-hook-fcoe-4.30.13-1.el7ev.noarch vdsm-python-4.30.13-1.el7ev.noarch vdsm-4.30.13-1.el7ev.x86_64
I see some communication happening between the engine and the host's vdsmd on port 54321, but it is encrypted. It does break off immediately, so I wonder if this is an SSL issue. I already downgraded gnutls due to https://bugzilla.redhat.com/show_bug.cgi?id=1648190
The engine just complains on communication errors, e.g. 2019-05-14 09:30:56,275 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler_Worker-83) [] Command 'GetCapabilitiesVDSCommand(HostName = hetzner-XXXXXX, VdsIdAndVdsVDSCommandParam etersBase:{runAsync='true', hostId='2bc7bd41-aaa2-4973-95ab-402a0fe32daf', vds='Host[hetzner-XXXXXX,2bc7bd41-aaa2-4973-95ab-402a0fe32daf]'})' execution failed: VDSGenericException: VDSNetworkException: Message timeout which ca n be caused by communication issues 2019-05-14 09:30:56,275 ERROR [org.ovirt.engine.core.vdsbroker.HostMonitoring] (DefaultQuartzScheduler_Worker-83) [] Failure to refresh Vds runtime info: VDSGenericException: VDSNetworkException: Message timeout which can be c aused by communication issues 2019-05-14 09:30:56,275 ERROR [org.ovirt.engine.core.vdsbroker.HostMonitoring] (DefaultQuartzScheduler_Worker-83) [] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetworkExce ption: Message timeout which can be caused by communication issues
Would trying
hosted-engine --upgrade-appliance
make any sense w/o restoring the communication on vdsm level?
Might not make sense at all, --upgrade-appliance is only for el6/3.6->el7/4.0. Later upgrades you do inside the VM. I'd personally first try to fix the engine<->vdsm comm issue. How did you upgrade the host? yum update? Is is ovirt-node? If you are ok debugging/fixing yourself and only need the occasional tip, fine. Otherwise, please provide more details - exact versions of engine/vdsm, last version that worked, whether you can reinstall the host or need anything on it, etc. Best regards, -- Didi