Bug 967488 - Unable to create alert definition with condition based on operation result
Unable to create alert definition with condition based on operation result
Product: RHQ Project
Classification: Other
Component: REST (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: RHQ 4.8
Assigned To: Heiko W. Rupp
Mike Foley
Depends On:
Blocks: 970756
  Show dependency treegraph
Reported: 2013-05-27 05:40 EDT by Libor Zoubek
Modified: 2015-11-01 19:43 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 970756 (view as bug list)
Last Closed: 2013-08-31 06:15:08 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
shot1.png (51.13 KB, image/png)
2013-05-27 05:40 EDT, Libor Zoubek
no flags Details

  None (edit)
Description Libor Zoubek 2013-05-27 05:40:51 EDT
Created attachment 753531 [details]

Description of problem: Creating alert definitions via REST API is very unclear to me. I am trying to POST a definition that would trigger an alert when given operation on given resource fails. I am not able to submit correct body to REST API to create such alert def.

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

How reproducible: always

Steps to Reproduce:

I've been trying to send this body:


Actual results: see shot1.png attachment about how that condition looks in UI

According to shot1.png .. I tried to send this: 

Actual results: 
REST API returns: Can not construct instance of org.rhq.core.domain.alert.AlertConditionOperator from String value 'EQUAL': value not one of declared Enum instance names\n at [Source: org.apache.catalina.connector.CoyoteInputStream@2bd7b0c6; line: 1, column: 68] (through reference chain: org.rhq.enterprise.server.rest.domain.AlertDefinitionRest[\"conditions\"]->org.rhq.enterprise.server.rest.domain.AlertConditionRest[\"name

Additional info:
The key issue is in "name" property of of condition, because it can be an operation name in when "category" equals "CONTROL", for this case we should also check, if operation by given name exists (if not just list all possible operations), same could apply to "option" value which is valid only if it can be parsed to OperationResult enum.
Comment 1 Heiko W. Rupp 2013-06-04 15:13:50 EDT
master e718326

checking for valid operation names still needs to be implemented. I'll clone this BZ for that purpose.
Comment 2 Heiko W. Rupp 2013-08-31 06:15:08 EDT
Bulk close of old bugs in VERIFIED state.

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