Race between delete_subnet and delete_network
Bug #1405197 reported by
Eugene Nikanorov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Eugene Nikanorov | ||
Juno |
Fix Released
|
Medium
|
Eugene Nikanorov |
Bug Description
If the code executes the following sequence:
delete_
delete_
where subnet subnet_id belongs to a network with net_id, there's a possible race condition between dhcp_port_release initiated by subnet deletion and deletion of service ports (DHCP) during network deletion.
Latter operation throws PortNotFound and network deletion stops.
The solution could be to just catch such error during port deletion.
The chance of catching this bug increases in the environment with multiple neutron servers where DB access could not be synchronized within one process.
tags: | added: ml2 |
Changed in neutron: | |
milestone: | none → kilo-2 |
description: | updated |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
tags: | added: in-stable-juno |
tags: |
added: juno-backport-potential removed: in-stable-juno |
Changed in neutron: | |
milestone: | kilo-2 → 2015.1.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/143698
Review: https:/