Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1390933 - invalid state transition planned >> paused on foreman-tasks restart
invalid state transition planned >> paused on foreman-tasks restart
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Tasks Plugin (Show other bugs)
6.2.0
Unspecified Unspecified
high Severity high (vote)
: 6.2.5
: Unused
Assigned To: Ivan Necas
Renzo Nuccitelli
: Triaged
: 1379820 (view as bug list)
Depends On:
Blocks: 1394385
  Show dependency treegraph
 
Reported: 2016-11-02 05:41 EDT by Ivan Necas
Modified: 2016-12-12 12:15 EST (History)
7 users (show)

See Also:
Fixed In Version: rubygem-dynflow-0.8.13.3-2
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1394385 (view as bug list)
Environment:
Last Closed: 2016-12-12 12:15:22 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 17178 None None None 2016-11-02 07:06 EDT
Red Hat Product Errata RHBA-2016:2940 normal SHIPPED_LIVE Satellite 6.2.5 Async Bug Release 2016-12-12 17:08:21 EST

  None (edit)
Description Ivan Necas 2016-11-02 05:41:09 EDT
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
Comment 2 Ivan Necas 2016-11-02 07:06:23 EDT
Created redmine issue http://projects.theforeman.org/issues/17178 from this bug
Comment 3 Ivan Necas 2016-11-02 07:23:35 EDT
It is another case of https://bugzilla.redhat.com/show_bug.cgi?id=1379820
Comment 5 Bryan Kearney 2016-11-02 08:11:32 EDT
Upstream bug assigned to inecas@redhat.com
Comment 6 Bryan Kearney 2016-11-02 08:11:34 EDT
Upstream bug assigned to inecas@redhat.com
Comment 7 Bryan Kearney 2016-11-07 06:11:21 EST
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17178 has been resolved.
Comment 8 Ivan Necas 2016-12-01 17:37:26 EST
*** Bug 1379820 has been marked as a duplicate of this bug. ***
Comment 10 Renzo Nuccitelli 2016-12-08 13:38:29 EST
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.
Comment 11 Renzo Nuccitelli 2016-12-08 13:38:54 EST
No info is needed anymore.
Comment 13 errata-xmlrpc 2016-12-12 12:15:22 EST
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

Note You need to log in before you can comment on or make changes to this bug.