Comment 2 for bug 1177973

We encounter the same problem with the Grizzly release and OVS plugin.
I set up a node which handle l2 agent, l3 agent and DHCP agent.
I doesn't modify intervals 'agent_down_time' (5sec) and 'report_interval' (4sec).

When the l2 agent has about 25 interfaces to handle, the pooling-base check take more time than the interval 'report_interval':

2013-06-03 15:44:21 WARNING [quantum.openstack.common.loopingcall] task run outlasted interval by 0.80157 sec

And the Quantum server think that the agent is down because the report state takes more than interval 'agent_down_time'.

It's possible to change the intervals value to correct the problem but when the number of interfaces increases these intervals time have a chance to be reach.