Tune up report and downtime intervals for l2 agent
If the neutron server erroneously thinks that the l2 agent is down
it will fail to bind a port, which can lead to VM's spawn errors.
However, the issue is only transient because the agent effectively
is only 'late' in reporting back.
Best solution would be an alpha-count algorithm (so that we can detect
persistent failures more reliably), but for now let's be more tolerant
assuming that the agent is down by waiting at least twice the report
interval plus a tiny teeny bit.
(cherry picked from commit 291048aba2fcaec8afee3011fb4c12c6ca0ebbba)
Reviewed: https:/ /review. openstack. org/57478 github. com/openstack/ neutron/ commit/ ea25bc0051621d6 1f321735b5e8c5a 771fe449af
Committed: http://
Submitter: Jenkins
Branch: stable/havana
commit ea25bc0051621d6 1f321735b5e8c5a 771fe449af
Author: armando-migliaccio <email address hidden>
Date: Fri Nov 1 15:47:22 2013 -0700
Tune up report and downtime intervals for l2 agent
If the neutron server erroneously thinks that the l2 agent is down
it will fail to bind a port, which can lead to VM's spawn errors.
However, the issue is only transient because the agent effectively
is only 'late' in reporting back.
Best solution would be an alpha-count algorithm (so that we can detect
persistent failures more reliably), but for now let's be more tolerant
assuming that the agent is down by waiting at least twice the report
interval plus a tiny teeny bit.
(cherry picked from commit 291048aba2fcaec 8afee3011fb4c12 c6ca0ebbba)
Close-bug: #1244255
Change-Id: I544135ce1f6b7e aefb34ac44af8f5 844d92ddd95