Bug 999821 - Sometimes snapshot deletion fails because of engine restart during the deletion process.
Summary: Sometimes snapshot deletion fails because of engine restart during the deleti...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.5.0
Assignee: Liron Aravot
QA Contact:
URL:
Whiteboard: storage
: 996996 (view as bug list)
Depends On: 999896
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-22 08:23 UTC by Leonid Natapov
Modified: 2016-02-10 19:20 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-16 11:43:32 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
log (48.00 KB, application/x-gzip)
2013-08-22 08:29 UTC, Sergey Gotliv
no flags Details
log2 (120.75 KB, application/x-gzip)
2013-08-22 08:30 UTC, Sergey Gotliv
no flags Details

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.


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