Bug 2152951 - "Capsule Upgrade Playbook" job template is now "Smart Proxy Upgrade Playbook"
Summary: "Capsule Upgrade Playbook" job template is now "Smart Proxy Upgrade Playbook"
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 6.14.0
Assignee: Eric Helms
QA Contact: visawant
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-13 15:01 UTC by Peter Ondrejka
Modified: 2023-06-27 14:37 UTC (History)
11 users (show)

Fixed In Version: rubygem-foreman_ansible-11.1.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2211955 (view as bug list)
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github theforeman foreman_ansible pull 590 0 None Merged Fixes #36011 - Split Capsule and Smart Proxy upgrades to separate tem… 2023-05-30 04:01:58 UTC
Red Hat Issue Tracker SAT-15086 0 None None None 2023-01-24 18:08:27 UTC
Red Hat Issue Tracker SAT-17345 0 None None None 2023-05-24 11:54:49 UTC

Description Peter Ondrejka 2022-12-13 15:01:51 UTC
Description of problem:

In 6.13, Smart Proxy Upgrade Playbook appears in the job template list.

Version-Release number of selected component (if applicable):
6.13 snap 1

How reproducible:
always

Steps to Reproduce:
Hosts > Job Templates, search for Capsule upgrade playbook

Actual results:
Smart Proxy Upgrade Playbook is listed. Interestingly in template details, "Edit Capsule Upgrade Playbook" appears in the breadcrumb.

Expected results:
Naming consistency with previous releases.

Comment 1 Adam Ruzicka 2022-12-13 15:14:56 UTC
The job template in question can now be used in upstream, where capsule as a concept does not exist at all[1].

The breadcrumbs are probably being somehow mangled by the branding plugin.

[1] - https://github.com/theforeman/foreman_ansible/pull/568#pullrequestreview-1153040653

Comment 2 nalfassi 2023-02-13 08:57:53 UTC
Created redmine issue https://projects.theforeman.org/issues/36085 from this bug

Comment 3 Adam Ruzicka 2023-02-13 09:05:45 UTC
FYI this is already being handled in https://projects.theforeman.org/issues/36011

Comment 4 nalfassi 2023-02-13 09:10:16 UTC
Oh, it wasn't clear to me. Thanks Adam and I will know better next time :)

Comment 6 nalfassi 2023-05-24 11:52:40 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36011 has been resolved.

Comment 7 visawant 2023-06-27 14:37:58 UTC
Verified

Satellite version: 6.14.0

Package version:
satellite-installer-6.14.0.5-1.el8sat.noarch
satellite-maintain-0.0.2-1.el8sat.noarch
satellite-6.14.0-2.el8sat.noarch
satellite-cli-6.14.0-2.el8sat.noarch
rubygem-foreman_theme_satellite-12.0.0.1-1.el8sat.noarch
satellite-common-6.14.0-2.el8sat.noarch

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

Steps performed:
1. Navigate to Hosts > Job Templates
2. Search for "Capsule upgrade playbook"
3. Click on the "Capsule upgrade playbook" template name, and check breadcrumb

Observation: 
Consistency appears in the breadcrumb "Edit Capsule Upgrade Playbook" in template detail.


Note You need to log in before you can comment on or make changes to this bug.