Any type of bad update lease request causes lease ERROR status

Bug #1786031 reported by Masahito Muroi on 2018-08-08
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Blazar
High
Pierre Riteau

Bug Description

Lease status goes ERROR status when the update lease API fails because of any failure. Even though the failure happens because of a wrong input and Blazar denies the request, the lease status goes ERROR status.

How to reproduce:

1. Create a lease

$ blazar lease-create --physical-reservation min=1,max=1,hypervisor_properties=[] --start-date '2020-01-01 10:00' --end-date '2020-01-01 11:00' lease-1

2. Update the lease with bigger number than blazar's freepool

$ blazar lease-update --reservation min=100000,max=100000 lease-1

# this request fails with 'Not Enough Host available' error

3. Check the lease status

$ blazar lease-show lease-1

# the lease status goes ERROR even though the request was denied and anything was updated.

Workaround:
- When an user receives error response code for the update lease API, the user re-updates the lease with old lease information.

Pierre Riteau (priteau) on 2018-09-10
Changed in blazar:
assignee: nobody → Pierre Riteau (priteau)
milestone: none → stein-1
importance: Medium → High
status: New → Confirmed
Pierre Riteau (priteau) on 2018-10-23
Changed in blazar:
milestone: stein-1 → stein-2
Pierre Riteau (priteau) on 2019-01-10
Changed in blazar:
milestone: stein-2 → stein-3
Pierre Riteau (priteau) on 2019-01-23
Changed in blazar:
status: Confirmed → In Progress
Pierre Riteau (priteau) on 2019-04-15
Changed in blazar:
milestone: stein-3 → train-1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers