Description of problem: In some cases (such as content view update), when foreman-tasks is not running, the task can and up with success result but pending state, and block the other actions to be performed Version-Release number of selected component (if applicable): satellite 6.2.0 beta How reproducible: On special occasions Steps to Reproduce: 1. stop foreman-tasks service 2. rename a content view 3. start the foreman-tasks Actual results: the content view action ends up in success result but pending state Expected results: the content view action finishes once foreman-tasks start Additional info: A workaround is: ``` cat <<SCRIPT | foreman-rake console ForemanTasks::Task.where(:state => :planned, :result => :success).map do |task| task.update_attributes(:state => 'stopped') end SCRIPT ```
Created redmine issue http://projects.theforeman.org/issues/14883 from this bug
Upstream bug component is Tasks Plugin
Fix merged in dynflow https://github.com/Dynflow/dynflow/pull/184
Verified on RHEL6, snap 12, Dynflow 0.8.11 The tasks end up in stopped state with success and do not block other tasks.
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:1501