There was an outdated ovirtvolumepopulator in the namespace which was leftover from the previous failed migration. When a new plan was started for the same VM, the phase 'CreateDataVolumes' didn't created the populator PVCs [1]  and the plan phase was transitioned into CopyDisks. Then the plan remains in this phase indefinitely without making any progress until the user cancels the migration.

Please provide the package NVR for which bug is seen:

Migration Toolkit for Virtualization Operator   2.5.4

How reproducible:

100%

Steps to reproduce

1. Create an ovirtvolumepopulator with the name set as the disk UUID of the VM which you are planning to migrate. It was leftover from the previous failed migration on the customer's environment where the issue was observed.
2. Create a new plan and start it .
3. Look for PVC and PODs in the target namespace, they will not be created and the plan will be in status "Transfer disks" for ever .

Expected results

Fail the plan and give a proper message to the user if there is a leftover  ovirtvolumepopulator object from previous migration.

Actual results

Plan running indefinitely in "CopyDisks" phase if there is a outdated ovirtvolumepopulator 

 [1]https://github.com/kubev2v/forklift/blob/331de53c36b84b032047c62ca3fdc501e26843c1/pkg/controller/plan/adapter/ovirt/builder.go#L738