Comment 4 for bug 1930096
Revision history for this message
| Rodolfo Alonso (rodolfo-alonso-hernandez) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hello:
When the router instance has the GW port down, no route related to this port is written in the routing table of the namespace. This is not a problem while the router is in "backup" mode. The problem is when the router becomes "active" and keepalived tries to write the routes.
(I'm deploying an environment to check the following statement) -->
Since [1], we set the GW port to DOWN when the router instance is "backup" and set it to UP when "active". The problem is that we raise the port when keepalived has declared this router instance as "active". That is too late and keepalived was not able to set those routes: http://
Once we set the GW port to UP, we should also force keepalived to refresh the config (send a SIGHUP signal to the running process).
I'll update the bug once I've confirmed that.
Regards.
[1]https:/