Bug 1963266

Summary:	[RFE]: Provide Capsule Load Balancer as an option for Global Registration Feature
Product:	Red Hat Satellite	Reporter:	Taft Sanders <tasander>
Component:	Registration	Assignee:	Leos Stejskal <lstejska>
Status:	CLOSED ERRATA	QA Contact:	Shweta Singh <shwsingh>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.9.0	CC:	ahumbe, aperotti, ehelms, gtalreja, ktordeur, lstejska, rfurlan, rlavi, shwsingh, thadzhie
Target Milestone:	6.13.0	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-03 13:20:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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. ***