Bug 1694073

Summary: Incorrect repository when registering CloudForms in the UI
Product: Red Hat CloudForms Management Engine Reporter: Ryan Spagnola <rspagnol>
Component: UI - OPSAssignee: Brian McLaughlin <bmclaugh>
Status: CLOSED ERRATA QA Contact: Jaroslav Henner <jhenner>
Severity: medium Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: 5.10.0CC: bmclaugh, bmidwood, dmetzger, hkataria, jprause, lavenel, mpovolny, mshriver, obarenbo, simaishi
Target Milestone: GAKeywords: ZStream
Target Release: 5.10.4   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: 5.10.4.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-21 05:46:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:

Description Ryan Spagnola 2019-03-29 12:53:30 UTC
Description of problem:
Following the documentation [1] it lists the rhel-7-server-rh-common-rpms
The UI is missing this repo and instead lists rhel-7server-optional-rpms which is not in the documentation.

Version-Release number of selected component (if applicable):
5.10

How reproducible:
Always

Steps to Reproduce:
1. Settings > Region > Red Hat Updates
2. click Edit Registration

Actual results:
Default repos have the discrepancy

Expected results:
repos match documentation

Additional info:
https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.7/html-single/migrating_to_red_hat_cloudforms_4.7/#preparing_for_migration46

Comment 6 Jaroslav Henner 2019-05-02 10:22:11 UTC
There are these repos:

rhel-7-server-rpms
cf-me-5.10-for-rhel-7-rpms
rhel-7-server-extras-rpms
rhel-7-server-ansible-2.7-rpms
rhel-7-server-rh-common-rpms
rhel-server-rhscl-7-rpms

Which seems to match the documentation.

Comment 8 errata-xmlrpc 2019-05-21 05:46: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-2019:1247