Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1793893

Summary: [RFE][usability]It was not clear when uninstalling an operator that works for all namespaces
Product: OpenShift Container Platform Reporter: Fan Jia <jfan>
Component: Management ConsoleAssignee: Jakub Hadvig <jhadvig>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: low    
Version: 4.3.0CC: aos-bugs, hasha, jhadvig, jokerman
Target Milestone: ---Keywords: UsabilityStudyPriority
Target Release: 4.4.0   
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: 2020-05-04 11:25:48 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:

Description Fan Jia 2020-01-22 08:29:05 UTC
Description of problem:
It was not clear when uninstalling an operator that works for all namespaces, whether it was uninstalled for a particular namespace or all namespaces.
1.One user questioned if he could uninstall an operator from a specific namespace without impacting other namespaces.
2.User will receive the message: “This will remove the operator from openshift-operators. “ but it was not clear this means all namespaces.

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2020-01-21-205041

Comment 2 shahan 2020-02-10 11:46:21 UTC
When uninstall all-namespaced install mode operators, the console will say:
Uninstall Anchore Engine Operator?

This will remove the operator from all namespaces. Your application will keep running, but it will no longer receive updates or configuration changes.
4.4.0-0.nightly-2020-02-09-220310

Comment 4 errata-xmlrpc 2020-05-04 11:25:48 UTC
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, 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/RHBA-2020:0581