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.
A commit was recently introduced to attempt to surmise when a host is being registered thru a load balancer.
To do this, candlepin_proxies_controller needs to look through ::SmartProxy.all to find smart proxies matching the hostname of the server receiving the registration request.
However, if there are smart proxies assigned to locations, and those locations are not the same locations assigned to the registering user (the --username passed to subscription-manager), Rails will act as if those smart proxies don't exist.
The effect is that Katello doesn't have access to its own list of smart proxies, and so doesn't know how to correctly assign a content source.
So the host will get registered, and its "registered_through" smart proxies for REX will be correct, but content source will be incorrectly nil.
Verified in 6.15.0 snap 6 using standard and load balanced setup.
With Capsule assigned to a location where the registering user does not belong to I was able to register a content host to that Capsule and verify the Content Source is set properly. In case of the LB setup the Content Source is set regardless the selection in the global registration (the first Capsule behind the load balancer is picked) which is expected since the content will be synced from the source with lower load.
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 (Important: Satellite 6.15.0 release), 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-2024:2010