Adam - https://gerrit.ovirt.org/#/c/53318/ is merged to the 3.6 branch. Is there anything else we need here?
https://gerrit.ovirt.org/#/q/topic:live-merge-no-raw-extension shows the patches are merged for 3.5, 3.6, and master. These patches will prevent the base raw image from growing beyond its capacity. Unfortunately for people who have experienced this problem a manual intervention will be required to lvreduce the affected base raw volume(s).
This patch is included in the 3.6.3 branch, setting target milestone accordingly.
(In reply to Allon Mureinik from comment #5)
> This patch is included in the 3.6.3 branch, setting target milestone
Arg, no, it isn't, but it must be, as this fix was delivered in 3.5.8.
"low level image copy failed.." after executing the following steps:
1. Create VM (preallocated disk over ISCSI SD)
2. Create 2 snapshots
3. Live merge one of the snapshots
4. Clone a VM from the snapshot left
Clone VM operation falied.
5fe78e7a-40d4-45d6-924e-6b5a746603b7::ERROR::2016-02-25 11:44:21,258::task::866::Storage.TaskManager.Task::(_setError) Task=`5fe78e7a-40d4-45d6-924e-6b5a746603b7`::Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 873, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/storage/task.py", line 332, in run
return self.cmd(*self.argslist, **self.argsdict)
File "/usr/share/vdsm/storage/securable.py", line 77, in wrapper
return method(self, *args, **kwargs)
File "/usr/share/vdsm/storage/sp.py", line 1570, in copyImage
File "/usr/share/vdsm/storage/image.py", line 866, in copyCollapsed
CopyImageError: low level Image copy failed: ("ecode=1, stdout=, stderr=['qemu-img: /rhev/data-center/mnt/blockSD/8fc9541e-e584-4f9c-a626-f217162eafc5/images/7a4b7fa4-d739-43d6-8908-5b
6558b8d4c0/5ab11d88-04a3-4993-808d-493d6ddcfdcc: error while converting raw: Device is too small'], message=None",)
Logs will be attached
Sorry, my mistake, the build I tested with is from Feb 17. Using the latest (Feb 24), the clone operation ended successfully.
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.