DVR lost centralized floating ip when the ha state switched.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
sunzuohua |
Bug Description
Reproduction steps:
The l3 agent mode is as follows:
Network:
Compute:
1、Create a DVR(HA). Then add interface and gateway to the DVR.
2、Create a vm and associate a floating ip to the vm.
3、Check the keepalived.conf and snat ns on the master and backup network nodes for the DVR.
4、The floating ip can be found in the keepalived.conf on the master network node but not in the keepalived.conf on the backup network node for the DVR .On the master network node for the DVR , the floating ip is found normal in the snat ns.
5.Swith the ha state of the DVR, Check the keepalived.conf and snat ns on the current master network node for the DVR.
6.The floating ip still can not be found in the keepalived.conf on the current master network node. And on the current master network node for the DVR , the floating ip is not found in the snat ns.
Mybe the check for the router ha state[1] should be moved just before [2].
[1]https:/
[2]https:/
tags: | added: l3-dvr-backlog |
Changed in neutron: | |
assignee: | sunzuohua (zuohuasun) → Swaminathan Vasudevan (swaminathan-vasudevan) |
Changed in neutron: | |
assignee: | Swaminathan Vasudevan (swaminathan-vasudevan) → sunzuohua (zuohuasun) |
tags: | added: neutron-proactive-backport-potential |
So when the check for the router ha state[1] moved to [2] is that working as designed? Meanwhile I will take a look at it.