Incorrect event retry count calculation

Bug #1786249 reported by Pierre Riteau on 2018-08-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Blazar
Medium
Pierre Riteau

Bug Description

If an event is updated towards the end of a minute, event['time'] can be up to 60 seconds away when executing it. For example, if the end_date of a lease is changed to 14:44 at 14:44:50, event['time'] will be 14:44, but the first execution attempt would be at 14:44:50 or even 14:45:00. This makes the retry calculation in _exec_event() incorrect.

If the event execution is triggered while the update request is still in progress, it can result in API errors due to an invalid state transition. See the following traces around 14:44:50 for details.

http://logs.openstack.org/98/589898/1/check/blazar-devstack-dsvm-py35/24b6daf/logs/screen-blazar-m.txt.gz#_Aug_08_14_44_50_165340
http://logs.openstack.org/98/589898/1/check/blazar-devstack-dsvm-py35/24b6daf/ara-report/result/c4be3ab9-8416-46bc-957b-4b82d5c88249/

Pierre Riteau (priteau) on 2018-09-10
Changed in blazar:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Pierre Riteau (priteau)
milestone: none → stein-1
Pierre Riteau (priteau) wrote :

The best option would be to extend the event model to keep track of the number of retries of each event.

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