Description of problem: At some occasions, the task data can get into a state that prevent the system to recover properly from inconsistent state. How reproducible: Rarely Steps to Reproduce: 1. kill -9 dynflow executor while some task is running (has to be shortly after enough triggering some tasks) 2. foreman-tasks restart Actual results: the task still acting as being run by killed executor Expected results: the task marked as planned on running by new executor
Created redmine issue http://projects.theforeman.org/issues/17178 from this bug
It is another case of https://bugzilla.redhat.com/show_bug.cgi?id=1379820
Upstream bug assigned to inecas
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17178 has been resolved.
*** Bug 1379820 has been marked as a duplicate of this bug. ***
A deterministic way of reproduce it: 1. Run service foreman-tasks stop 2. Initiate your task 3. Check planned state working as expected 4. Run Run service foreman-tasks start And now system is working for tasks on planned state on version 6.2.5.
No info is needed anymore.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:2940