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:
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:
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.
*** Bug 2036338 has been marked as a duplicate of this bug. ***
Comment 19Griffin Sullivan
2022-01-10 16:34:58 UTC
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
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