Bug 1659414

Summary:	force-content-source does not work in an loadbalanced scenario
Product:	Red Hat Satellite	Reporter:	Evgeni Golov <egolov>
Component:	Bootstrap	Assignee:	Evgeni Golov <egolov>
Status:	CLOSED ERRATA	QA Contact:	Stephen Wadeley <swadeley>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	bkearney, ehelms, john.berninger, zhunting
Target Milestone:	6.7.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	katello-client-bootstrap-1.7.3-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:23:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1747581
Bug Blocks:

Description Evgeni Golov 2018-12-14 10:32:57 UTC

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:

Comment 4 Evgeni Golov 2019-09-26 12:34:55 UTC

this is blocked by #1747581

Comment 5 Evgeni Golov 2019-09-26 12:35:46 UTC

to be clear: *verification* of this is blocked

Comment 6 Stephen Wadeley 2019-09-26 13:10:47 UTC

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

Comment 7 Bryan Kearney 2020-03-05 15:59:07 UTC

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

Comment 10 errata-xmlrpc 2020-04-14 13:23:48 UTC

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