L3 agent: at some point an agent becomes unable to handle new routers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Oleg Bondarev |
Bug Description
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_
Changed in neutron: | |
importance: | Undecided → High |
description: | updated |
tags: | added: mitaka-backport-potential |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: mitaka-backport-potential neutron-proactive-backport-potential |
Fix proposed to branch: master /review. openstack. org/301685
Review: https:/