Created attachment 1426829 [details] Screenshot Description of problem: Trying to migrate VM with long name fails in state 5 (as per logs) Version-Release number of selected component (if applicable): master.20180424003235_96b2aa1 How reproducible: Believe 100% Steps to Reproduce: 1.Create a VMware VM with long name (65 characters) 2.Setup MIQ appliance for migration 3.Try to migrate the VM 4. see automation.log Actual results: VM is migrated to RHV but migration plan failed Expected results: Migration should not fail, as I believe up to 65 characters is VM name limit, if not please elaborate what is acceptable limit. Additional info:
Upstream issues created: https://github.com/priley86/miq_v2v_ui_plugin/issues/258
OoooooOOOooOOoooo I'll jump on this one, we have a solution employed elsewhere in the app, truncate with ellipses and throw up a tooltip with the rest of the name...
yep comment for the wrong bz :sob: comment intended for https://bugzilla.redhat.com/show_bug.cgi?id=1571948
Cloned to https://bugzilla.redhat.com/show_bug.cgi?id=1581749 Closing with Insufficient data, since its not a bug for CFME.
IIUC the current behavior is that when VM has >65 chars (same applies to unsupported chars) the migration succeeds but the VM cannot be started (as it is not supported by RHV) The fix on RHV side is about properly fail such VM import It will _not_ make it work as this bugs description assumes. There is a fix required on CFME side to follow the same validation as RHV has, or we need to agree on some reliable mapping from the original name - that's probably a bit more complicated as disks would need to be renamed as well and those are created by virt-v2v itself now.
Don't expect this will be fixed in a planned release at this time. Will revisit if it is identified as an issue or blocker with more tool usage.