Bug #25935
closed
Tasks cleanup rake tasks acts as an executor
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1669973
Description of problem:
The foreman_tasks:cleanup rake task runs as an executor. This means that during the task cleanup the rake task can actually start processing satellite's tasks. When the rake task exits it may (or may not) leave the tasks it was processing in some kind of bad state (abnormal termination?).
Version-Release number of selected component (if applicable):
I'm not aware of any recent change which could introduce this behavior, this probably affects all satellite versions.
How reproducible:
Always
Steps to Reproduce:
1. Go into dynflow console
2. Run foreman_tasks:cleanup rake task
3. Keep refreshing the page until a new world record appears
Actual results:
The world used by the rake task appears under executor worlds
Expected results:
The world used by the rake task appears under client worlds
Additional info:
Updated by Ivan Necas almost 6 years ago
- Subject changed from Tasks cleanup rake tasks acts as an executor to Tasks cleanup rake tasks acts as an executor
This seems like development-environment only issue
Updated by Adam Ruzicka over 3 years ago
- Is duplicate of Bug #30145: foreman-rake foreman_tasks:cleanup fails because Dynflow world is not initialized yet added