Bug 999024
| Summary: | [engine-backend] EJBComponentUnavailableException when engine crashes after task of CreateSnapshotVDSCommand was sent | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Elad <ebenahar> | ||||||||
| Component: | ovirt-engine | Assignee: | Martin Perina <mperina> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Tareq Alayan <talayan> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 3.3.0 | CC: | acathrow, bazulay, ebenahar, iheim, lpeer, pstehlik, rgolan, Rhev-m-bugs, yeylon, yzaslavs | ||||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||||
| Target Release: | 3.4.0 | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | infra | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-12-12 12:54:35 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1078909, 1142926 | ||||||||||
| Attachments: |
|
||||||||||
CORRECTION: Engine throws this exception after it crashes after CreateSnapshotVDSCommand was send. So the reproduction step is to create a snapshot to vm and restart ovirt-engine right after the task starts on spm. Does the operation succeeds ? No, engine performs roll-back for CreateAllSnapshotsFromVmCommand. The roll-back ends successfully. The only problem here is the log issue Attaching the relevant engine.log Created attachment 790093 [details]
engine.log
(In reply to Elad from comment #1) > CORRECTION: > Engine throws this exception after it crashes after CreateSnapshotVDSCommand > was send. > So the reproduction step is to create a snapshot to vm and restart > ovirt-engine right after the task starts on spm. 1st please supply the server.log as well 2nd The engine doesn't crash. it shuts down so the EJB components (LockManager, DB connection manager etc) throws exceptions with a clear message (component is shutting down) The real issue here is WHY the engine shuts down? bug 962180 with possibly similar case so I want to know if thats a real issue. (In reply to Roy Golan from comment #5) > (In reply to Elad from comment #1) > > CORRECTION: > > Engine throws this exception after it crashes after CreateSnapshotVDSCommand > > was send. > > So the reproduction step is to create a snapshot to vm and restart > > ovirt-engine right after the task starts on spm. > > 1st please supply the server.log as well > > 2nd The engine doesn't crash. it shuts down so the EJB components > (LockManager, DB connection manager etc) throws exceptions with a clear > message (component is shutting down) > > The real issue here is WHY the engine shuts down? That was part of the my test - the restart was done manually. The only issue is the ugly exception server.log will be attached Created attachment 795856 [details]
server.log
(In reply to Elad from comment #6) > (In reply to Roy Golan from comment #5) > > (In reply to Elad from comment #1) > > > CORRECTION: > > > Engine throws this exception after it crashes after CreateSnapshotVDSCommand > > > was send. > > > So the reproduction step is to create a snapshot to vm and restart > > > ovirt-engine right after the task starts on spm. > > > > 1st please supply the server.log as well > > > > 2nd The engine doesn't crash. it shuts down so the EJB components > > (LockManager, DB connection manager etc) throws exceptions with a clear > > message (component is shutting down) > > > > The real issue here is WHY the engine shuts down? > That was part of the my test - the restart was done manually. The only issue > is the ugly exception > not an issue. > > server.log will be attached (In reply to Elad from comment #0) > Created attachment 788521 [details] > logs > > Description of problem: > When engine looses it's connection with host after CreateSnapshotVDSCommand > was send, it throws this exception in log: > > 2013-08-20 16:01:40,877 ERROR > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > (DefaultQuartzScheduler_Worker-74) EJBComponentUnavailableException: > JBAS014559: Invocation cannot proceed as component is shutting down: > org.jboss.as.ejb3.component.EJBComponentUnavailableException: JBAS014559: > Invocation cannot proceed as component is shutting down > at > org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1. > processInvocation(ShutDownInterceptorFactory.java:59) > [jboss-as-ejb3.jar:7.2.0.Final-redhat-8] > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) > [jboss-invocation.jar:1.1.1.Final-redhat-2] This is standard JBoss error message when you try to invoke some method on EJB during JBoss shutdown. Since the rollback was successful, there's no error. |
Created attachment 788521 [details] logs Description of problem: When engine looses it's connection with host after CreateSnapshotVDSCommand was send, it throws this exception in log: 2013-08-20 16:01:40,877 ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-74) EJBComponentUnavailableException: JBAS014559: Invocation cannot proceed as component is shutting down: org.jboss.as.ejb3.component.EJBComponentUnavailableException: JBAS014559: Invocation cannot proceed as component is shutting down at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:59) [jboss-as-ejb3.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation.jar:1.1.1.Final-redhat-2] Version-Release number of selected component (if applicable): rhevm-3.3.0-0.15.master.el6ev.noarch How reproducible: 100% Steps to Reproduce: On a block pool: - create a snapshot to vm and restart vdsm right after the task starts Actual results: When vdsm crashes after engine send the createVolume command, engine throws the mentioned exception. There are no other issues, just the exception in log Expected results: Engine should revert the CreateSnapshotVDSCommand without throwing these exception Additional info: logs