Bug 1546747 - Fix ImportVmFromConfiguration for upload OVA
Summary: Fix ImportVmFromConfiguration for upload OVA
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.2.1
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ovirt-4.2.2
: ---
Assignee: Arik
QA Contact: Liran Rotenberg
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-19 13:50 UTC by Arik
Modified: 2018-03-29 11:10 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-4.2.2.1
Clone Of:
Environment:
Last Closed: 2018-03-29 11:10:44 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 87746 0 master MERGED core: fix import vm from configuration for upload ova 2018-02-19 13:56:19 UTC
oVirt gerrit 87850 0 ovirt-engine-4.2 MERGED core: fix import vm from configuration for upload ova 2018-02-19 16:49:44 UTC

Description Arik 2018-02-19 13:50:02 UTC
Need to fix regressions that broke ImportVmFromConfigurationCommand for uploading an OVA via REST-API.

Comment 1 Arik 2018-02-19 15:27:09 UTC
This patch should be verified by uploading an OVA through the SDK as in [1]

[1] https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_ova_as_vm.py

Comment 2 Liran Rotenberg 2018-03-06 13:28:54 UTC
Verified on:
ovirt-engine-4.2.2.1-0.1.el7.noarch

Steps:
1. Use the SDK in https://bugzilla.redhat.com/show_bug.cgi?id=1546747#c1 to upload an OVA. 
2. Create a VM with the new disk.
3. Start the VM.

Results:
The disk was created correctly, the VM run without any problems.

Comment 3 Sandro Bonazzola 2018-03-29 11:10:44 UTC
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

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


Note You need to log in before you can comment on or make changes to this bug.