Bug 810679 - [TEXT] engine-upgrade tool is referred as ovirt-engine-upgrade
Summary: [TEXT] engine-upgrade tool is referred as ovirt-engine-upgrade
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 3.1
Assignee: Alex Lourie
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-08 08:49 UTC by Rami Vaknin
Modified: 2014-01-12 23:54 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-09 08:00:16 UTC
oVirt Team: ---


Attachments (Terms of Use)

Description Rami Vaknin 2012-04-08 08:49:34 UTC
The output of engine-upgrade asks to run "ovirt-engine-upgrade" while the correct tool's name is "engine-upgrade". The same happens in the engine-upgrade log filename which better be the same as the log filenames of other engine tools log files:

engine-upgrade's output:
------------------------
Please execute `yum update ovirt-engine-setup`, then re-execute 'ovirt-engine-upgrade'.
To use the current ovirt-engine-setup rpm, execute 'ovirt-engine-upgrade --force-current-setup-rpm'.

engine-upgrade's log:
---------------------
-rw-r--r--. 1 root     root       20754 Apr  5 17:53 ovirt-engine-upgrade_2012_04_05_17_52_24.log

Comment 1 Alex Lourie 2012-04-22 13:50:24 UTC
Fixed posted: http://gerrit.ovirt.org/#change,3785

Comment 2 Ofer Schreiber 2012-05-08 09:44:29 UTC
Alex - any update on the status?

Comment 4 Itamar Heim 2012-08-09 08:00:16 UTC
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/


Note You need to log in before you can comment on or make changes to this bug.