Description of problem: When VDSM patch - https://gerrit.ovirt.org/#/c/109793/ will be merged There will be no need to use the isDeferringFileVolumePreallocationSupported database config value. The following flows should be tested once the use of this flag is removed - In all the flows the VM/template has a raw preallocated disk. - Clone VM - Create Template from VM with preallocated disk - Create template from snapshot - Create VM from tempalte as 'clone' with disk format raw - Create VM from snapshot - Copy floating Disk - Copy VM Disk - Copy template disk - Import VM with raw-preallocated disk - Live/cold migrate raw-preallocated disk The validation is that the raw-preallocated disk keeps the disk format/type after performing the above operations. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
(In reply to Eyal Shenitzky from comment #0) > The validation is that the raw-preallocated disk keeps the disk format/type > after performing the above operations. If vdsm does not report "deferred_preallocation" capability engine creates a thin disk instead of preallocated? This is a bad bug on engine side if it does. "deferred_preallocation" is a performance optimization and should not affect image properties. If this is the case we need to fix this in engine before we remove the capability in vdsm.
CLOSING low QE severity 4.4.2 issuees with NEXT_RELESE. If you believe these bugs indeed require QE Verification feel free to reopen.