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.
Description of problem:
foreman-maintain self-upgrade command added in BZ 2026415 for updating rubygem-foreman_maintain from next stream, this is missing the bit for an upgrade from 6.10 to 7.0
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Verified.
Tested on Satellite & Capsule 6.10.4 Snap 2.0
Version: rubygem-foreman_maintain-0.8.24-1.el7sat.noarch
Steps:
1. # foreman-maintain self-upgrade --target-version 6.11
Observation:
1. self-upgrade disables all repositories(as well as stores data for repos to reenable later) on the system, then it only enables a new version-specific maintenance repository(labeled like "rhel-7-server-satellite-maintenance-<target-version>-rpms") and updates satellite-maintain and rubygem-foreman_maintain packages through it.
2. In case if repository label "rhel-7-server-satellite-maintenance-<target-version>-rpms" doesn't exist in CDN, then also self-upgrade passes, but doesn't update maintain packages, due to limitation mentioned in Comment 8 and hit BZ 2060396
3. For disconnected environments, add a custom repo for a new version-specific maintenance repository, export an environment variable "maintenance_repo='<repo-name/id>'" and pass any target-version, which enables repository with `'<repo-name/id>'` on the system after disabling all repos on the system and updates maintain packages.
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 Maintenance 6.10.4 Async 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/RHBA-2022:1115