Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2154397

Summary: Missing upgrade scenarios for 6.13 and 6.13.z in foreman-maintain
Product: Red Hat Satellite Reporter: Gaurav Talreja <gtalreja>
Component: Satellite MaintainAssignee: Evgeni Golov <egolov>
Status: CLOSED ERRATA QA Contact: Lukas Pramuk <lpramuk>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.13.0CC: egolov, ehelms, jpathan, lpramuk, lstejska, pcreech
Target Milestone: 6.13.0Keywords: Regression, Triaged, UpgradeBlocker
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rubygem-foreman_maintain-1.2.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-03 13:23:43 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:

Description Gaurav Talreja 2022-12-16 18:29:42 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
Satellite 6.13.0 Snap 3.0

How reproducible:
Always

Steps to Reproduce:
1. # satellite-maintain upgrade list-versions

2. # satellite-maintain upgrade run --assumeyes --target-version=6.13.z --whitelist=repositories-validate,repositories-setup


Actual results:
Nothing to update, can't find new version of satellite-maintain.

Expected results:
upgrade path should exist for upgrading to 6.13 and 6.13.z

Additional info:
Comment 1 Evgeni Golov 2023-01-04 08:36:59 UTC 
Created redmine issue https://projects.theforeman.org/issues/35897 from this bug
Comment 2 Bryan Kearney 2023-01-04 12:03:20 UTC 
Upstream bug assigned to egolov
Comment 3 Bryan Kearney 2023-01-04 12:03:22 UTC 
Upstream bug assigned to egolov
Comment 4 Lukas Pramuk 2023-01-30 13:48:58 UTC 
VERIFIED.

@Satellite 6.13.0 Snap8
rubygem-foreman_maintain-1.2.3-1.el8sat.noarch


# foreman-maintain upgrade list-versions
Checking for new version of satellite-maintain...
Nothing to update, can't find new version of satellite-maintain.
6.12.z
6.13

>>> there are now 6.13 and 6.13.z scenarios for both Satellite and Capsule
Comment 7 errata-xmlrpc 2023-05-03 13:23:43 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.13 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-2023:2097