Instance reservation update wrongly succeeds
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Blazar |
Fix Released
|
High
|
Masahito Muroi |
Bug Description
Update lease API for instance reservation wrongly succeed even though there is no enough hosts to accommodate update request.
How to reproduce the error
1. create new lease1 with max memory_mb for the computehost
$ blazar lease-create --reservation resource_
2. create new lease2 with same parameter with lease1
$ blazar lease-create --reservation resource_
3. extend end_date of lease-1 to overwrap start_date of lease-2
$ blazar lease-update --end-date '2020-01-01 13:00' lease-1
Blazar server doesn't return any error and accept the update request. However, there is no allocation information about lease-1 in computehost_
Changed in blazar: | |
importance: | Undecided → High |
Changed in blazar: | |
milestone: | none → rocky-rc1 |
Fix proposed to branch: master /review. openstack. org/589824
Review: https:/