Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Normal
Fix Version/s: None
Affects Version/s: 4.13, 4.12
Component/s: Management Console
Labels:
None

Regression:
None
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
Previously, if a user with regular account privileges attempted to issue the `oc delete csv` command when uninstalling the Operator, the Operator's subscription becomes stuck. After this action, an administrator cannot reinstall the uninstalled Operator, because a conflict exists with the stuck subscription. With this update, a detailed error message displays when an administrator attempts to reinstall the uninstalled Operator. (link:https://issues.redhat.com/browse/OCPBUGS-3822[*~~OCPBUGS-3822~~])

Show
Previously, if a user with regular account privileges attempted to issue the `oc delete csv` command when uninstalling the Operator, the Operator's subscription becomes stuck. After this action, an administrator cannot reinstall the uninstalled Operator, because a conflict exists with the stuck subscription. With this update, a detailed error message displays when an administrator attempts to reinstall the uninstalled Operator. (link: https://issues.redhat.com/browse/OCPBUGS-3822 [* OCPBUGS-3822 ])
Release Note Type:
Bug Fix
Release Note Status:
Done
Target Version:

4.13.0

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Description of problem:

Cluster-admin cannot know whether operator is fully deleted or not after normal user trigger "Delete CSV".
For an operator that is installed in one particular namespace:
After normal user triggers "Delete CSV", the operator will be removed from the list on the "Installed Operator" for the cluster-admin. Therefore, when cluster-admin would like to re-install the operator to the same namespace again, there will be an error shown on the page.

As normal user do not have suffiecient permission to delete an operator
This behavior will bring confusion to cluster-admin in console

Attached video for more details

Version-Release number of selected component (if applicable):

4.12.0-0.nightly-2022-11-16-003434

How reproducible:

Always

Steps to Reproduce:

1. Login OCP as a normal user, and create a project like "testnormal"
2. Login OCP as Administrator again, Install the operator like "Business Automation" into the project of "testnormal"
3. Login OCP as normal user again, and remove the operator by using option "Delete ClusterServiceVersion", check the option of  "Delete dependent objects of this resource"
4. Login OCP as Administrator again, use command "oc get csv -n testnormal“ to double check the csv has been removed
5. check if admin is able to re-install the operator to the project of "testnormal"

Actual results:

For cluster-admin:
1. The operator will not be found on the Installed Operators list anymore
2. Re-install the operator to the same namespace would be forbidden

Expected results:

For cluster-admin: 
If the operator is not fully deleted, better that does not to remove them from the Installed Operators list,
Or Have a notification to let cluster-admin know (why) the operator was not fully deleted, and what cluster-admin needs to do via Command-Line if they still wants to install the operator in the same namespace 
Or better have an entrance to let cluster-admin completely delete the operator via console

Additional info: