-
Bug
-
Resolution: Unresolved
-
Undefined
-
2.9.0
Description of problem:
When migrating a VM from VMware to OCP, VM names that contain special characters like a plus sign (+) or spaces ( ) are not preserved correctly. During the migration process, these characters are removed, and the resulting VM name becomes a concatenated string without separators. Example: Original VM name in VMware: namemtv+func rhel8 Ameen Resulting VM name in CNV: mtvfuncrhel8Ameen
Version-Release number of selected component (if applicable):
OCP: 4.19 CNV: 4.19.1 MTV: 2.9.0 - forklift-fbc-prod-v419:on-pr-0a284bcac660e2515fe8d0f7e5fd3894438e96c3
How reproducible:
Always
Steps to Reproduce:
1. Create VM in VMware vCenter with the name namemtv+func+rhel8+Ameen 2. Start migration
Actual results:
VM name - inventory: namemtv func rhel8 Ameen VM name during migration - Plan YAML: newName: mtvfuncrhel8ameen VM name - CNV: mtvfuncrhel8ameen
Expected results:
VM name - inventory: namemtv-func-rhel8-Ameen VM name during migration - Plan YAML: newName: mtv-func-rhel8-ameen VM name - CNV: mtv-func-rhel8-ameen
Additional info: