| 2016-06-30 01:18:19 |
Carl Baldwin |
bug |
|
|
added bug |
| 2016-06-30 01:18:28 |
Carl Baldwin |
neutron: importance |
Undecided |
High |
|
| 2016-06-30 01:18:32 |
Carl Baldwin |
neutron: status |
New |
Confirmed |
|
| 2016-06-30 01:18:43 |
Carl Baldwin |
tags |
|
l3-dvr-backlog l3-ipam-dhcp |
|
| 2016-06-30 01:19:14 |
Carl Baldwin |
description |
At the end of deleting a GW port for a router, l3_dvr_db.py will look for any
more router gw ports on the external network. If there are none, then it calls
delete_floatingip_agent_gateway_port [1]. This should fan out to all l3 agents
on all compute nodes [2]. Each agent should then delete the port [3].
In some cases, the fip namespace and the gateway port are not deleted. I don't
know where things are going wrong. This seems pretty straight-forward. Do
some agents miss the fanout? We know at least some of them are getting the
fanout. So, it is definitely being sent.
When I checked, the port had been deleted from the database. The fact that a
new one is created supports this because if one existed in the DB already then
it would be returned.
[1] https://github.com/openstack/neutron/blob/d3cd20151a67289f023875de682a6d3c4ccee645/neutron/db/l3_dvr_db.py#L179
[2] https://github.com/openstack/neutron/blob/d3cd20151a67289f023875de682a6d3c4ccee645/neutron/api/rpc/agentnotifiers/l3_rpc_agent_api.py#L166
[3] https://github.com/openstack/neutron/blob/d3cd20151a67289f023875de682a6d3c4ccee645/neutron/agent/l3/dvr.py#L73 |
At the end of deleting a GW port for a router, l3_dvr_db.py will look
for any more router gw ports on the external network. If there are
none, then it calls delete_floatingip_agent_gateway_port [1]. This
should fan out to all l3 agents on all compute nodes [2]. Each agent
should then delete the port [3].
In some cases, the fip namespace and the gateway port are not deleted.
I don't know where things are going wrong. This seems pretty
straight-forward. Do some agents miss the fanout? We know at least
some of them are getting the fanout. So, it is definitely being sent.
When I checked, the port had been deleted from the database. The fact
that a new one is created supports this because if one existed in the DB
already then it would be returned.
[1] https://github.com/openstack/neutron/blob/d3cd20151a67289f023875de682a6d3c4ccee645/neutron/db/l3_dvr_db.py#L179
[2] https://github.com/openstack/neutron/blob/d3cd20151a67289f023875de682a6d3c4ccee645/neutron/api/rpc/agentnotifiers/l3_rpc_agent_api.py#L166
[3] https://github.com/openstack/neutron/blob/d3cd20151a67289f023875de682a6d3c4ccee645/neutron/agent/l3/dvr.py#L73 |
|
| 2016-06-30 01:30:26 |
OpenStack Infra |
neutron: status |
Confirmed |
In Progress |
|
| 2016-06-30 01:30:26 |
OpenStack Infra |
neutron: assignee |
|
Carl Baldwin (carl-baldwin) |
|
| 2016-07-05 19:49:40 |
Carl Baldwin |
neutron: milestone |
|
newton-2 |
|
| 2016-07-06 14:56:41 |
OpenStack Infra |
neutron: assignee |
Carl Baldwin (carl-baldwin) |
Brian Haley (brian-haley) |
|
| 2016-07-06 18:06:15 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
| 2016-07-06 18:16:53 |
Carl Baldwin |
tags |
l3-dvr-backlog l3-ipam-dhcp |
l3-dvr-backlog l3-ipam-dhcp mitaka-backport-potential |
|
| 2016-07-09 06:22:43 |
OpenStack Infra |
tags |
l3-dvr-backlog l3-ipam-dhcp mitaka-backport-potential |
in-stable-mitaka l3-dvr-backlog l3-ipam-dhcp mitaka-backport-potential |
|
| 2016-07-25 22:08:30 |
Ihar Hrachyshka |
tags |
in-stable-mitaka l3-dvr-backlog l3-ipam-dhcp mitaka-backport-potential |
in-stable-mitaka l3-dvr-backlog l3-ipam-dhcp mitaka-backport-potential neutron-proactive-backport-potential |
|
| 2016-07-27 18:15:09 |
OpenStack Infra |
tags |
in-stable-mitaka l3-dvr-backlog l3-ipam-dhcp mitaka-backport-potential neutron-proactive-backport-potential |
in-stable-liberty in-stable-mitaka l3-dvr-backlog l3-ipam-dhcp mitaka-backport-potential neutron-proactive-backport-potential |
|
| 2016-10-07 15:44:36 |
Ihar Hrachyshka |
tags |
in-stable-liberty in-stable-mitaka l3-dvr-backlog l3-ipam-dhcp mitaka-backport-potential neutron-proactive-backport-potential |
in-stable-liberty in-stable-mitaka l3-dvr-backlog l3-ipam-dhcp |
|
