Bug 2108169

Summary:	foreman-maintain self-upgrade enables RH repos when custom repo mentioned with --maintenance-repo-label for RHEL8
Product:	Red Hat Satellite	Reporter:	Gaurav Talreja <gtalreja>
Component:	Satellite Maintain	Assignee:	Amit Upadhye <aupadhye>
Status:	CLOSED ERRATA	QA Contact:	Gaurav Talreja <gtalreja>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.11.1	CC:	ahumbe, apatel, aupadhye, kgaikwad
Target Milestone:	6.12.0	Keywords:	PrioBumpGSS, Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2122200 (view as bug list)		Environment:
Last Closed:	2022-11-16 13:34:39 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-07-18 13:55:33 UTC

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:

Comment 3 Gaurav Talreja 2022-09-08 14:47:03 UTC

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

Comment 4 Brad Buckingham 2022-09-12 13:36:19 UTC

Moving to VERIFIED on 6.12 based upon comment 3.

Comment 8 errata-xmlrpc 2022-11-16 13:34:39 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.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