Bug 1556875

Summary: VM created in oVirt 4.2 could not be imported to oVirt 4.1 setup because of malformed envelope OVF
Product: [oVirt] ovirt-engine Reporter: Maor <mlipchuk>
Component: Backend.CoreAssignee: Maor <mlipchuk>
Status: CLOSED CURRENTRELEASE QA Contact: Avihai <aefrat>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.2CC: ahadas, amureini, bugs, dpinhas, mlipchuk
Target Milestone: ovirt-4.2.2Flags: rule-engine: ovirt-4.2+
Target Release: 4.2.2.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.2.5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-05 09:39:08 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 Maor 2018-03-15 12:09:22 UTC
Description of problem:
VM which was generated in oVirt 4.2 and was exported to an export storage domain, could not be imported to oVirt 4.1 because of malformed OVF

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Create VM in oVirt 4.2
2. Export it to an export domain
3. Attach and activate the export SD to oVirt 4.1
4. Import the VM to 4.1 cluster

Actual results:
The VM willfail to be imported

Expected results:
The VM should succeed to be imported

Additional info:

Comment 1 Yaniv Kaul 2018-03-15 13:27:21 UTC
Severity?

Comment 2 Maor 2018-03-15 14:40:57 UTC
(In reply to Yaniv Kaul from comment #1)
> Severity?

high, as Allon already updated in the bug

Comment 3 Avihai 2018-04-04 12:36:27 UTC
Verified on 4.2.2.6-0.1

Comment 4 Sandro Bonazzola 2018-04-05 09:39:08 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.