yahoo-eng-team team mailing list archive

[Chris Behrens <1352510@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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".

** Affects: nova
     Importance: Medium
     Assignee: Chris Behrens (cbehrens)
         Status: In Progress

** Changed in: nova
       Status: New => In Progress

** Changed in: nova
     Assignee: (unassigned) => Chris Behrens (cbehrens)

** Changed in: nova
   Importance: Undecided => Medium

-- 
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):
  In Progress

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