Bug 1026723

Summary:	remove the use of health servlet
Product:	[Retired] oVirt	Reporter:	Alon Bar-Lev <alonbl>
Component:	ovirt-engine-installer	Assignee:	Simone Tiraboschi <stirabos>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tareq Alayan <talayan>
Severity:	low	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	alonbl, bazulay, gklein, iheim, rbalakri, Rhev-m-bugs, sbonazzo, sherold, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:	ovirt-3.5.0-alpha1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1027210 (view as bug list)		Environment:
Last Closed:	2014-10-17 12:23:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alon Bar-Lev 2013-11-05 10:00:06 UTC

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!

Comment 1 Sandro Bonazzola 2013-11-06 09:24:11 UTC

(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?

Comment 2 Alon Bar-Lev 2013-11-06 09:35:27 UTC

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...

Comment 3 Alon Bar-Lev 2014-04-02 12:45:02 UTC

Sandro,
Is there any real reason why do this for 3.4 if upstream already released?

Comment 4 Sandro Bonazzola 2014-04-02 13:40:26 UTC

(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.

Comment 5 Tareq Alayan 2014-07-30 09:14:14 UTC

ovirt-engine-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch

Comment 6 Sandro Bonazzola 2014-10-17 12:23:11 UTC

oVirt 3.5 has been released and should include the fix for this issue.