concurrent disassociate floating ip calls leads to 500 error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Vish Ishaya | ||
Folsom |
Fix Released
|
Medium
|
Vish Ishaya |
Bug Description
Disassocating the same floating ip concurrently will cause a 500 error as shown here (stable/folsom):
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
2012-12-21 00:59:13 8428 TRACE nova.openstack.
It should just ignore the remaining code if it cannot find the fixed ip.
Changed in nova: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Vish Ishaya (vishvananda) |
tags: | added: folsom-backport-potential |
Changed in nova: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
tags: | removed: folsom-backport-potential |
Changed in nova: | |
milestone: | grizzly-2 → 2013.1 |
This was partially fixed in trunk by: /review. openstack. org/#/c/ 14928/
https:/