Bug 1194410 - [AAA] process initialization errors
Summary: [AAA] process initialization errors
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.5
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 3.5.3
Assignee: Ravi Nori
QA Contact: Ondra Machacek
URL:
Whiteboard: infra
Depends On:
Blocks: oVirt-AAA-rewrite
TreeView+ depends on / blocked
 
Reported: 2015-02-19 18:37 UTC by Alon Bar-Lev
Modified: 2016-02-10 19:32 UTC (History)
12 users (show)

Fixed In Version: org.ovirt.engine-root-3.5.1-3
Clone Of:
Environment:
Last Closed: 2015-06-15 08:39:29 UTC
oVirt Team: Infra
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 38085 0 master MERGED aaa : process initialization errors Never
oVirt gerrit 38203 0 ovirt-engine-3.5 MERGED aaa : process initialization errors Never
oVirt gerrit 38204 0 ovirt-engine-3.5.2 MERGED aaa : process initialization errors Never

Description Alon Bar-Lev 2015-02-19 18:37:05 UTC
during initialization we should print and ignore exceptions from the built-in providers.

at EngineExtensionsLoader each time load() or initialize() is called, there should be a try/catch to show potentials errors. same for the entry 
engineInitialize().

for some reason an exception out of this method is not printed in engine.log nor server.log, maybe this should be fixed as well at the core initialization bean.

end result should be engine up with the most valid working built-in extensions.

Comment 1 Sandro Bonazzola 2015-06-15 08:39:29 UTC
This is an automated message.
oVirt 3.5.3 has been released on June 15th 2015 and should include the fix for this BZ. Moving to closed current release.


Note You need to log in before you can comment on or make changes to this bug.