Bug 874443
| Summary: | VM is in down status while its images are in locked status (breaks backward compatibility) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jakub Libosvar <jlibosva> | ||||
| Component: | ovirt-engine | Assignee: | Omer Frenkel <ofrenkel> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Jakub Libosvar <jlibosva> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.1.0 | CC: | bazulay, chetan, dyasny, hateya, iheim, lpeer, michal.skrivanek, ohadlevy, Rhev-m-bugs, sgordon, sgrinber, thildred, yeylon, ykaul | ||||
| Target Milestone: | --- | Keywords: | Improvement, Regression | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | virt | ||||||
| Fixed In Version: | Doc Type: | Release Note | |||||
| Doc Text: |
In previous releases when the disk image of a virtual machine was being modified or used by a task the entire virtual machine was locked. This lock is now more specific and applies to the disk. This means that users are still able to perform additional tasks on the virtual machine, such as adding or removing disks, concurrently.
As a result of this change of behavior the virtual machine status may indicate that a virtual machine is "Up" when the attached disk is in fact being used by another task. Users will not be aware of this lock until such time as they attempt to perform an action that requires a lock on the disk.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-06-25 13:31:13 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
That breaks existing 3.0 scripts running against 3.1. Setting as Regression and Urgent severity. We got reports about it. The return value for the user is the same as before (canDoAction message with explanation why vm can't run): 2012-11-08 09:14:02,830 WARN [org.ovirt.engine.core.bll.RunVmCommand] (ajp-/127.0.0.1:8702-8) CanDoAction of action RunVm failed. Reasons:VAR__ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_DISKS_ARE_LOCKED,$diskAliases vm_Disk2 AFAIR, one of the features of 3.1 was not to lock the vm when locking its disks, so operations on other disks can be made, and even run the vm if the disk is inactive. Please see https://bugzilla.redhat.com/show_bug.cgi?id=872961 (upstream!) which sounds similar, though in this case, the command is sent all the way to VDSM (and not blocked in Engine). (In reply to comment #2) > The return value for the user is the same as before (canDoAction message > with explanation why vm can't run): > 2012-11-08 09:14:02,830 WARN [org.ovirt.engine.core.bll.RunVmCommand] > (ajp-/127.0.0.1:8702-8) CanDoAction of action RunVm failed. > Reasons:VAR__ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_DISKS_ARE_LOCKED, > $diskAliases vm_Disk2 > > AFAIR, one of the features of 3.1 was not to lock the vm when locking its > disks, so operations on other disks can be made, and even run the vm if the > disk is inactive. All true, but we break 3.0-compatible scripts (example @ https://bugzilla.redhat.com/show_bug.cgi?id=872961#c2) (In reply to comment #4) . > > All true, but we break 3.0-compatible scripts (example @ > https://bugzilla.redhat.com/show_bug.cgi?id=872961#c2) Per comment #2 on that bz - it looks like the upstream and downstream behavior is different, it looks like that there the command actually got to VDSM. this effects Foreman (http://theforeman.org) and is tracked upstream at http://projects.theforeman.org/issues/2163. IMHO, this is a BUG and not a feature. foreman is fixed now and hopefully other people are now used to this behavior as well.... |
Created attachment 640643 [details] backend log Description of problem: When disk is created for VM, VM is kept in Down status but cannot be started. Getting error message: Error while executing action: Cannot run VM: The disks vm_Disk3 are locked. Please try again in a few minutes. Version-Release number of selected component (if applicable): rhevm-3.1.0-26.el6ev.noarch How reproducible: Always Steps to Reproduce: 1. Create a disk for VM 2. While disk is in locked status, start VM Actual results: VM cannot be started although it's in down status Expected results: VM should have some status, that says VM is not ready to start Additional info: