nova does not properly claim resources when server resized to a too big flavor
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Balazs Gibizer |
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:/
tags: | added: place |
tags: |
added: placement removed: place |
summary: |
- 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 |
Changed in nova: | |
importance: | Undecided → High |
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
assignee: | Balazs Gibizer (balazs-gibizer) → Ed Leafe (ed-leafe) |
Changed in nova: | |
assignee: | Ed Leafe (ed-leafe) → Balazs Gibizer (balazs-gibizer) |
tags: | removed: pike-rc-potential |
tags: | added: resize |
Fix proposed to branch: master /review. openstack. org/491491
Review: https:/