Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-27388 Newly provisioned systems get registered directly to the capsule instead of to the load balancer
  3. SAT-29445

[DEV] Newly provisioned systems get registered directly to the capsule instead of to the load balancer

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Capsule - Content
    • Sprint 142, Sprint 143, Sprint 144, Sprint 145, Sprint 146

      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.

       

      DEV Tracker for https://issues.redhat.com/browse/SAT-27388

              rhn-engineering-jlenz Jeremy Lenz
              satellite-jira-automation@redhat.com Satellite Jira-Automation
              Ian Ballou Ian Ballou
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: