Event execution failures for back to back leases

Bug #1785841 reported by Pierre Riteau on 2018-08-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Pierre Riteau

Bug Description

If two leases have at least one compute host in common, and the second lease starts when the first lease ends, there is the possibility of a race. The Blazar manager can first run the start_lease event of the second lease. This would fail since the end_lease event of the first lease wouldn't have been run yet: the compute host(s) in common would still be in aggregate(s) associated with the first lease, instead of being in the freepool.

Pierre Riteau (priteau) on 2018-08-07
Changed in blazar:
assignee: nobody → Pierre Riteau (priteau)
importance: Undecided → High
Masahito Muroi (muroi-masahito) wrote :

I imagine one of the purposes of cleaning time BP is resolving this issue. The first usecase of the new feature comes from Ironic usecase, but basically it fixes this issue, too.


Masahito Muroi (muroi-masahito) wrote :

Oops, I mean we've already fixed the bug and don't need to care it.

Fix proposed to branch: master
Review: https://review.openstack.org/589899

Changed in blazar:
status: New → In Progress
Pierre Riteau (priteau) wrote :

Cleaning time would help, but it's not enabled by default. Please check my patch instead: it fixes other issues, such as running before_end_lease after start_lease has completed.

Pierre Riteau (priteau) wrote :

I will push an updated patch.

Pierre Riteau (priteau) on 2018-10-15
Changed in blazar:
milestone: none → stein-1
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-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