Description of problem:

In the UI a user can "start" a Plan more than once, creating more than one Migration CR,

when set the cutover in UI, it set for the latest migration but not the running migration,

thus can't set cutover for the running migration in UI in this case

Version-Release number of selected component (if applicable):

MTV 2.7.8 with CNV 4.17.3

How reproducible:

70%

Steps to Reproduce:

1) Create vshpere 7 provider: v7-us

2) Create warm migration plan: mtv-warm-test to migrate vm: mtv-function-rhel8-8 to target cluster with storage class: nfs-csi

3) In the Plans -> Plan Details -> Virtual Machines page, select the VM and click "Start Migration" button, sometimes the page no change, then click the "Start Migration" button again, this cause the 2 Migration are created:

mtv-warm-test-prlvt is running, mtv-warm-test-d2fd2 is ready status

4) Set the cutover in webpage: Plans -> Plan Details: Virtual Machines page select the VM and click Acitions: Cutover

5) Check the cutover is set for the Reay status migration but not the Running status migration,

 thus the cutover in the web page is not take effect on the running migration

# oc describe migration mtv-warm-test-d2fd2| grep Cutover
  Cutover:  2025-01-17T03:45:36.100Z
 # oc describe migration mtv-warm-test-prlvt| grep Cutover
      Name:         Cutover

Actual result:

In step3: 2 migration are created
In step4,5: The cutover is set for the ready migration but not for the running migration

Expected result:

In step3: Only 1 migration can be created
In step4,5: The cutover is set for the running migration