Document link: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/automating_system_administration_by_using_rhel_system_roles/using-the-rhc-system-role-to-register-the-system_automating-system-administration-by-using-rhel-system-roles#registering-system-with-satellite-using-rhc-system-role_using-the-rhc-system-role-to-register-the-system

Section number and name: 

22.2. Registering a system with Satellite by using the rhc RHEL system role 

Describe the issue:

The section describes the use of the rhc system role to register systems to Satellite.

The rhc system role does not correctly register systems at this time. E.g. the certificate is missing (see RHEL-37838).

Impact of this issue:

The procedure as described leaves the system registered to Satellite but with an incomplete setup that prevents dnf using the repositories on Satellite.

Suggestions for improvement:

Customers should use the registration_command module from the redhat.satellite collection instead (https://console.redhat.com/ansible/automation-hub/repo/published/redhat/satellite/content/module/registration_command/) in this scenario.
Then use the rhc system role to enable/disable repositories.