Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/configuring_capsules_with_a_load_balancer/index#registering-clients-using-the-host-registration

Section Number and Name: 

6.1. Red Hat Satellite host registration

6.2. (Deprecated) Registering Clients Using the Bootstrap Script

6.3. (Deprecated) Registering Clients Manually with katello-ca-consumer rpm


Describe the issue: 
Need Proper Registration method in Load-balancing capsule setup for a clients 

We would like to explore using the methods detailed in Section 6.1 (6.1. Red Hat Satellite host registration) but we can't seem to use our load balancer FQDN in making a successful registration. We tried using the --smart-proxy option and attached the load balancer FQDN as the value for it but it failed. It somehow defaults to being registered directly to the Satellite server.


Suggestions for improvement: 

If the commands or the tools/options are not applicable then we need to remove them from the documentation. 

Even if it is Deprecated but is useful then there has to be a clear instruction that we can use it. 




Additional information:

To have a proper load-balanced Capsule support documentation for Global Registration method, https://bugzilla.redhat.com/show_bug.cgi?id=1963266 needs to be fixed first.

That being said, for now, we can update the "6.1. Red Hat Satellite host registration" section to include the following command that must be manually performed by the user after hitting the registration API:


subscription-manager config \
  --rhsm.baseurl=https://loadbalancer.example.com/pulp/content \
  --server.hostname=loadbalancer.example.com

PR created: https://github.com/theforeman/foreman-documentation/pull/1493

PR merged into master. Here are the published docs links for refernce:
Downstream docs:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/configuring_capsules_with_a_load_balancer/index#registering-clients-using-the-host-registration

Upstream docs:
https://theforeman-foreman-documentation-preview-pr-1493.surge.sh/nightly/Configuring_Load_Balancer/index-satellite.html#registering-clients-using-the-host-registration

no more updates are pending on this issue, hence closing this one. In case any more updates are required in this issue, feel free to reopen this issue or create a new one.

Thank you :)