Bug 1035816 - Creating alert definition with dampeningCategory=ONCE produces invalid alert def
Summary: Creating alert definition with dampeningCategory=ONCE produces invalid alert def
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: REST
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR01
: JON 3.2.0
Assignee: Heiko W. Rupp
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-28 14:41 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:
Environment:
Last Closed: 2014-01-02 20:40:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Libor Zoubek 2013-11-28 14:41:26 UTC
Description of problem:

REST API documentation says:

dampeningCategory	String	Category for dampening. ONCE means 'disable definition after firing'

So, to create an alert def, that would disable itself after firing, I send 'dampeningCategory'='ONCE' within it's body

But, it seems that special category name is not handled corretly by rest api, because when I open up such alert definition in UI, I get exeception + once this alert def fires alert it does not disable itsefl.


Version-Release number of selected component (if applicable):
JON 3.2.0.ER7

How reproducible: always


Steps to Reproduce:
1. create alert definition using rest with dampeningCategory=ONCE
2. open such alert def in UI
3. make such definition to fire alert

Actual results:
 2 - Global exception is raised: Invalid dampening category - please report this as a bug: ONCE
 3 - definition does not get disabled



Expected results:

such alert can be opened, and when fired, it gets disabled

Additional info:

Comment 1 Heiko W. Rupp 2013-11-29 10:07:25 UTC
I can not reproduce the issue with the Global Exception (in master), but see that the disabling does not work.

Comment 2 Heiko W. Rupp 2013-11-29 10:52:33 UTC
Now I see it. I consider that sort of a issue in the UI, as ONCE is a valid enum value (as well as the never used NO_DUPLICATES).

Comment 3 Heiko W. Rupp 2013-11-29 11:55:50 UTC
master b9e35b5 & eab765

release-branch: 0bf59fd0bcd (both above commits rebased into this one)

Comment 4 Simeon Pinder 2013-12-03 23:19:46 UTC
Moving to ON_QA for testing in latest(CR1) brew build.


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