Bug 1616445

Summary: Template creation does not respect disk allocation selection on NFS domains
Product: Red Hat Enterprise Virtualization Manager Reporter: Marina Kalinin <mkalinin>
Component: ovirt-engineAssignee: Eyal Shenitzky <eshenitz>
Status: CLOSED DUPLICATE QA Contact: Elad <ebenahar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.5CC: lsurette, Rhev-m-bugs, srevivo, tburke, tnisan
Target Milestone: ovirt-4.3.0   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-19 12:43:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marina Kalinin 2018-08-16 00:08:30 UTC 
Description of problem:
When creating a template, it is possible to select disk type (thin or preallocated), but the choice is not respected and all the disks are created thin.

Version-Release number of selected component (if applicable):
4.2.5-2

How reproducible:
100%

Steps to Reproduce:
1. Create a VM with preallocated disk on NFS storage domain
2. Start Create Template dialogue for that VM
3. Select disk type - RAW (BTW - this shoudl be changed to THIN/PREALLOCATED).
4. Hit ok and wait till template is completed.

Actual results:
The disk is Thin Provisioned

Expected results:
The disk is preallocated.

Additional info:
It does not work the other way around as well: create thin-provisioned disk and select RAW -> will still result in thin-provisioned.
It seem to work ok on block storage (iscsi tested).
Comment 1 Marina Kalinin 2018-08-16 00:24:13 UTC 
HA. Even when the template get it right (on block storage) and get the disk type as preallocated, when creating a VM from that template (on that same block storage type), it creates it as thin-provisioned.
I will skip opening separate bug for that.
Comment 3 Eyal Shenitzky 2018-08-19 12:43:54 UTC 

*** This bug has been marked as a duplicate of bug 1471138 ***