** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => grizzly-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1096722
Title:
inconsistent nova-bm state will prevent launching new instances
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
if the nova-bm state lists a deleted instance against a baremetal node, then
nova/virt/driver.py", line 160, in instance_exists
will throw:
InstanceNotFound_Remote: Instance 2c9b1224-bbbf-47a8-bbce-c9be61ac554b could
not be found.
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_get_by_uuid.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1096722/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
