MySQL Bugs: #46442: Error msg when scheduling a rule shows rule resource key instead of name

Bug #46442	Error msg when scheduling a rule shows rule resource key instead of name
Submitted:	28 Jul 2009 23:58	Modified:	7 Aug 2009 12:27
Reporter:	Bill Weber	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S3 (Non-critical)
Version:	2.1.0.1080	OS:	Any
Assigned to:	Josh Sled	CPU Architecture:	Any

Description:
The error message shown in the orange dialog when a rule is unable to be scheduled shows the rule's resource key instead of the name.

How to repeat:
- start an agent which is monitoring the MEM repository
- schedule the Administration rule "Binary Logging is Limited"
- after clicking "schedule" button, get following error in orange dlg:
U0146 Unable to schedule rule "binary_logging_is_limited.name" due to "mysql.MasterStatus.Binlog_Ignore_DB" data not being collected from server "net-dev2:13306". It may be an unsupported collection for that server.

Josh Sled writes: 
revno: 7426
revision-id: jsled@asynchronous.org-20090729221734-0z6tbjzss97hqg0y
parent: aggie@sun.com-20090729220509-16pfi3xopxs0ee4o
committer: Josh Sled <jsled@asynchronous.org>
branch nick: local
timestamp: Wed 2009-07-29 18:17:34 -0400
message:
  EM-3492, Bug#46442: translate the rule name for message construction

Keith Russell writes: 
Patch installed in versions => 2.1.0.1082.

Bill Weber writes: 
verified fixed in build 2.1.0.1085

An entry was added to the 2.1.0 changelog:

The error message shown in the orange dialog when a Rule could not be scheduled showed the Rule's resource key instead of its name. For example:

U0146 Unable to schedule rule "binary_logging_is_limited.name" due to
"mysql.MasterStatus.Binlog_Ignore_DB" data not being collected from server
"net-dev2:13306". It may be an unsupported collection for that server.