Red Hat Bugzilla – Bug 1277398
Unclear message if aaa-jdbc schema is not synced with package version
Last modified: 2016-02-10 14:14:33 EST
Description of problem:
Database schema of aaa-jdbc profile is not updated automatically, but it needs to be done manually. Correct way how to upgrade aaa-jdbc package is described in
If user upgraded aaa-jdbc package, but he didn't perform aaa-jdbc database schema upgrade, unclear exception is raised (the exact error message depends of type of database upgraded during versions).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install oVirt engine 3.6 with ovirt-engine-extension-aaa-jdbc 1.0.0-2
2. Execute engine-setup
3. Update ovirt-engine-extension-aaa-jdbc to 1.0.1-1
4. Restart ovirt-engine service
5. Try to login to webadmin
Unclear exception is raised, so it's hard for user to find out what's wrong
Clear error message should be raised, that user need to perform aaa-jdbc schema upgrade
Fix will be contained ovirt-engine-extension-aaa-jdbc-1.0.2
2015-11-26 09:50:39,343 ERROR [org.ovirt.engine.extension.aaa.jdbc.binding.api.AuthzExtension] (ServerService Thread Pool -- 47)  Unexpected Exception invoking: EXTENSION_INITIALIZE[e5ae1b7f-9104-4f23-a444-7b9175ff68d2]
2015-11-26 09:50:39,343 ERROR [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService Thread Pool -- 47)  Error in activating extension 'internal-authz': Database schema is older than required by currently installed ovirt-engine-extension-aaa-jdbc package version. Please upgrade profile database schema before proceeding (for more info about upgrade please take a look at README.admin file contained in ovirt-engine-extension-aaa-jdbc package).
Tested with ovirt-engine-extension-aaa-jdbc-1.0.3-1.el6ev.noarch and rhevm-188.8.131.52-0.1.el6.noarch
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.