Created attachment 1340571 [details] engine-log Description of problem: Faild to import a guest from a ova file by rhv4.1 GUI "Import Virtual Machines" function. Version-Release number of selected component (if applicable): virt-v2v-1.36.7-1.el7.x86_64 vdsm-4.19.34-1.el7ev.x86_64 rhv4.1.7.3-0.1.el7 How reproducible: 100% Steps to Reproduce: 1.Prepare a ova file on the host which register to rhv4.1. 2.Login rhv4.1 webUI--> NFS data center --> Virtual Machines --> import -->select source as " VMware Virtual Appliance(OVA) 3.Load the guest and failed to import the guest,with the error "VDSM NFS command GetOvaInfoVDS failed: [Errno 2] No such file or directory: u'/tmp/esx-rhel6.8-ova.tar' VDSM NFS command GetOvaInfoVDS failed: [Errno 2] No such file or directory: u'/tmp/esx-rhel6.8-ova.tar' VDSM NFS command GetOvaInfoVDS failed: OVA directory /tmp/ does not contain ovf file" 4.We can see engine log as attachment. Actual results: As above description Expected results: Should import guest from export domain to data domain successfully Additional info:
Can you double-check the filename /tmp/esx-rhel6.8-ova.tar for existence and qemu:qemu permissions? Nisim and I tried this yesterday and it failed, but not with this error.
yes,the file is true and qemu working normally.but i get the error still.If env different from me . From my log there is a error "5013",and from Nisim's log also contain "Failed with error MAC_ADDRESS_IS_IN_USE and code 5013".
kuwei, any idea why FutureFeature keyword is set on this bug? Why have you filed it under RHVM product? internal qe should file bugs on ovirt (unless the bugs are specific to downstream).
HI，Dan,I think we could remove the keyword "futurefeature" if the bug was on ovirt. And if it not under RHEVM product,we can change the product. Thanks
Please do!
this defect can be verified with 1503947 which it is blocking
This defect reproduces under the same circumstances as the defect it is blocking (1503947) - when no mac is provided in the OVA (null or empty string). Therefore they can be verified together.
A modify > 3.Load the guest and failed to import the guest,with the error > "VDSM NFS command GetOvaInfoVDS failed: [Errno 2] No such file or directory: > u'/tmp/esx-rhel6.8-ova.tar' > VDSM NFS command GetOvaInfoVDS failed: [Errno 2] No such file or directory: > u'/tmp/esx-rhel6.8-ova.tar' > VDSM NFS command GetOvaInfoVDS failed: OVA directory /tmp/ does not contain > ovf file" In the web GUI the below info is more correctly and same as engine.log: Failed to import Vm esx5.5-rhel6.8-x86_64 to Data Center Default, Cluster Default Network Interface nic1 has MAC address 00:1a:4a:16:01:53 which is in use.
Verification builds: rhevm-4.1.7.6-0.1.el7 qemu-kvm-rhev-2.9.0-16.el7_4.8.x86_64 vdsm-4.19.36-1.el7ev.x86_64 libvirt-client-3.2.0-14.el7_4.3.x86_64 sanlock-3.5.0-1.el7.x86_64 virt-v2v-1.36.3-6.el7_4.3.x86_64 Verification scenario: 1. Upload OVA to export domain using 'virt-v2v -i ova' command (esx-rhel6.8-ova file uploaded). 2. Browse Webadmin -> storage tab -> export domain -> VM import, select VM and import it. 3. Verify import succeed. 4. Run VM and verify VM is running properly.