Bug 1026330

Summary:	the VM should be in image_locked state when performing offline snapshot operation
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	David Jaša <djasa>
Component:	ovirt-engine-webadmin-portal	Assignee:	Liron Aravot <laravot>
Status:	CLOSED WONTFIX	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	acathrow, amureini, ecohen, hateya, iheim, Rhev-m-bugs, scohen, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-07 12:35:12 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:

Description David Jaša 2013-11-04 12:50:17 UTC

Description of problem:
When the VM is performing a snapshot operation and nothing else can be done, the VM should be in image_locked state

Version-Release number of selected component (if applicable):
is20.2 / rhevm-backend-3.3.0-0.30.beta1.el6ev.noarch

How reproducible:
always

Steps to Reproduce:
1. delete (create, preview, commit) a snapshot whev VM is down
2.
3.

Actual results:
VM status is down during snapshot operation

Expected results:
VM is in image_locked status

Additional info:

Comment 1 Liron Aravot 2013-11-07 11:46:52 UTC

Allon,
the removal of the lock of the vm during snapshot is since this patch (old one):
http://gerrit.ovirt.org/#/c/2314/

possibly the intention was that you could do other vm related operations while the snapshot is being taken. like  updating the vm configuration.

As this issue is very old, i think that regardless this could be postponed to 3.4 (as changing it might add some instabiility) and then we could decide on what is the behaviour that we want here.

Comment 2 Allon Mureinik 2013-11-07 12:35:12 UTC

On second thought, the initial description of the bug is  incorrect - if a VM is in image locked it cannot be RUN.