delete-subnets in the same network at concurrency, dhcp port may be reallocated ip in deleting subnet
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
New
|
Undecided
|
Unassigned | ||
Bug Description
Scenario:
When delete 10 subnets in the same network at concurrency, every thread will delete ip that belongs to the deleting subnet on the dhcp port, than neutron-server will send delete-sbunet notification to dhcp agent. After dhcp agent recieved the notification, dhcp agent will reconfigure the network dhcp process.
Steps:
In thread(A), dhcp agent received the delete-subnet(A) notification, than requests the newest dhcp port and subnets information from neutron-server.
In thread(B), neutron-server just deleted ips that belogs to the deleting subnet(B) on dhcp port, but the subnet(B) still exist.
In thread(A), dhcp agent recieved the newest dhcp port and subnets information from neutron-server, than it find subnet(B) exists, but dhcp port doesn't have fixed_ip under the subnet(B), the fixed_ip had deleted in thread(B).
In this case, dhcp agent will request neutron-server to allocat a fresh IP for subnet(B). https:/
| summary: |
- delete-subnets in one network at concurrency, dhcp port may be + delete-subnets in the same network at concurrency, dhcp port may be reallocated ip in deleting subnet |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| Rodolfo Alonso (rodolfo-alonso-hernandez) wrote | #1 |
Could this bug be related to https:/