Bug 1401702

Summary:	[RFE] Discuss if ovirt should limit the upgrade flow
Product:	[oVirt] ovirt-engine	Reporter:	Marina Kalinin <mkalinin>
Component:	General	Assignee:	bugs <bugs>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	future	CC:	bugs, oourfali
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	mkalinin: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
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-12-06 09:17:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Marina Kalinin 2016-12-05 21:25:56 UTC

Let's discuss in this bug whether oVirt should limit the upgrade flow to upgrading the hosts first and the manager later, or other way around, and blocking any unsupported flows.

For instance, if we decide that host must be upgraded first always, the manager would not allowed to be upgraded until all the hosts in the system have been upgraded to latest release. Or, if we decide that the manager would have to be upgraded first, it will block the upgrade of the hosts to a version it cannot support (but how would it know this?).

Reason for this RFE is some scenarios where due to bugs in release X, upgrading hosts first could prevent a failure state of the system. (see bz#1398664).

Comment 2 Oved Ourfali 2016-12-06 09:17:56 UTC

Closing, as we shouldn't discuss this in bugzilla, but on mailing lists.