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:
- Changing concurrency level while executing Ansible jobs fail with NoMethodError: undefined method `[]' for nil:NilClass
- The action on the servers themselves finishes correctly, the only issue is Satellite reporting the job as failed
Version-Release number of selected component (if applicable):
- satellite-6.6.0-7.el7sat.noarch
How reproducible: 100%
Steps to Reproduce:
1. Monitor > Jobs > Run job > (default) Ansible commands | Run command > fill search query to 'name ~ test-rhel*' > hit 'Refresh' button to ensure it matches the right hosts > complete Command field to 'uname -a' -> set concurrency level field to 1 -> hit Submit
2. If we run a job on a list of 55 hosts with default concurrency level (unset, all jobs launched simultaneously), job finish detection works fine and all are maked as OK.
3. If we run a job on the same 55 hosts with concurrency level = 5 (or 10 or whatever); the first batch of servers works ok, but any other server after that, their job is executed on the target machine but marked as Failed on Satellite.
Actual results:
- Ansible jobs fail with "Error:NoMethodError undefined method `[]' for nil:NilClass"
Expected results:
- Ansible REX jobs should succeed.
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 (Important: Satellite 6.8 release), 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-2020:4366