Red Hat Bugzilla – Bug 1259345
engine-cleanup fails due to error 'must be owner of ...'
Last modified: 2016-02-10 14:14:33 EST
Description of problem:
When executing engine-cleanup on F22, it fails with error:
[ ERROR ] Failed to execute stage 'Misc configuration': must be owner of schema pg_catalog
The issue is that we try to remove all schemas from returned from 'select * from information_schema.schemata' and it return also system schemas (on Centos 6/7 this query returns only schemas owned by logged in user).
Version-Release number of selected component (if applicable):
oVirt 3.6 beta3
Steps to Reproduce:
1. Install and configure engine using engine-setup
2. After successful setup try to remove all engine configuration using engine-cleanup
engine-cleanup should be successful
Only now saw .
If that was enough for dropping the schema created for aaa-jdbc, and you didn't have to individually drop each object in it, keeping the conditions elsewhere to drop objects only from schema 'public', why isn't it enough to replace the entire logic dropping our objects with:
drop SCHEMA public cascade;
(Setting needinfo on Eli although 'you' above is Martin).
(In reply to Yedidyah Bar David from comment #1)
> Only now saw .
> If that was enough for dropping the schema created for aaa-jdbc, and you
> didn't have to individually drop each object in it, keeping the conditions
> elsewhere to drop objects only from schema 'public', why isn't it enough to
> replace the entire logic dropping our objects with:
> drop SCHEMA public cascade;
The 'public' schema is created by the database engine and is actually the default schema
for example , the following are equivalent :
CREATE TABLE products ( ... );
CREATE TABLE public.products ( ... );
Therefor, when cleanup is used it should drop each object specifically
verified in rhevm-setup-base-184.108.40.206-0.1.el6.noarch
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.