-
Bug
-
Resolution: Unresolved
-
Normal
-
2.9.0
-
Quality / Stability / Reliability
-
False
-
-
True
-
-
Description of problem:
Try to cold migrate VM from vCenter to OCP cluster, the migration plan failed without any error message and the conversion pod is not created
After debugging, the root cause is that, in target OCP cluster, another VM with interface with the same mac address, how about sharing the error message in the failed plan, as the user will confused by why the plan is failed, and why the conversion pod is not created, they can't find useful information in forklift-controller pod log
Version-Release number of selected component (if applicable):
MTV 2.9.0 (forklift-fbc-prod-v418:on-pr-16546d253dda4fc8d8b838f0703040f30a985cf0) with CNV 4.18.7 (IIB: 983760)
How reproducible:
100%
Steps to Reproduce:
1) Cold migrate VM: mtv-function-rhel7-9-staticips with 4 interfaces from vCenter 7 without certificate verification to OCP cluster with preserve static ip, the plan failed in ImageConversion phase, no conversion pod is created. And user can't find useful information in controller pod log: forklift-controller-5bbb448f79-w4gcb-main.log
Actual results:
Step1: The plan is failed without error message
Expected results:
Step1: The failed plan show the error message
- is duplicated by
-
MTV-2732 MAC Address Conflict Not Properly Propagated in ImageConversion Step
-
- Closed
-