Description of problem:

1) When load balancer is configured and customer want to register the system to one of the capsule but the load balancer is down, in that scenario global registration is getting failed and unable to register to capsule though capsule server is running.

How reproducible:

Always

Is this issue a regression from an earlier version:

No, as in lower versions we had katello-ca-consumer file to register but as in satellite 6.16 this got removed, started facing this issue.

Steps to Reproduce:

1. Ensure loadbalancer is not reachable, however rest of 2 capsules are reachable , the global registration method fails when try to register to one of the reachable capsule using global registration template. And its time consuming process as it takes 4m27.799s to process this request via global registration template.

2. As all things of customer environment are automated, can't run manual commands like subscription-manager clean directly when load balancer is unreachable to unregister the system.

3. And this leads to time consuming process of registration where normal registration works just in 12 seconds.

Actual behavior:

Global Registration fails, and takes longer than normal.

Expected behavior:

Global registration should not take longer than normal registration time.

Business Impact / Additional info:

Delaying the provisioning, patching activity.