On Wed, Jun 19, 2019 at 12:44 PM Stefano Danzi <s.danzi(a)hawai.it> wrote:
Solved!
During host installation it run yum to install some packages.
Corporate firewall was blocking internet access for this host so
installation fails.
Enabling internet access and readding the host solved the problem.
Glad to hear that :-)
I think that a more specific error entry in Engine UI could be nice.
Something like "Yum on host was unable to reach servers".
Makes sense, would you like to open an RFE bug for this?
Thanks and best regards,
Il 19/06/2019 07:27, Yedidyah Bar David ha scritto:
> On Tue, Jun 18, 2019 at 6:55 PM Stefano Danzi <s.danzi(a)hawai.it> wrote:
>> Hello,
>> I have i running cluster ad I have to add a new host.
>> Current cluster has AMD type cpu, new host has intel CPU su I added a new
cluster in same datacenter (datacenter default compatibility 4.2).
>>
>> New Host is running node 4.3.4, engine is 4.3.4.3-1.el7
>>
>> The new host is attached to ths new cluster, but engine can't connect.
>> Engine logs tell me:
>>
>> 2019-06-18 13:04:21,873+02 ERROR
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process
messages General SSLEngine problem
>> 2019-06-18 13:04:21,878+02 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
(EE-ManagedThreadFactory-engineScheduled-Thread-46) [] Unable to RefreshCapabilities:
VDSNetworkException: VDSGenericException: VDSNetworkException: General SSLEngine problem
4.3..4.3-1.el7
> Please check/share relevant logs - from the engine:
>
> /var/log/ovirt-engine/host-deploy/*
>
> >From the host:
>
> /var/log/vdsm/vdsm.log
>
> Thanks and best regards,
--
Didi