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

[release-5.4] The configmap grafana-dashboard-cluster-logging can not be updated

XMLWordPrintable

    • False
    • False
    • NEW
    • VERIFIED
    • Hide
      Before this update, changes to the metrics dashboards did not deploy because the cluster-logging-operator did not correctly compare existing and desired configmaps containing the dashboard. With this update, the addition of unique hash value to object labels resolves the issue.
      Show
      Before this update, changes to the metrics dashboards did not deploy because the cluster-logging-operator did not correctly compare existing and desired configmaps containing the dashboard. With this update, the addition of unique hash value to object labels resolves the issue.
    • Logging (Core) - Sprint 211, Logging (Core) - Sprint 213

      The configmap/grafana-dashboard-cluster-logging can’t be updated after upgrade from 5.2 to 5.3

       

      Steps to Reproduce:

      1. Deploy cluster-logging 5.2
      2. Save the  cm/grafana-dashboard-cluster-logging
      oc extract cm/grafana-dashboard-cluster-logging -n openshift-config-managed
mv openshift-logging.json to openshift-logging.json-5.2

       

      1. Upgrade logging to 5.3
      2. Wait about several minutes (10 minutes in my testing).  diff the configmaps
      oc extract cm/grafana-dashboard-cluster-logging -n openshift-config-managed
mv openshift-logging.json to openshift-logging.json-5.3
diff openshift-logging.json-5.3 openshift-logging.json-5.1

       

      Expected result:

      The cm/grafana-dashboard-cluster-logging includes  https://github.com/openshift/cluster-logging-operator/pull/1269/files

      Actual result: 

      The cm/grafana-dashboard-cluster-logging wasn’t updated.

       

              jcantril@redhat.com Jeffrey Cantrill
              rhn-support-anli Anping Li
              Anping Li Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: