Bug 2041886
| Summary: | virt-v2v hangs for several minutes when using -ic vpx://... -it vddk with incorrect IP address | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Xiaodai Wang <xiaodwan> |
| Component: | virt-v2v | Assignee: | Richard W.M. Jones <rjones> |
| Status: | CLOSED ERRATA | QA Contact: | Vera <vwu> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 9.0 | CC: | jsuchane, juzhou, kkiwi, lersek, mxie, mzhan, ptoscano, rjones, tyan, tzheng, xiaodwan, zili |
| Target Milestone: | rc | Keywords: | Regression, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-v2v-1.45.97-2.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1839917 | Environment: | |
| Last Closed: | 2022-05-17 13:42:09 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1839917 | ||
| Bug Blocks: | |||
|
Description
Xiaodai Wang
2022-01-18 13:12:10 UTC
So I'm not sure what the ask is here: the connection to time out earlier, or that virt-v2v print the URL before it starts connecting? The former is NOTABUG for virt-v2v (see comment 3), and the latter is already solved in RHEL9 (by inheriting upstream commit 86d87563ee03 ("-i libvirt: print URI without connecting (RHBZ#1839917)", 2020-05-26)), so that would be CURRENTRELEASE or WORKSFORME I guess. Upstream fix: https://github.com/libguestfs/virt-v2v/commit/924aa8b70a64e9b076f8f56328a2b49650ab713c Verified with the versions: virt-v2v-1.45.97-2.el9.x86_64 libguestfs-1.46.1-2.el9.x86_64 Steps: Scenario 1: 1. Convert a guest from VMware by v2v but write incorrect vCenter IP in command line 1.1.1 # virt-v2v -ic vpx://root.198.169/data/10.73.199.216/?no_verify=1 -it vddk -io vddk-libdir=/root/vddk_libdir/latest -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 esx7.0-win2019-x86_64 -ip /v2v-ops/esxpw -o null [ 0.0] Setting up the source: -i libvirt -ic vpx://root.198.169/data/10.73.199.216/?no_verify=1 -it vddk esx7.0-win2019-x86_64 virt-v2v: error: exception: libvirt: VIR_ERR_INTERNAL_ERROR: VIR_FROM_ESX: internal error: Could not find compute resource specified in '/data/10.73.199.216/' If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...] 1.1.2 Add -v -x to convert again, can see the error info is reported instantly # virt-v2v -ic vpx://root.198.168/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/root/vddk_libdir/latest -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 esx7.0-win2019-x86_64 -o null -v -x|& ts Jan 26 05:44:56 virt-v2v: virt-v2v 1.45.97rhel=9,release=2.el9 (x86_64) Jan 26 05:44:56 libvirt version: 8.0.0 Jan 26 05:44:56 [ 0.0] Setting up the source: -i libvirt -ic vpx://root.198.168/data/10.73.199.217/?no_verify=1 -it vddk esx7.0-win2019-x86_64 Jan 26 05:45:12 Enter root's password for 10.73.198.168: virt-v2v: error: exception: libvirt: VIR_ERR_INTERNAL_ERROR: VIR_FROM_NONE: Jan 26 05:45:12 An error occurred, but the cause is unknown Jan 26 05:45:12 rm -rf '/tmp/v2v.ku8xQ3' Scenario2: 2.1 Convert a guest from VMware by v2v but write incorrect ESXi IP in command line # virt-v2v -ic vpx://root.198.169/data/10.73.199.216/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0.2 -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 esx7.0-win2019-x86_64 -ip /home/esxpw -o null -v -x |& ts Jan 26 05:56:27 virt-v2v: virt-v2v 1.45.97rhel=9,release=2.el9 (x86_64) Jan 26 05:56:27 libvirt version: 8.0.0 Jan 26 05:56:27 [ 0.0] Setting up the source: -i libvirt -ic vpx://root.198.169/data/10.73.199.216/?no_verify=1 -it vddk esx7.0-win2019-x86_64 Jan 26 05:56:31 virt-v2v: error: exception: libvirt: VIR_ERR_INTERNAL_ERROR: VIR_FROM_ESX: Jan 26 05:56:31 internal error: HTTP response code 500 for call to 'Login'. Fault: Jan 26 05:56:31 ServerFaultCode - Cannot complete login due to an incorrect user name or Jan 26 05:56:31 password. Jan 26 05:56:31 rm -rf '/tmp/v2v.ZdZz9S' Scenario3: 3.1 Convert a guest from VMware by v2v and make sure vpx:// URL is correct # virt-v2v -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0.2 -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 esx7.0-win2019-x86_64 -ip /home/esxpw -o null -v -x |& ts Jan 26 05:57:37 virt-v2v: virt-v2v 1.45.97rhel=9,release=2.el9 (x86_64) Jan 26 05:57:37 libvirt version: 8.0.0 Jan 26 05:57:37 [ 0.0] Setting up the source: -i libvirt -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 -it vddk esx7.0-win2019-x86_64 Jan 26 05:57:41 virt-v2v: error: exception: libvirt: VIR_ERR_INTERNAL_ERROR: VIR_FROM_ESX: Jan 26 05:57:41 internal error: HTTP response code 500 for call to 'Login'. Fault: Jan 26 05:57:41 ServerFaultCode - Cannot complete login due to an incorrect user name or Jan 26 05:57:41 password. Jan 26 05:57:41 rm -rf '/tmp/v2v.MGxh6N' Moving to verified. 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 (new packages: virt-v2v), 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://access.redhat.com/errata/RHEA-2022:2566 |