Created attachment 1430873[details]
Screenshot
Description of problem:
Migration Fails when VM contains special characters and oVirtSDK4 cannot handle it.
Version-Release number of selected component (if applicable):
master.20180502231427_a22b03c
How reproducible:
100%
Steps to Reproduce:
1.Create Infra Mapping and Migration plan to migrate a VM that has special characters in its name e.g. kk_$#!*)!%!)(^%#*%)(#@*%#)(@*$
2.Try to migrate this VM
3.
Actual results:
Migration fails with error shown in Screenshot attached, but VM is actually present on the RHV. That means migration failed to perform some step post migration of the actual VM.
Expected results:
Migration should not fail, complete successfully by handling the naming issues.
Additional info:
Both RHV and VMware support the names such as kk_$#!*)!%!)(^%#*%)(#@*%#)(@*$ for the VMs.
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.
If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
please add logs from the conversion from both CFME and RHV side
The name is not a valid RHV name, but apparently we do not check that on import and it only fails once we try an update
Created attachment 1430873 [details] Screenshot Description of problem: Migration Fails when VM contains special characters and oVirtSDK4 cannot handle it. Version-Release number of selected component (if applicable): master.20180502231427_a22b03c How reproducible: 100% Steps to Reproduce: 1.Create Infra Mapping and Migration plan to migrate a VM that has special characters in its name e.g. kk_$#!*)!%!)(^%#*%)(#@*%#)(@*$ 2.Try to migrate this VM 3. Actual results: Migration fails with error shown in Screenshot attached, but VM is actually present on the RHV. That means migration failed to perform some step post migration of the actual VM. Expected results: Migration should not fail, complete successfully by handling the naming issues. Additional info: Both RHV and VMware support the names such as kk_$#!*)!%!)(^%#*%)(#@*%#)(@*$ for the VMs.