Created attachment 1830437 [details] Uninstall dialog Description of problem: On OCP 4.9 UI there is a new optional flag (see the attached uninstall dialog) to delete operands as a side effect of uninstalling the operator. If the user tries to do that with existing VMs, our validating webhooks refuses to the delete request for CDI, Kubevirt and then HCO CRs. But the UI ignores the errors and continue deleting other operator CRs, the CSV and the subscription simply reporting the errors at the end to the user suggesting to manually remove the remaining CRs that cannot be removed because the operator supposed to remove the finalizers are not there anymore (see errors screenshot). Version-Release number of selected component (if applicable): 4.9.0 How reproducible: 100% Steps to Reproduce: 1. Deploy CNV 2. Create a VM 3. Unistall CNV from the UI choosing also "delete all operands instances for this operator". Actual results: The product got only partially removed with hard to delete leftovers Expected results: The product is correctly removed Additional info:
see: https://github.com/operator-framework/enhancements/blob/master/enhancements/olm-deletes-operands.md#operand-cleanup-api for a mechanism to avoid getting the CSV (and so the operands) deleted until the CRs are there. Although what we really want is probably a mechanism where OLM tries to delete the operators CRs in dry-run mode first.
Looking at https://github.com/openshift/console/pull/9142 I think that the deletion of operands is completely implemented in the UI regardless of cleanup: enabled: false
Closing as a dup of https://bugzilla.redhat.com/show_bug.cgi?id=2012120 Currently we cannot do that much for this on CNV side. *** This bug has been marked as a duplicate of bug 2012120 ***