loopingcall: _running() can report wrong state

Bug #1847568 reported by Adriaan Schmidt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.service
New
Undecided
Unassigned

Bug Description

The _running() method of LoopingCallBase uses the state of the "_abort" event to determine if the loopingcall is running.

Upon initialization (before the first call to start()), _abort is not set, and _running() will report True, even though the loopingcall is not running.

I believe the change was introduced here:
https://github.com/openstack/oslo.service/commit/c2463470f5e7edad1ffd369a472267d559590495

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.