loopingcall: _running() can report wrong state
Bug #1847568 reported by
Adriaan Schmidt
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:/
To post a comment you must log in.