Submitter: Jenkins
Branch:    master

commit 6b0ab40e4233a480c9bdcca657f594d7e90fadc8
Author: Balazs Gibizer <>
Date:   Mon Aug 7 15:12:25 2017 +0200

    Raise NoValidHost if no allocation candidates
    Placement took over the role of the CoreFilter, RamFilter and DiskFilter
    from the FilterScheduler. Therefore if placement returns no allocation
    candidates for a request then scheduling should be stopped as this means
    there is not enough VCPU, MEMORY_MB, or DISK_GB available in any compute
    node for the request.
    Change-Id: If20a20e5cce7ab490998643e32556a1016646b07
    Closes-Bug: #1708637

** 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).

  nova does not properly claim resources when server resized to a too
  big flavor

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Problematic scenario: Boot a server then try to resize it to a flavor
  which requests more vcpu than what available in any compute hosts.

  If the CoreFilter is enabled then the resize fails with NoValidHost
  and the resource allocation is OK.

  However if the CoreFilter is not enabled in the FilterScheduler then
  the resize is accepted but the placement API is not updated with the
  actual resource (over) allocation.

  In this case I don't know which would be the expected behavior:
  Option A: No valid host shall be raised
  Option B: Resize is accepted and the resources state are updated properly

  There is a patch proposed with functional tests that reproduces the

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to