-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
ACM 2.11.8
-
None
-
Moderate
-
None
Description of problem:
observability configuration changes are not applied for days - or until a redeployment is done
Version-Release number of selected component (if applicable):
2.11.8
How reproducible:
customer environment
Steps to Reproduce:
- enable observability
- configure an interval of 60s
- deploy clusters
- configure an interval of 300s
Actual results:
the interval of 60s remains applied for a long period of time
Expected results:
the interval of 300s is applied after the configuration change is pulled
Additional info:
changes on hub done :
$ oc get ObservabilityAddon -n samplecluster -o yaml
apiVersion: v1
items:
- apiVersion: observability.open-cluster-management.io/v1beta1
kind: ObservabilityAddon
metadata:
creationTimestamp: "2024-10-02T13:02:39Z"
finalizers:
- observability.open-cluster-management.io/addon-cleanup
generation: 1
labels:
owner: multicluster-observability-operator
velero.io/backup-name: acm-resources-schedule-20251211131950
velero.io/restore-name: restore-acm-full-202511121408-acm-resources-schedule-2025f0beaf
name: observability-addon
namespace: acm-c-ort1-str
resourceVersion: "1642933258"
uid: 5dac06c6-c8a1-4ec2-82e0-ae1e77a6a14a
spec:
enableMetrics: false
interval: 300
on spoke cluster we see on the observability-addon
spec:
enableMetrics: true
interval: 60
resources:
requests:
cpu: 200m
memory: 8Gi
it takes an unknown amount of time for it to be applied - suspected days.
