In rare cases, after migration - both pods Target and Source remain in the Running state, while the VMIM is in the Succeeded state.

$ oc get vmim
NAME        PHASE       VMI
vm-migr-5   Succeeded   vm-migr-5

$ oc get pod -o wide
NAME                            READY   STATUS    RESTARTS   AGE   IP             NODE                                NOMINATED NODE   READINESS GATES
virt-launcher-vm-migr-5-78pls   3/3     Running   0          38m   10.129.0.205   cnvqe-056.lab.eng.tlv2.redhat.com   <none>           1/1
virt-launcher-vm-migr-5-qnhnp   3/3     Running   0          36m   10.128.0.124   cnvqe-057.lab.eng.tlv2.redhat.com   <none>           1/1


When trying to delete this VM - it stuck in Terminating state. 
Target pod removed
Source pod is in Error state
VMI - in Succeded state.

4.20

We've observed it in automation in very rare cases, but I was able to reproduce it by migrating tens of VMs in a loop

1. create multiple vms
2. migrate all VMs in a loop
3.

Both Source and Target pods may remain in Running state

Only target pod should be in running state. 
Source pod should be in Completed.

probably this issue related to:
https://issues.redhat.com/browse/CNV-67515