-
Bug
-
Resolution: Unresolved
-
Undefined
-
CNV v4.21.0
-
None
Description of problem:
VirtualMachineStorageMigrationPlan/VirtualMachineStorageMigration are not deleted when deleting MultiNamespaceVirtualMachineStorageMigrationPlan/MultiNamespaceVirtualMachineStorageMigration
Version-Release number of selected component (if applicable):
CNV-v4.21.0.rhel9-127
How reproducible:
Always
Steps to Reproduce:
1. Create a VM 2. Create a MultiNamespaceVirtualMachineStorageMigrationPlan 3. Create a MultiNamespaceVirtualMachineStorageMigration to start the migration 4. Wait the migration completed 5. Deleting the MultiNamespaceVirtualMachineStorageMigrationPlan and MultiNamespaceVirtualMachineStorageMigration 6. Check the VirtualMachineStorageMigrationPlan and VirtualMachineStorageMigration
Actual results:
6. VirtualMachineStorageMigrationPlan and VirtualMachineStorageMigration are still exist when MultiNamespaceVirtualMachineStorageMigrationPlan and MultiNamespaceVirtualMachineStorageMigration are deleted, user have to delete every kind of resources manually.
Expected results:
Users only create the MultiNamespaceVirtualMachineStorageMigrationPlan and MultiNamespaceVirtualMachineStorageMigration and the controller helps to create the VirtualMachineStorageMigrationPlan and VirtualMachineStorageMigration, so when we deleting Multi-xxx resources, it is better to cleaned up the VirtualMachineStorageMigrationPlan and VirtualMachineStorageMigration
Additional info:
A lot of leftover migration plans and migrations resources remain after the migration completed. Is there a more efficient way to manage or automate the cleanup of these resources?
