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:

Job execution with concurrency set broken with nilclass at 100 servers out of 116 if batch size >= 100
Version-Release number of selected component (if applicable):

Satellite version 6.11

How reproducible:
Always.

Steps to Reproduce:

Job details for reproducer:
- Type: SSH Command
- Query '*'  (make sure > 100 servers are there)
- Command: 'date'
- Concurrency: 30



Actual results:

Job execution with concurrency set broken with nilclass at 100 servers out of 116 if batch size >= 100

Expected results:
It should not fail.

Additional info:

Issue related to 'Concurrency level limited to: 30 tasks at a time'.
If do not set the concurrency level it successfully processes all ~116 servers. 
If set the concurrency to 30 tasks then it exactly hangs/fails again at ~100

i tested it with various capsule batch sizes in the settings and there it proved that >= 100 it started to fail and with <100 it completed.

Job on ~120 servers with concurrency 30 and the following Capsule batch sizes:
- 50: ok
- 99; ok
- 100: FAIL
- 101: FAIL
- 150: FAIL

Yes, this is a known issue, there's already an older BZ for it, closing as duplicate.

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