When upgrading from Red Hat Enterprise Virtualization Manager 3.0 to 3.1 if the upgrade process fails then instructions to roll back the changes are displayed to the user.
Previously these instructions omitted the steps required to roll back the history database used by the reporting engine. The rhevm-upgrade script has been upgraded and now provides steps for rolling back the history database in the event that the upgrade process fails.
3.1/si25.1
Missing instructions for engine rollback
Should add rollback message for the engine
Since rhevm could be already in 3.1
If we would like to leave engine in 3.1
and it is working
Then
we should install rhevm-dwh (3.1)
and rhevm-reports (3.1)
And run setup for both
----------------------------------------------------
Updating Database... [ DONE ]
**Error: Upgrade failed, rolling back**
**Reason: Jasper done backup!!**
To restore DWH perform the following:
1. Install dwh package:
yum install rhevm-reports-dwh-3.0.8-2
2. Start ETL service:
service rhevm-etl start
service rhevm-notifierd start
To restore reports installation perform the following:
1. Install reports packages:
yum install rhevm-reports-3.0.8-2
2. Stop the JBoss service:
service jbossas stop
3. Rename the original DB:
psql -U postgres -c "ALTER DATABASE rhevmreports RENAME TO rhevmreports_orig;"
4. Run reports setup. Answers to interactive questions do not matter:
rhevm-reports-setup
5. Drop the newly created DB and restore the original one:
psql -U postgres -c "DROP DATABASE rhevmreports"
psql -U postgres -c "ALTER DATABASE rhevmreports_orig RENAME TO rhevmreports;"
6. Restart Jboss service:
service jbossas start
Restoring Database... [ DONE ]
Skipping yum rollback
Starting ovirt-engine... [ DONE ]
Error: Upgrade failed.
please check log at /var/log/ovirt-engine/ovirt-engine-upgrade_2012_12_17_19_40_44.log
* DB Backup available at /var/lib/ovirt-engine/backups/ovirt-engine_db_backup_2012_12_17_19_40_45.sql
Instructions for rhevm (engine)rollback are right and correct,
All instructions for rollback - engine, reports,dwh should be added to upgrade log
/var/log/ovirt-engine/ovirt-engine-upgrade_.log
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0003.html
3.1/si25.1 Missing instructions for engine rollback Should add rollback message for the engine Since rhevm could be already in 3.1 If we would like to leave engine in 3.1 and it is working Then we should install rhevm-dwh (3.1) and rhevm-reports (3.1) And run setup for both ---------------------------------------------------- Updating Database... [ DONE ] **Error: Upgrade failed, rolling back** **Reason: Jasper done backup!!** To restore DWH perform the following: 1. Install dwh package: yum install rhevm-reports-dwh-3.0.8-2 2. Start ETL service: service rhevm-etl start service rhevm-notifierd start To restore reports installation perform the following: 1. Install reports packages: yum install rhevm-reports-3.0.8-2 2. Stop the JBoss service: service jbossas stop 3. Rename the original DB: psql -U postgres -c "ALTER DATABASE rhevmreports RENAME TO rhevmreports_orig;" 4. Run reports setup. Answers to interactive questions do not matter: rhevm-reports-setup 5. Drop the newly created DB and restore the original one: psql -U postgres -c "DROP DATABASE rhevmreports" psql -U postgres -c "ALTER DATABASE rhevmreports_orig RENAME TO rhevmreports;" 6. Restart Jboss service: service jbossas start Restoring Database... [ DONE ] Skipping yum rollback Starting ovirt-engine... [ DONE ] Error: Upgrade failed. please check log at /var/log/ovirt-engine/ovirt-engine-upgrade_2012_12_17_19_40_44.log * DB Backup available at /var/lib/ovirt-engine/backups/ovirt-engine_db_backup_2012_12_17_19_40_45.sql