l3 agent rescheduling query is not joining tables
Bug #1359460 reported by
Kevin Benton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Kevin Benton |
Bug Description
The code to reschedule the L3 agents cross-references the heartbeat in the agents table but does not join the records between the tables so incorrect results are returned.
Changed in neutron: | |
importance: | Undecided → Medium |
milestone: | none → juno-3 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-3 → 2014.2 |
To post a comment you must log in.
Current code was emitting queries like this.
SELECT routerl3agentbi ndings. id AS routerl3agentbi ndings_ id, routerl3agentbi ndings. router_ id AS routerl3agentbi ndings_ router_ id, routerl3agentbi ndings. l3_agent_ id AS routerl3agentbi ndings_ l3_agent_ id ndings, agents heartbeat_ timestamp < '2014-08-20 23:21:27.289744' AND agents. admin_state_ up;
FROM routerl3agentbi
WHERE agents.