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.
Bug 1548362 - [RFE] foreman-maintain should check for unsupported repos
Summary: [RFE] foreman-maintain should check for unsupported repos
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Amit Upadhye
QA Contact: Nikhil Kathole
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-23 10:21 UTC by Evgeni Golov
Modified: 2020-03-05 16:22 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-05 16:22:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 23500 0 Normal Closed foreman-maintain should check for unsupported repos 2020-03-05 16:15:25 UTC

Description Evgeni Golov 2018-02-23 10:21:40 UTC 
Description of problem:
Currently, foreman-maintain will do (on a downstream install):
subscription-manager repos --disable '*'
subscription-manager repos --enable <the_repos_we_need>

However, this does not take into account repos not managed by sub-man.

I think it would be beneficial if f-m could check `yum repolist` (or /etc/yum.repos.d) for any upstream (Foreman, Katello, Puppet, Pulp, Candlepin) repos and disable them/warn the user if such are found.

Version-Release number of selected component (if applicable):
rubygem-foreman_maintain-0.1.3-1.el7sat.noarch
Comment 2 Amit Upadhye 2018-05-04 09:34:07 UTC 
Created redmine issue http://projects.theforeman.org/issues/23500 from this bug
Comment 4 Francisco Garcia 2018-05-22 07:17:29 UTC 
Just for clarification, I understand this RFE will *not* attempt to disable custom repos like 'MyFancyMonitoringTool' or 'MyFancyBackupTool'? :)
Comment 6 Bryan Kearney 2019-02-26 15:06:15 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/23500 has been resolved.
Comment 7 Kavita 2019-06-18 10:00:33 UTC 
Available in foreman-maintain version >= 0.4.0 so moving to ON_QA
Comment 8 Nikhil Kathole 2019-06-24 06:09:51 UTC 
VERIFIED

Version tested:
rubygem-foreman_maintain-0.4.3-1.el7sat.noarch

[check-upstream-repository] Check if any upstream repositories are enabled on system [pre-upgrade]

# foreman-maintain health check --label check-upstream-repository
Running ForemanMaintain::Scenario::FilteredScenario
================================================================================
Check if any upstream repositories are enabled on system: 
| Checking for presence of upstream repositories                      [OK]      
--------------------------------------------------------------------------------
Comment 9 Bryan Kearney 2020-03-05 16:22:44 UTC 
The current version of foreman_maintain includes this fix.
Note You need to log in before you can comment on or make changes to this bug.