Bug 1047117 - [reports] upgrade backs up the database only after changing ownership of objects
Summary: [reports] upgrade backs up the database only after changing ownership of objects
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-reports
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.3.0
Assignee: Yedidyah Bar David
QA Contact: Tareq Alayan
URL:
Whiteboard: integration
Depends On:
Blocks: rhev3.3ga
TreeView+ depends on / blocked
 
Reported: 2013-12-29 08:18 UTC by Yedidyah Bar David
Modified: 2015-09-22 13:10 UTC (History)
10 users (show)

Fixed In Version: IS31 - rhevm-reports-3.3.0-28.el6ev.noarch.rpm
Doc Type: Bug Fix
Doc Text:
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.
Clone Of: 1046679
Environment:
Last Closed: 2014-01-21 14:57:16 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
logs (62.35 KB, application/x-tar-gz)
2014-01-17 09:52 UTC, Tareq Alayan 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0035 0 normal SHIPPED_LIVE rhevm-reports 3.3 bug fix and enhancement update 2014-01-21 19:53:30 UTC
oVirt gerrit 22708 0 None None None Never
oVirt gerrit 23047 0 None None None Never

Description Yedidyah 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.
Comment 2 Tareq Alayan 2014-01-17 09:51:50 UTC 
verified on rhevm-reports-3.3.0-28.el6ev.noarch rhevm-dwh-3.3.0-28.el6ev.noarch
the backup is done before the upgrade see log attached
Comment 3 Tareq Alayan 2014-01-17 09:52:28 UTC 
Created attachment 851495 [details]
logs
Comment 5 errata-xmlrpc 2014-01-21 14:57:16 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.