-
Bug
-
Resolution: Unresolved
-
Major
-
CNV v4.20.0
-
None
-
Quality / Stability / Reliability
-
3
-
False
-
-
False
-
None
-
-
CNV Storage 277, CNV Storage 278
-
Moderate
-
None
Description of problem:
source VMIM can not be deleted when the migration is failed
Version-Release number of selected component (if applicable):
CNV 4.20.0-144
How reproducible:
Always
Steps to Reproduce:
1. Create a VM 2. Migrate to another cluster by MTV 3. Stop the VM when the migration is started (make sure stop the vm when migration is not finished) 4. Delete the source vmim
Actual results:
source cluster: $ oc delete vmim forklift-v6csv virtualmachineinstancemigration.kubevirt.io "forklift-v6csv" deleted ^C$ oc get vmim NAME PHASE VMI forklift-v6csv TargetReady fedora-02 tarage cluster: $ oc get vm NAME AGE STATUS READY fedora-02 27m Starting False $ oc get vmim NAME PHASE VMI forklift-77pbw Failed fedora-02 $ oc get migration NAMESPACE NAME READY RUNNING SUCCEEDED FAILED AGE openshift-mtv plan40-nj88w True True 29m in target cluster, both vm/vmi and vmim can be deleted normally
Expected results:
source vmim can be deleted
Additional info:
if we remove the finalizers in source vmim, it can be deleted finalizers: - kubevirt.io/migrationJobFinalize
- links to