Description of problem: I'm creating this BZ, from this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1810600 Version-Release number of selected component (if applicable): tfm-rubygem-foreman_ansible-3.0.7.1-1.el7sat.noarch ansible-2.8.8-1.el7ae.noarch How reproducible: 100% Steps to Reproduce: 1. Create host with attached ansible roles 2. WebUI -> All Hosts -> Select Host -> Select Action -> Play Ansible roles 3. Wait until finished 4. WebUI -> Monitor -> Config Management 5. remove filter 6. select Ansible report Actual results: in step 5. you see N/A origin instead of Ansible origin Expected results: Icon for Ansible report. Additional info:
Created redmine issue https://projects.theforeman.org/issues/29573 from this bug
Created attachment 1683258 [details] Reports image
Connecting redmine issue https://projects.theforeman.org/issues/22804 from this bug
Marking as duplicate of BZ#1800870 as there is more info and it has the same root cause. *** This bug has been marked as a duplicate of bug 1800870 ***
I'm reopening since the origin is still not correctly recognized. The callback that is shipped with Ansible 2.9 still does not add reporter information to the payload. The 2.10 is no longer released as rpm. We should start depending on foreman_ansible_modules collection on the smart_proxy_ansible side and configure the callback whitelist to use theforeman.foreman.foreman (instead of foreman). Similarly in Satellite, just using ansible-collection-redhat-satellite rpm with redhat.satellite.foreman in the whitelist.
And we should add "Provides: ansible-collection-theforeman-foreman" and "Obsoletes: ansible-collection-theforeman-foreman" to the downstream RPM, so we don't need to play dependency ping pong anywhere.
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/22804 has been resolved.
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31890 has been resolved.
*** Bug 2036338 has been marked as a duplicate of this bug. ***
Verified in 7.0 snap 3 Config reports display Ansible icon under origin. Steps to Reproduce: 1. Create host with attached ansible roles 2. **WebUI -> All Hosts -> Select Host -> Select Action -> Play Ansible roles 3. Wait until finished 4. WebUI -> Monitor -> Config Management 5. remove filter 6. select Ansible report Expected results: Step 5 displays the Ansible icon under origin. Actual results: Step 5 displays the Ansible icon under origin. **Note: There is a bug with playing Ansible roles in Satellite 7.0. I had to use the workaround described in this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2010863#c3
*** Bug 1989539 has been marked as a duplicate of this bug. ***
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 (Moderate: Satellite 6.11 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:5498