yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => grizzly-rc1

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

Title:
  compute node update available resources should always update
  updated_at

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  The scheduler's host_manager tries to cache capacity changes in
  between resource tracker updates on the compute side.  It uses its
  cache while each compute_node['updated_at'] is older than the
  scheduler cache.

  It's possible that under failure scenarios that this cache is updated
  to use a resource that is never committed on the compute side.  It's
  also possible due to a race condition that the scheduler updates its
  cache at nearly the same time the compute manager does.

  There's a periodic task that runs on compute nodes that constantly updates the compute_node's entry to make sure used resources are in sync with the DB.
  However, when there's no differences, despite calling compute_node_update(), 'updated_at' does not get updated in the DB.  This can result in the scheduler forever having an incorrect view of resources as it never sees a newer 'updated_at' in the compute_node entry.

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