inconsistent nova-bm state will prevent launching new instances
Bug #1096722 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Critical
|
Robert Collins |
Bug Description
if the nova-bm state lists a deleted instance against a baremetal node, then
nova/virt/
will throw:
InstanceNotFoun
where the instance id will be that of the deleted instance.
This is a horribly inefficient implementation anyhow, its iterating all baremetal nodes to check for the desired one not existing.
This suggests we should implement instance_exists more directly, *and* we should make
baremetal list_instances have a try: except around the call to instance_
Changed in nova: | |
milestone: | none → grizzly-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-3 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/19069
Review: https:/