Bug 1436966 - EJB Invocation failed on component MacPoolPerCluster for method public org.ovirt.engine.core.bll.network.macpool.ReadMacPool
Summary: EJB Invocation failed on component MacPoolPerCluster for method public org.ov...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: ---
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.1.2
: 4.1.2
Assignee: Yevgeny Zaspitsky
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-29 06:27 UTC by Yaniv Kaul
Modified: 2017-05-23 08:20 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-05-23 08:20:16 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: blocker+

Attachments (Terms of Use)
server log (12.08 KB, application/x-gzip)
2017-03-29 09:14 UTC, Yaniv Kaul 		no flags Details
engine log (896.51 KB, application/x-gzip)
2017-03-29 09:14 UTC, Yaniv Kaul 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 74827 0 'None' MERGED engine: avoid running ChangeVmCluster upon targetClusterId==null 2020-05-28 15:33:09 UTC
oVirt gerrit 75077 0 'None' MERGED engine: avoid running ChangeVmCluster upon targetClusterId==null 2020-05-28 15:33:09 UTC

Description Yaniv Kaul 2017-03-29 06:27:59 UTC 
Description of problem:
Not sure what the cause is, but I'm seeing this exception on server.log:
2017-03-29 01:52:42,652-04 ERROR [org.jboss.as.ejb3.invocation] (ForkJoinPool-1-worker-2) WFLYEJB0034: EJB Invocation failed on component MacPoolPerCluster for method public org.ovirt.engine.core.bll.network.macpool.ReadMacPool org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster.getMacPoolForCluster(org.ovirt.engine.core.compat.Guid): javax.ejb.EJBException: java.lang.IllegalStateException: Pool for id="null" does not exist
        at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:187) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
        at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:277) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
        at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:327) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
        at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
        at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
        at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
        at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
        at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
        at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
        at org.jboss.as.ejb3.concurrency.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:110) [wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]


Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.0.master.20170328185427.gitb0842bf.el7.centos.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Red Hat Bugzilla Rules Engine 2017-03-29 06:31:55 UTC 
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Comment 2 Yevgeny Zaspitsky 2017-03-29 06:44:09 UTC 
Yaniv, could you provide some more leading info: flow that was run and/or the rest of the stacktrace?
Comment 3 Yaniv Kaul 2017-03-29 06:51:13 UTC 
(In reply to Yevgeny Zaspitsky from comment #2)
> Yaniv, could you provide some more leading info: flow that was run and/or
> the rest of the stacktrace?

Regular ovirt-system-tests on Master.
Comment 4 Dan Kenigsberg 2017-03-29 07:14:48 UTC 
Do you still have the complete engine.log? Did any test fail?
Comment 5 Yevgeny Zaspitsky 2017-03-29 08:32:41 UTC 
The same for server.log...
Comment 6 Yaniv Kaul 2017-03-29 09:14:10 UTC 
Created attachment 1267265 [details]
server log
Comment 7 Yaniv Kaul 2017-03-29 09:14:43 UTC 
Created attachment 1267266 [details]
engine log
Comment 8 Yaniv Kaul 2017-03-30 12:50:17 UTC 
(In reply to Yevgeny Zaspitsky from comment #2)
> Yaniv, could you provide some more leading info: flow that was run and/or
> the rest of the stacktrace?

Regular ovirt-system-tests on Master.
Comment 9 Dan Kenigsberg 2017-04-27 11:58:56 UTC 
Verify this bug if you no longer see the reported exception in engine.log.
Note You need to log in before you can comment on or make changes to this bug.