Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1034936

Summary:	Changedbowner.sh is useless in case that only several tables have wrong permission
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Tomas Dosek <tdosek>
Component:	ovirt-engine-config	Assignee:	Eli Mesika <emesika>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.3.0	CC:	acathrow, alonbl, iheim, lyarwood, pablo.iranzo, Rhev-m-bugs, sbonazzo, sgordon, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-27 10:04:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1020228

Description Tomas Dosek 2013-11-26 17:54:16 UTC

Description of problem:
Please take a look at: 1034929

The mentioned script Alters only DB owner which in case we check all entities
in otopi setup has a hole.

The hole are for instance temporary tables created and owned by postgres as they do not get affected by alter db owner.

This causes the script to be useless in few scenarios of broken upgrade due to DB schema issues.

Version-Release number of selected component (if applicable):
is24

How reproducible:
100 %

Steps to Reproduce:
1. Have a table unde engine DB owned by postgres
2. Try to upgrade (upgrade fails)
3. Try changedbowner.sh
4. Try to upgrade again (it indeed does not work)

Actual results:
Doesn't work - entites are not affected

Expected results:
Should change all entities owneship as well, not only DB schema ownership

Additional info:
More detailed info in BZ: 1034929

Comment 3 Eli Mesika 2013-11-27 10:04:24 UTC

Reason for Close :

Please see https://bugzilla.redhat.com/show_bug.cgi?id=1034929 Comment #3

*** This bug has been marked as a duplicate of bug 1034929 ***