Bug 2042268

Summary: After Uninstall CNV operator there are still a lot of the resources in openshift-cnv namespace
Product: Container Native Virtualization (CNV) Reporter: Anna Savina <asavina>
Component: InstallationAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED DUPLICATE QA Contact: Natalie Gavrielov <ngavrilo>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.10.0CC: cnv-qe-bugs, kmajcher, stirabos
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-06 05:58:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
resources after uninstall none

Description Anna Savina 2022-01-19 07:00:41 UTC
Created attachment 1851798 [details]
resources after uninstall

Description of problem:
After Uninstall OpenShift Virtualization operator via UI there are still a lot of the resources in openshift-cnv namespace (pods, services, deployments and etc).

-------------------

Version-Release number of selected component (if applicable):
OCP 4.10 and earlier

-------------------

How reproducible:
100%

-------------------

Steps to Reproduce:
1. Install CNV operator
2. Uninstall CNV operator via UI

-------------------

Actual results:
no resources in openshift-cnv name space

-------------------

Expected results:
a lot of the resources in openshift-cnv namespace (pods, services, deployments and etc)

-------------------

Additional info:

Comment 2 Yaacov Zamir 2022-05-23 09:40:00 UTC
The UI does not handle the cleanup of operators (any operator not specific to CNV),
I do not know what component is responsible for CNV operator cleanup, moving to installer, please move to the correct component if needed.

Comment 3 Simone Tiraboschi 2022-06-06 05:58:58 UTC
This is actually by design: removing an operator from the console is not going to remove the operands.
See bug 2012120 for a different solution.

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