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.
Bug 1258342 - extra slashes in vcenter URL confuses virt-v2v
Summary: extra slashes in vcenter URL confuses virt-v2v
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.2
Hardware: x86_64
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard: V2V
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-31 06:48 UTC by tingting zheng
Modified: 2015-11-19 07:03 UTC (History)
5 users (show)

Fixed In Version: libguestfs-1.28.1-1.51.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 07:03:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Debug info for virt-v2v (18.33 KB, text/plain)
2015-08-31 06:48 UTC, tingting zheng 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2183 0 normal SHIPPED_LIVE libguestfs bug fix and enhancement update 2015-11-19 08:18:42 UTC

Description tingting zheng 2015-08-31 06:48:05 UTC 
Created attachment 1068509 [details]
Debug info for virt-v2v

Description:
virt-v2v fails to convert guests from esx server

Version:
virt-v2v-1.28.1-1.50.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Use virt-v2v to convert guests from esx server,error shows as below.
# virt-v2v -ic vpx://root.72.112/data/10.66.72.49/?no_verify=1 -os default -of raw -b virbr0 -n default esx6.0-rhel6.7-x86_64 --password-file /tmp/v2v_vpx_passwd
[   0.0] Opening the source -i libvirt -ic vpx://root.72.112/data/10.66.72.49/?no_verify=1 esx6.0-rhel6.7-x86_64
curl -q --insecure --user '<hidden>' --head --silent --url 'https://10.66.72.112/folder/esx6.0-rhel6.7-x86%5f64/esx6.0-rhel6.7-x86%5f64-flat.vmdk?dcPath=data/10.66.72.49&dsName=esx6.0'
HTTP/1.1 404 Not Found
Date: Mon, 31 Aug 2015 00:50:38 GMT
Set-Cookie: vmware_soap_session="301d8281cbf82a0af4d5dde88934643e7b70d4e0"; Path=/; HttpOnly; Secure; 
Connection: close
Content-Type: text; charset=plain
Content-Length: 0

virt-v2v: error: vcenter: URL not found: 
https://10.66.72.112/folder/esx6.0-rhel6.7-x86%5f64/esx6.0-rhel6.7-x86%5f64-flat.vmdk?dcPath=data/10.66.72.49&dsName=esx6.0

If reporting bugs, run virt-v2v with debugging enabled and include the 
complete output:

  virt-v2v -v -x [...]

Actual results：
As description.

Expected results:
Guests from esx server can be converted by virt-v2v successfully.

Additional info:
The bug can not reproduced on virt-v2v-1.28.1-1.49.el7.x86_64.
Attached debug log.
Comment 4 Richard W.M. Jones 2015-08-31 13:29:26 UTC 
I think it will work if you strip off the final slash:

vpx://root.72.112/data/10.66.72.49/?no_verify=1
                                        ^
                                         -- remove this

However yes this is a regression caused by the fix for bug 1256823.
Comment 5 Richard W.M. Jones 2015-09-01 14:06:08 UTC 
https://github.com/libguestfs/libguestfs/commit/51bc573d0c4e78104a682e7c42d63d701aedd093
Comment 7 tingting zheng 2015-09-02 09:47:21 UTC 
Tested with:
virt-v2v-1.28.1-1.51.el7.x86_64

Virt-v2v can convert guests from esx server successfully.

# virt-v2v -ic vpx://root.72.112/data/10.66.72.49/?no_verify=1 -os default -of raw -b virbr0 -n default esx6.0-rhel6.7-x86_64 --password-file /tmp/v2v_vpx_passwd -on tzheng-test
[   0.0] Opening the source -i libvirt -ic vpx://root.72.112/data/10.66.72.49/?no_verify=1 esx6.0-rhel6.7-x86_64
[   1.0] Creating an overlay to protect the source from being modified
[   1.0] Opening the overlay
[ 109.0] Initializing the target -o libvirt -os default
[ 109.0] Inspecting the overlay
[ 185.0] Checking for sufficient free disk space in the guest
[ 185.0] Estimating space required on target for each disk
[ 185.0] Converting Red Hat Enterprise Linux Server release 6.7 Beta (Santiago) to run on KVM
virt-v2v: This guest has virtio drivers installed.
[ 634.0] Mapping filesystem data to avoid copying unused and blank areas
[ 635.0] Closing the overlay
[ 636.0] Checking if the guest needs BIOS or UEFI to boot
[ 636.0] Copying disk 1/1 to /var/lib/libvirt/images/tzheng-test-sda (raw)
    (100.00/100%)
[ 897.0] Creating output metadata
Pool default refreshed

Domain tzheng-test defined from /tmp/v2vlibvirt05e8a0.xml

[ 898.0] Finishing off

Refer to the above comments,move the bug to VERIFIED.
Comment 9 errata-xmlrpc 2015-11-19 07:03:31 UTC 
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-2015-2183.html
Note You need to log in before you can comment on or make changes to this bug.