Lease update api wrongly succeeds
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Blazar |
New
|
Medium
|
Masahito Muroi |
Bug Description
Description:
-------------
Instance reservation update request is accepted even if the value provided for disk_gb,
memory_mb, vcpus greater than the capacity of computehost.
Steps to reproduce:
-------
1. blazar host-list
+----+
| id | hypervisor_hostname | vcpus | memory_mb | local_gb |
+----+
| 1 | <host-name> | 4 | 11941 | 91 |
+----+
2. update a lease with "memory_mb": 1194444 > 11941
curl -g -i -X PUT http://<host-ip>
Expected result:
-----------------
It should not allow to update greater than capacity available.
Actual result:
-----------------
Blazar server doesn't return any error and accept the update request also successfully updates DB.
Changed in blazar: | |
assignee: | nobody → Masahito Muroi (muroi-masahito) |
importance: | Undecided → Medium |
milestone: | none → stein-1 |
Changed in blazar: | |
milestone: | stein-1 → stein-2 |
Changed in blazar: | |
milestone: | stein-2 → stein-3 |
Changed in blazar: | |
milestone: | stein-3 → train-1 |
This might be resolved by the fix implemented for #1786007, need to test. We should write a Tempest test for this.