Comment 10 for bug 1648242
Revision history for this message
| James Denton (james-denton) wrote Re: Failure to retry update_ha_routers_states | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
@Brian - This is an OSA/RPC build with RabbitMQ clustering across 3 infra nodes. In this test we simply wanted to kill the server where the router was 'master' and observe the behavior. As you pointed out, VRRP under the hood was operating correctly - one of the two remaining nodes took over as master and the user did not sustain a long period of downtime. However, there was no clear indication from the API which infra node had taken over, and there was no way to update that state without either restarting the L3 agent(s) or causing a transition through manual means.