-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-9.6
-
None
-
Important
-
1
-
rhel-virt-core-libvirt-1
-
None
-
False
-
False
-
-
No
-
Libvirt Refining
-
Unspecified Release Note Type - Unknown
-
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:
libvirt-libs-10.10.0-7.6.el9_6.x86_64
(also reproduces with all versions of libvirt in RHEL 10, Fedora and upstream)
How reproducible is this bug?:
Always
Steps to reproduce
- In vSphere, have a datastore with '+' in the name
- Try to migrate with MTV a VM from that datastore
Expected results
VM migrated correctly.
Actual results
Error 404 when downloading the vmx file:
# virsh -c vpx://root@10.73.213.134/data/cluster-1/10.73.225.34/?no_verify=1 dumpxml esx8.0-rhel9.6-efi-with-tpm Enter root's password for 10.73.213.134: error: internal error: HTTP response code 404 for download from 'https://10.73.213.134:443/folder/esx8.0-rhel9.6-efi-with-tpm%2Fesx8.0-rhel9.6-efi-with-tpm.vmx?dcPath=data&dsName=datastore2%2B'
(This requires a password, please ask mxie@redhat.com)
- blocks
-
RHEL-133729 virt-v2v migration from vSphere fails when datastore name has characters like '+'
-
- New
-
- clones
-
RHEL-133729 virt-v2v migration from vSphere fails when datastore name has characters like '+'
-
- New
-