race condition when updating instance after it's deleted
Bug #948632 reported by
Chris Behrens
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Chris Behrens |
Bug Description
Because we allow deletes during build again... There's a race condition in compute manager's _run_instance() where an instance can be deleted in the middle of an rpc.call to the network manager to allocate networks. rpc.call will raise a RemoteError and we will try to set the instance to ERROR state. The setting of instance to ERROR state fails with InstanceNotFound... and eats the original exception.
We shouldn't blow up when we try to set an instance to ERROR that has been deleted out from under us.
Changed in nova: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Chris Behrens (cbehrens) |
Changed in nova: | |
milestone: | none → essex-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-rc1 → 2012.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/5007
Review: https:/