Bug 1313278 - handle hosted-engine global maintenance
Summary: handle hosted-engine global maintenance
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Setup.Engine
Version: 3.6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
: ---
Assignee: Sandro Bonazzola
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-01 10:19 UTC by Yedidyah Bar David
Modified: 2017-05-11 09:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-03 09:32:57 UTC
oVirt Team: Integration
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.