Bug 1047117 – [reports] upgrade backs up the database only after changing ownership of objects

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

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

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine-reports (Show other bugs)
Sub Component:
Version:	3.3.0
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	---
Target Release:	3.3.0
Assigned To:	Yedidyah Bar David
QA Contact:	Tareq Alayan
Docs Contact:

URL:
Whiteboard:	integration
Keywords:	Triaged

Depends On:
Blocks:	rhev3.3ga
	Show dependency tree / graph

Reported:	2013-12-29 03:18 EST by Yedidyah Bar David
Modified:	2015-09-22 09 EDT (History)
CC List:	10 users (show)

See Also:
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.
Story Points:	---
Clone Of:	1046679
Environment:
Last Closed:	2014-01-21 09:57:16 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
logs (62.35 KB, application/x-tar-gz) 2014-01-17 04:52 EST, Tareq Alayan	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	22708	None	None	None	Never
oVirt gerrit	23047	None	None	None	Never
Red Hat Product Errata	RHBA-2014:0035	normal	SHIPPED_LIVE	rhevm-reports 3.3 bug fix and enhancement update	2014-01-21 14:53:30 EST

Groups: None (edit)

Description Yedidyah Bar David 2013-12-29 03:18:45 EST

+++ 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 04:51:50 EST

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 04:52:28 EST

Created attachment 851495 [details]
logs

Comment 5 errata-xmlrpc 2014-01-21 09:57:16 EST

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.