A subnet-delete immediately after a port-delete may fail in multi-config-node setup
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R1.1 |
Won't Fix
|
Medium
|
Prakash Bailkeri | |||
R2.0 |
Won't Fix
|
Medium
|
Prakash Bailkeri | |||
R2.1 |
Won't Fix
|
Medium
|
Prakash Bailkeri | |||
R3.0 |
Won't Fix
|
Medium
|
Prakash Bailkeri | |||
Trunk |
New
|
Medium
|
Vedamurthy Joshi |
Bug Description
Build 1.10 7
This bug is for release-noting the behavior.
In a multi-config setup, A subnet-delete immediately after a port-delete may fail in multi-config-node setup saying that there are existing references to the subnet.
Users will have to retry when this happens.
2014-08-07 00:46:45,121 - INFO - Deleting subnet 804f1c1a-
2014-08-07 00:46:45,192 - ERROR - 409-{u'
Traceback (most recent call last):
File "scripts/
result = self.neutron_
File "/usr/lib/
ret = self.function(
File "/usr/lib/
return self.delete(
File "/usr/lib/
headers=
File "/usr/lib/
headers=
File "/usr/lib/
self.
File "/usr/lib/
exception_
File "/usr/lib/
message=msg)
NeutronClientEx
no fix for r1.1, release note.