I was was half wrong with the previous statement. When a router instance goes to "active", the keepalived process tries to set the routes in the interface but it cannot, as commented before, because the interface is DOWN an the GW IP is not reachable.
But in [1], when the interface becomes active, the method in charge of the GW port status updates the router namespace router, adding those routes that keepalived couldn't before.
Hello:
I was was half wrong with the previous statement. When a router instance goes to "active", the keepalived process tries to set the routes in the interface but it cannot, as commented before, because the interface is DOWN an the GW IP is not reachable.
But in [1], when the interface becomes active, the method in charge of the GW port status updates the router namespace router, adding those routes that keepalived couldn't before.
This is the logs timeline: http:// paste.openstack .org/show/ 806306/
I think we should close this bug.
Regards.
[1]https:/ /github. com/openstack/ neutron/ blob/0bdf3b56e0 d4ede2d46eed09a 4bb07dd3c00807d /neutron/ agent/l3/ ha_router. py#L556