Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-7972

Querying the ReST API for alarms using an invalid alarmId returns HTTP 200

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Meridian-2015.1.0, 16.0.3, 17.0.0
    • Fix Version/s: 17.0.0
    • Component/s: REST
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None

      Description

      When querying a ReST API for an element that doesn't exist, the answer should be either an HTTP 204 (No Content) or an HTTP 404 (Not Found).

      Unfortunately, this is not the case for the Alarms end point. It returns an HTTP 200 with no content.

      In order to reproduce the problem, do the following:

      • Install OpenNMS
      • Add a test node
      • Generate a fake node down event using send-event.pl
      • Query the alarms ReST end point to verify that there is one alarm for the node down.
      • Query the alarms ReST end point for a specific alarm using a number you know it doesn't exist on the alarms table

      I verified this behavior with Meridian 2015.1.0 and latest build of 17.0.0-SNAPSHOT.

        Attachments

          Activity

            People

            • Assignee:
              agalue Alejandro Galue
              Reporter:
              agalue Alejandro Galue
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: