Bug 1535574 - Webadmin importing VM event is stuck in importing state although the import failed.
Summary: Webadmin importing VM event is stuck in importing state although the import f...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.2.1.1
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.2.2
: ---
Assignee: Arik
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-17 16:09 UTC by Nisim Simsolo
Modified: 2018-03-29 11:02 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.2.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-29 11:02:47 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
engine.log (494.24 KB, application/x-xz)
2018-01-17 16:10 UTC, Nisim Simsolo
no flags Details
Webadmin events screenshot (133.74 KB, image/png)
2018-01-17 16:11 UTC, Nisim Simsolo
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 87109 0 master MERGED core: adjust ova extraction to python 2 2020-09-07 17:10:42 UTC

Description Nisim Simsolo 2018-01-17 16:09:45 UTC
Description of problem:
This issue happened after importing RHV OVA with big disk size (https://bugzilla.redhat.com/show_bug.cgi?id=1535521), after an engine exception, the event of importing VM from OVA is getting stuck at importing state.

engine.log:
2018-01-17 16:10:36,522+02 ERROR [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-36268) [2bc68f25] [within thread]: endAction for act
ion type ImportVmFromOva threw an exception.: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLExcepti
on: javax.resource.ResourceException: IJ000457: Unchecked throwable in managedConnectionReconnected() cl=org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@765
67bd3[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@6e0da44a connection handles=0 lastReturned=1516198236471 lastValidated=151619806
1752 lastCheckedOut=1516198210358 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@16e5b275 mcp=SemaphoreConcurrentLinkedQueueManagedConnectionP
ool@224483fe[pool=ENGINEDataSource] xaResource=LocalXAResourceImpl@37aca81d[connectionListener=76567bd3 connectionManager=e862ccb warned=false currentXid=null productName=Post
greSQL productVersion=9.5.9 jndiName=java:/ENGINEDataSource] txSync=null]


Version-Release number of selected component (if applicable):
ovirt-engine-4.2.1.1-0.1.el7
libvirt-client-3.2.0-14.el7_4.7.x86_64
vdsm-4.20.13-1.el7ev.x86_64
qemu-kvm-rhev-2.9.0-16.el7_4.13.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Import OVA (exported by RHV) with big disk size (more than 10G)
2.
3.

Actual results:
After engine exception, the importing event is stuck at "importing" state.

Expected results:
An event for import failed should be loggeg in the webadmin events.

Additional info:
engine.log attached (2018-01-17 16:10:36,522+02 ERROR)
Webadmin screenshot attached

Comment 1 Nisim Simsolo 2018-01-17 16:10:54 UTC
Created attachment 1382559 [details]
engine.log

Comment 2 Nisim Simsolo 2018-01-17 16:11:25 UTC
Created attachment 1382560 [details]
Webadmin events screenshot

Comment 3 Michal Skrivanek 2018-01-19 13:01:43 UTC
great analysis in the screenshot
:-)

Comment 4 Nisim Simsolo 2018-02-25 15:03:59 UTC
Verified: 
rhvm-4.2.2.1-0.1.el7
vdsm-4.20.19-1.el7ev.x86_64
qemu-kvm-rhev-2.10.0-19.el7.x86_64
libvirt-client-3.9.0-13.el7.x86_64

Comment 5 Sandro Bonazzola 2018-03-29 11:02:47 UTC
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.