Document URL: https://access.redhat.com/documentation/en-us/red_hat_update_infrastructure/4/html-single/installing_red_hat_update_infrastructure/index#assembly_setting-up-cds-nodes_installing-red-hat-update-infrastructure Section Number and Name: 6.1. Registering the CDS node 6.3. Enabling the required repositories on the CDS node 7.1. Registering the HAProxy node 7.3. Enabling the required repositories on the HAProxy node Describe the issue: For non-SCA (simple content access) environments --type=rhui is required to subscribe to 'Red Hat Update Infrastructure and RHEL Add-Ons for Providers' using 'subscription-manager register'. It should be similar to the one used in 'Registering the RHUA node' section. If the node is registered with --type=rhui and attached to 'Red Hat Update Infrastructure and RHEL Add-Ons for Providers' then it should consume a different set of repositories: === with -rhui- suffix rhel-8-for-x86_64-appstream-rhui-rpms rhel-8-for-x86_64-baseos-rhui-rpms rhceph-5-tools-for-rhel-8-x86_64-rhui-rpms === instead of: === rhel-8-for-x86_64-appstream-rpms rhel-8-for-x86_64-baseos-rpms rhceph-5-tools-for-rhel-8-x86_64-rpms === Suggestions for improvement: Correct the list of enabled repositories and the 'subscription-manager register' command in non-SCA sections accordingly. Additional information:
The RHUI consumer type is really only needed on the RHUA node. This consumer type provides access to the RHUI 4 repository, which contains the packages required on the RHUA node such as rhui-tools or various Pulpcore builds. The CDS and HAProxy nodes don't run any software from the RHUI 4 repository. Therefore, they can be registered as the default consumer type and use the standard RHEL repositories. Note that this was different in RHUI 3.
That would lead to using another subscription pool on the CDS and HAProxy nodes (anything that provides "Red Hat Enterprise Linux"). I reckon we need to streamline this procedure even more by using the same pool or consuming the content from the RHUA.