MySQL Bugs: #79875: one random server missing from group while assigning assets in event handler

Bug #79875	one random server missing from group while assigning assets in event handler
Submitted:	8 Jan 2016 2:05	Modified:	19 Feb 2016 12:50
Reporter:	Jesse Duce	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Enterprise Monitor	Severity:	S3 (Non-critical)
Version:	3.1.1.7806	OS:	CentOS
Assigned to:		CPU Architecture:	Any

Description:
When I try to create an event handler, then choose assets, one server from each replication group is randomly missing.

I had this problem in 3.0 as well and decided I would try a fresh install to get rid of it.

This happens with two different groups of servers. A test environment as well as a production environment.

I have 4 servers in each group.

Each group is set up for circular replication.

Each server has its own unique UUID.

Each server has its own unique server-id.

To try to get around this issue, I made two new groups, each with the server missing from the one of the replication groups.

I returned to create event handler, where one of the servers is now in both groups while the other server does not display at all.

I then created a group for each server and the same thing happens. One server group will display the wrong server.

How to repeat:
I'm assuming this can be achieved by setting up a circular replication environment with potentially 4 or more servers. Could be 3, could be 2, but I have successfully screwed it up twice with 4 servers on two installations of mysql enterprise monitor.

I set up to groups of 4 circular MySQL servers and can't see the same problem with 3.0. I am using the built-in agent to monitor all the severs. What do you see in the other asset list on the left of Events page, is the list similar there missing some servers?

I suspect some other MEM uuid's are the same, other than the ones you mention, connect with the mysql client and check that all of your 'SELECT * FROM mysql.inventory;" values unique?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".