-
Bug
-
Resolution: Done-Errata
-
Normal
-
Logging 5.9.0
-
False
-
None
-
False
-
NEW
-
VERIFIED
-
Before this update, operator not watch for grafana-dashboard-cluster-logging ConfigMap resources so not react on changes on it. With this changes, operator can react to changes/removing in ConfigMap objects, ensuring that the system remains synchronized
-
Bug Fix
-
-
-
Log Collection - Sprint 252, Log Collection - Sprint 253
Description of problem:
The configmap/grafana-dashboard-cluster-logging in openshift-config-managed project is not recreated after upgrading CLO from 5.8 to 5.9.0
Version-Release number of selected component (if applicable):
cluster-logging.v5.9.0
How reproducible:
Always
Steps to Reproduce:
- Deploy logging 5.8, then check dashboards
- Upgrade to logging 5.9
- Check dashboards again
Actual results:
No Logging/Collection dashboard after upgrading CLO from 5.8 to 5.9.0
Expected results:
The Logging/Collection dashboard should be displayed after upgrading from 5.8 to 5.9.0.
Additional info:
No issue when it's a fresh installed logging 5.9.
Workaround: delete pod/cluster-logging-operator-xxxx manually and wait for it to be redeployed, then the cm/grafana-dashboard-cluster-logging can be created.
- links to
-
RHSA-2024:131451
security update Logging for Red Hat OpenShift - 5.9.2
- mentioned on
(17 mentioned on)
