Description of problem: ======================= Currently L3 agent has an explicit call to self.periodic_sync_routers_task() after initialization. Given that periodic job spacing is set to 1 second, this may lead to double syncing with server on initialization (especially if there are a lot of routers scheduled to the agent): - agent starts, fullsync flag is True - periodic_sync_routers_task is called from after_start(), agent requests router info from server, fullsync flag is True - periodic_sync_routers_task is called by periodic task framework, fullsync flag is still True, agent requests router info from server once again. So it's double work on both server and agent sides which might be quite expensive at scale. The proposal is to just use run_immediately parameter. To fix this, we should backport https://bugs.launchpad.net/neutron/+bug/1505282
The code exists within the release. Tested on openstack-neutron-2014.2.3-32.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0130.html