Bug 866143 - [rhevm] - Upgrade - No Roll-Back when Upgrade 3.0 to 3.1 fails
Summary: [rhevm] - Upgrade - No Roll-Back when Upgrade 3.0 to 3.1 fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Alex Lourie
QA Contact: Tareq Alayan
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-14 10:46 UTC by David Botzer
Modified: 2014-01-14 00:04 UTC (History)
9 users (show)

Fixed In Version: si24
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 20:03:25 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
rhevm-old (48.91 KB, application/x-gzip)
2012-10-14 10:46 UTC, David Botzer
no flags Details

Description David Botzer 2012-10-14 10:46:33 UTC
Created attachment 626885 [details]
rhevm-old

Description of problem:
Upgrade 3.0 to 3.1 fails for some reason (e.x open db connections)
As a result of that - /etc/rhevm & /etc/pki/rhevm folders are changed to rhevm-old
-- cannot rerun rhevm-upgrade

Version-Release number of selected component (if applicable):
3.0 ic157
3.1 si20

How reproducible:
always

Steps to Reproduce:
1.install rhevm30+ETL+reports
2.upgrade rhevm-setup
3.rhevm-upgrade - will fail on a BZ that setup doesnt asks to close connections
4.Close DB connections (restart ETL, postgresql)
4.Rerun of rhevm-upgrade Fails
  
Actual results:
/etc/rhevm & /etc/pki/rhevm folders are changed to rhevm-old

Expected results:
Rollback should return state

Additional info:

Comment 3 Tareq Alayan 2012-11-13 18:39:12 UTC
couldn't reproduce.
DB backup-ed and renamed.


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