Bug 1825761

Summary: Ansible Role execution reports do not show Ansible Icon
Product: Red Hat Satellite Reporter: Shira Maximov <mshira>
Component: Ansible CollectionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Griffin Sullivan <gsulliva>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.6.0CC: ahumbe, alsouza, bshahu, dsynk, egolov, ehelms, nshaik, oezr, snemeth
Target Milestone: 6.11.0Keywords: Reopened, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-05 14:27:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Reports image none

Description Shira Maximov 2020-04-20 07:49:57 UTC
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:

Comment 3 Shira Maximov 2020-04-20 07:54:28 UTC
Created redmine issue https://projects.theforeman.org/issues/29573 from this bug

Comment 7 Shira Maximov 2020-04-30 09:43:47 UTC
Created attachment 1683258 [details]
Reports image

Comment 8 Shira Maximov 2020-04-30 10:10:25 UTC
Connecting redmine issue https://projects.theforeman.org/issues/22804 from this bug

Comment 9 Ondřej Ezr 2020-07-13 11:29:41 UTC
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 ***

Comment 10 Marek Hulan 2021-02-16 12:44:16 UTC
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.

Comment 11 Evgeni Golov 2021-02-16 12:52:11 UTC
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.

Comment 12 Bryan Kearney 2021-04-06 00:05:17 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/22804 has been resolved.

Comment 14 Bryan Kearney 2021-12-18 20:02:45 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31890 has been resolved.

Comment 16 Brad Buckingham 2022-01-05 15:19:10 UTC
*** Bug 2036338 has been marked as a duplicate of this bug. ***

Comment 19 Griffin 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

Comment 20 Ondřej Ezr 2022-01-19 21:37:40 UTC
*** Bug 1989539 has been marked as a duplicate of this bug. ***

Comment 23 errata-xmlrpc 2022-07-05 14:27:59 UTC
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