Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1408405

Summary: Creating a snapshot job doesn't get mark as finish when restarting the engine
Product: [oVirt] ovirt-engine Reporter: Carlos Mestre González <cmestreg>
Component: BLL.StorageAssignee: Liron Aravot <laravot>
Status: CLOSED DUPLICATE QA Contact: Raz Tamir <ratamir>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0.6CC: bugs
Target Milestone: ovirt-4.1.0-betaFlags: rule-engine: ovirt-4.1+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-08 15:41:57 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
Engine and vsdm logs none

Description Carlos Mestre González 2016-12-23 09:49:50 UTC
Created attachment 1234980 [details]
Engine and vsdm logs

Description of problem:
When creating a snapshot of a vm and restarting the engine, after the engine is back the job "Creating VM Snapshot test for VM" keep running even though the snapshot is created successfully.

Version-Release number of selected component (if applicable):
rhevm-4.0.6.3-0.1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create a vm with a disk(doens't seem to matter the type, I did on iscsi and a clone from a template)
2. Take a snapshot of the vm
3. Restart the engine service ovirt-engine restart

Actual results:
After the engine is back up the job "Creating VM Snapshot ..." is still running but the snapshot is finishe and in status OK.

Expected results:
Job is marked as finish

Additional info:

Comment 1 Carlos Mestre González 2016-12-23 09:50:13 UTC
in logs, vm id is: c77af408-52b4-48ed-a663-68d21dacbc1d

Comment 2 Tal Nisan 2016-12-25 11:00:15 UTC
Liron this looks familiar, didn't you fix a similar problem for 4.1?

Comment 3 Liron Aravot 2017-01-08 15:41:57 UTC

*** This bug has been marked as a duplicate of bug 1393459 ***