MySQL Bugs: #42923: Replication advisor which is not applicable now but in near future causes error

Bug #42923	Replication advisor which is not applicable now but in near future causes error
Submitted:	17 Feb 2009 9:55	Modified:	9 Jan 2015 10:08
Reporter:	Oli Sennhauser	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S4 (Feature request)
Version:	2.0.4	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	advisor, dashboard, monitor, replication

Description:
Customer tried to enable some rules/advisors on some servers which are not applicable at the moment (replication rules).

Then he got some error messages on these rules and they were not applied.

How to repeat:
Advisors > Add to Schedule > Replication > Slave has been stopped > Schedule > Schedule --> Error message

> Current Schedule --> Rule is not applied

Suggested fix:
If the box is not configured as a slave then the rule should simply be deactivated (as not applicable) rather than not enabled.
The status of a box may change from being a standalone box to being a slave and customer would prefer not to have to change the scheduled rules because of this.

So the rules of this type should effectively say:

If "I am a slave" then run_the_rule_body

This requires less maintenance on all boxes which is better for a large installation.

Also see Bug #43621 (Version Specific Description) for a bit more info, which I will now close as a duplicate of this one.