Bug 975526 - Improve validation of alert conditions for different resource types
Improve validation of alert conditions for different resource types
Status: NEW
Product: RHQ Project
Classification: Other
Component: REST (Show other bugs)
4.8
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: Heiko W. Rupp
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-18 13:08 EDT by Libor Zoubek
Modified: 2015-11-01 19:45 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Libor Zoubek 2013-06-18 13:08:18 EDT
Description of problem: Currently, REST api allows to create alert conditions, that are not allowed in UI.


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

How reproducible: always


For example: 
1. You can create a condition of RESOURCE_CONFIG category for resource that does not support configuration
2. You can create a condition of AVAILABILITY with various availability options for platform resource (where some options are not allowed)
3. You can create a condition of DRIFT type for resource without drift support

REST API Should check for these "special" conditions.

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