Bug 999821

Summary: Sometimes snapshot deletion fails because of engine restart during the deletion process.
Product: Red Hat Enterprise Virtualization Manager Reporter: Leonid Natapov <lnatapov>
Component: ovirt-engineAssignee: Liron Aravot <laravot>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.3.0CC: acanan, acathrow, amureini, iheim, lpeer, Rhev-m-bugs, scohen, sgotliv, tnisan, yeylon, yzaslavs
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-16 11:43:32 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:
Bug Depends On: 999896    
Bug Blocks:    
Attachments:
Description Flags
log
none
log2 none

Description Leonid Natapov 2013-08-22 08:23:07 UTC 
Description of problem:

When snapshot deletion fails because engine was restarted in the middle of deletion process the task never stops running. Getting exceptions in engine and  snapshot names that user sees in the Events Log presented as  "UNKNOWN" 

here is the engine log.
It's a race ,reproduces not 100%.
Version-Release number of selected component (if applicable):


How reproducible:

how to reproduce:
1.Create VM with disks.
2.Create snapshot.
2.Delete snapshot. Make the deletion fail. (restart engine while deleting snapshot).

logs attached.
Comment 1 Sergey Gotliv 2013-08-22 08:29:10 UTC 
Created attachment 789084 [details]
log
Comment 2 Sergey Gotliv 2013-08-22 08:30:03 UTC 
Created attachment 789085 [details]
log2
Comment 8 Sergey Gotliv 2013-08-22 11:15:07 UTC 
*** Bug 996996 has been marked as a duplicate of this bug. ***
Comment 12 Liron Aravot 2014-06-16 11:43:32 UTC 
There were multiple fixes and changes on those areas since this bug has been opened.
I tested the scenario in log (1) again (restarted the engine after the task polling has started and the flow ended succeslly.

Closing as WORKSFORME at the moment.