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: | |
| Category: | MySQL Enterprise Monitor: Server | Severity: | S3 (Non-critical) |
| Version: | 2.1.0.1080 | OS: | Any |
| Assigned to: | Josh Sled | CPU Architecture: | Any |
[28 Jul 2009 23:58]
Bill Weber
[29 Jul 2009 22:45]
Enterprise Tools JIRA Robot
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
[30 Jul 2009 16:52]
Enterprise Tools JIRA Robot
Keith Russell writes: Patch installed in versions => 2.1.0.1082.
[5 Aug 2009 1:14]
Enterprise Tools JIRA Robot
Bill Weber writes: verified fixed in build 2.1.0.1085
[7 Aug 2009 12:27]
Tony Bedford
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.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.