Bug #28483
closedThe host or global parameter 'remote_execution_ssh_keys' is ignored during provisioning
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1781402
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.