Description of problem: V2VVMWare or OvirtProvider objects are not cleaned up How reproducible: 100 Steps to Reproduce: 1. visit VM Import Wizard 2. select instance 3. redirect to deployments 4. mentioned objects live forever caused by this patch https://github.com/openshift/console/pull/6538 there are also subtle mistakes with data loading which concern the same part of the code
moving out until there is a lgtm on the patch
@Filip, Could you please provide verification steps?
Verified on Openshift version: 4.7.0-fc.0. Entered the VM import wizard, picked VM from VMware/RHV providers, and then moved to deployment tab (as steps in the bug description). Run those commands, before and after moving to the Deployments tab. $ oc get ovirtproviders.v2v.kubevirt.io $ oc get V2VVMWare.v2v.kubevirt.io Before the move the providers object existed, and right after the move they were no longer listed - As expected.
+1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633