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.
Description of problem:
The remote_execution_ssh_keys provisioning template (snippet)
Satellite WebUI -> Host -> Provisioning Templates > remote_execution_ssh_keys
seems to indicate that by creating a host or global parameter labelled
'remote_execution_ssh_keys' and setting the public key as the parameter value will ensure that the set value will be inserted into "~/.ssh/authorized_keys file" on the provisioned machine. However this does not work as
suggested. The template seems to be inserting the foreman-proxy key into authorized_keys file and not anything else.
Version-Release number of selected component (if applicable):
Satellite-6.6.0
Steps to Reproduce:
Navigate to Satellite WebUI -> Configure -> Host Groups -> <Hostgroup_Name> -> Parameters -> Host Group Parameters -> Add Parameter and enter below values.
Name: remote_execution_ssh_keys
Value: <Public_Key_To_Be_Deployed>
Once done, provision a new host using above host group.
Actual results:
My assumption is this is a setting that is
overridden somehow by foreman for the foreman-proxy key only and the global or host parameters are ignored contrary to the comments in the snippet template.
Expected results:
The key value set for 'remote_execution_ssh_keys' parameter should be inserted into "~/.ssh/authorized_keys file" on the provisioned machine.
Verified on Satellite 6.7 snap 10 with the pubkey supplied to the remote_execution_ssh_keys hostgroup parameter quoted in an array. The key is correctly resolved in the provisioning template and is present in authorized keys on provisioned host.
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
Description of problem: The remote_execution_ssh_keys provisioning template (snippet) Satellite WebUI -> Host -> Provisioning Templates > remote_execution_ssh_keys seems to indicate that by creating a host or global parameter labelled 'remote_execution_ssh_keys' and setting the public key as the parameter value will ensure that the set value will be inserted into "~/.ssh/authorized_keys file" on the provisioned machine. However this does not work as suggested. The template seems to be inserting the foreman-proxy key into authorized_keys file and not anything else. Version-Release number of selected component (if applicable): Satellite-6.6.0 Steps to Reproduce: Navigate to Satellite WebUI -> Configure -> Host Groups -> <Hostgroup_Name> -> Parameters -> Host Group Parameters -> Add Parameter and enter below values. Name: remote_execution_ssh_keys Value: <Public_Key_To_Be_Deployed> Once done, provision a new host using above host group. Actual results: My assumption is this is a setting that is overridden somehow by foreman for the foreman-proxy key only and the global or host parameters are ignored contrary to the comments in the snippet template. Expected results: The key value set for 'remote_execution_ssh_keys' parameter should be inserted into "~/.ssh/authorized_keys file" on the provisioned machine.