Bug 973101 - API allows creating alert with condition type with incorrect measurementDefinitionID
Summary: API allows creating alert with condition type with incorrect measurementDefin...
Alias: None
Product: RHQ Project
Classification: Other
Component: REST
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified vote
Target Milestone: ---
: RHQ 4.9
Assignee: Heiko W. Rupp
QA Contact: Mike Foley
: 973102 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2013-06-11 09:45 UTC by Libor Zoubek
Modified: 2015-11-02 00:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-03-26 08:32:01 UTC

Attachments (Terms of Use)

Description Libor Zoubek 2013-06-11 09:45:20 UTC
Description of problem: 

I did a mistake when writing my tests, and I was sending scheduleId instead of measurementDefinitionId when creating alert with condition where measurementDef is required.

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

How reproducible:

Steps to Reproduce:
1. do POST /rest/alert/definitions?resourceId=10001
with body

{"dampeningCategory": "NONE", "conditions": [{"category": "BASELINE", "threshold": "0.2", "measurementDefinition": <MID>, "option": "max", "comparator": "<"}], "conditionMode": "ALL", "enabled": true, "name": "rest-condition-incorrect-mdef"}

where <MID> is measurementDefinnitionId valid ID, but not related to 10001's resource type (it's measurementDef for different resource type)

Actual results: alert with such condition is created -it's invalid and such alert would never get triggered

Expected results: server must reject condition with such measurementDefId

Additional info:

Comment 1 Heiko W. Rupp 2013-09-02 16:06:19 UTC
*** Bug 973102 has been marked as a duplicate of this bug. ***

Comment 2 Heiko W. Rupp 2013-09-03 10:29:20 UTC
master 399d058

Comment 3 Heiko W. Rupp 2014-03-26 08:32:01 UTC
Bulk closing now that 4.10 is out.

If you think an issue is not resolved, please open a new BZ and link to the existing one.

Note You need to log in before you can comment on or make changes to this bug.