On Tue, Feb 12, 2019 at 4:47 PM <joshuaosko@gmail.com> wrote:
The self-hosted engine had an issue whereby it'd /var partition was full. A few days later the engine was rebooted; however, it did not come back up gracefully. I presently have three CentOS 7 hosts which can spin up a new hosted engine vm; however every attempt to do so results in: Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"}
The VM is not "up" as it does not even respond to ping, let alone having any ability to ssh or console into it to see what's wrong.
check if that VM is really up with virsh -r list If so maybe it could be something with fsck previnting it from booting due to disk errors; you can try to connect with VNC since in that case neither ssh or the serial console will work due to the lack of guest OS support. You can use hosted-engine --add-console-password to add a temporary VNC password; it will also print out the connection string.
All of the VMs that have been built using this engine appear to be fully operational. Is there any guidance anyone can give me? At this point I'm wondering what the consequences are to deploying a new hosted engine within that same cluster.
If anyone could shed light on this matter it would be tremendously appreciated! Thanks. _______________________________________________ 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/6UENXHDTWSMYX5...