Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1465296 - It takes too long for parent task to stop after its sub-tasks have stopped
Summary: It takes too long for parent task to stop after its sub-tasks have stopped
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Jan Hutař
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-27 07:00 UTC by Adam Ruzicka
Modified: 2021-06-10 12:30 UTC (History)
9 users (show)

Fixed In Version: tfm-rubygem-foreman_remote_execution 1.3.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 20114 0 None None None 2017-06-27 07:00:42 UTC
Foreman Issue Tracker 20466 0 None None None 2017-09-28 14:01:28 UTC
Red Hat Bugzilla 1438951 0 unspecified CLOSED when remote execution job is running, numbers in Monitor -> Jobs columns are not updated correctly/in time 2021-02-22 00:41:40 UTC

Internal Links: 1438951

Description Adam Ruzicka 2017-06-27 07:00:13 UTC
Description of problem:
Bulk tasks are receiving events when their sub-tasks finish. This gets rather slow with large number of sub-tasks. We should take another approach and make the parent task poll the state of its sub-tasks.

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


How reproducible:
Easily triggered by using REX at scale

Steps to Reproduce:
1. Run a remote execution job on high number (thousands) of hosts
2. Wait until all of its sub-tasks are stopped
3. It may reach into state where all the sub-tasks are stopped but the parent task is still running for another hour or so (depends on numbers of hosts)

Actual results:
Parent task keeps running for hours after its sub-tasks have stopped

Expected results:
The parent task is stopped shortly after its sub-tasks have stopped

Additional info:

Comment 1 Adam Ruzicka 2017-06-27 07:00:40 UTC
Created redmine issue http://projects.theforeman.org/issues/20114 from this bug

Comment 5 Ivan Necas 2017-09-25 07:24:51 UTC
Align to 6.3+ please: the upstream release, compatible with 1.15 will come after the the tasks dependency gets in https://github.com/theforeman/foreman-packaging/pull/1822

Comment 7 Satellite Program 2018-02-21 16:54:37 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/RHSA-2018:0336


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