-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
2.10.1, 2.9.6
-
Quality / Stability / Reliability
-
False
-
-
True
-
-
Description of problem:
User can "start" a migration plan more than one time in UI, create more than one Migrations, when set the cutover, it's set for the latest Migration but not the running Migration, which caused the warm migration plan hang
Version-Release number of selected component (if applicable):
MTV 2.9.6-1 and 2.10.1-1
How reproducible:
80%
Steps to Reproduce:
1) Create vshpere 7 provider: v7-us
2) Create warm migration plan: warm-win2022-test to migrate vm: mtv-func-win2022-uefi-sb to target cluster with storage class: nfs-csi
3) In the Plans -> Plan Details -> Details page, click "Start" button, click Start Migration "Start" button for three times.
4) Check 3 Migrations are created
5) Set the cutover for this plan, the plan hang
6) The Cutover is set for Migration: warm-win2022-test-c87f5, but the running Migration is warm-win2022-test-zzn9q, which caused the migration plan hang
# oc get migration|grep warm-win2022-test NAME READY RUNNING SUCCEEDED FAILED AGE warm-win2022-test-c87f5 True 40m warm-win2022-test-lmjvs True 40m warm-win2022-test-zzn9q True True 40m # oc describe migration warm-win2022-test-zzn9q |grep Cutover Name: Cutover # oc describe migration warm-win2022-test-c87f5 |grep Cutover Cutover: 2025-11-18T06:20:51Z
Actual results:
In step5,6: the Cutover is set for the latest Migration but not the running Migration
Expected results:
In step5,6: the Cutover is set for the running Migration
Additional info:
