-
Bug
-
Resolution: Unresolved
-
Normal
-
2.10.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
True
-
-
-
MTV Sprint 4
Description of problem:
Cold migrate VM: mtv-feature-rhel9-luks-nbde from VCenter7 to OCP cluster mtv-test project, the plan executed successfully, delete the VM on target OCP cluster. Warm migrate the same VM from vCenter7 to same OCP cluster mtv-test project, hit unexpect MacConflicts error
- category: Critical items: - ' id:vm-175 name:''mtv-feature-rhel9-luks-nbde'' ' lastTransitionTime: "2025-09-18T02:13:04Z" message: 'VM id:vm-175 name:''mtv-feature-rhel9-luks-nbde'' has MAC address conflicts: MACs 00:50:56:94:fd:0f conflict with destination VM mtv-test/mtv-feature-rhel9-luks-nbde' reason: NotValid status: "True" type: MacConflicts
Version-Release number of selected component (if applicable):
2.10.0-6 build (IIB: forklift-fbc-prod-v420:on-pr-52e94dd9cd11eaf7e225644c31cb966f2c8e4494) with CNV 4.20.0
How reproducible:
Always
Steps to Reproduce:
1) Cold migrate VM: mtv-feature-rhel9-luks-nbde from VCenter7 to OCP cluster mtv-test project, the plan executed successfully
2) Delete the VM on target OCP cluster
3) Warm migrate the same VM from vCenter7 to same OCP cluster mtv-test project, the plan executed successfully, but the plan condition part with MacConfilicts message
- category: Critical items: - ' id:vm-175 name:''mtv-feature-rhel9-luks-nbde'' ' lastTransitionTime: "2025-09-18T02:13:04Z" message: 'VM id:vm-175 name:''mtv-feature-rhel9-luks-nbde'' has MAC address conflicts: MACs 00:50:56:94:fd:0f conflict with destination VM mtv-test/mtv-feature-rhel9-luks-nbde' reason: NotValid status: "True" type: MacConflicts
4) Check on the cluster, there is only one VM: mtv-feature-rhel9-luks-nbde
# oc get vm --all-namespaces NAMESPACE NAME AGE STATUS READY mtv-test mtv-feature-rhel9-luks-nbde 10m Running True
Actual results:
In step3: The migration plan conditons with "MacConflicts"
Expected results:
In step3: The migration plan conditions without "MacConfilicts", as the VM is deleted from OCP cluster before the migration
Additional info:
