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.
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.