Description of problem: right now it is not possible to create alert notification with sender name "Resource Operations" and set input parameters for selected operation. Version-Release number of selected component (if applicable): JON 3.2.0 How reproducible: always Steps to Reproduce: 1. via REST: create alert notification of type "Resource Operations", pass extraConfig to provide input parameters for operation. 2. open your alert notification in UI Actual results: notification is created, but without input parameters Expected results: notification is created including input parameters Additional info:
in master commit 9916185a5097df1b25f6b246f913ec8301574674 Author: Libor Zoubek <lzoubek> Date: Wed Aug 6 16:36:29 2014 +0200 Bug 1127264 - Creating alert notification of type Resource Operations ignores extraConfig field
branch: release/jon3.3.x link: https://github.com/rhq-project/rhq/commit/0a3d6dc5d time: 2014-08-06 18:25:24 +0200 commit: 0a3d6dc5d2f09595002c43d070da5126dfa40cfc author: Libor Zoubek - lzoubek message: Bug 1127264 - Creating alert notification of type Resource Operations ignores extraConfig field (cherry picked from commit 9916185a5097df1b25f6b246f913ec8301574674) Signed-off-by: Jirka Kremser <jkremser>
Moving to ON_QA as available to test in the following brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=379025
Moving to VERIFIED. I tested adding notification definition to alert defined for servers' EAP resource . The notification should trigger script execution. When inspected via web UI, all parameters were set as required using REST. Command used: curl -u rhqadmin:rhqadmin -X POST -H 'Content-Type:application/json' http://<server_ip>:7080/rest/alert/definition/<alert_def_id>/notifications -d '{"senderName":"Resource Operations","config":{"operation-definition-id":10459},"extraConfig":{"file":"testscript.sh","triggerAvailability":"false","triggerDiscovery":"false","waitTime":12345,"killOnTimeout":"true"}}'