Bug 1661292

Summary: Running a `sync_task` while the tasks service gets restarted might lead to passenger process hanging forever
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: Tasks PluginAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.2CC: aruzicka, egolov, inecas
Target Milestone: 6.4.2Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman-tasks-0.13.4.3-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1635540 Environment:
Last Closed: 2019-02-13 19:08:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot 1
none
screenshot 2
none
screenshot 3 none

Comment 2 jcallaha 2019-01-23 21:52:59 UTC 
Verified in Satellite 6.4.2 Snap 1

I kicked off a set of add subscriptions tasks against 30 content hosts.
Then, I killed all dynflow_executor processes

Screenshot 1 shows one of the tasks waiting to be resumed, since dynflow was killed

I then restarted foreman-tasks service and resumed the task.

Screenshot 2 shows the task being resumed.

Screenshot 3 shows the task completing successfully.
Comment 3 jcallaha 2019-01-23 21:53:21 UTC 
Created attachment 1522898 [details]
screenshot 1
Comment 4 jcallaha 2019-01-23 21:53:53 UTC 
Created attachment 1522899 [details]
screenshot 2
Comment 5 jcallaha 2019-01-23 21:54:28 UTC 
Created attachment 1522900 [details]
screenshot 3
Comment 7 errata-xmlrpc 2019-02-13 19:08:21 UTC 
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-2019:0345