-
Bug
-
Resolution: Won't Do
-
Normal
-
Logging 5.7.2
-
False
-
None
-
False
-
NEW
-
NEW
-
Bug Fix
-
-
-
Moderate
Description of problem:
After upgrade logging to 5.7.2, when removing clusterlogging CR, the CLO keeps reporting below error:
{"_ts":"2023-05-29T05:34:31.849582652Z","_level":"0","_component":"cluster-logging-operator","_message":"Error removing RBAC for accessing LokiStack.","_error":{"msg":"clusterrolebindings.rbac.authorization.k8s.io \"logging-all-authenticated-application-logs-reader\" not found"}}
The clusterlogging CR can't be removed, and below is the finalizers in the clusterlogging CR:
finalizers: - logging.openshift.io/lokistack-rbac
Version-Release number of selected component (if applicable):
cluster-logging.v5.7.2
loki-operator.v5.7.2
How reproducible:
Always
Steps to Reproduce:
- deploy logging 5.6 or 5.7.1, and use lokistack as the default log store
- upgrade logging to 5.7.2, and wait for all the logging components to be upgraded
- try to remove clusterlogging CR
- check pod status
Actual results:
Clusterlogging CR can't be removed.
Expected results:
Clusterlogging CR should be removed.
Additional info:
No issue when testing upgrade from 5.6 to 5.7.1, and no issue when it's a fresh installed logging 5.7.2.
Workaround: remove the finalizers from the clusterlogging CR.