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):
Steps to Reproduce:
Navigate to Satellite WebUI -> Configure -> Host Groups -> <Hostgroup_Name> -> Parameters -> Host Group Parameters -> Add Parameter and enter below values.
Once done, provision a new host using above host group.
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.
The key value set for 'remote_execution_ssh_keys' parameter should be inserted into "~/.ssh/authorized_keys file" on the provisioned machine.
Created redmine issue https://projects.theforeman.org/issues/28483 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28483 has been resolved.
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.