On Tue, Dec 22, 2015 at 2:54 PM, Alexander Wels <awels@redhat.com> wrote:
If you can provide us with the obfuscated stack trace, we can point to you
what to look for in the mapping file.
Hello,
I'm going to try.
In the mean time, do you think it could be related somehow with what below?
After engine upgrade to 3.6.1 from 3.6.0 I updated via yum the package ovirt-engine-extension-aaa-jdbc, without running its own update phase (in practice another engine-setup as I only have internal profile)
And this caused problems with the internal profile.
Can this in some way influence the exception I'm getting? O that perhaps it is better to first solve this problem?
Let me know. I can downgrade again the ovirt-engine-extension-aaa-jdbc package and try your suggestions instead and let see after the problem with the extension.