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

Bug 870755

Summary: engine [TEXT]: when we perform action which locks the vm the CanDoAction is on locked disk
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: ovirt-engineAssignee: Maor <mlipchuk>
Status: CLOSED CURRENTRELEASE QA Contact: Dafna Ron <dron>
Severity: medium Docs Contact:
Priority: high    
Version: 3.1.0CC: abaron, dyasny, hateya, iheim, lpeer, Rhev-m-bugs, sgrinber, yeylon, ykaul
Target Milestone: ---   
Target Release: 3.1.1   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: SI24 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 20:03:47 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
log none

Description Dafna Ron 2012-10-28 14:09:32 UTC
Created attachment 634533 [details]
log

Description of problem:

if we perform an action (such as add disk) which locks the vm (such as create vm from template, create template. export/import, create snapshot) we get a CanDoAction that the disk is locked. 
this is wrong, if only the disk is locked we should succeed, but when perform an action which lockes the whole vm we should fail with error that the vm is locked. 

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

si22.1

How reproducible:

100%

Steps to Reproduce:
1. create a vm from template
2. create a new disk while the vm is locked 
3.
  
Actual results:

Error while executing action: Cannot add Virtual Machine Disk: The disks XP_iSCSI_Disk1 are locked. Please try again in a few minutes.

Expected results:

we should be able to create multiple disks one after the other. 
however, if we perform actions which require the vm to be locked we should be stopped with error on the vm itself and not its disks. 

Additional info: log

Comment 1 Maor 2012-10-31 13:27:02 UTC
This should be already fixed at commit #39a10ff3e619a71de3d34eeb692f1b1d7c3d449e with change_id Ifb3714b8aa301fd12a2837e00d899b09cc0001f6

Comment 2 Dafna Ron 2012-11-06 08:28:34 UTC
verified on si24