-
Bug
-
Resolution: Done-Errata
-
Major
-
4.12.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
No
-
None
-
None
-
MON Sprint 259, MON Sprint 260
-
2
-
Done
-
Bug Fix
-
-
None
-
None
-
None
-
None
User Workload Monitoring Alertmanager configuration can get screwed by not correctly sanitized CR content
Customer recently encountered that malformed CR content will prevent User Workload Monitoring Alertmanager configuration.
routes: - receiver: "XXXX" # optional route matchers: - severity: "!~'^critical$'"
will be added as CR but rejected by Alertmanager due to quoting issue.
err="invalid label name \"\""
Even though we should have some sanitizing implemented, it seems we missed that corner case.
- is related to
-
OBSDOCS-1327 Improve "troubleshooting monitoring issues: new section troubleshooting alertmanager configurations
-
- Closed
-
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update
(1 links to)