Hi,

the health status is pretty stupid simple call to database:


So it should definitely not hang forever unless there is some serious issue in the engine start up or PostgreSQL database. Could you please share logs? Especially interesting would server.log and engine.log from /var/log/ovirt-engine

Martin


On Thu, Nov 26, 2020 at 4:24 PM Marcin Sobczyk <msobczyk@redhat.com> wrote:
Hi,

I'm trying out (I think) the latest build of ovirt-engine in OST [1] and
the basic suite
fails when we do engine reconfiguration and then restart the service [2].
After restarting we wait on the health check endpoint status here [3].
This however ends with a timeout.
I tried running manually:

curl -D - http://engine/ovirt-engine/services/health

and that command also hangs forever.
In the engine log the last related entry seem to be:

2020-11-26 16:20:15,761+01 DEBUG
[org.ovirt.engine.core.utils.servlet.LocaleFilter] (default task-7) []
Incoming locale 'en-US'. Filter determined locale to be 'en-US'
2020-11-26 16:20:15,761+01 DEBUG
[org.ovirt.engine.core.services.HealthStatus] (default task-7) [] Health
Status servlet: entry
2020-11-26 16:20:15,761+01 DEBUG
[org.ovirt.engine.core.services.HealthStatus] (default task-7) []
Calling CheckDBConnection query

Has anyone else also encountered that?

Regards, Marcin

[1] ovirt-engine-4.4.4.3-0.0.master.20201126133903.gitc2c805a2662.el8.noarch
[2]
https://github.com/oVirt/ovirt-system-tests/blob/3e2fc267b376a12eda131fa0e9cda2d94e36e2be/basic-suite-master/test-scenarios/test_001_initialize_engine.py#L88
[3]
https://github.com/oVirt/ovirt-system-tests/blob/3e2fc267b376a12eda131fa0e9cda2d94e36e2be/ost_utils/ost_utils/pytest/fixtures/engine.py#L160



--
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.