Bug 2257331

Summary: Registering host through load balancer causes REX not to know what capsule to choose for 'registered_through'
Product: Red Hat Satellite Reporter: Odilon Sousa <osousa>
Component: Capsule - ContentAssignee: Jeremy Lenz <jlenz>
Status: CLOSED ERRATA QA Contact: Vladimír Sedmík <vsedmik>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 6.13.4CC: ahumbe, jlenz, lstejska, nalfassi, pmendezh, rlavi, saydas, shwsingh, vsedmik, zhunting
Target Milestone: 6.14.2Keywords: Regression, Triaged, UserExperience
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rubygem-katello-4.9.0.20-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2240956 Environment:
Last Closed: 2024-02-13 14:43:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 4 Vladimír Sedmík 2024-01-30 11:35:39 UTC 
Verified in 6.14.2 snap 2.0 using the load balanced setup (Satellite, 2 Capsules, HAproxy)

After registering or re-registering a host to a load balanced capsule (via global registration and `subscription-manager register --serverurl=...`) the host had the Content Source set properly and the REX commands run against the host succeeded.
Comment 9 errata-xmlrpc 2024-02-13 14:43:41 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.14.2 Async Security Update), 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:0797