-
Bug
-
Resolution: Done
-
Major
-
ACM 2.11.Z
-
1
-
False
-
None
-
False
-
-
-
Observability Sprint 32, Observability Sprint 33, Observability Sprint 34, Observability Sprint 35
-
None
Description of problem:
As per https://prometheus.io/docs/alerting/latest/alertmanager/#high-availability, when configuring Alertmanager HA, the Prometheus should send requests to all alertmanagers.
RHACM run 3 alertmanagers in clustered mode in the Hub cluster. However we send alerts over a single Route from the managed clusters configuration which means we might run into the problems described in https://groups.google.com/g/prometheus-users/c/ul3tFfPxkC0
Discussed in https://redhat-internal.slack.com/archives/CUU609ZQC/p1723548761663429
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
- ...
Actual results:
Expected results:
Additional info:
- clones
-
ACM-13481 ACM 2.13 - Alertmanager is stuck in HA mode even if there is only one replica
-
- Closed
-
- is related to
-
ACM-14934 Support Alertmanager fanout notifications in Hub Alertmanager
-
- New
-
- links to
-
RHSA-2024:143822 Red Hat Advanced Cluster Management 2.12.2 bug fixes and container updates
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Important: Red Hat Advanced Cluster Management 2.12.2 security and bug fix updates), and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2025:0851