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.
Bug 2211955 - "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: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible - Configuration Management
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 6.13.2
Assignee: Eric Helms
QA Contact: visawant
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-02 18:32 UTC by Odilon Sousa
Modified: 2023-07-12 15:37 UTC (History)
9 users (show)

Fixed In Version: rubygem-foreman_ansible-10.4.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2152951
Environment:
Last Closed: 2023-07-12 15:37:22 UTC
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-06-02 18:32:54 UTC
Red Hat Issue Tracker SAT-15086 0 None None None 2023-06-02 18:32:54 UTC
Red Hat Issue Tracker SAT-17345 0 None None None 2023-06-02 18:32:54 UTC
Red Hat Issue Tracker SAT-18078 0 None None None 2023-06-02 18:38:01 UTC
Red Hat Product Errata RHBA-2023:4043 0 None None None 2023-07-12 15:37:35 UTC

Comment 4 Leos Stejskal 2023-06-19 11:52:22 UTC 
Hi,
summarizing discussion with QAs:

* There should be one template called "Capsule Upgrade Playbook" without any mention of smart proxy
* This template  should use satellite-installer & satellite tools
* There is also a template "Smart Proxy ..." which should be hidden for Satellite users (problem for another BZ)
* Capsule upgrade should work, using of course the "Capsule Upgrade Playbook" template
Comment 5 visawant 2023-06-19 14:58:51 UTC 
Verified

Satellite version: 6.13.2 

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

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.
Comment 15 errata-xmlrpc 2023-07-12 15:37:22 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 (Satellite 6.13.2 Async 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/RHBA-2023:4043
Note You need to log in before you can comment on or make changes to this bug.