DVR: cannot manually remove router from l3 agent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Hong Hui Xiao |
Bug Description
This is a regression from this commit [1]. If there are dvr serviceable ports on the node with agent, server now will notify agent with router_updated rather than router_removed, however when updating router, agent will request router_info and that's where server will schedule router back to this l3 agent due to autoscheduling being enabled.
[1] https:/
The potential fix might be not scheduler router when agent request router_info.
Now there are 2 code path that will auto schedule routers to agent.
The first one is get_router_ids, which will bind all un-scheduled
routers to the agent. This will happen at agent startup, revive, and
update.
The second one is sync_routers, which will bind the specified routers
to agent. This will happen when agent requires some router info.
Since 'router_id' was removed in bug 1594711, get_router_ids
will always be called at agent startup, revive, and update, which can
cover all the cases that auto schedule needs. And no need for other
code path.
tags: | added: l3-ipam-dhcp |
description: | updated |
description: | updated |
description: | updated |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
This will likely be fixed by https:/ /review. openstack. org/#/c/ 317949/ which removes autoscheduling from sync_routers rpc handler.
It's unlikely it will be backported so we probably need some other fix for stable/mitaka or revert commit 1f444899ca22584 6ac54ed9e33e112 a30cc8bc0f