Red Hat Bugzilla – Bug 1262831
engine db infrastructure doesn't work properly with other schemas
Last modified: 2016-02-10 14:05:00 EST
Description of problem:
In oVirt 3.6 engine and aaa-jdbc extension providing 'internal' domain are both installed in the same database using same database user. Engine is installed by default into 'public' schema, aaa-jdbc extension providing 'internal' domain is installed into 'aaa_jdbc' schema. Unfortunately engine db infrastructure functions included in common_sp.sql doesn't work properly if 'aaa_jdbc' schema is present.
Version-Release number of selected component (if applicable):
Any 3.6 version or master
Steps to Reproduce:
This is reproducing steps for fn_db_add_column function:
1. Create an upgrade script which will try to add column 'password_valid_to' to engine 'users' table
2. Execute engine-setup
3. Column 'password_valid_to' is not added into engine 'users' table, because column of the same name already exists in aaa-jdbc 'users' table
Engine database infrastructure functions doesn't work correctly if multiple schemas are present in engine database
Engine database infrastructure function should use only 'public' schema
verified in rhevm-3.6.1-0.2.el6.noarch
Since oVirt 3.6.0 has been released, moving from verified to closed current release.