Bug 2215986

Summary: In Downstream satellite, both "Capsule Upgrade Playbook" and "Smart Proxy Upgrade Playbook" job template are listing.
Product: Red Hat Satellite Reporter: visawant
Component: Ansible - Configuration ManagementAssignee: nalfassi
Status: CLOSED ERRATA QA Contact: visawant
Severity: medium Docs Contact:
Priority: high    
Version: 6.13.2CC: lstejska, nalfassi, pcreech, rlavi, sshtein
Target Milestone: 6.14.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-foreman_ansible-12.0.5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-08 14:19:51 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
Smart proxy upgrade playbook also listed in downstream none

Description visawant 2023-06-19 15:13:36 UTC
Created attachment 1971572 [details]
Smart proxy upgrade playbook also listed in downstream

Description of problem: Upon searching for query "name ~ Upgrade Playbook" on Hosts > Job Templates, "Capsule Upgrade Playbook" and "Smart Proxy Upgrade Playbook" both job template are listed in Satellite Web UI


Version-Release number of selected component (if applicable): 6.13.2


How reproducible: Always


Steps to Reproduce:
1. Navigate to Hosts > Job Templates
2. Search for 'name ~ "upgrade playbook"'

Actual results:
Both job templates are listing

Expected results:
As we are on Downstream satellite, only Capsule upgrade playbook should list

Additional info: Attached screenshot
Hammer output:
[root@ip-fqdn ~]# hammer job-template list | grep -e "Upgrade Playbook"
210 | Capsule Upgrade Playbook                                  | Maintenance Operations     | Ansible  | job_template
222 | Smart Proxy Upgrade Playbook                              | Maintenance Operations     | Ansible  | job_template

Package version:
satellite-cli-6.13.2-1.el8sat.noarch
satellite-6.13.2-1.el8sat.noarch
rubygem-foreman_theme_satellite-11.0.0.5-1.el8sat.noarch
satellite-installer-6.13.0.7-1.el8sat.noarch

# rpm -qa | grep rubygem-foreman_ansible
rubygem-foreman_ansible-10.4.2-1.el8sat.noarch

Comment 4 nalfassi 2023-07-05 09:34:15 UTC
Created redmine issue https://projects.theforeman.org/issues/36569 from this bug

Comment 5 Bryan Kearney 2023-07-25 16:03:11 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36569 has been resolved.

Comment 6 Patrick Creech 2023-07-26 03:45:48 UTC
Can we get a release of foreman_ansible 12.0.z with this fix in it?

Comment 9 visawant 2023-08-03 13:38:04 UTC
Verified

Version tested: 
Satellite 6.14.0 Snap 10

Comment 12 errata-xmlrpc 2023-11-08 14:19:51 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 (Important: Satellite 6.14 security and bug fix update), 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-2023:6818