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 1963266 - [RFE]: Provide Capsule Load Balancer as an option for Global Registration Feature
Summary: [RFE]: Provide Capsule Load Balancer as an option for Global Registration Fea...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Registration
Version: 6.9.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: 6.13.0
Assignee: Leos Stejskal
QA Contact: Shweta Singh
URL:
Whiteboard:
: 1919991 2143328 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-21 20:47 UTC by Taft Sanders
Modified: 2024-01-03 13:24 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-03 13:20:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35351 0 Normal New Provide Proxy Load Balancer as an option for Global Registration 2022-08-10 05:31:23 UTC
Github Katello katello pull 10315 0 None Merged Fixes #35627 - Use proxy registration_url from Proxy in registration 2022-11-08 08:13:19 UTC
Github theforeman foreman pull 9464 0 None Merged Fixes #35626 - Registration & proxy's registration_url 2022-11-08 08:13:19 UTC
Github theforeman puppet-foreman_proxy_content pull 432 0 None Merged Fixes #35681: Use registration_url for RHSM and Pulp content URL 2022-12-19 12:53:12 UTC
Github theforeman smart-proxy pull 850 0 None Merged Fixes #35639 - registration_url setting for Registration module 2022-11-08 08:13:19 UTC
Red Hat Product Errata RHSA-2023:2097 0 None None None 2023-05-03 13:20:50 UTC

Internal Links: 2143328

Description Taft Sanders 2021-05-21 20:47:47 UTC 
Description of problem:
Currently the only options to set the capsule to as a global registration feature is the Satellite and Capsules (internal and external capsules with the Registration feature on foreman-proxy).
This RFE is to request the ability to select any and all load balancers for Capsules as part of the registration template process. This would provide users with the ability to let the load balancer decide on the registration path of the client at the time to of the request.

Version-Release number of selected component (if applicable):
6.9

How reproducible:
n/a

Steps to Reproduce:
1.
2.
3.

Actual results:
Only Satellite and Capsule that include the Registration feature on foreman-proxy show up on the list.

Expected results:
Load balancers would also be listed to allow users to select a load balancer to have the clients set to register to.

Additional info:
This is a POST RFE for https://bugzilla.redhat.com/show_bug.cgi?id=1963264

It would also be really nice to see the LB on the list then see the capsules nested under each LB on the list. As an informative illustration of which capsules belong to which LBs.
Example:
satellite.example.com
lb1.example.com
|
--capsule1.example.com
|
--capsule2.example.com
lb2.example.com
|
--capsule3.example.com
|
--capsule4.example.com
Comment 2 Riccardo Furlan 2022-11-24 13:34:33 UTC 
*** Bug 2143328 has been marked as a duplicate of this bug. ***
Comment 3 Leos Stejskal 2022-12-19 12:53:13 UTC 
Last PR [0] have been merged,
@ehelms are there any other tasks that needs to be done
or can we move it to the POST?

[0] https://github.com/theforeman/puppet-foreman_proxy_content/pull/432
Comment 4 Shweta Singh 2023-02-28 05:16:37 UTC 
Verified.

Version Tested: Satellite 6.13.0 Snap 8.0

Verification Steps:
1. Install 2-3 capsules and setup haproxy.
2. Setup content for haproxy installation.
3. Try to register a host.

Result:
Registered host is configured to the haproxy & can consume data.
Comment 7 errata-xmlrpc 2023-05-03 13:20:33 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.13 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-2023:2097
Comment 8 nalfassi 2023-05-16 08:06:01 UTC 
*** Bug 1919991 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.