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 enables RH repos along with custom repo mentioned with --maintenance-repo-label for RHEL8, whereas for RHEL7 it only enables custom repo, which was identified while testing BZ 2087753

Version-Release number of selected component (if applicable):
Satellite 6.11.1 Snap 2
rubygem-foreman_maintain-1.0.14-1.el8sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Add repo for next major version maintenance repo under /etc/yum.repos.d/ for disconnected/testing environment.
2. # foreman-maintain self-upgrade --maintenance-repo-label sat-maintain
3.

Actual results:
self-upgrade enables RH repos along with custom repo for el8

Expected results:
self-upgrade should enable only custom repo for el8

Additional info:

Hi Brad,

Yes, this has already been fixed for 6.12 by mentioned PR, but not as part of any bugzilla, and I've verified a 6.11.3 clone of this bugzilla, so yes we can move this to closed/verified state.

Thanks,
Gaurav

Moving to VERIFIED on 6.12 based upon comment 3.

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.12 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:8506