From what I've read on the HA VIP with mysql, I would expect that the HA VIP would be assigned to one of the machines in the cluster at all times and would fail over to another machine should the first one become unresponsive. I'm just double checking that this is the expected behavior.
Once this HA VIP issue gets resolved, I'll close this bug out as a DUP of bug #1416928. We aren't able to backport that fix to 1.20, but there is a workaround of manually modifying the agent.conf file should you run into this again.
From what I've read on the HA VIP with mysql, I would expect that the HA VIP would be assigned to one of the machines in the cluster at all times and would fail over to another machine should the first one become unresponsive. I'm just double checking that this is the expected behavior.
Once this HA VIP issue gets resolved, I'll close this bug out as a DUP of bug #1416928. We aren't able to backport that fix to 1.20, but there is a workaround of manually modifying the agent.conf file should you run into this again.