Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-4165

After upgrade logging to 5.7.2, the clusterlogging CR can't be removed if use lokistack as the default log store.

XMLWordPrintable

    • 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:

      1. deploy logging 5.6 or 5.7.1, and use lokistack as the default log store
      2. upgrade logging to 5.7.2, and wait for all the logging components to be upgraded
      3. try to remove clusterlogging CR
      4. 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. 

              Unassigned Unassigned
              qitang@redhat.com Qiaoling Tang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: