Bug 1658249 - Importing a VM from OVA that has been imported already fails and its disk status becomes illegal
Summary: Importing a VM from OVA that has been imported already fails and its disk sta...
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.2.5
Hardware: All
OS: Linux
Target Milestone: ovirt-4.3.1
: 4.3.0
Assignee: shani
QA Contact: Nisim Simsolo
Depends On: 1684140
TreeView+ depends on / blocked
Reported: 2018-12-11 15:47 UTC by Ron van der Wees
Modified: 2020-08-03 15:43 UTC (History)
7 users (show)

Fixed In Version: ovirt-engine-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-05-08 12:39:09 UTC
oVirt Team: Storage
Target Upstream Version:
lsvaty: testing_plan_complete-

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3749251 0 None None None 2018-12-11 16:03:25 UTC
Red Hat Product Errata RHEA-2019:1085 0 None None None 2019-05-08 12:39:19 UTC
oVirt gerrit 97675 0 master MERGED core: Fix importing a VM with two disks from an OVA 2020-06-01 15:51:27 UTC

Description Ron van der Wees 2018-12-11 15:47:28 UTC
Description of problem:
Importing a VM from OVA that has imported before corrupts the disk of the first imported VM. Same with importing a VM from OVA on a HE where the original VM still exists will render the disk of the original VM "illegal".

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

How reproducible:

Steps to Reproduce:
1. Export a VM to OVA:
   webUI -> Compute -> Virtual Machines -> <vm> -> Menu -> Export as OVA
2. On a different HE, Compute -> Virtual Machines -> Menu -> Import
   Source: Virtual Appliance (OVA)
   and follow the steps to import the VM
3. Rename the imported VM
4. Repeat step 2

Actual results:
The second import fails, the task displays a RED "X" with
"Importing VM host1 to Cluster Default" 
The disk of the original (first imported VM) under
Compute -> Virtual Machines -> <vm> -> Disks
shows: "Status: Illegal"

Expected results:
Import to succeed resulting in a new VM with new UUID and new disk.

Additional info:
It seems that importing a VM from OVA will keep its UUID but its disk will get
a new UUID (seen from the API) resulting in the first imported VM having a
failed imported disk which is corrupt.

First imported or original VM data:
<disk href="/ovirt-engine/api/disks/05339fff-775b-403b-8c6b-05b4b450c7e9" id="05339fff-775b-403b-8c6b-05b4b450c7e9"/>

Second imported VM has a different UUID for the disk:
<disk href="/ovirt-engine/api/disks/90c9db9d-5625-47a8-bd3a-e78b4abeb1ac" id="90c9db9d-5625-47a8-bd3a-e78b4abeb1ac"/>

However the UUID of the VM remained the same!

Comment 1 Ron van der Wees 2018-12-11 15:50:48 UTC
Same happens when importing the VM from OVA on the HE where the VM still is
available and thus corrupting the original VM!

Comment 2 Sandro Bonazzola 2019-01-28 09:44:38 UTC
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.

Comment 5 RHV bug bot 2019-02-21 17:26:24 UTC
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]

For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]

For more info please contact: rhv-devops

Comment 8 Eyal Edri 2019-02-24 11:40:19 UTC
Please make sure to attach it to the Errata and not move manually to ON_QA.

Comment 10 Nisim Simsolo 2019-03-19 12:09:06 UTC

Verification scenario:
1. Export VM with 5 disks as OVA.
2. Import OVA 10 times.
3. Verify imports succeed.
4. Run VMs, verify VMs are running with 5 disks inside each one.

Comment 12 errata-xmlrpc 2019-05-08 12:39:09 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, and where to find the updated
files, follow the link below.

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


Comment 13 Daniel Gur 2019-08-28 13:15:28 UTC

Comment 14 Daniel Gur 2019-08-28 13:21:16 UTC

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