-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
OpenShift 4.17 Release Notes
-
False
-
-
False
-
-
Below logs seen is alertmanager pods
ts=2026-01-08T13:03:19.023Z caller=parse.go:176 level=warn msg="Alertmanager is moving to a new parser for labels and matchers, and this input is incompatible. Alertmanager has instead parsed the input using the classic matchers parser as a fallback. To make this input compatible with the UTF-8 matchers parser please make sure all regular expressions and values are double-quoted. If you are still seeing this message please open an issue." input="alertname = Optimize - Route existiert nicht" origin=config err="21:22: unexpected -: expected a comma or close brace" suggestion="alertname=\"Optimize - Route existiert nicht\"" ts=2026-01-08T13:03:19.023Z caller=parse.go:176 level=warn msg="Alertmanager is moving to a new parser for labels and matchers, and this input is incompatible. Alertmanager has instead parsed the input using the classic matchers parser as a fallback. To make this input compatible with the UTF-8 matchers parser please make sure all regular expressions and values are double-quoted. If you are still seeing this message please open an issue." input="alertname = Optimize - Service existiert" origin=config err="21:22: unexpected -: expected a comma or close brace" suggestion="alertname=\"Optimize - Service existiert\""
No note about this is mentioned In OCP docs when Alertmanager was upgraded to 0.27 version
Upstream captures this NOTE:
https://prometheus.io/docs/alerting/0.27/configuration/#label-matchers
"Alertmanager versions 0.27 and later have a new parser for matchers that has a number of backwards incompatible changes."
and
"Alertmanager will make UTF-8 strict mode the default in the next two versions, so it's important to transition as soon as possible."
As there is NO note Customers are not able to understand why these logs are comming