Bug 1912941

Unfortunatelly ansible-runner that is running the ansible playbook is not providing host related data for the verbose debug events, so we don't know what host to send this to, that is why it gets send to all of them.
I'll try to reach out to them and ask for our options here.

Created redmine issue https://projects.theforeman.org/issues/32188 from this bug

I found a possible solution at least for the connection events - that is most of the verbose events, so it should significantly improve the situation

Upstream bug assigned to oezr

Upstream bug assigned to oezr

*** Bug 1943347 has been marked as a duplicate of this bug. ***

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32188 has been resolved.

Version: Satellite 6.12.0 - 6.1

Steps to Reproduce:
1. Enable Ansible log debugging at -vvv level
2. Select two hosts.
3. Run ansible roles on those hosts.
4. Check the Dynflow Console Log on the hosts.

Actual results:
The host execution log is showing the debug log for all hosts present on the inventory instead of just the expected host.

Expected results:
Just the debug output log for the host that the output is being checked.

Additional info:
version of smart_proxy on the satellite in question
rubygem-smart_proxy_ansible.noarch                    3.4.0-1.el8sat 

Some output from the run's Dynflow Console log (The host here is 3-58, but you will see an inverted log if you check 2-183 ):


    timestamp: 1660765430.3873568
  - output_type: stdout
    output: "<dhcp-2-183.vms.sat.rdu2.redhat.com> ESTABLISH SSH CONNECTION FOR USER:
      root\n"
    timestamp: 1660765430.387411
  - output_type: stdout
    output: !ruby/string:Sequel::SQL::Blob '<dhcp-2-183.vms.sat.rdu2.redhat.com> SSH:
      EXEC ssh -o ProxyCommand=none -C -o ControlMaster=auto -o ControlPersist=60s
      -o StrictHostKeyChecking=no -o Port=22 -o ''IdentityFile="/var/lib/foreman-proxy/ssh/id_rsa_foreman_proxy"''
      -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey
      -o PasswordAuthentication=no -o ''User="root"'' -o ConnectTimeout=10 -o ''ControlPath="/var/lib/foreman-proxy/ansible/cp/f2058edf75"''
      dhcp-2-183.vms.sat.rdu2.redhat.com ''/bin/sh -c ''"''"''( umask 77 && mkdir
      -p "` echo /root/.ansible/tmp `"&& mkdir "` echo /root/.ansible/tmp/ansible-tmp-1660765425.1873856-18588-142048714011140
      `" && echo ansible-tmp-1660765425.1873856-18588-142048714011140="` echo /root/.ansible/tmp/ansible-tmp-1660765425.1873856-18588-142048714011140
      `" ) && sleep 0''"''"''''

'
    timestamp: 1660765430.3874888
  - output_type: stdout
    output: "<dhcp-3-58.vms.sat.rdu2.redhat.com> (0, b'/root\\n', b'')\n"
    timestamp: 1660765430.3875659
  - output_type: stdout
    output: "<dhcp-3-58.vms.sat.rdu2.redhat.com> ESTABLISH SSH CONNECTION FOR USER:
      root\n"
    timestamp: 1660765430.387669
  - output_type: stdout

Unless the fix was cherrypicked in downstream packaging, and I don't think it was, this had no chance to get into 6.12 yet. If I'm reading things right this was not released in any version of smart_proxy_ansible yet.

Version: Satellite 6.12.0 - 10

Steps to Reproduce:
1. Enable Ansible log debugging at -vvv level
2. Select two hosts.
3. Run ansible roles on those hosts.
4. Check the Dynflow Console Log on the hosts.

Actual results:
The host execution log is showing the debug log for all hosts present on the inventory instead of just the expected host.

Expected results:
The host execution log is showing the debug log for all hosts present on the inventory instead of just the expected host.

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