yahoo-eng-team team mailing list archive

[Devananda van der Veen <1260102@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

With the baremetal driver, if a baremetal node is deleted, it is not
removed from pool of available resources until the next run of
update_available_resource(). During this window, the scheduler may
continue to attempt to schedule instances on it, leading to unnecessary
failures and scheduling retries.

This bug will also apply to the ironic driver, which will rely on the
same mechanism(s) for listing and scheduling compute resources.

** Affects: nova
     Importance: Medium
         Status: Triaged


** Tags: baremetal ironic scheduler

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

Title:
  Removal of a baremetal node does not propagate to scheduler quickly

Status in OpenStack Compute (Nova):
  Triaged

Bug description:
  With the baremetal driver, if a baremetal node is deleted, it is not
  removed from pool of available resources until the next run of
  update_available_resource(). During this window, the scheduler may
  continue to attempt to schedule instances on it, leading to
  unnecessary failures and scheduling retries.

  This bug will also apply to the ironic driver, which will rely on the
  same mechanism(s) for listing and scheduling compute resources.

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