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