Bug 1005256 - When deleting snapshots created for Live Storage Migration, RHEV removes the source disk rather than the snapshot
When deleting snapshots created for Live Storage Migration, RHEV removes the ...
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
All Linux
high Severity urgent
: ---
: 3.3.0
Assigned To: Daniel Erez
Aharon Canan
: ZStream
Depends On: 1015071
Blocks: 1011543
  Show dependency treegraph
Reported: 2013-09-06 10:12 EDT by Allan Voss
Modified: 2016-02-10 12:34 EST (History)
16 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-01-21 12:36:56 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
scohen: needinfo+

Attachments (Terms of Use)

  None (edit)
Description Allan Voss 2013-09-06 10:12:57 EDT
Description of problem:
When deleting the snapshot created for Live Storage Migration, it seems to have swapped the snapshot and the original image. The resulting preallocated image is marked in the database as being the size of the snapshot, and the image isn't bootable

Version-Release number of selected component (if applicable):
RHEV-H 20130709.0.el6_4

How reproducible:

Steps to Reproduce:
1. Live migrate several VMs with preallocated disks to another storage domain
2. While VMs are down, attempt to remove the snapshot created by the migration
3. Attempt to start those VMs

Actual results:
- VM refuses to boot
- Disk image in database listed as the size of the snapshot, rather than the disk size
- Image on disk is full size of original preallocated image

Expected results:
- successful VM boot
- correct image size in database

Additional info:
In the hopes that the problem was simply incorrect size data in teh database, I modified the disk_image_dynamic table to match the size on disk. Image still isn't bootable.
Comment 18 Aharon Canan 2013-10-14 09:15:37 EDT
it should be closed, (not sure even why with have clone if no issue exists)
anyway I rechecked it and everything looks fine
I also discussed it with derez, no real issue here.
marking verified.
Comment 19 Charlie 2013-11-27 19:14:33 EST
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:


Thanks in advance.
Comment 20 errata-xmlrpc 2014-01-21 12:36:56 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.