Bug 2105031 - Virtual Machine Instance Migration cant be deleted after VMI deletion
Summary: Virtual Machine Instance Migration cant be deleted after VMI deletion
Keywords:
Status: CLOSED DUPLICATE of bug 2040377
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 4.11.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: sgott
QA Contact: Kedar Bidarkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-07 18:21 UTC by Roni Kishner
Modified: 2022-07-13 05:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-13 05:32:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Roni Kishner 2022-07-07 18:21:05 UTC
Description of problem:
In case we delete a VM while a migration is in progress and the VMIM isn't finished yet, the VMIM is cant be deleted, this also prevents the deletion of the namespace it was created


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

How reproducible:
100%

Steps to Reproduce:
1. Create a number of VMs (15)
2. Start live migration on all of them
3. delete all the VMs
4. try to delete the VMIM

Actual results:
The VMIM still exists (VM + VMI are deleted)

Expected results:
The VMIM is deleted 

Additional info:
the VMIM finlizer section shows:
  finalizers:
  - kubevirt.io/migrationJobFinalize

the VMIM will be automatically deleted by editing the VMIM and removing the "finalizer" section

I think the best approach would be to delete the VMIM in case one exists before deleting the VMI.

Comment 1 Kedar Bidarkar 2022-07-12 16:05:21 UTC
This bug appears to be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2040377

Comment 2 Roni Kishner 2022-07-13 05:32:42 UTC

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


Note You need to log in before you can comment on or make changes to this bug.