Bug 896439
Summary: | engine: cannot live migrate disks which are linked to template | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Dafna Ron <dron> | ||||
Component: | ovirt-engine | Assignee: | Daniel Erez <derez> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Dafna Ron <dron> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 3.2.0 | CC: | acathrow, amureini, dyasny, hateya, iheim, lpeer, Rhev-m-bugs, sgrinber, yeylon, ykaul | ||||
Target Milestone: | --- | Keywords: | Regression | ||||
Target Release: | 3.2.0 | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | storage | ||||||
Fixed In Version: | sf5 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 915537 | ||||||
Attachments: |
|
If a copy of the template disk exist on the target SD the migration should succeed. If it does not, the migration should fail on canDoAction, but with a relevant message, not VM_IS_NOT_DOWN. verified on sf5 we can move a disk which is attached to a template 3.2 has been released 3.2 has been released 3.2 has been released 3.2 has been released 3.2 has been released |
Created attachment 680116 [details] log Description of problem: I tried migrating disks for vm's which were created as thin provision copy of a template (they are linked to template) and we are getting a CaDoAction: Error: Cannot move Virtual Machine Disk. At least one of the VMs is not down. 2013-01-17 12:07:09,738 WARN [org.ovirt.engine.core.bll.MoveOrCopyDiskCommand] (ajp-/127.0.0.1:8702-4) [61d428e1] CanDoAction of action MoveOrCopyDisk failed. Reasons:VAR__ACTION__MOVE,VAR__TYPE__VM_DISK,ACTION_TYPE_FAILED_VM_IS_NOT_DOWN Version-Release number of selected component (if applicable): sf3 How reproducible: 100% Steps to Reproduce: 1. create a new vm from template as thin provision copy 2. run the vm 3. try to move the disk Actual results: we are failing on CanDoAction: Error: Cannot move Virtual Machine Disk. At least one of the VMs is not down. Expected results: we should be able to move the disk Additional info: engine log