-
Bug
-
Resolution: Done-Errata
-
Major
-
6.15.1.1
-
Phoenix - Subscriptions
-
2
-
False
-
foreman-cli-3.12.0.6, rubygem-katello-4.14.0.8
-
Important
-
Sprint 146
-
None
-
None
-
None
-
To Do
Description of problem:
This is only the case via provisioning template. When is try to provisions a new system.
After upgrade to Satellite 6.15 content source no longer shows registered through load balance but instead points to a specific capsule.
Instead, if you try re-register a system already registered works as expected I mean showing the LB and not eventually capsule-fqdn
Steps to Reproduce:
1. Satellite - Capsule - Load Balancer
2. provisions a new system
3. Register the new system selecting a capsule
Actual behavior
When It try to register a new system select "any of the capsules" ,somehow ends up registered directly to the capsule and not show the LB
Expected behavior:
When I provision a new host and I want register it, should be registered showing LB and no capsule FQDN.
- clones
-
SAT-27388 Newly provisioned systems get registered directly to the capsule instead of to the load balancer
-
- Testing
-
- links to
-
RHSA-2025:146558 Satellite 6.16.3 Async Update