yahoo-eng-team team mailing list archive

[Jim Rollenhagen <jim@xxxxxxxxxxxxxxxxxx>]

15:15:57         edleafe | jroll: ok, got to look at that bug, and yeah,
it should have closed it, but I forgot to put Closes-bug: in the commit
message

And I agree it appears to fix it.

This was released with Liberty-1

** Changed in: nova
       Status: In Progress => Fix Released

-- 
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/1352510

Title:
  Delete and re-add of same node to compute_nodes table is broken

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  When a compute node is deleted (or marked deleted) in the DB and
  another compute node is re-added with the same name, things break.

  This is because the resource tracker caches the compute node
  object/dict and uses the 'id' to update the record. When this happens,
  rt.update_available_resources will raise a ComputeHostNotFound. This
  ends up short-circuiting the full run of the
  update_available_resource() periodic task.

  This mostly applies when using a virt driver where a nova-compute
  manages more than 1 "hypervisor".

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1352510/+subscriptions