Bug 877752

Summary: engine: .CannotGetJdbcConnectionException on extend domain command
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: ovirt-engineAssignee: Daniel Erez <derez>
Status: CLOSED WONTFIX QA Contact: Dafna Ron <dron>
Severity: high Docs Contact:
Priority: high    
Version: 3.1.0CC: abaron, dyasny, hateya, iheim, lpeer, Rhev-m-bugs, sgrinber, yeylon, ykaul
Target Milestone: ---   
Target Release: 3.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-22 01:53:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
logs none

Description Dafna Ron 2012-11-18 14:30:50 UTC
Created attachment 647185 [details]
logs

Description of problem:

after resource timeout on extend in vdsm I tried extending domain again and got .CannotGetJdbcConnectionException

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

si24.2

How reproducible:

100%

Steps to Reproduce:
1. live migrate a vm
2. try to extend the dst/src domains
3.
  
Actual results:

2012-11-18 14:20:09,074 ERROR [org.ovirt.engine.core.bll.storage.ExtendSANStorageDomainCommand] (ajp-/127.0.0.1:8702-2) [3d876efe] Command org.ovirt.engine.core.bll.storage.ExtendSANStorageDomainCommand throw exception: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: javax.resource.ResourceException: IJ000460: Error checking for a transaction
        at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:80) [spring-jdbc-3.1.1.RELEASE.jar:3.1.1.RELEASE]


Expected results:

we should not open a global transaction

Additional info:
logs

Comment 1 Simon Grinberg 2012-12-24 16:46:37 UTC
Dafna, is this regular VM migration or live storage migration?

Comment 2 Dafna Ron 2012-12-24 16:53:22 UTC
live storage migration

Comment 3 Ayal Baron 2012-12-26 10:36:18 UTC
Extend failed first time because of bug 876663

Comment 4 Ayal Baron 2013-01-22 01:53:54 UTC
Since bug 876663 will prevent us from reaching this state and fixing this apparently requires changing the command to be non transactive (almost a rewrite of the command) I'm closing wontfix.