Description of problem: If a user attaches an SNMP Alert Sender Plugin to an alert (or configures the plugin), they can set the OID of the traps sent by it to a string, like 'bork'. Since SNMP OIDs are integers, this field should be checked to ensure that only integers can be entered. Version-Release number of selected component (if applicable): RHQ, 12/16 git pull from alertPlugin branch How reproducible: Always Steps to Reproduce: 1. Attempt to set the OID for traps sent by the SNMP Alert Sender Plugin to a string, like 'bork', either on the plugin configuration page or while attaching it to an alert Actual results: Input accepted and SNMP traps for alert will fail to send Expected results: Input rejected with error message Additional info:
mass move to rhq_chainsaw tracker bug
This bug has now been triaged by Chainsaw on 2/18. The expectation is the bug to be addressed by the end of sprint06 roughly 3/10/10.
What is the exact format? Is it X.X.X or are dashes allowed?
Oids follow the x.y.z.a.b.c format with variable length. All of a,b,c,d need to be numeric in our implementation, but can in theory be strings like sys.system.interfaces.eth.packets.sent. So bork would be a valid oid if someone would define a mib accordingly.
So, this is a works as designed?
Sort of - as long as we have no real OID/MIB parser (hooked into the UI classes). One could add some basic oid validation (e.g at least one dot, no two dots adjacent) to the general UI config elements in having this as an additional input type to the configuration schema.
Given that customers can use custom MIBs which do not follow any given pattern, we will keep this as is.