Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Bug 1568838

Summary:	[RFE] Handle multiple capsules' ssh keys
Product:	Red Hat Satellite	Reporter:	François Cami <fcami>
Component:	Remote Execution	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3.1	CC:	akarsale, apatel, aruzicka, egolov, fcami, inecas, mhulan, pcreech
Target Milestone:	6.5.0	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-14 12:37:13 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:

Description François Cami 2018-04-18 10:15:04 UTC

Description of problem:

In an environment where capsule servers are added when capacity requires it, it is desirable to maintain the list of capsule servers' public keys centrally.

As not all clients have access to all the capsule due to network firewalls, either the Satellite has to maintain that list to be able to feed it to clients when they register through bootstrap.py or we need to have an API call that would pull all capsules' ssh keys and feed it back to the caller.

I'd rather we did #2, perhaps with caching mechanism.

Comment 2 Brad Buckingham 2018-04-19 16:34:32 UTC

Related to bug 1568848

Comment 4 Adam Ruzicka 2018-07-03 07:20:34 UTC

Created redmine issue http://projects.theforeman.org/issues/24136 from this bug

Comment 5 Satellite Program 2018-09-26 12:04:24 UTC

Upstream bug assigned to aruzicka

Comment 6 Satellite Program 2018-09-26 12:04:28 UTC

Upstream bug assigned to aruzicka

Comment 7 Satellite Program 2018-10-02 16:04:37 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24136 has been resolved.

Comment 8 Peter Ondrejka 2018-11-08 09:32:19 UTC

Verified on Satellite 6.5 snap 2, the API exposes remote_execution_pubkey for capsule as requested

Comment 11 errata-xmlrpc 2019-05-14 12:37:13 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-2019:1222