Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
While running large scale Remote Execution (currently we ran Remote Execution on 30k hosts), it becomes very hard to cancel or abort the job until all the hosts have been queued for the execution.
This situation becomes more grave when tasks are taking too long to get queued.
Version-Release number of selected component (if applicable):
How reproducible: Everytime
Steps to Reproduce:
1. Run Remote Execution on Large Number of hosts (we did with 30k)
2. Try to cancel the job while it is running and not all hosts are queued for execution
3. The job doesn't cancels till all the hosts are queued.
Actual results:
The job doesn't cancels till all hosts are queued for execution
Expected results:
The job should be cancelled no matter even if some of the hosts are still remaining to be queued
Additional info:
There is a related BZ that resolving this issue will help moving forward as well https://bugzilla.redhat.com/show_bug.cgi?id=1370139, not closing as duplicate, as this one talks directly about job cancelling and it's worth verifying this specific case separately.
Comment 5Satellite Program
2017-12-14 17:26:08 UTC
Verified in Sat 6.3 snap 29, when the job is canceled in progress, it finishes scheduling the current batch of hosts (100) and the rest of tasks is not started.
Comment 8Satellite 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