Comment 0 for bug 1597461
Revision history for this message
| Ann Taraday (akamyshnikova) wrote L3 HA + DVR: 2 masters after reboot of controller | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
ENV: Mitaka 3 controllers 45 computes DVR + L3 HA
After reboot of controller on which l3 agent is active, another l3 agent becomes active. When rebooted node recover, that l3 agent becomes active as well - this lead to extra loss of external connectivity in tenant network. After some time the only one agent remains to be active - the one from rebooted node. Sometimes connectivity does not come back, as snat port ends up on wrong host.
The root cause of this problem is that routers are processed by l3 agent before openvswitch agent sets up appropriate ha ports, so for some time recovered ha routers is isolated from ha routers on other hosts and becomes active.
The possible solution for this is proper serialization of ha network creation by l3 agent after ha network is set up on controller.
With 100 routers and networks this issues has been reproduced with every reboot.