Plugins » Foreman Remote Execution

Is there a fix for this? I just started having this problem on one of my Foreman servers. Please let me know, thanks!

Foreman: 1.15.6-1
Katello: 3.4.5-1

tfm-rubygem-foreman_remote_execution-1.3.7-1.fm1_15.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.0.6-1.fm1_15.el7.noarch
tfm-rubygem-hammer_cli_foreman_remote_execution-0.0.5-2.fm1_12.el7.noarch

Workaround is to purge /usr/share/foreman-proxy/.ssh/known_hosts (or just remove the one conflicting record) on Foreman (or Smart Proxies). Permanent workaround is to make /usr/share/foreman-proxy/.ssh/known_hosts a symlink to /dev/null so the issue won't happen again when the host keys change again. But please bear in mind this is supposed to be a security feature which may indicate something went wrong.

OK that makes sense. Thanks for pointing me to the location of where the known_hosts file is for the foreman-proxy user.

The hosts which are offending at the moment are test provisioning servers. So what I am going to do and others who are in my situation should do and ONLY for machines that you plan to provision over and over for testing is to use a /usr/share/foreman-proxy/.ssh/config file and define ONLY those servers have a /dev/null UserKnownHostsFile: i.e. ->

Host hostname.domain.com
  UserKnownHostsFile=/dev/null
  StrictHostKeyChecking=no

I think clearing the known_hosts file will solve a one time conflict but symlinking known_hosts to /dev/null would be less secure that using the above if the situation calls for it. My 2 cents ;)

Thanks!