yahoo-eng-team team mailing list archive

[Belmiro Moreira <1805984@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Placement doesn't know if a resource provider (in this particular case a
compute node) is disabled. This is only filtered by the scheduler using
the "ComputeFilter".

However, when using the option "max_placement_results" to restrict the
amount of placement results there is the possibility to get only
"disabled" allocation candidates from placement. The creation of new VMs
will end up in ERROR because there are "No Valid Hosts".

There are several use-cases when an operator may want to disable nodes
to avoid the creation of new VMs.

Related with: https://bugs.launchpad.net/nova/+bug/1708958

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: placement

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

Title:
  Placement is not aware of disable compute nodes

Status in OpenStack Compute (nova):
  New

Bug description:
  Placement doesn't know if a resource provider (in this particular case
  a compute node) is disabled. This is only filtered by the scheduler
  using the "ComputeFilter".

  However, when using the option "max_placement_results" to restrict the
  amount of placement results there is the possibility to get only
  "disabled" allocation candidates from placement. The creation of new
  VMs will end up in ERROR because there are "No Valid Hosts".

  There are several use-cases when an operator may want to disable nodes
  to avoid the creation of new VMs.

  Related with: https://bugs.launchpad.net/nova/+bug/1708958

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