Description of problem: Some virtualization stacks export as OVA without including a .mf manifest file. DTMF's official OVF spec (http://www.dmtf.org/standards/ovf) under 5.1 states that "An OVF package shall consist of the following (...) zero or one OVF manifest with extension .mf" However, if no such manifest exists, virt-v2v will collapse with "Use of uninitialized value $mf_path in open at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Connection/VMwareOVASource.pm line 254." Version-Release number of selected component (if applicable): 0.9.0 (latest from Fedora 20 repo) How reproducible: Attempt an import of an OVA without a .mf file in it Actual results: Use of uninitialized value $mf_path in open at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Connection/VMwareOVASource.pm line 254. virt-v2v: Failed to open {path}: No such file or directory Expected results: Pass over manifest verification and proceed with the import
Created attachment 853325 [details] (proposed) patch, although it's not a 100% nice one Simple check; if $mf_path remains empty, just return.
Hi, thanks for the bug report. Unfortunately it is filed against a very old version of virt-v2v (0.9) which we don't support at all. Luckily there is a newer version which almost certainly fixes your bug already. It's available starting in Fedora 21. If you still experience this bug, please try with the new version, and reopen if it still happens.
(In reply to Richard W.M. Jones from comment #1) > Unfortunately it is filed against a > very old version of virt-v2v (0.9) Well, that tends to happen if you wait 16 months with a reply to a ready2commit submitted patch.