Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-25997

[release-4.14] When a receiver is created for alert notification through web console uses match instead of matchers


    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.15.0
    • 4.13, 4.12
    • Management Console
    • None
    • Low
    • No
    • False
    • Hide



      Description of problem:

      Alert notification receiver created through web console creates receiver with field match which is deprecated instead of matchers and when match is changed to matchers causes Alertmanager pods to crashloopbackoff state throwing the error:
      ts=2023-11-14T08:42:39.694Z caller=coordinator.go:118 level=error component=configuration msg="Loading configuration file failed" file=/etc/alertmanager/config_out/alertmanager.env.yaml err="yaml: unmarshal errors:\n  line 51: cannot unmarshal !!map into []string"

      Version-Release number of selected component (if applicable):


      How reproducible:


      Steps to Reproduce:

      1. Create alert notification receiver through web console.
      Administration-->configuration-->Alertmanager-->create receiver-->add receiver
      2. Check the yaml created which would contain route section with match and not matchers.
      3. correct the match to matchers and not change the matchers defined like severity or alertname correctly  .
      4. Restart the Alertmanager pods which leads to crashloopbackoff state.

      Actual results:

      Alert notification receiver uses match field

      Expected results:

      Alert notification receiver should use matchers filed

      Additional info:


            rhn-engineering-rhamilto Robb Hamilton
            rhn-support-krg Kruthika G
            Yanping Zhang Yanping Zhang
            0 Vote for this issue
            5 Start watching this issue