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

Dev console > Observe > Alerts page: Reenabling notifications for one alert also reenables the notifications for other alerts

XMLWordPrintable

    • Important
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      In the developer console, reenabling notifications for one alert also reenables the notifications for other alerts. In other words, trying to expire one silence actually expires other silences too.

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

      4.15, 4.14, 4.13, possibly earlier, but not tested yet

      How reproducible:

      Always

      Steps to Reproduce:

      1. Navigate to Dev console > Observe > Alerts page
      2. Disable notifications for 2 different alerts
      3. Reenable notifications for 1 alert
      4. If testing with 4.13 or earlier you will probably need to refresh the page
      

      Actual results:

      Both of the alerts now have notifications enabled

      Expected results:

      Only the one alert that you reenabled notifications for should have changed. The other alert should still have notifications disabled.

      Additional info:

      Disabling / reenabling notifications is actually creating / expiring Alertmanager silences, so what is happening is that when notifications are reenabled for one alert, both of the silences are being expired. Only the one silence for that alert should be expired.

              jakumar jaivardhan Kumar
              anpicker@redhat.com Andrew Pickering
              Sanket Pathak Sanket Pathak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: