The health servlet is a legacy interface that IMO should not be used at all, marked obsolete and removed as soon as we can. Please make the notification service use the formal supported API to pull engine status. This applies to both setup and hosted. Thanks!
(In reply to Alon Bar-Lev from comment #0) > Please make the notification service use the formal supported API to pull > engine status. import ovirtsdk.api ovirtapi=ovirtsdk.api.API( url='https://sbonazzo.csb/api', username='admin@internal', password='****', ca_file='/etc/pki/ovirt-engine/ca.pem', ) once connection is established (engine running), how may I know if DB is Up?
our application is not initialized if database connection is down... or do you suggest otherwise...? # systemctl stop ovirt-engine # systemctl stop postgresql # systemctl start ovirt-engine # curl -v -k https://admin%40internal:engine@localhost/api # systemctl start postgresql # curl -v -k https://admin%40internal:engine@localhost/api BTW: I do not see our application recovering from database down anyway...
Sandro, Is there any real reason why do this for 3.4 if upstream already released?
(In reply to Alon Bar-Lev from comment #3) > Sandro, > Is there any real reason why do this for 3.4 if upstream already released? No, it can be postponed to 3.5.0. It doesn't solve any real issue, just avoiding to use features considered deprecated.
ovirt-engine-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch
oVirt 3.5 has been released and should include the fix for this issue.