[Backport 1566291] L3 agent: at some point an agent becomes unable to handle new routers
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Mirantis OpenStack | Status tracked in 10.0.x | |||||
10.0.x |
Invalid
|
High
|
Oleg Bondarev |
Bug Description
Upstream: https:/
Following seen in l3 agent logs:
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
2016-04-05 09:30:09.033 24216 ERROR neutron.
So agent is constantly resyncing (causing load on neutron server) and unable to handle new routers.
I believe that set "ADDRESS_
tags: | added: wait-for-stable |
Changed in mos: | |
status: | Confirmed → In Progress |
Changed in mos: | |
status: | In Progress → Fix Committed |
tags: | added: on-verification |
(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:
actual result
version
expected result
steps to reproduce
For more detailed information on the contents of each of the listed sections see https:/ /wiki.openstack .org/wiki/ Fuel/How_ to_contribute# Here_is_ how_you_ file_a_ bug