Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Trying to import VMware VM from RHEVM failed with "HTTP/1.1 404 Not Found" when trying to get storage path.
VMware environment is 6.0.0 licensed and VMware VM I'm trying to import is with NFS disk.
Version-Release number of selected component (if applicable):
engine:
rhevm-3.6.1.2-0.1.el6
host (RHEL 7.2):
libvirt-client-1.2.17-13.el7_2.2.x86_64
qemu-kvm-rhev-2.3.0-31.el7_2.4.x86_64
vdsm-4.17.13-1.el7ev
How reproducible:
100%
Steps to Reproduce:
1. From vSphere client, create DC -> Cluster -> add host -> create VM with NFS storage (keep VM powered off during the next steps).
2. Open RHEVM, navigate to virtual machines tab -> click import.
3. Enter vCenter details and credentials -> click "load"
4. Select one of the VMs that were listed to import and click "next".
5. Select host and storage domain destination -> click "ok"
Actual results:
After import process started, it failed during import VM disk phase with the next engine.log (IP address changed to 10.X.X.X by me):
2015-12-13 10:15:40,742 INFO [org.ovirt.engine.core.bll.ConvertVmCallback] (DefaultQuartzScheduler_Worker-27) [] Conversion of VM from exteral enironment failed: Job u'423c3d8c-15e9-4650-f0fa-02d0a8332ea9' process failed exit-code: 1, stderr: curl -q --insecure --user '<hidden>' --head --silent --url 'https://10.X.X.X/folder/rhel7/rhel7-flat.vmdk?dcPath=Compute/cluster&dsName=storage'
HTTP/1.1 404 Not Found
Date: Sun, 13 Dec 2015 08:16:14 GMT
Set-Cookie: vmware_soap_session="c905314a0fd3cec35f9442c995f067b3704e08ec"; Path=/; HttpOnly; Secure;
Connection: close
Content-Type: text; charset=plain
Content-Length: 0
virt-v2v: error: vcenter: URL not found:
https://10.35.161.20/folder/rhel7/rhel7-flat.vmdk?dcPath=Compute/cluster&dsName=storage
Expected results:
Import VM should succeed.
Additional info:
engine.log and vdsm.log attached.
vdsm issue occurred at: Thread-29651::ERROR::2015-12-13 10:16:14,715
engine issue occurred at: 2015-12-13 10:15:40,742
I also tried to disable SELinux and turn off iptables, issue is still reproduced.
Comment 4Richard W.M. Jones
2015-12-13 15:13:23 UTC
This is probably a duplicate of
https://bugzilla.redhat.com/show_bug.cgi?id=1256823
There are only two realistic solutions to this:
(1) Modify the UI so that the user can pass in the dcpath
parameter (which is then passed through to the virt-v2v
command line).
However that's going to be annoying to document, so a
better solution is:
(2) Wait for RHEL 7.3 where a combination of libguestfs and
libvirt [bug 1263574] updates will fix this automatically
without any need to use --dcpath.
In any case, we cannot solve this in libguestfs.
Comment 5Richard W.M. Jones
2015-12-13 15:16:28 UTC
BTW neither of the log files contains any useful information. To
really diagnose if this is a duplicate, I need the output of the
'virt-v2v -v -x' command.
based on comment #4, and assuming bug 1263574 and bug 1292437 get the backport approval, there is indeed no need to track this separately
Richard, if you're fine with that I would close as dupe of RHEV bug 1292096
Comment 7Richard W.M. Jones
2016-01-07 14:19:37 UTC
Closing as duplicate per comment 6.
*** This bug has been marked as a duplicate of bug 1292096 ***