Description of problem: Alert operation tokens resource.parentName and target.parentName resolve to the parent resource id value instead of the name. Version-Release number of selected component (if applicable): JBoss ON 3.1.2 How reproducible: very Steps to Reproduce: 1. Import script (below) as a script server resource 2. Set up an alert with an alert notification type of Resource Operation 3. Configure notification to point to the imported script server resource from step 1 4. Configure the arguments of the Execute operation: <%resource.parentName%> <%resource.parentId%> <%targetResource.parentName%> <%targetResource.parentId%> 5. Trigger the alert 6. Verify the output of the script testScript.sh contents: #!/bin/sh echo $# number of arguments > output.txt echo $* >> output.txt echo $@ >> output.txt Actual results: output contains 4 occurrences of the parent resource ids instead of the parent resource names and ids. Expected results: The output should contain both the parent resource names and id values.
I'll see if I can figure this one out...
master commit 962eda4d551d8185bd75291b37e694891eb04435 Author: Jay Shaughnessy <jshaughn> Date: Mon Jan 6 17:32:47 2014 -0500 Fixed what looks like cut+paste issue. release/jon3.2.x commit 389de01b266269d8e81b1a5979ecf3bfb349aadc Author: Jay Shaughnessy <jshaughn> Date: Mon Jan 6 17:32:47 2014 -0500 Cherry Pick of Master 962eda4d551d8185bd75291b37e694891eb04435 release/jon3.1.x commit a8d9a2ac71b57f70236a23cba7b7b0da64e14ec1 Author: Jay Shaughnessy <jshaughn> Date: Mon Jan 6 17:32:47 2014 -0500 Cherry Pick of Master 962eda4d551d8185bd75291b37e694891eb04435
Moving to ON_QA as available for testing in the following brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=336752 Note: the installed version is still JON 3.2.0.GA by design and this represents part of the payload for JON 3.2.1 also known as cumulative patch 1 for 3.2.0.GA. How this will be delivered to customers is still being discussed.
Verified on JON 3.2.1 DR1 (Build Number: c758688:4c03150) tested using server's CPU0 as an alerting resource. The contents of the output.txt file are correct: jbe-jon321-server.bc.jonqe.lab.eng.bos.redhat.com 10001 jbe-jon321-server.bc.jonqe.lab.eng.bos.redhat.com 10001 jbe-jon321-server.bc.jonqe.lab.eng.bos.redhat.com 10001 jbe-jon321-server.bc.jonqe.lab.eng.bos.redhat.com 10001
JON 3.2.1 released week of 5/5/2014