Bug 1403183

Summary: Cloned VMs created from template with "Raw" format are having "Thin Provision" Allocation Policy
Product: Red Hat Enterprise Virtualization Manager Reporter: Ameya Charekar <achareka>
Component: ovirt-engineAssignee: Eyal Shenitzky <eshenitz>
Status: CLOSED ERRATA QA Contact: Evelina Shames <eshames>
Severity: high Docs Contact:
Priority: high    
Version: 4.0.4CC: achareka, aefrat, appraprv, chris.brown, ebenahar, eshenitz, frolland, lsurette, lzitnits, mmartinv, nsoffer, Rhev-m-bugs, sborella, srevivo, tnisan, ybenshim
Target Milestone: ovirt-4.3.3Keywords: Reopened
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: vdsm-4.30.12, ovirt-engine-4.3.3.1 Doc Type: If docs needed, set a value
Doc Text:
This release ensures that virtual machines with file-based storage created from a template where the Resource Allocation > Storage Allocation > Clone > Format setting is set to Raw results in virtual machines having an Allocation Policy set to "Preallocated."
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-08 12:36:48 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 Ameya Charekar 2016-12-09 11:18:30 UTC
Description of problem:

Cloned VMs created from template with "Raw" format are having volume_type "Preallocated" instead of "Preallocated" volume_type.

Version-Release number of selected component (if applicable):
rhevm-4.0.4.4-0.1.el7ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create "New VM" from template.
2. From "Resource Allocation" select "Storage Allocation" as "Clone" and Format as "Raw".
3. VM disks are created with Raw Format but with "Thin Provision" Allocation Policy.

Actual results:
Vms are having "Thin Provision" Allocation Policy.

Expected results:
Vms should have "Preallocated" Allocation Policy.

Additional info:
Issue is with file based storage domains only. Also in rhev 3.6 this works as expected even with file based storage domains.

Comment 2 Tal Nisan 2017-01-23 13:41:16 UTC
*** Bug 1405822 has been marked as a duplicate of this bug. ***

Comment 6 Yaniv Lavi 2017-02-23 11:24:33 UTC
Moving out all non blocker\exceptions.

Comment 7 Maor 2017-04-05 10:59:05 UTC
Once it was chosen to create a VM from Template with RAW on file SD
The volume format that will be created in indeed RAW, the volume type is dependent on the storage type.
Volumes on block storage domain will get created with volume type of pre-allocated.
Volumes on file storage domain will be created with volume type of sparse since there is no benefit to pre-allocate them.

Comment 8 Maor 2017-04-20 16:44:53 UTC
Hi Ameya,

Is there anything that can be done here?
The volume format is indeed RAW as expected the only change is that the volume type is sparse.

Comment 9 Maor 2017-04-20 16:55:24 UTC
(In reply to Maor from comment #8)
> Hi Ameya,
> 
> Is there anything that can be done here?
> The volume format is indeed RAW as expected the only change is that the
> volume type is sparse.

Regarding the mismatch of the preallocation and sparse this should be solved as part of https://bugzilla.redhat.com/show_bug.cgi?id=1429286
If the issue is only about RAW then it should work as expected

Comment 14 Eyal Shenitzky 2018-03-28 12:54:15 UTC

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

Comment 15 Eyal Shenitzky 2018-04-04 09:24:49 UTC
Reopen, 

this bug is about clone a VM from a template and bug 1429286 is about cloning a VM.

Comment 16 Eyal Shenitzky 2018-05-29 12:17:12 UTC
This fix requires a data center 4.3 compatibility version because of modifications that implemented in the VDSM and will be available to the engine from that compatibility version.

Tal, can you push it to 4.3.0?

Comment 18 Sandro Bonazzola 2019-01-28 09:43:58 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 20 Tal Nisan 2019-02-18 11:20:31 UTC
Eyal, can we make sure this makes it to the 4.3 GA?

Comment 21 Eyal Shenitzky 2019-02-18 13:39:06 UTC
(In reply to Tal Nisan from comment #20)
> Eyal, can we make sure this makes it to the 4.3 GA?

This bug fix requirs a VDSM fix and an engine fix, I will do my best.

Comment 22 RHV bug bot 2019-03-29 11:14:46 UTC
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Project 'vdsm'/Component 'ovirt-engine' mismatch]

For more info please contact: rhv-devops

Comment 24 Evelina Shames 2019-04-02 11:39:15 UTC
Verified on:
ovirt-engine-4.3.3.1-0.1.el7.noarch
vdsm-4.30.12-1.el7ev.x86_64

Comment 26 errata-xmlrpc 2019-05-08 12:36:48 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:1085

Comment 27 Franta Kust 2019-05-16 13:09:24 UTC
BZ<2>Jira Resync