Bug 1596642 - Task execution stuck as "pending" when a callback from smart proxy to foreman fails
Summary: Task execution stuck as "pending" when a callback from smart proxy to foreman...
Keywords:
Status: CLOSED DUPLICATE of bug 1431956
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-29 11:23 UTC by Radovan Drazny
Modified: 2018-08-27 11:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-29 17:10:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1431956 0 medium CLOSED about 22 sub-tasks of remote execution task on 5000 systems were left in pending after 7.5 hours 2021-02-22 00:41:40 UTC

Internal Links: 1431956

Description Radovan Drazny 2018-06-29 11:23:44 UTC
Description of problem:
When a callback from the smart proxy to foreman fails during a tast execution, the task will stay in pending state forever. This was encountered together with BZ 1596636.

Version-Release number of selected component (if applicable):
Satellite 6.4 Snap 9

Steps to Reproduce:
See the BZ 1596636 for the reproducer, but any fail during a callback will probably produce a same problem.

Actual results:
Task is stuck as "Pending" forever

Expected results:
Task is successfully completed.

Additional info:
Raw output of the stuck task:


Id: 709cffa0-74e5-4347-8f72-3b1fb3f77828
Label: Actions::RemoteExecution::RunHostJob
Duration: about 17 hours
Raw input:

{"host"=>{"id"=>155, "name"=>"docker1container100.example.com"},
 "job_category"=>"Commands",
 "description"=>"Run date",
 "delegated_action_id"=>2,
 "locale"=>"en",
 "current_user_id"=>4}

Raw output:

{}

External Id: 4c13db96-3e99-4f91-8493-58c2147e2bb5

Comment 3 Ivan Necas 2018-06-29 17:10:59 UTC
Marking as duplicate of 1431956, as that's where we tried to handle rex resiliency.

*** This bug has been marked as a duplicate of bug 1431956 ***

Comment 4 Radovan Drazny 2018-08-27 11:18:55 UTC
There are no side effect of the stuck task I'm aware of.


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