Problems with Ovirt HostedEngine, why doesn't reinstalling the host help?

Question

Virtualization

Good afternoon.
There are problems with Ovirt version 4.2. Question about one of them.
2 hosts installed, Engine running in HostedEngine mode. The problem is that one of the hosts cannot determine the status of the HostedEngine VM. And if the VM is running on it, after a while it sends it to reboot.
If it is started on other host - no problems arise.
However, the hosted-engine --vm-status status query outputs the following:
Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"}
In host logs (/var/log/messages):
error : qemuDomainAgentAvailable:6946 : Guest agent not responding:
hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 3400)
Engine logs contain this(/var/log/messages):
[9B blob data]
code 400, message Bad HTTP/0.9 request type ( '\x16\x03\x03\x00\xb9\x01\x00\x00\xb5\x03\x03[\x91\x02r!d\x1f\x00\x95\x1a\x93\x13\x10N\xe9t\xb2\xc9 \x92^r'), etc.
The same thing happens when the systemctl status ovirt-provider-ovn -l command is output.
If I understand correctly, the problem is in ovirt-provider-ovn. Moreover, as far as I understand, the problem is inconsistency of requests, such as an https request is sent to http and vice versa. But why is everything okay with the second host? A set of packages, versions, etc. the same. Both hosts were rearranged, and from the Engine interface - the result is the same.
Thanks in advance for the tip/solution.

Answer 1

I'll answer here myself, maybe it will help someone. The problem was in one incorrect entry in the hosts of this host. The HostedEngine FQDN entry was pointing to the wrong IP address. All.