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