Bug 995502 - rhevm-upgrade attempts to stop the ovirt-engine service when migrating from RHEV 3.0 to RHEV 3.1
Summary: rhevm-upgrade attempts to stop the ovirt-engine service when migrating from R...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.1.5
Hardware: All
OS: Linux
high
high
Target Milestone: ---
: 3.3.0
Assignee: Alex Lourie
QA Contact: Pavel Stehlik
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-09 14:36 UTC by Allie DeVolder
Modified: 2018-12-03 19:36 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-16 16:20:52 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Allie DeVolder 2013-08-09 14:36:12 UTC
Description of problem:
When running the rhevm-upgrade to migrate from RHEV 3.0 to RHEV 3.1, the script attempts to stop the ovirt-engine service instead of the jbossas service


Version-Release number of selected component (if applicable):
rhevm-setup-3.1.0-55

How reproducible:
Very

Steps to Reproduce:
1. Build RHEV 3.0 environment
2. Change proper channels and run 'yum update rhevm-setup'
3. Run rhevm-upgrade to migration to 3.1


Actual results:
Script fails because it attempts to stop the non-existent ovirt-engine service

Expected results:
Script stops the jbossas service and continues the migration

Additional info:
The workaround is to manually edit the engine-upgrade script, and find:

def stopEngine(service=basedefs.ENGINE_SERVICE_NAME):

and relace basedefs.EXEC_SERVICE, service, "stop", 

with basedefs.EXEC_SERVICE, "jbossas", "stop",

Comment 22 Alex Lourie 2013-12-05 16:19:54 UTC
The update to the upgrade article https://access.redhat.com/site/articles/269333 is published.

Comment 24 Sandro Bonazzola 2013-12-16 16:20:52 UTC
Closing since the bug doesn't affect current release ( >= 3.2.0 ) and documentation exists for previous releases ( https://access.redhat.com/site/articles/269333 ).


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