yahoo-eng-team team mailing list archive

[Balazs Gibizer <balazs.gibizer@xxxxxxxxxxxx>]

Public bug reported:

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
problem https://review.openstack.org/#/c/490814

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: placement

** Tags added: place

** Tags removed: place
** Tags added: placement

** Summary changed:

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

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

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

Status in OpenStack Compute (nova):
  New

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
  problem https://review.openstack.org/#/c/490814

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