Description of problem: The satellite-maintain provides a self-upgrade command which accepts custom repository label. This repository can be used to update foreman-maintain and satellite-maintain packages from non RHSM repository in disconnected and test environments. The custom repository should be disable on completing the package update if it was not enabled on system. Version-Release number of selected component (if applicable): Satellite 6.11 How reproducible: Every time Steps to Reproduce: 1. Confirm that custom repository is not enabled 2. Run the satellite-maintain command with custom repo label # satellite-maintain self-upgrade --maintenance-repo-label custom-repo 3. Confirm that custom-repo stays enabled after completion of the run Actual results: custom repo stays enabled Expected results: custom repo should be disabled if it was not enabled already on system Additional info:
Created redmine issue https://projects.theforeman.org/issues/34854 from this bug
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34854 has been resolved.
We need to get 1.0.10 version with cherry picks : https://github.com/theforeman/foreman-packaging/pull/7887
Verified. Tested on Satellite 6.11.0 Snap 21.0 Version: rubygem-foreman_maintain-1.0.10-1.el7sat.noarch Steps: 1. Add custom repo (label: sat-maintain) with `enabled=0` for new maintenance repository. 2. # foreman-maintain self-upgrade --maintenance-repo-label sat-maintain 3. Update `s/enabled=0/enabled=1` in custom repo of new maintenance repository. 4. # foreman-maintain self-upgrade --maintenance-repo-label sat-maintain Observations: After executing a self-upgrade, the custom repo is disabled if it was previously disabled, and enabled if it had previously been enabled on the system.
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 (Moderate: Satellite 6.11 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-2022:5498