MySQL Bugs: #30154: removing slave information is not picked up properly

Bug #30154	removing slave information is not picked up properly
Submitted:	31 Jul 2007 19:41	Modified:	23 Aug 2007 17:42
Reporter:	Monty Taylor	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor	Severity:	S3 (Non-critical)
Version:	1.2.0.6893	OS:	Any
Assigned to:	Darren Oldag	CPU Architecture:	Any
Tags:	mer 120

Description:
Installed NMAS and it showed that a circular replication existed where one was not intended. Went to the machine that should be the master and removed slave information from it. At this point, NMAS did not re-order the replication info, as it was not able to remove the old information that the master server had a master. Specifically, errors like the follow appeared: 

attrib 'mysql::server->Master_Log_File' is unknown, skipping collection

How to repeat:
Monitor a machine that is a slave. Then remove it's slave info (change master to master_host="", master_log_file="";) 

Suggested fix:

Looks like we are not removing dc_known_items that are no longer supported on re-inventory.

Here's a workaround until this is fixed:

1) Stop the agent that is monitoring the server on which you removed the slave information.

2) Wait for the agent to show as "down" in the Dashboard (its label will turn bold red in the Servers tab).

3) Go to Settings->Manager Servers and delete that server.

4) Generate a new UUID for the agent and place it in the agent's INI file.  See section 3.5.2.2. Generate a New UUID: Windows or section 3.5.2.4. Generate a New UUID: Unix and Mac OS X in the online help for instructions on how to create a new UUID.

5) Start the agent.

r30154 trunk

Verified that a server which becomes a slave or stops being a slave while monitored is reflected correctly in the dashboard with build 1.2.0.7224.