Bug 2222122 - VirtualMachineClone object should be removed when associated VM deleted
Summary: VirtualMachineClone object should be removed when associated VM deleted
Keywords:
Status: NEW
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 4.14.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.15.0
Assignee: sgott
QA Contact: Kedar Bidarkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-11 21:59 UTC by Denys Shchedrivyi
Modified: 2023-07-13 12:01 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-30877 0 None None None 2023-07-11 22:01:05 UTC

Description Denys Shchedrivyi 2023-07-11 21:59:19 UTC 
Description of problem:
 After removing cloned VM the VirtualMachineClone is still present on a cluster, however it should be removed (similar to migrations)

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


How reproducible:


Steps to Reproduce:
1. create VM
2. clone VM
3. delete VMs


Actual results:
 VirtualMachineClone is still present

Expected results:
 VirtualMachineClone should be removed when VM removed 

Additional info:
Comment 1 Kedar Bidarkar 2023-07-13 11:45:55 UTC 
Targeting this to 4.15, taking severity and priority into consideration. Also this was discussed with the Virt Devs.
Note You need to log in before you can comment on or make changes to this bug.