Description of problem: Up until now, DAD (Discard After Delete) [1] was not related to Pass Discard [2], i.e a disk was first discarded before it was deleted only if its block storage domain's DAD value was true. That created a situation where a vm disk that had its Pass Discard enabled was not discarded before it was deleted if its storage domain's DAD value was disabled. This situation does not make sense because if the user specifies that he wants "live" discarding (Pass Discard), he will most likely want to discard the whole disk before it's deleted. Version-Release number of selected component (if applicable): cf5293c9b1faa6c09d9cb44a1124fedd8e8abb49 How reproducible: 100% Additional info: [1] http://www.ovirt.org/develop/release-management/features/storage/discard-after-delete [2] http://www.ovirt.org/develop/release-management/features/storage/pass-discard-from-guest-to-underlying-storage/
Severity?
(In reply to Yaniv Kaul from comment #1) > Severity? It's a medium severity bug, IMHO. It's not terrible (after all, we supported block storage but didn't discard deleted disks since 3.1), but it's ugly, and unintuitive - if I delete something from within the guest a discard would (eventually/potentially) be issued to the array, but if I delete the whole thing it wouldn't. That doesn't make too much sense from a user's perspective.
Verfied with the following code: ------------------------------------ ovirt-engine-4.1.2.1-0.1.el7.noarch rhevm-4.1.2.1-0.1.el7.noarch vdsm-4.19.14-1.el7ev.x86_64 Verfied with the following scenario: -------------------------------------- 1. Created 2 VMs and attache the same shared disk 2. Verfiied the scenario's of Wipe after Delete and Discard Enabled Moving to verified!