Bug 2151432 - Ansible icon under 'Origin' column in 'Config Management' Reports is broken on Satellite 6.11 Web UI.
Summary: Ansible icon under 'Origin' column in 'Config Management' Reports is broken o...
Keywords:
Status: POST
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible
Version: 6.11.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Unspecified
Assignee: nalfassi
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-07 04:44 UTC by Akshay Kapse
Modified: 2023-07-02 07:39 UTC (History)
5 users (show)

Fixed In Version: rubygem-foreman_ansible-7.1.7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36354 0 Low New Ansible icon under 'Origin' column in 'Config Management' Reports is broken on Satellite 6.11 Web UI. 2023-05-03 16:55:25 UTC
Red Hat Issue Tracker SAT-17523 0 None None None 2023-05-11 12:37:31 UTC
Red Hat Issue Tracker SAT-17845 0 None None None 2023-07-02 07:39:00 UTC

Description Akshay Kapse 2022-12-07 04:44:42 UTC 
Description of problem:
- On Satellite 6.11 Web UI --> Monitor --> Reports --> Config Management' --> Under 'Origin' column icon for 'Ansible' is broken, which can be seen working for Satellite 6.10.

How reproducible:
- Easily

Steps to Reproduce:
1. Run ansible job for the host.
2. Check under the path (tested on Firefox and Chrome):
- Satellite 6.11 Web UI --> Monitor --> Reports --> Config Management' --> Under 'Origin' column check icon for 'Ansible'.


Actual results:
- Broken Icon.

Expected results:
- Should be 'Ansible' icon as in earlier Satellite version 6.10.
Comment 2 nalfassi 2023-05-03 16:55:23 UTC 
Created redmine issue https://projects.theforeman.org/issues/36354 from this bug
Comment 3 Bryan Kearney 2023-05-04 16:02:50 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36354 has been resolved.
Note You need to log in before you can comment on or make changes to this bug.