Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1062973

Summary:	3.2 channel should not be disabled before upgrade
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Yedidyah Bar David <didi>
Component:	Documentation	Assignee:	Andrew Dahms <adahms>
Status:	CLOSED DUPLICATE	QA Contact:	ecs-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	acathrow, byount, gklein, sbonazzo, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Build Name: 12875, Installation Guide-3.3-6 Build Date: 09-01-2014 16:06:08 Topic ID: 22421-574531 [Latest]
Last Closed:	2014-02-10 23:23:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yedidyah Bar David 2014-02-09 11:03:59 UTC

Title: Upgrading to Red Hat Enterprise Virtualization Manager 3.3

Describe the issue:

section 6.2.3 instructs to disable the 3.2 channel before upgrading the engine to 3.3.

This has two problems:
1. It causes errors related to dependencies/locking/etc., e.g. bug #1062774 .
2. It prevents rollback.

(2.) is especially important. Even if we somehow manage to solve all such and similar errors, and make the upgrade finish smoothly, we definitely do not want to disable 3.2 - because this will prevent downgrading gracefully back to 3.2 in case there is some problem during the upgrade. 'engine-setup' supports such a downgrade, but this is not possible if the 3.2 channel is disabled.

Comment 2 Andrew Dahms 2014-02-10 23:23:30 UTC

Hi Yedidyah,

Thank you for raising this bug.

I have had a look at this bug and am working on the changes now.
Because Bug #1062793 was raised before this bug, I will close this bug and handle all further contact in Bug #1062793.

*** This bug has been marked as a duplicate of bug 1062793 ***