In certain cases compute does not clean up neutron ports after unsuccessful vm spawn
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Oleg Bondarev |
Bug Description
When allocating networks for instance compute first creates ports and then fetches them from neutron to build network info.
Under high load it might be possible that neutron/keystone timeouts on a request to fetch ports for instance (traceback attached).
In this case exception is caught and _shutdown_
Then the exception is reraised, caught in _build_
RescheduledExce
Eventually only self.network_
self.network_
I see two possible fixes: either do network deallocation on _shutdown_
[1] bug 1332198 commit 5120c4f7c2670ea
[2] https:/
[3] https:/
[4] https:/
Changed in nova: | |
importance: | Undecided → Low |
Changed in nova: | |
milestone: | none → kilo-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-rc1 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/157755
Review: https:/