Description of problem: The Configuration -> Settings -> Red Hat Updates tab only lists two repositories: Repository Name(s) cf-me-5.9-for-rhel-7-rpms rhel-server-rhscl-7-rpms However the 'Migrating to CloudForms 4.6" Guide now documents that a further three repositories are required: subscription-manager repos --enable=rhel-7-server-rpms \ --enable=cf-me-5.9-for-rhel-7-rpms \ --enable=rhel-7-server-optional-rpms \ --enable=rhel-7-server-supplementary-rpms \ --enable=rhel-7-server-extras-rpms \ --enable=rhel-server-rhscl-7-rpms Version-Release number of selected component (if applicable): 5.9.0.22 How reproducible: Every time Steps to Reproduce: 1. Navigate to Configuration -> Settings -> Red Hat Updates 2. Enter valid credentials and register the CFME appliance Actual results: Observe that only two repositories are listed Expected results: Five repositories should be listed Additional info: I think that perhaps the registration of an appliance for updates might be better done from the command line using appliance_console rather that from the WebUI?
Satoe, can you verify that these additional repos are required for install / update?
Not sure what "rhel-7-server-supplementary-rpms" is... all others listed in the Description are needed.
Verified on 5.9.2.0.20180320210136_355c506 that the following repos are now listed by default under Configuration -> (select Region) -> Red Hat Updates -> Edit Registration for a Red Hat Subscription: 'cf-me-5.9-for-rhel-7-rpms rhel-7-server-extras-rpms rhel-7-server-optional-rpms rhel-7-server-rpms rhel-server-rhscl-7-rpms' So this is all the repos listed initially in Peter's comment aside from 'rhel-7-server-supplementary-rpms', which Satoe indicated is not required.
The Migrating to CloudForms 4.6 document (https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/html/migrating_to_red_hat_cloudforms_4.6/) lists the rhel-7-server-supplementary-rpms repo as being needed. Where it has been identified that the repo is not needed it should be removed from the documentation as well.
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/RHSA-2018:1328