Bug 2035924

Summary: virtualmachineinstancemigration cannot be deleted
Product: Container Native Virtualization (CNV) Reporter: awax
Component: VirtualizationAssignee: sgott
Status: CLOSED DUPLICATE QA Contact: Kedar Bidarkar <kbidarka>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.9.2CC: cnv-qe-bugs
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-28 22:22:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vmb.yaml none

Description awax 2021-12-28 15:52:10 UTC
Created attachment 1848079 [details]
vmb.yaml

Description of problem:
Unable to delete a VirtualMachineInstanceMigration (VMIM) created for a VM that cannot migrate.



Version-Release number of selected component (if applicable):
CNV - v.4.10.0
OCP - v.4.9.11
Kubernetes Version: v1.22.3+ffbb954



Steps to Reproduce:
1. Create a VM (This VM has a node selector, change it to apply to your cluster):
oc create -f vmb.yaml
2. Create a VMIM object:
oc create -f migration_virtualmachineinstancemigration.yaml
(The migration cannot take place - the VM has a node selector.)
3. Attempt to delete the VMIM object - the attempt will not succeed (must cntl+c to quit the attempt).


Actual results:
VMIM will not get deleted.


Expected results:
VMIM will be deleted.

Comment 2 Kedar Bidarkar 2022-01-05 13:17:42 UTC
Anat, Could you please provide the VMI details from the cluster, by using the command "oc get vmi <vmi-name> -o yaml"

Comment 3 sgott 2022-01-28 22:22:52 UTC
After looking closely at the description I realized this is essentially the same thing as https://bugzilla.redhat.com/show_bug.cgi?id=1719190 -- it's just that the means of triggering the pending condition is different. Thus I'm closing this BZ as a dup (The other bz has more context in the comments).

If you feel this action was in error, please feel free to re-open this BZ.

*** This bug has been marked as a duplicate of bug 1719190 ***

Comment 4 Red Hat Bugzilla 2023-09-15 01:18:26 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days