From ebba9edb26a591c5a76d344e8ca43d1bce774ec8 Mon Sep 17 00:00:00 2001 From: Jacob Baungard Hansen Date: Tue, 25 Nov 2025 13:07:59 +0100 Subject: [PATCH 1/2] ACM-26604 Observability alertmanager secret rename Fixes: https://issues.redhat.com/browse/ACM-26604 Signed-off-by: Jacob Baungard Hansen --- release_notes/known_issues_observability.adoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/release_notes/known_issues_observability.adoc b/release_notes/known_issues_observability.adoc index e120ed61d4..b3e37cd330 100644 --- a/release_notes/known_issues_observability.adoc +++ b/release_notes/known_issues_observability.adoc @@ -7,6 +7,12 @@ For your {ocp} cluster, see link:https://docs.redhat.com/en/documentation/opensh For more about deprecations and removals, see xref:../release_notes/acm_deprecate_remove.adoc#deprecations-removals-acm[Deprecations and removals for {acm-short}]. +[#alertmanager-accessor-change] +== Manually configured alert forwarding not working after updating to {acm-short} 2.15 +In {acm-short} 2.15 the name of the `observability-alertmanager-accessor` secret was changed to include a postfix of the hub cluster name, for example: `observability-alertmanager-accessor-hub1-region1`. On systems where the automatic handling for alert-forwarding config has been disabled with the annotation: `mco-disable-alerting: true` on the `MultiClusterObservability` CR, and alert forwarding has been manually configured to forward alerts to the hub (with a policy, GitOps or by other methods), this config needs updating. + +For platform alerts the `cluster-monitoring-config` configmap in namespace `openshift-monitoring` should be updated and for user-workload alerts the configmap `user-workload-monitoring-config` in namespace: ` openshift-user-workload-monitoring` should be updated. The exact secret name can be found by viewing the secrets in the mentioned namespaces. + [#retention-change] == Retention change causes data loss From 8062d49224f99a0cdc3dacbf0b87ec8f2235447d Mon Sep 17 00:00:00 2001 From: Jacob Baungard Hansen Date: Mon, 1 Dec 2025 10:45:43 +0100 Subject: [PATCH 2/2] Mention both secrets changes Signed-off-by: Jacob Baungard Hansen --- release_notes/known_issues_observability.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/release_notes/known_issues_observability.adoc b/release_notes/known_issues_observability.adoc index b3e37cd330..c8657030ee 100644 --- a/release_notes/known_issues_observability.adoc +++ b/release_notes/known_issues_observability.adoc @@ -9,9 +9,9 @@ For more about deprecations and removals, see xref:../release_notes/acm_deprecat [#alertmanager-accessor-change] == Manually configured alert forwarding not working after updating to {acm-short} 2.15 -In {acm-short} 2.15 the name of the `observability-alertmanager-accessor` secret was changed to include a postfix of the hub cluster name, for example: `observability-alertmanager-accessor-hub1-region1`. On systems where the automatic handling for alert-forwarding config has been disabled with the annotation: `mco-disable-alerting: true` on the `MultiClusterObservability` CR, and alert forwarding has been manually configured to forward alerts to the hub (with a policy, GitOps or by other methods), this config needs updating. +In {acm-short} 2.15 the name of the `observability-alertmanager-accessor`, and `hub-alertmanager-router-ca` secrets were changed to include a postfix of the hub cluster name, for example: `observability-alertmanager-accessor-hub1-region1`. On systems where the automatic handling for alert-forwarding config has been disabled with the annotation: `mco-disable-alerting: true` on the `MultiClusterObservability` CR, and alert forwarding has been manually configured to forward alerts to the hub (with a policy, GitOps or by other methods), this config needs updating. -For platform alerts the `cluster-monitoring-config` configmap in namespace `openshift-monitoring` should be updated and for user-workload alerts the configmap `user-workload-monitoring-config` in namespace: ` openshift-user-workload-monitoring` should be updated. The exact secret name can be found by viewing the secrets in the mentioned namespaces. +For platform alerts the `cluster-monitoring-config` configmap in namespace `openshift-monitoring` should be updated and for user-workload alerts the configmap `user-workload-monitoring-config` in namespace: ` openshift-user-workload-monitoring` should be updated. The exact secret names can be found by viewing the secrets in the mentioned namespaces. [#retention-change] == Retention change causes data loss