Bug 1043898

Summary:	rhevm-upgrade is deprecated
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Yedidyah Bar David <didi>
Component:	Documentation	Assignee:	Andrew Dahms <adahms>
Status:	CLOSED NOTABUG	QA Contact:	ecs-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	acathrow, gklein, yeylon
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Build Name: 22493, Administration Guide-3.3-Beta-1 Build Date: 21-11-2013 20:49:12 Topic ID: 7524-546995 [Specified]
Last Closed:	2014-02-17 00:16:10 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:

Description Yedidyah Bar David 2013-12-17 12:22:57 UTC

Title: Updating Red Hat Enterprise Virtualization Manager

Describe the issue:

In rhevm 3.3, engine-upgrade is deprecated. rhevm-setup (which is a link to engine-setup) does both clean installs and upgrades.

Suggestions for improvement:

rhevm-upgrade should be replaced by rhevm-setup everywhere (almost?). Perhaps a note explaining the above should be added somewhere.

Note that in 3.2 it's not deprecated. So a typical scenario might be:

install 3.2
rhevm-upgrade
get a notification to do 'yum update rhevm-setup' and try again
yum update rhevm-setup
rhevm-upgrade
get a notification that it's deprecated in favor of rhevm-setup
rhevm-setup

Comment 1 Yedidyah Bar David 2013-12-18 08:45:37 UTC

I see that a newer version (than the one on https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/ which is "3.3-Beta") already has this.

Comment 2 Andrew Dahms 2014-02-17 00:16:10 UTC

Hi Yedidyah,

Thank you for raising this bug, and my apologies for not getting to it sooner.

The changes requested in this bug have been made in all documents in the suite now, as managed under Bug #997341.
Because the changes are managed via that bug, I will close this bug, but please let me know if you have any further requests in regards to this issue and I will implement them for you.