[ovirt-devel] Re: Health check endpoint in the engine hanging forever on CheckDBConnection

It would be good to notify on devel list when there are breaking changes across multiple components, development envs usually do not update everything. If there is an actual incompatibility like in this case, it would also be good to not only require new version, but properly conflict with an old

[ovirt-devel] Re: Health check endpoint in the engine hanging forever on CheckDBConnection

In this run there is ovirt-engine-* used with git c2c805a2662, however, vdsm-jsonrpc-client is in version 1.6.0 which has a breaking change of removing reactive streams support in favor to java.util.concurrent.FLOW [1] which is handled by engine's commit ff3aa4da956 [2] [1] https://gerrit.ovirt.o

[ovirt-devel] Re: Health check endpoint in the engine hanging forever on CheckDBConnection

I can see something I was recently touching. Removal of reactive stream from vdsm-jsonrpc-java. Checking... Artur On Fri, Nov 27, 2020 at 11:47 AM Marcin Sobczyk wrote: > > > On 11/27/20 11:24 AM, Martin Perina wrote: > > Hi, > > > > the health status is pretty stupid simple call to database: >

[ovirt-devel] Re: Health check endpoint in the engine hanging forever on CheckDBConnection

On 11/27/20 11:24 AM, Martin Perina wrote: Hi, the health status is pretty stupid simple call to database: https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/services/src/main/java/org/ovirt/engine/core/services/HealthStatus.java

[ovirt-devel] Re: Health check endpoint in the engine hanging forever on CheckDBConnection

Hi, the health status is pretty stupid simple call to database: https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/services/src/main/java/org/ovirt/engine/core/services/HealthStatus.java https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/bll/src/main/