Not all hosts are capable of performing Live Merge operations. Those that are will indicate it with a flag in the vdsm capabilities API (see bug 1109925). Based on that flag, the engine will restrict Live Merge.
Hi I tested the following regarding the blocking of the live merge feature based on the host version: On a LIVE VM including block and nfs disks with 4 snapshots I tried deleting snapshots 2 and 3 On a LIVE VM including block and nfs disks with 4 snapshots I tried deleting snapshot DISKS from snapshots 2 and 3 Results: rhel 6.5 Live merge is blocked in the UI rhel 7.0 Liver merge is blocked in the UI Does this resolve this issue?
(In reply to Kevin Alon Goldblatt from comment #1) > Hi I tested the following regarding the blocking of the live merge feature > based on the host version: > > On a LIVE VM including block and nfs disks with 4 snapshots I tried deleting > snapshots 2 and 3 > On a LIVE VM including block and nfs disks with 4 snapshots I tried deleting > snapshot DISKS from snapshots 2 and 3 > > Results: > rhel 6.5 Live merge is blocked in the UI > rhel 7.0 Liver merge is blocked in the UI > > > Does this resolve this issue? Half of it, I suppose :) Looking at Adam's verification instructions in bug 1109925 comment 5, the points at which to test whether the engine is allowing live merge would be after numbers 3 and 11. The engine should respect vdsClient's returned liveMerge = <"false"|"true"> value, and should correspondingly block (or not) the live merge operation in the UI.
(That should say "vdsm's returned liveMerge [...] value". Of course the value can be checked using vdsClient.)
oVirt 3.5 has been released and should include the fix for this issue.