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.
DescriptionDhananjay Pramod Mule
2021-07-15 13:27:44 UTC
Description of problem:
if playbook has directive 'hosts: localhost' execution crash and below error is logged in '/var/log/foreman-proxy/smart_proxy_dynflow_core.log'
~~~~
2021-07-14T13:48:51 [E] error while dispatching request to runner 13bfe0aa-9733-45f6-8e6d-e5df1ad83346:NoMethodError undefined method `add_output' for nil:NilClass:
~~~
Version-Release number of selected component (if applicable):
How reproducible:
every-time
Steps to Reproduce:
1. add playbook on the satellite with below directive
~~~
- name: XYZ
hosts: localhost
~~~
2. execute job for client server.
Actual results:
responsible task goes in pending state and error logged smart_proxy_dynflow_core.log
~~~
error while dispatching request to runner
~~~
- satellite will have defunct process for ansible
~~~
# ps -aux | grep ansible
foreman+ 31033 0.0 0.0 0 0 ? Zs Jul14 0:00 [ansible-runner] <defunct>
~~~
Expected results:
localhost should be acceptable for category 'hosts'
Additional info:
reference links > - https://github.com/theforeman/foreman_ansible/pull/391
- https://github.com/theforeman/foreman_ansible/pull/398
Version- 6.12.0 - snap 7
Steps to Reproduce:
1. Add the playbook as listed
2. Run it on a host
Actual results:
No error encountered.
Expected results:
No error encountered.
Additional Info:
Upon running # ps -aux | grep ansible on Satellite, no defunct runner was present.
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.12 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-2022:8506