DescriptionMichal Skrivanek
2016-08-18 20:54:30 UTC
Clone for 3.6.9
+++ This bug was initially created as a clone of Bug #1367839 +++
Description of problem:
- Trying to import VM from Xen or VMware using RHEL7.3 host failed with the next vdsm.log error:
Thread-1287::ERROR::2016-08-17 17:48:12,679::v2v::670::root::(_run) Job u'4235cea0-e706-af4f-c296-0346c347741e' failed
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 665, in _run
self._import()
File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 692, in _import
self._proc.stderr.read(1024)))
V2VProcessError: Job u'4235cea0-e706-af4f-c296-0346c347741e' process failed exit-code: 1, stderr: virt-v2v: error: internal error: Not_found exception was thrown
- Manually importing the same VM using virt-v2v command succeeds:
root@**** nisim]# LIBGUESTFS_BACKEND=direct virt-v2v -ic vpx://administrator@****/Folder1/Folder2/Compute/Folder3/Cluster/*****?no_verify=1 tg-centos -o null
[ 0.0] Opening the source -i libvirt -ic vpx://administrator@*****/Folder1/Folder2/Compute/Folder3/Cluster/*****?no_verify=1 tg-centos
Enter administrator's password for *****:
Enter host password for user 'administrator':
[ 8.5] Creating an overlay to protect the source from being modified
[ 9.3] Initializing the target -o null
[ 9.3] Opening the overlay
[ 37.8] Inspecting the overlay
[ 80.8] Checking for sufficient free disk space in the guest
[ 80.8] Estimating space required on target for each disk
[ 80.8] Converting Red Hat Enterprise Linux Server 7.0 (Maipo) to run on KVM
virt-v2v: This guest has virtio drivers installed.
[ 807.7] Mapping filesystem data to avoid copying unused and blank areas
[ 810.3] Closing the overlay
[ 810.3] Checking if the guest needs BIOS or UEFI to boot
[ 810.3] Assigning disks to buses
[ 810.3] Copying disk 1/1 to /var/tmp/null.Sy8WQa/sda (raw)
(100.00/100%)
[ 950.0] Creating output metadata
[ 950.0] Finishing off
Version-Release number of selected component (if applicable):
rhevm-4.0.2.6-0.1.el7ev.noarch
libvirt-client-2.0.0-5.el7.x86_64
vdsm-4.18.11-1.el7ev.x86_64
qemu-kvm-rhev-2.6.0-21.el7.x86_64
sanlock-3.4.0-1.el7.x86_64
3.10.0-492.el7.x86_64
How reproducible:
Consistently
Steps to Reproduce:
1. Try to import VM from Xen or VMware.
2.
3.
Actual results:
import failed.
Expected results:
VM should be imported successfully.
Additional info:
Bug is relevant only for virt-v2v. importing from RHEL KVM environment is possible.
vdsm and engine logs attached.
--- Additional comment from Nisim Simsolo on 2016-08-17 17:26 CEST ---
--- Additional comment from Nisim Simsolo on 2016-08-17 17:27 CEST ---
--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-08-18 10:02:30 CEST ---
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
--- Additional comment from Nisim Simsolo on 2016-08-18 16:34:28 CEST ---
This bug is also relevant for rhevm-3.6.8-0.1.el6 with RHEL 7.3 host.
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.
https://rhn.redhat.com/errata/RHBA-2016-1925.html