Created attachment 940077 [details] vdsm+engine Description of problem: view BZ #1145073 BZ #1145188 BZ #1121929 Version-Release number of selected component (if applicable): vt3.1 How reproducible: 100% Steps to Reproduce: 1.Have one Block domain on setup 2.Have vm+disk(wipe_after_delete='True') 3.take live snapshot 4.power of the Vm,remove VM+it's disk Actual results: memory snapshots are not deleted Expected results: memory snapshots should be WIPED out Additional info:
This is the same flow as bug 1145073 - the different storage type is inconsequential. *** This bug has been marked as a duplicate of bug 1145073 ***
reopened After discussion with,Allon, When commencing steps described at BZ #1145073 , on Block the operation successful, the images are not deleting only when setting wipe_after_delete='true'.
MODIFIED for 3.5.0 - this bug should be cloned and backported to 3.4.z too.
this bug status was moved to MODIFIED before engine vt5 was built, hence moving to on_qa, if this was mistake and the fix isn't in, please contact rhev-integ
Memory snapshots are now deleted. Tested with: rhevm-3.5.0-0.14.beta.el6ev.noarch vdsm-4.16.6-1.el6ev.x86_64 Moving to verified!
RHEV-M 3.5.0 has been released, closing this bug.