[L3] snat gateway port may stay 4095 after router fully initialized in l3 agent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Unassigned |
Bug Description
ENV: stable/queens, but master branch has the same code.
There are some extremly conditions which will result the unbound router gateway port. Then all the centrilized floating IPs will not be reachable since the gateway port was set to 4095 tag.
How to reproduce:
just simply creating dvr HA router, set gateway, and add interface.
You can run the following script 100 times to create 100 routers:
for i in {1..100};do script.sh $i;done
Then you may see there are some gatway ports are set to 4095 in the snat node.
Test script:
function create_net_struct()
{
neutron router-create scale-test-
neutron net-create scale-test-net-${1}
neutron subnet-create --name scale-test-
neutron router-gateway-set scale-test-
neutron router-
}
create_net_struct $1
Changed in neutron: | |
assignee: | nobody → LIU Yulong (dragon889) |
Changed in neutron: | |
status: | New → Confirmed |
tags: | added: l3-dvr-backlog |
tags: | added: queens-backport-potential rocky-backport-potential stein-backport-potential |
Changed in neutron: | |
importance: | Undecided → High |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential rocky-backport-potential stein-backport-potential |
Fix proposed to branch: master /review. opendev. org/657207
Review: https:/