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.
Bug 2254612 - Registration can't find any Capsules when their locations are not assigned to admin user
Summary: Registration can't find any Capsules when their locations are not assigned to...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule - Content
Version: 6.15.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.15.0
Assignee: Jeremy Lenz
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-14 20:50 UTC by Jeremy Lenz
Modified: 2024-04-23 17:16 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2257332 (view as bug list)
Environment:
Last Closed: 2024-04-23 17:16:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36989 0 Normal Ready For Testing Registration can't find any smart proxies when their locations are not assigned to admin user 2023-12-18 17:59:41 UTC
Red Hat Issue Tracker SAT-21949 0 None None None 2023-12-14 20:52:26 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:16:23 UTC

Description Jeremy Lenz 2023-12-14 20:50:05 UTC 
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.
Comment 1 Jeremy Lenz 2023-12-14 20:50:08 UTC 
Created from redmine issue https://projects.theforeman.org/issues/36989
Comment 2 Jeremy Lenz 2023-12-14 20:50:10 UTC 
Upstream bug assigned to None
Comment 6 Bryan Kearney 2023-12-15 00:02:48 UTC 
Upstream bug assigned to jlenz
Comment 7 Bryan Kearney 2023-12-15 00:02:51 UTC 
Upstream bug assigned to jlenz
Comment 9 Bryan Kearney 2023-12-19 20:02:55 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36989 has been resolved.
Comment 10 Vladimír Sedmík 2024-01-17 08:38:58 UTC 
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.
Comment 13 errata-xmlrpc 2024-04-23 17:16:22 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 (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
Note You need to log in before you can comment on or make changes to this bug.