NAT rule on l3-agent will not be deleted after deletion
Bug #1200749 reported by
Nachi Ueno
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
Medium
|
Nachi Ueno | ||
Bug Description
Even if after I delete floating ip from nova api,
NAT rule on l3-agent will not be deleted.
It remains in iptables-rule.
| Changed in neutron: | |
| assignee: | nobody → Nachi Ueno (nati-ueno) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to neutron (master) | #1 |
| Changed in neutron: | |
| status: | In Progress → Fix Committed |
| Changed in neutron: | |
| milestone: | none → havana-2 |
| status: | Fix Committed → Fix Released |
| Changed in neutron: | |
| importance: | Undecided → Medium |
| tags: | added: l3-ipam-dhcp |
| Changed in neutron: | |
| milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit 57e1fa32648a28a
Author: Nachi Ueno <email address hidden>
Date: Fri Jul 12 12:21:46 2013 -0700
Improve l3-agent performance and prevent races in it.
Fixes bug 1194026
Fixes bug 1200749
Introduce a looping call for performing synchronization with
neutron server.
The sync will be performed only if router changes are notified
via rpc. Only affected routers will be synchronized.
Changes will be implemented by the l3 agent spawning a
distinct greenthread for each router - iptables will
be executed only once using iptables_
This patch will prevent the occurence of the following issues:
- Out-of-order rpc message processing
- Long processing time for router changes due to serial execution
- Occasional and expected RPC blocks for long periods
- Unnecessary processing of multiple requests
Change-Id: I0978d1c38ac5c3