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:
Connecting upstream issue to this BZ.
Upstream bug assigned to aruzicka
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.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21716 has been resolved.
Upstream release here https://github.com/theforeman/foreman-packaging/pull/1983
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.
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