VM resize and confirm on the same host fails with custom resources
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Unassigned |
Bug Description
VM resize and confirm on the same host fails with custom resources, as the old resources are not deallocated after 'confirmResize'.
Steps to reproduce:
- boot a VM with old_flavor
- resize to new_flavor to the same host
- send confirmResize
- check usages and compare with new_flavor, and there will be double allocations (old_flavor + new_flavor)
Related Nova log:
2017-08-29 16:22:22,666 INFO [nova.api.
2017-08-29 16:22:22,666 DEBUG [nova.scheduler
60b3f076-
, u'generation': 4}}
2017-08-29 16:22:22,666 DEBUG [nova.scheduler
2017-08-29 16:22:22,666 DEBUG [nova.scheduler
2017-08-29 16:22:22,667 DEBUG [nova.scheduler
2017-08-29 16:22:22,667 DEBUG [nova.scheduler
}, {'resource_
'MEMORY_MB': 1024, u'DISK_GB': 40, u'VCPU': 1, u'CUSTOM_MAGIC': -256}}] for instance 8d989deb-
2017-08-29 16:22:22,667 DEBUG [nova.api.
2017-08-29 16:22:22,670 DEBUG [nova.api.
Failed validating 'minimum' in schema[
{'minimum': 1, 'type': 'integer'}
On instance[
-256
2017-08-29 16:22:22,671 INFO [nova.api.
2017-08-29 16:22:22,671 WARNING [nova.scheduler
<head>
<title>400 Bad Request</title>
</head>
<body>
<h1>400 Bad Request</h1>
The server could not comply with the request since it is either malformed or otherwise incorrect.<br /><br />
JSON does not validate: -256 is less than the minimum of 1
Failed validating 'minimum' in schema[
{'minimum': 1, 'type': 'integer'}
On instance[
-256
</body>
</html>
tags: | added: custom-resource-class placement resize |
tags: | added: resource-tracker scheduler |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → High |
Lajos has a regression test for it as well and he will push that up soon.