Sometimes, the external network connection and floating IP may stop working, but L3 agent has no errors in the logs.
Currently, it's supposed that this is somehow caused by clean-up script that launches or works out in a wrong way, so that it deletes router interfaces that must support a connection to an external network.
There is no stable workaround yet.
A temporary way of getting rid of this bug is the following: to recreate router or reschedule L3 agent.
Meg, this information is for you:
Sometimes, the external network connection and floating IP may stop working, but L3 agent has no errors in the logs.
Currently, it's supposed that this is somehow caused by clean-up script that launches or works out in a wrong way, so that it deletes router interfaces that must support a connection to an external network.
There is no stable workaround yet.
A temporary way of getting rid of this bug is the following: to recreate router or reschedule L3 agent.