Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1546747

Summary:	Fix ImportVmFromConfiguration for upload OVA
Product:	[oVirt] ovirt-engine	Reporter:	Arik <ahadas>
Component:	BLL.Virt	Assignee:	Arik <ahadas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Liran Rotenberg <lrotenbe>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	4.2.1	CC:	bugs, lveyde, mavital
Target Milestone:	ovirt-4.2.2	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.2.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-29 11:10:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.