Bug 973102
| Summary: | API allows creating alert with condition type with incorrect measurementDefinitionID | ||
|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Libor Zoubek <lzoubek> |
| Component: | REST | Assignee: | Heiko W. Rupp <hrupp> |
| Status: | CLOSED DUPLICATE | QA Contact: | Mike Foley <mfoley> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.8 | CC: | theute |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-02 16:06:19 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** This bug has been marked as a duplicate of bug 973101 *** |
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: