Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1741520

Summary: foreman-maintain's message about EPEL repository presence is misleading, when you're an idiot
Product: Red Hat Satellite Reporter: Ben <ben.argyle>
Component: Satellite MaintainAssignee: Kavita <kgaikwad>
Status: CLOSED ERRATA QA Contact: Jameer Pathan <jpathan>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: apatel, inecas, jpathan, kgaikwad, mbacovsk
Target Milestone: 6.8.0Keywords: Triaged, UserExperience
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: rubygem-foreman_maintain-0.6.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:38:20 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 Ben 2019-08-15 11:11:22 UTC
Description of problem:
When running

 foreman-maintain upgrade check --target-version 6.5.z

leads to the following message:

[...]
--------------------------------------------------------------------------------
Check if EPEL repository enabled on system: 
\ Checking for presence of EPEL repository                            [OK]      
--------------------------------------------------------------------------------
[...]

if you're an idiot (like me), you think this means EPEL is required (and is enabled) on the Satellite server.  If you don't think to check /etc/yum.repos.d/ you get quite confused as to why a RH product, on RHEL, requires EPEL packages.


Version-Release number of selected component (if applicable):
All versions of Satellite, on RHEL7.

How reproducible:
Every time you forget to engage brain.

Steps to Reproduce:
1. Disengage brain
2. Run foreman-maintain
3. Honestly believe the text of the above isn't all that clear

Actual results:
All is well.

Expected results:
Now that I know what the text is getting at, I think I'd expect a better way of foreman-maintain saying "the EPEL repository isn't enabled, and that's good; all is well."

Additional info:
Please don't laugh at me too much.

Comment 3 Kavita 2020-04-17 14:03:03 UTC
Created redmine issue https://projects.theforeman.org/issues/29560 from this bug

Comment 4 Bryan Kearney 2020-05-14 16:01:16 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29560 has been resolved.

Comment 6 Kavita 2020-06-09 07:11:29 UTC
Hello Brad,

Yes, that's correct.
This is resolved in Satellite 6.8 so adding flag sat-6.8.0+ and moving to ON_QA.

Thank you!

Comment 11 errata-xmlrpc 2020-10-27 12:38:20 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 (Satellite 6.8 Satellite Maintenance 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/RHBA-2020:4365