Remote execution keys regenerated on Katello 3.6 -> 3.7 upgrade

Support
1

Problem:
Following a Katello 3.6 - > 3.7 upgrade, the remote execution keys were wiped out and regenerated.

Expected outcome:

Keys to remain in place

Foreman and Proxy versions:
foreman-1.18.0-2.el7.noarch
foreman-proxy-1.18.0-1.el7.noarch

Foreman and Proxy plugin versions:
tfm-rubygem-foreman_remote_execution-1.5.4-1.fm1_18.el7.noarch
rubygem-smart_proxy_remote_execution_ssh-0.2.0-2.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.1.2-2.el7.noarch

Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]

2

Hi,
do you have installer log from the upgrade?

3

There is an issue in the installer that it isn’t aware of the new location we chose for this. Generating files in /usr/share/foreman-proxy is a bad practice so in our RPM packaging we moved it to /var/lib/foreman-proxy. We still need to do the same on the Debian side and make the installer aware of this. For now the workaround is to set --foreman-proxy-plugin-remote-execution-ssh-identity-dir /var/lib/foreman-proxy/.ssh. The RPM package should have moved your keys there as well.

4

Thanks.

I used --foreman-proxy-plugin-remote-execution-ssh-ssh-identity-dir /var/lib/foreman-proxy/ssh and it fixed me right up.

I appreciate the pointer and I totally agree with moving this location. It never felt right having this live in /usr/share.