AgentNotFoundByTypeHost exception logged when L3-agent starts up
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Stephen Ma | ||
Juno |
Fix Released
|
Undecided
|
Unassigned | ||
Kilo |
New
|
Undecided
|
Unassigned |
Bug Description
On my single-node devstack setup running the latest neutron code, there is one AgentNotFoundBy
Exception found in the L3-agent log:
2015-05-19 11:27:57.490 23948 DEBUG oslo_messaging.
2015-05-19 11:27:57.550 23948 ERROR neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
2015-05-19 11:27:57.550 23948 TRACE neutron.
Changed in neutron: | |
assignee: | nobody → Stephen Ma (stephen-ma) |
assignee: | Stephen Ma (stephen-ma) → nobody |
Changed in neutron: | |
assignee: | nobody → Stephen Ma (stephen-ma) |
Changed in neutron: | |
status: | Confirmed → In Progress |
tags: | added: juno-backport-potential kilo-backport-potential |
Changed in neutron: | |
milestone: | none → liberty-1 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | liberty-1 → 7.0.0 |
That's really interesting.
I guess it might happen when request for routers came in before L3 agent has registered.
It should not cause problems because later it would register and do another attempt.
But still it's interesting how state report could arrive later than the request for routers.