liveliness check fails on one host

I have an ovirt installation (4.2.6), and I have come accross this issue: Hosted engine can migrate to a certain host say host5. Admin portal is working fine, everything is working fine AFAIK but hosted-engne --vm-status shows "failed livelines check", when engine is on that host, so after a while the engine migrates somewhere else, it not a terrible problem, but it is annoying and I would like to know why is this happening, and if there is a way to fix it On every other host in the cluster this problem does not exists. firewall rules are exactly the same on hosts (in fact they are copied) . Any places to look at? Thank you

On Sun, Sep 30, 2018 at 9:22 AM <g.vasilopoulos@uoc.gr> wrote:
I have an ovirt installation (4.2.6), and I have come accross this issue: Hosted engine can migrate to a certain host say host5. Admin portal is working fine, everything is working fine AFAIK but hosted-engne --vm-status shows "failed livelines check", when engine is on that host, so after a while the engine migrates somewhere else, it not a terrible problem, but it is annoying and I would like to know why is this happening, and if there is a way to fix it On every other host in the cluster this problem does not exists. firewall rules are exactly the same on hosts (in fact they are copied) . Any places to look at?
Liveliness check is performed over http so I'd suggest to check whatever on the host could cause it to fail like routing rules and name resolution for the engine VM and so on. You can try to manually reproduce the check executing: . /etc/ovirt-hosted-engine/hosted-engine.conf curl http://${fqdn}/ovirt-engine/services/health
Thank you _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/YO5IP3P4FGXVWF...

ok fixed it. For some strange reason there was a leftover record on /etc/hosts showing to 192.168.122.15 thank you very much
participants (2)
-
g.vasilopoulos@uoc.gr
-
Simone Tiraboschi