Bug 1986726 - VM imported from OVA gets thin provisioned disk despite of allocation policy set as 'preallocated'
Summary: VM imported from OVA gets thin provisioned disk despite of allocation policy ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.4.6
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.5.0
: 4.5.0
Assignee: Arik
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On: 2076465 2076474
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-28 08:23 UTC by Chetan Nagarkar
Modified: 2022-08-15 11:50 UTC (History)
5 users (show)

Fixed In Version: ovirt-engine-4.5.0
Doc Type: Bug Fix
Doc Text:
When importing VM from OVA and setting the allocation policy to Preallocated, the disks were imported as Thin provisioned. In this release, the selected allocation policy is followed.
Clone Of:
Environment:
Last Closed: 2022-05-26 16:22:29 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 6222701 0 None None None 2021-07-29 01:51:23 UTC
Red Hat Product Errata RHSA-2022:4711 0 None None None 2022-05-26 16:22:55 UTC
oVirt gerrit 116317 0 master MERGED core: Wrong allocation policy is assigned to VM imported by OVA 2021-10-19 17:02:11 UTC
oVirt gerrit 117422 0 master MERGED webadmin: add Auto detect item to VM import allocation policy 2021-12-13 09:23:28 UTC
oVirt gerrit 117449 0 master MERGED restapi: add option to import VM without specifying sparseness 2021-11-29 19:15:22 UTC
oVirt gerrit 117797 0 master MERGED api-model: update ExternalVmImport sparse field documentation 2021-12-13 07:50:46 UTC

Comment 1 Arik 2021-07-28 14:26:23 UTC 
Yeah, we don't respect the allocation policy when importing from OVA [1]

[1] https://github.com/oVirt/ovirt-engine/blob/ovirt-engine-4.4.8.1/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/exportimport/ImportVmFromOvaCommand.java#L107-L109
Comment 2 Arik 2021-08-02 11:11:40 UTC 
(In reply to Arik from comment #1)
> Yeah, we don't respect the allocation policy when importing from OVA [1]
> 
> [1]
> https://github.com/oVirt/ovirt-engine/blob/ovirt-engine-4.4.8.1/backend/
> manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/exportimport/
> ImportVmFromOvaCommand.java#L107-L109

Adding to the above that we don't want to change the format within the OVA because we wish to preserve sparseness
Comment 9 Nisim Simsolo 2022-05-02 17:22:44 UTC 
Verified:
ovirt-engine-4.5.0.5-0.7.el8ev
vdsm-4.50.0.13-1.el8ev.x86_64
qemu-kvm-6.2.0-11.module+el8.6.0+14707+5aa4b42d.x86_64
libvirt-daemon-8.0.0-5.module+el8.6.0+14480+c0a3aa0f.x86_64

Verification scenario:
1. Export VM with preallocated disk as OVA.
   Import OVA, select preallocated policy in import dialog.
   Verify VM imported, verify disk policy is preallocated.
   Run VM and verify VM is running properly.
2. Export VM with thin provision disk as OVA.
   Import OVA, select preallocated policy in import dialog.
   Verify VM imported, verify disk policy is preallocated.
   Run VM and verify VM is running properly.
3. Export VM with preallocated disk as OVA.
   Import OVA, select "auto detect" policy in import dialog.
   Verify VM imported, verify disk policy is preallocated.
   Run VM and verify VM is running properly.
4. Export VM with thin provision disk as OVA.
   Import OVA, select "auto detect" policy in import dialog.
   Verify VM imported, verify disk policy is thin provision.
   Run VM and verify VM is running properly.
Comment 14 errata-xmlrpc 2022-05-26 16:22:29 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 (Moderate: RHV Manager (ovirt-engine) [ovirt-4.5.0] security update), 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/RHSA-2022:4711
Note You need to log in before you can comment on or make changes to this bug.