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:
When you have capsules deployed in an loadbalanced scenario, and try to use bootstrap.py with --force-content-source, it errors out, as the loadbalanced name is not known to the Satellite.

Version-Release number of selected component (if applicable):
katello-client-bootstrap-1.6.0-1.el7sat.noarch.rpm

How reproducible:
100%

Steps to Reproduce:
1. bootstrap.py --server loadbalanced.example.com --force-content-source …

Actual results:
"[ERROR], [2018-12-13 16:39:19], EXITING: [0 element in array for search key 'name="loadbalanced.example.com"' in API '/api/v2/smart_proxies'. Please note that all searches are case-sensitive. Fatal error.] failed to execute properly."

Expected results:
successful registration

Additional info:

this is blocked by #1747581

to be clear: *verification* of this is blocked

Hello

bootstrap code is fixed, issue in comment 0 no longer occurs. However, the command will not work correctly until the certificate generation code is fixed in BZ#1747581

I am moving this to 6.7.0 since Comment 6 ties this to a bug being delivered in 6.7.0.

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, 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-2020:1454