Bug 1370102

Summary:	[Doc-text] Testing flow for HE 3.6 to 4.0 migration is not clear
Product:	[oVirt] ovirt-engine	Reporter:	sefi litmanovich <slitmano>
Component:	Documentation	Assignee:	bugs <bugs>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0.2.7	CC:	adahms, dfediuck, gklein, slitmano, stirabos, ylavi
Target Milestone:	---	Flags:	sbonazzo: needinfo? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-22 08:13:13 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 sefi litmanovich 2016-08-25 10:28:36 UTC

Description of problem:

The testing flow described in the following document isn't clear enough and should be more clear about how to handle the hosts and the HE vm before upgrading the host's rpms to 4.0 to perform hosted-engine --upgrade-appliance:

http://www.ovirt.org/develop/release-management/features/hosted-engine-migration-to-4-0/

A suggestion from simone for a better description of this flow is instead of:

-    Set the global maintenance mode
-    Put the host where the engin VM is running into maintenance
-    Add the 4.0 repo and upgrade the host

Maybe something like this:

- Set the global maintenance mode
- set the host in maintenance mode: all the vm but the engine one will migrate away
- stop the engine VM with hosted-engine --vm-shutdown
- upgrade the host with 4.0 packages
- re-start the engine VM on that host with hosted-engine --vm-start

Comment 1 Sandro Bonazzola 2016-09-22 08:12:15 UTC

Can you please send a patch to the oVirt website fixing it? We'll review it there