I just ran into the exact same problem. The bas thing about this bug is that mmm_control show thinks everything is peachy, while in reality your cluster is unreachable!
Besides adding that check after the call to add_ip, I think a checker should also be written to ping/mysql connect on the virtual ip. When that fails, there doesn't necessarily have to be anything wrong with the underlying machines, so other checks might not catch that.
Google code bug 48 is a direct result of this bug: code.google. com/p/mysql- master- master/ issues/ detail? id=48
http://
I just ran into the exact same problem. The bas thing about this bug is that mmm_control show thinks everything is peachy, while in reality your cluster is unreachable!
Besides adding that check after the call to add_ip, I think a checker should also be written to ping/mysql connect on the virtual ip. When that fails, there doesn't necessarily have to be anything wrong with the underlying machines, so other checks might not catch that.