Description of problem: In some situations, the new repos are not yet known on the client, and f-maintain aborts with Error: 'rhel-7-server-satellite-6.3-rpms' does not match a valid repository ID. Use "subscription-manager repos --list" to see valid repositories. If it would run "sub-man refresh" before, this would not happen. Version-Release number of selected component (if applicable): rubygem-foreman_maintain-0.1.3-1.el7sat.noarch
Upstream bug assigned to kgaikwad
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22686 has been resolved.
VERIFIED Version tested: # rpm -qa | grep maintain rubygem-foreman_maintain-0.1.5-1.el7sat.noarch Foreman-maintain includes the check to validate availability of repositories. If any repo is missing while validating, foreman-maintain run `subscription-manager refresh`. Steps: 1. only subscribed the server without any pool 2. foreman-maintain upgrade check --target-version 6.2 -------------------------------------------------------------------------------- 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 -------------------------------------------------------------------------------- For 6.3 upgrade, -------------------------------------------------------------------------------- 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.3-rpms, rhel-7-server-satellite-6.3-rpms --------------------------------------------------------------------------------
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