Bug 1401702 - [RFE] Discuss if ovirt should limit the upgrade flow
Summary: [RFE] Discuss if ovirt should limit the upgrade flow
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-05 21:25 UTC by Marina Kalinin
Modified: 2016-12-06 09:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-06 09:17:56 UTC
oVirt Team: Infra
mkalinin: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

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

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