Bug 1588779 - "some executors are not responding" logged when satellite is busy
Summary: "some executors are not responding" logged when satellite is busy
Keywords:
Status: CLOSED DUPLICATE of bug 1538688
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Tasks Plugin
Version: 6.3.1
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-07 20:36 UTC by Chris Duryee
Modified: 2018-06-13 19:48 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description Chris Duryee 2018-06-07 20:36:20 UTC
Description of problem:

If a Satellite is doing a lot of work, production.log may show a message with the string "some executors are not responding, check /foreman_tasks/dynflow/status".

This prints a message, and also prints a long stack trace. However, there is no action for the Satellite administrator to perform besides waiting for all of the work to complete.

It would be better if this message was only printed if user intervention is required. If foreman-tasks is busy, restarting it can create further problems.

Version-Release number of selected component (if applicable): 6.3.1


I am not sure how to make this happen reliably, but if you kick off a large number of registrations you can make it happen since foreman-tasks does fact processing and pkg profile upload.

NOTE: I put this bug in tasks plugin because I couldn't find a better category, but the check itself happens in katello.

Comment 2 Ivan Necas 2018-06-13 19:46:17 UTC

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

Comment 3 Ivan Necas 2018-06-13 19:48:07 UTC

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


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