I have a new installation of ovirt hyperconverged single node using glusterfs. I was able to run gdeploy and then use the web interface to run the self hosted engine setup. Ovirt node is running 4.2.5.1. If I go to localhost>ovirt machines tab from my node
I see a message in the upper right corner saying "ovirt login in progress" with spinning icon after putting in the credentials. After a minute or less I am redirected to -
where the web page says- "the connection has timed out."
"The server at engine.cyber-range.lan is taking too long to respond." I also notice I no longer have the option to choose VNC or console because the web page keeps on attempting to reconnect. When I tried to connect using a console with virt-viewer
it errored out on me. (I didn't make note of the message)
Virtualization>hosted engine tab reports that my hosted engine is up. This is further confirmed by CLI
#hosted-engine --check-liveliness. On occasion though, CLI reports HE is not up. If I try to ssh to HE sometimes I can connect, but it is VERY slow to do so. Once I connect it often appears to freeze or be very slow to enter any input commands to the
HE. HE is effectively useless.
I get frequent log messages in the console- "ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR Engine VM has bad health status, timeout in 300 seconds"
This is a new setup, so I haven't lost anything if I need to start over. What do you suggest? Is there an easy way to recover or should I reinstall HE? Thanks for your advice!