-
Bug
-
Resolution: Done-Errata
-
Major
-
2.7.1
-
None
-
None
-
False
-
None
-
False
-
-
-
Important
Attempted migration of VMware VM with non-compliant Kubernetes name due to capital letter in VM name epassaroMigrate-2.
In the Openshift console a warning is shown saying that the VM would be renamed:
Warning Target VM name does not comply with DNS1123 RFC, will be automatically changed. To troubleshoot, view the plan details page and check the Forklift controller pod logs.
But after starting the migration plan, after some time it hangs since the migration pod is in Error state:
$ oc logs -n openshift-mtv epassaro-migration-folder-vm-56858-qm2fj Defaulted container "virt-v2v" out of: virt-v2v, vddk-side-car (init) exec: /usr/bin/virt-v2v -v -x -o kubevirt -os /var/tmp/v2v -i libvirt -ic vpx://administrator%40ecosystem.content.vsphere@eco-vcenter-server.lab.eng.tlv2.redhat.com/Eco-Datacenter/host/Eco-Cluster/10.46.29.136 -ip /etc/secret/secretKey --root first -it vddk -io vddk-libdir=/opt/vmware-vix-disklib-distrib -io vddk-thumbprint=00:9E:D2:C0:ED:19:CC:C5:C8:CD:E2:F2:4E:CC:88:AB:32:77:8F:DE -- epassaroMigrate-2 -on epassaromigrate-2 virt-v2v monitoring: Setting up prometheus endpoint :2112/metrics virt-v2v monitoring: Prometheus progress counter registered. virt-v2v: virt-v2v 2.4.0rhel=9,release=4.el9_4 (x86_64) libvirt version: 10.0.0 check_host_free_space: large_tmpdir=/var/tmp free_space=35811217408 [ 0.0] Setting up the source: -i libvirt -ic vpx://administrator%40ecosystem.content.vsphere@eco-vcenter-server.lab.eng.tlv2.redhat.com/Eco-Datacenter/host/Eco-Cluster/10.46.29.136 -it vddk epassaroMigrate-2 -on epassaromigrate-2 virt-v2v: error: -i libvirt: expecting a libvirt guest name on the command line rm -rf -- '/tmp/v2v.s9pzjd' Error executing v2v command: exit status 1 Failed to execute virt-v2v command: exit status 1
