Description of problem: When I upgraded from 2.3.1 to 2.4.0, I have a few alert definitions with SNMP trap notifications. It appears that the OID fields of the SNMP traps are getting dropped/lost during the database upgrade. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
From joseph: 'this I think can be fixed by changing line 76 of the rhq-serverplugin.xml file to "oid" instead of "OID". the data should have been properly translated during db-upgrade, but the metadata in the server-side plugin is accessing the wrong property due to case-sensitivity' John can you try this fix out and if it works, joseph can push the change to release branch.
Tested the change as per Joseph's suggestion locally, and it looked good. I pushed the commit to the release branch. commit hash: c3b143eec4f67612e868a947f370f1dd7bfc7dee I will verify when hudson has a build ready.
The above change is *not* enough, as the alert sender depends on the name of the property too. Fix is in 0bfff55
QA Verified -- the values for alerts now persist across an upgrade. As noted by others earlier, they do /not/ persist from the JON system settings (<2.4) to the JON plugin config (2.4+) level. As long as we have a docs bug for that, I think we're good to go here.
Mass-closure of verified bugs against JON.