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.
*** Bug 1405822 has been marked as a duplicate of this bug. ***
Moving out all non blocker\exceptions.
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.
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.
(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
*** This bug has been marked as a duplicate of bug 1429286 ***
Reopen, this bug is about clone a VM from a template and bug 1429286 is about cloning a VM.
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?
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.
Eyal, can we make sure this makes it to the 4.3 GA?
(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.
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
Verified on: ovirt-engine-4.3.3.1-0.1.el7.noarch vdsm-4.30.12-1.el7ev.x86_64
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
BZ<2>Jira Resync