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

Configmap/grafana-dashboard-cluster-logging is not removed after removing CLO.

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • NEW
    • This is a known issue whereupon uninstalling the operator, the dashboard configmap in the `openshift-config-managed` namespace will be orphaned. The current workaround is to manually delete the configmap.
    • Known Issue
    • Log Collection - Sprint 241

      Description of problem:

      After removing cluster-logging-operator, the configmap/grafana-dashboard-cluster-logging is not removed.

      $ oc get sub -A
      No resources found
      $ oc get csv 
      No resources found in openshift-logging namespace.
      $ oc get cm -n openshift-config-managed grafana-dashboard-cluster-logging 
      NAME                                DATA   AGE
      grafana-dashboard-cluster-logging   1      32m 

      No ownerReferences in cm/grafana-dashboard-cluster-logging:

      $ oc get cm -n openshift-config-managed grafana-dashboard-cluster-logging -ojsonpath={.metadata} |jq
      {
        "creationTimestamp": "2023-08-23T06:20:47Z",
        "labels": {
          "console.openshift.io/dashboard": "true",
          "contentHash": "4ff03ba56b95547ab80032f6370bf47e",
          "pod-security.kubernetes.io/enforce": "privileged",
          "security.openshift.io/scc.podSecurityLabelSync": "false"
        },
        "managedFields": [
          {
            "apiVersion": "v1",
            "fieldsType": "FieldsV1",
            "fieldsV1": {
              "f:data": {
                ".": {},
                "f:openshift-logging.json": {}
              },
              "f:metadata": {
                "f:labels": {
                  ".": {},
                  "f:console.openshift.io/dashboard": {},
                  "f:contentHash": {},
                  "f:pod-security.kubernetes.io/enforce": {},
                  "f:security.openshift.io/scc.podSecurityLabelSync": {}
                }
              }
            },
            "manager": "cluster-logging-operator",
            "operation": "Update",
            "time": "2023-08-23T06:20:47Z"
          }
        ],
        "name": "grafana-dashboard-cluster-logging",
        "namespace": "openshift-config-managed",
        "resourceVersion": "206230",
        "uid": "35931335-6ca7-4a79-bb56-35f05a8989c1"
      }

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

      openshift-logging/cluster-logging-rhel9-operator/images/v5.8.0-119

      How reproducible:

      Always

      Steps to Reproduce:

      1. Deploy CLO, check configmaps in openshift-config-managed project, ensure cm/grafana-dashboard-cluster-logging is created
      2. Uninstall CLO, then check configmaps in openshift-config-managed project again

      Actual results:

      The cm/grafana-dashboard-cluster-logging is not removed after uninstalling CLO

      Expected results:

      The cm/grafana-dashboard-cluster-logging should be removed after uninstalling CLO

      Additional info:

      The prometheusrule/collector can be removed along with CLO, below ownerReferences are added to it:

      $ oc get prometheusrule  collector -ojsonpath={.metadata.ownerReferences} |jq
      [
        {
          "apiVersion": "operators.coreos.com/v1alpha1",
          "blockOwnerDeletion": false,
          "controller": false,
          "kind": "ClusterServiceVersion",
          "name": "cluster-logging.v5.8.0",
          "uid": "0d7ec4d9-66b3-493d-a25a-5f4d4f1858f9"
        }
      ] 

            rh-ee-calee Calvin Lee
            qitang@redhat.com Qiaoling Tang
            Qiaoling Tang Qiaoling Tang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: