Bug 1254230 - REST API : Operation of exporting template to Export domain stucks
Summary: REST API : Operation of exporting template to Export domain stucks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.6.0
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ovirt-3.6.0-rc
: 3.6.0
Assignee: Moti Asayag
QA Contact:
URL:
Whiteboard:
: 1256026 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-17 13:14 UTC by GenadiC
Modified: 2016-04-20 01:37 UTC (History)
15 users (show)

Fixed In Version: 3.6.0-12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-20 01:37:13 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 45327 0 master ABANDONED core: Index entity managers by transaction Never
oVirt gerrit 45547 0 master MERGED engine: Revert JPA Never
oVirt gerrit 45586 0 ovirt-engine-3.6 MERGED engine: Revert JPA Never

Description GenadiC 2015-08-17 13:14:23 UTC 
Description of problem:
Though action of exporting template to Export Domain succeeds (template exists after several minutes in GUI), the Rest command is stucked

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


How reproducible:
Always

Steps to Reproduce:
1. Send xml (attached below) to the API


Actual results:
API action is stucked though action succeeds

Expected results:
API action should not stuck

Additional info:
In our case we sent the follwoing "body" to https://jenkins-vm-07.scl.lab.tlv.redhat.com/ovirt-engine/api/templates/3b8f685b-a503-4974-bdf6-a46d5a9bf7df/export


<action>    
<async>false</async>    
<grace_period>        
<expiry>10</expiry>   
 </grace_period>    
<storage_domain>        
<name>export_domain</name>    
</storage_domain>    
<exclusive>false</exclusive>
</action>
Comment 1 Juan Hernández 2015-08-18 08:27:15 UTC 
It is the second time that I see this problem in the last few days, see bug 1253338. Initially I thought that bug was a specific problem when restoring a snapshot, but it looks like it is a more generic issue with caching in the DAO layer. In both cases (this bug and bug 1253338) the command executed returns a job and checking the status of that job (using the GetJobByJobId query) always returns STARTED, even if the database already contains FINISHED.
Comment 2 Allon Mureinik 2015-08-25 10:16:43 UTC 
*** Bug 1256026 has been marked as a duplicate of this bug. ***
Comment 3 GenadiC 2015-10-07 13:51:26 UTC 
Verified on 3.6.0-0.18.el6
Note You need to log in before you can comment on or make changes to this bug.