Bug 1046679 – [dwh] 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 1046679 - [dwh] upgrade backs up the database only after changing ownership of objects

Summary:	[dwh] 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-dwh (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:	Jiri Belka
Docs Contact:

URL:
Whiteboard:	integration
Keywords:	Triaged

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

Reported:	2013-12-26 09:06 EST by Yedidyah Bar David
Modified:	2014-03-20 10:18 EDT (History)
CC List:	8 users (show)

See Also:
Fixed In Version:	IS30 - rhevm-dwh-3.3.0-27.el6ev.src.rpm
Doc Type:	Bug Fix
Doc Text:	Previously, upgrading from 3.2 to 3.3 only backed up the database after changing ownership of all objects. If failure occurred before the ownership was updated, no backup will be created, or the restoration will be performed from a different backup. Now, the backup is performed before any changes are made to the database, and all ownership changes are run in a single psql command.
Story Points:	---
Clone Of:
Clones:	1047117 (view as bug list)
Environment:
Last Closed:	2014-01-21 10:05:45 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	22797	None	None	None	Never
oVirt gerrit	22906	None	None	None	Never
Red Hat Product Errata	RHBA-2014:0036	normal	SHIPPED_LIVE	rhevm-dwh 3.3 bug fix and enhancement update	2014-01-21 14:53:35 EST

Groups: None (edit)

Description Yedidyah Bar David 2013-12-26 09:06:32 EST

Description of problem:

Upgrade from 3.2 does:
1. create a database user 'engine_history'
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 Jiri Belka 2014-01-16 06:28:23 EST

ok is32.2.

backup before `rhevm-dwh-setup' and one created by upgrade itself is equal.

# /bin/su -l postgres -c "PGPASSWORD=123456 /usr/bin/pg_dump -C -E UTF8 -w --disable-dollar-quoting --disable-triggers --format=p -Fc ovirt_engine_history" > ovirt_engine_history
# rhevm-dwh-setup
...snip...
# ls -l /root/ovirt_engine_history /var/lib/ovirt-engine/backups/ovirt-engine-history.backup.2014_01_16_12_25_56
-rw-r--r--. 1 root root 750422 Jan 16 12:24 /root/ovirt_engine_history
-rw-r--r--. 1 root root 750422 Jan 16 12:25 /var/lib/ovirt-engine/backups/ovirt-engine-history.backup.2014_01_16_12_25_56

Comment 4 errata-xmlrpc 2014-01-21 10:05:45 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-0036.html

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