Red Hat Bugzilla – Bug 967742
Unable to create alert definition with Drift condition type
Last modified: 2015-11-01 19:43:20 EST
Description of problem: I a not able to create alert condition of 'Drift' type. Issue is very similar to Bug 967488 Version-Release number of selected component (if applicable): 4.8-master How reproducible: always Steps to Reproduce: do POST /alert/definition/?resourceId=xxx with t{"dampeningCategory": "NONE", "conditions": [{"category": "DRIFT", "name": "drift.*", "option": ".*"}], "conditionMode": "ALL", "enabled": true, "name": "rest-condition-drift-detection"}his body Actual results: Can not construct instance of org.rhq.core.domain.alert.AlertConditionOperator from String value 'drift.*': value not one of declared Enum instance names\n at [Source: org.apache.catalina.connector.CoyoteInputStream@46cb0d63; line: 1, column: 66] (through reference chain: org.rhq.enterprise.server.rest.domain.AlertDefinitionRest[\"conditions\"]->org.rhq.enterprise.server.rest.domain.AlertConditionRest[\"name\"] Expected results: alert definition is created. When creating a definition of type "DRIFT", "name" should be interpreted as "drift definition name" regular expression, do match drift definition, and "option" is a regular expression to match pathname. Additional info:
master e718326
Bulk closing of old issues now that HRQ 4.9 is in front of the door. If you think the issue has not been solved, then please open a new bug and mention this one in the description.