Centralized floating ip Error status
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Brian Haley |
Bug Description
DVR
l3 agent mode on network nodes : dvr_snat
l3 agent mode on compute nodes : dvr_no_external
Reproduction steps:
1.Create a dvr.
2.Create a vm and associate a floating ip.
3.Restart l3 agent on the compute node which hosting the vm or add a new interface to the router.
4.The floating ip status becomes error.
Reason:
When l3 agent gets dvr info from server
1) If the agent mode is "dvr_snat", the value of "host" for the fip will be "FLOATING_
2) If the agent mode is not "dvr_snat", the value of "host" for the fip will be the real host that hosting the vm and there is not "dvr_snat_bound".
Then l3 agents on the compute nodes will get dvr infos including centralized floating ips and try to config them in fip ns. But the agent mode on compute node is "dvr_no_external" and there is no fip ns, so the agent will fail to config the fips.
https:/
tags: | added: l3-dvr |
tags: |
added: l3-dvr-backlog removed: l3-dvr |
Changed in neutron: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
assignee: | nobody → Swaminathan Vasudevan (swaminathan-vasudevan) |
Changed in neutron: | |
assignee: | Swaminathan Vasudevan (swaminathan-vasudevan) → Brian Haley (brian-haley) |
Just to confirm, is this with master branch?