Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): JON 3.2.ER7 How reproducible: always Steps to Reproduce: 1. create syntetic platform via rest 2. choose a trait (ie. Trait.osname) 3. create alert def with traitValueChange condition type 4. push trait using rest api so condition for your alert is met Actual results: alert does not get fired Expected results: alert gets fired Additional info: I'll provide automated test once I push it to github
You can run test to detect/verify this bug: go through https://github.com/RedHatQE/jon-tests/blob/master/alerts/README.md git clone https://github.com/RedHatQE/jon-tests.git cd jon-tests nosetests -a "single,trait"
*** Bug 1041079 has been marked as a duplicate of this bug. ***
*** Bug 1058658 has been marked as a duplicate of this bug. ***
Moving this to post-GA. While the impl for this is mostly ready (https://github.com/rhq-project/rhq/pull/51), there are still some TODOs mentioned but more importantly, the fix introduces a whole new type of resources (synthetic) and quite big changes across the codebase to correctly support these. I find this too risky to include in JON 3.3 without prior bake time in RHQ.
As per Libor, the fix for this will require schema changes and therefore can not go into an update. Setting target for consideration in a future minor/major release.
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121. This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.