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 1549080

Summary: foreman-maintain should check the availability for the repositories to be enabled in the pre-upgrade check
Product: Red Hat Satellite Reporter: Ivan Necas <inecas>
Component: Satellite MaintainAssignee: Swapnil Abnave <sabnave>
Status: CLOSED ERRATA QA Contact: Nikhil Kathole <nkathole>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: apatel, cdonnell, fgarciad, inecas, kgaikwad, mmccune, nkathole, omaciel
Target Milestone: UnspecifiedKeywords: PrioBumpGSS, PrioBumpQA, Triaged, Upgrades, VerifiedUpstream
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-04 14:02:54 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 Ivan Necas 2018-02-26 11:07:03 UTC
Description of problem:
As a user, I want to be warned about the repositories not being available before running into the maintanence mode/modifying part of the ugprades

Comment 2 Swapnil Abnave 2018-03-05 11:08:14 UTC
Created redmine issue http://projects.theforeman.org/issues/22762 from this bug

Comment 4 Satellite Program 2018-03-19 10:28:45 UTC
Upstream bug assigned to sabnave

Comment 6 Satellite Program 2018-03-20 00:28:13 UTC
Upstream bug assigned to sabnave

Comment 7 Nikhil Kathole 2018-03-26 10:42:36 UTC
VERIFIED

Version tested:
# rpm -qa | grep maintain
rubygem-foreman_maintain-0.1.5-1.el7sat.noarch

For 6.2/6.3,
--------------------------------------------------------------------------------
Validate availability of repositories:
/ Validating availability of repositories for 6.3                     [OK]
--------------------------------------------------------------------------------

For 6.1,
--------------------------------------------------------------------------------
Validate availability of repositories:
/ Validating availability of repositories for 6.2                     [OK]
--------------------------------------------------------------------------------

If repositories are not present,

--------------------------------------------------------------------------------
Validate availability of repositories:
/ Some repositories missing, calling `subscription-manager refresh`   [FAIL]
Following repositories are not available on your system: rhel-7-server-rpms, rhel-server-rhscl-7-rpms, rhel-7-server-satellite-maintenance-6-rpms, rhel-7-server-satellite-tools-6.2-rpms, rhel-7-server-satellite-6.2-rpms
--------------------------------------------------------------------------------

Comment 10 errata-xmlrpc 2018-04-04 14:02:54 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, 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-2018:0633