Bug 1069305 - [oVirt] [AAA] ModuleNotFoundException: extension-manager is not found in local module loader
Summary: [oVirt] [AAA] ModuleNotFoundException: extension-manager is not found in loca...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.5.0
Assignee: Yair Zaslavsky
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-24 17:15 UTC by gustavo.pedrosa
Modified: 2016-02-10 19:34 UTC (History)
11 users (show)

Fixed In Version: ovirt-3.5.0-alpha1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-17 12:43:30 UTC
oVirt Team: Infra
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 24967 0 None MERGED aaa: cleanup module usage Never

Description gustavo.pedrosa 2014-02-24 17:15:24 UTC 
Description of problem:
After compile using the Development Environment (install-dev), the JBoss does not start

Version-Release number of selected component (if applicable):
3.5

How reproducible:
100%

Steps to Reproduce:
1. http://www.ovirt.org/OVirt_Engine_Development_Environment
2.
3.

Actual results:
org.jboss.modules.ModuleNotFoundException: Module org.ovirt.engine.core.extension-manager:main is not found in local module loader 

Expected results:
JBoss started

Additional info:
Comment 1 Alon Bar-Lev 2014-02-24 18:04:32 UTC 
Yair,

Even with this patch, now modules are OK, I cannot login, jboss is not responding even to terminate.

Please try to verify these kind of changes using clean environment.

Thanks,
Alon
Comment 2 Itamar Heim 2014-03-02 05:42:23 UTC 
Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.
Comment 3 Sandro Bonazzola 2014-10-17 12:43:30 UTC 
oVirt 3.5 has been released and should include the fix for this issue.
Note You need to log in before you can comment on or make changes to this bug.