Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-133729

virt-v2v migration from vSphere fails when datastore name has characters like '+'

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • rhel-9.6
    • virt-v2v
    • None
    • Low
    • 1
    • rhel-virt-tools
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • Virt-tools Refining
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      What were you trying to do that didn't work?

      Migrating a VM from vSphere 6.5.0 to OpenShift using MTV 2.8.7 fails when the source datastore has characters like '+' in the name.

      What is the impact of this issue to you?

      Important. This is blocking migrations from VMware and renaming the datastore can have implications that need to be investigated.

      Please provide the package NVR for which the bug is seen:

       

      virt-v2v-2.7.1-10.el9_6.x86_64
      libvirt-libs-10.10.0-7.6.el9_6.x86_64
      registry.redhat.io/migration-toolkit-virtualization/mtv-virt-v2v-rhel9@sha256:6d928c9d498ed9626dc887c1a274f78089115b0285f91f42888ffbf64b773e3c
      mtv-operator.v2.8.7

       

      How reproducible is this bug?:

      Always

      Steps to reproduce

      1.  In vSphere, have a datastore with '+' in the name
      2. Try to migrate with MTV a VM from that datastore

      Expected results

      VM migrated correctly.

      Actual results

      Error 404 when downloading the vmx file:

       

      Building command:virt-v2v[-v -x -o kubevirt -os /var/tmp/v2v -on vm-name -i libvirt -ic vpx://administrator%40vsphere.local@vcenter.example.com/Datacenter/host/CLUSTER/192.168.1.1?no_verify=1 -ip /etc/secret/secretKey --root first -it vddk -io vddk-libdir=/opt/vmware-vix-disklib-distrib -io vddk-thumbprint=C3:2E:EA:5E:72:D9:0C:9C:41:2B:F4:68:8E:31:E1:B1:E9:7B:3A:A9 -- vm-name]Building command:/usr/local/bin/virt-v2v-monitor[]virt-v2v monitoring: Setting up prometheus endpoint :2112/metrics
      virt-v2v monitoring: Prometheus progress counter registered.
      info: virt-v2v: virt-v2v 2.7.1rhel=9,release=10.el9_6 (x86_64)
      info: libvirt version: 10.10.0
      check_host_free_space: large_tmpdir=/var/tmp free_space=356736024576
      [   0.0] Setting up the source: -i libvirt -ic vpx://administrator%40vsphere.local@vcenter.example.com/Datacenter/host/CLUSTER/192.168.1.1?no_verify=1 -it vddk vm-name
      virt-v2v: error: exception: libvirt: VIR_ERR_INTERNAL_ERROR: VIR_FROM_ESX: internal error: HTTP response code 404 for download from 'https://vcenter.example.com:443/folder/vm-name%2Fvm-name.vmx?dcPath=Datacenter&dsName=Test%2BDatastore1'
      rm -rf -- '/tmp/v2v.3QT5wB'
      Error executing v2v command: exit status 1
      Failed to execute virt-v2v command exit status 1

       

       

              rhn-engineering-colerobinson Cole Robinson
              rhn-support-jortialc Juan Orti
              virt-maint virt-maint
              virt-bugs virt-bugs
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: