Bug 1313278

Summary:	handle hosted-engine global maintenance
Product:	[oVirt] ovirt-engine	Reporter:	Yedidyah Bar David <didi>
Component:	Setup.Engine	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED WONTFIX	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6.1	CC:	bugs, dfediuck, ylavi
Target Milestone:	---	Flags:	rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-03 09:32:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Yedidyah Bar David 2016-03-01 10:19:10 UTC

Description of problem:

Currently, if the engine is a hosted-engine, and engine-setup is ran without first moving to global maintenance (e.g. for upgrades), the hosted-engine HA will try to migrate the engine vm.

IMO engine-setup should check if it's a hosted-engine, and if so, prompt the user, suggesting to move to global maintenance, and if user accepts, move to global maint at start of the engine-setup transaction and move back at end.

We might consider also doing the same at engine service stop/start for other normal maintenance jobs. Is there is a reasonable flow in which we want a service stop to _not_ move to global maint, and instead cause HA to try and handle it? Not sure. Not opening another bug for this for now, feel free to open/clone.

Comment 1 Yaniv Lavi 2016-03-03 09:32:57 UTC

This is working by design. This appears in the docs and user is expected to review it.