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

Bug 1561603

Summary: virt-v2v: VMware OVA cannot be imported.
Product: [oVirt] ovirt-engine Reporter: Nisim Simsolo <nsimsolo>
Component: BLL.VirtAssignee: Arik <ahadas>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: high    
Version: 4.2.2CC: bugs, michal.skrivanek, nsimsolo
Target Milestone: ovirt-4.2.3Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 07:13:19 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:
Attachments:
Description Flags
VMware OVF example
none
engine.log
none
vdsm.log
none
ovirt-query-ova-ansible log none

Description Nisim Simsolo 2018-03-28 15:10:33 UTC 
Description of problem:
When importing VMware OVA, the next engine.log ERROR occurs:

2018-03-28 17:47:57,749+03 ERROR [org.ovirt.engine.core.bll.exportimport.ImportVmFromOvaCommand] (EE-ManagedThreadFactory-engine-Thread-3750) [b162d1ca-5ec5-4d32-955b-64fdac36
27be] Command 'org.ovirt.engine.core.bll.exportimport.ImportVmFromOvaCommand' failed: For input string: ""
2018-03-28 17:47:57,749+03 ERROR [org.ovirt.engine.core.bll.exportimport.ImportVmFromOvaCommand] (EE-ManagedThreadFactory-engine-Thread-3750) [b162d1ca-5ec5-4d32-955b-64fdac36
27be] Exception: java.lang.NumberFormatException: For input string: ""

this ERROR might be related to https://bugzilla.redhat.com/show_bug.cgi?id=1560684 because in normal VMware OVA file there is no MAC address at all, and when creating VMware OVA with MAC address, the MAC address is set as <rasd:Address> and we expect to <rasd:macAddress>, so in both cases the MAC address will be an empty string.

This issue occurs also when importing VMware OVA as clone.

Version-Release number of selected component (if applicable):
rhvm-4.2.2.5-0.1.el7
libvirt-client-3.9.0-14.el7_5.2.x86_64
qemu-kvm-rhev-2.10.0-21.el7_5.1.x86_64
vdsm-4.20.23-1.el7ev.x86_64
sanlock-3.6.0-1.el7.x86_64
virt-v2v-1.36.10-6.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Import VMware OVA file or directory.
2.
3.

Actual results:
Import failed.

Expected results:
OVA should be imported.

Additional info:
engine.log and vdsm.log, ovirt-query-ova-ansible.log and OVF example attached
Comment 1 Nisim Simsolo 2018-03-28 15:13:41 UTC 
Created attachment 1414275 [details]
VMware OVF example
Comment 2 Nisim Simsolo 2018-03-28 15:14:27 UTC 
Created attachment 1414276 [details]
engine.log
Comment 3 Nisim Simsolo 2018-03-28 15:14:50 UTC 
Created attachment 1414277 [details]
vdsm.log
Comment 4 Nisim Simsolo 2018-03-28 15:15:18 UTC 
Created attachment 1414278 [details]
ovirt-query-ova-ansible log
Comment 5 Michal Skrivanek 2018-03-29 07:13:19 UTC 
addressed as part of bug 1547936

*** This bug has been marked as a duplicate of bug 1547936 ***