Previously, upgrading from 3.2 to 3.3 with a local database only backed up the database after changing ownership of all objects. If a failure occurred before the ownership was updated, no backup would be created, or the restoration would be performed from a different backup. Now, the backup is performed before any changes are made to the database.
DescriptionYedidyah Bar David
2013-12-29 08:18:45 UTC
+++ This bug was initially created as a clone of Bug #1046679 +++
Description of problem:
Upgrade from 3.2 does:
1. create a database user 'engine_reports'
2. Update ownership of all objects to this user
3. backup
4. update the schema to 3.3
This means that if we fail during 1 or 2, we have no backup, and if we fail during 4 we restore from a backup that is different from what we started with.
We should backup as soon as possible, then start doing other things.
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-2014-0035.html