How to update remoteExecution SSH key properly? and where?

Support
1

Hi, folks!

I can't figure out where remoteExecution plugin keeps the old version of
SSH pub key - I've replaced the old id_rsa and id_rsa.pub, updated
/etc/foreman-proxy/settings.d/remote_execution_ssh.yml with a proper path
to new id_rsa file, restarted foreman-proxy, foreman-tasks and
httpd/foreman, but both host YAML and templates for the hosts still show me
the old public key.

The strangest part is that Foreman remoteExec API
https://localhost:8443/ssh/pubkey shows me the correct, new public key.

What am I missing? I'm on Foreman 1.10.1 and remoteExec 0.2.3 running on
CentOS7.1.

Thanks!

2

> From: "'Konstantin Orekhov' via Foreman users" <foreman-users@googlegroups.com>
> To: "Foreman users" <foreman-users@googlegroups.com>
> Sent: Monday, April 18, 2016 3:34:06 PM
> Subject: [foreman-users] How to update remoteExecution SSH key properly? and where?
>
> Hi, folks!
>
> I can't figure out where remoteExecution plugin keeps the old version of
> SSH pub key - I've replaced the old id_rsa and id_rsa.pub, updated
> /etc/foreman-proxy/settings.d/remote_execution_ssh.yml with a proper path
> to new id_rsa file, restarted foreman-proxy, foreman-tasks and
> httpd/foreman, but both host YAML and templates for the hosts still show me
> the old public key.
>
> The strangest part is that Foreman remoteExec API
> https://localhost:8443/ssh/pubkey shows me the correct, new public key.
>
> What am I missing? I'm on Foreman 1.10.1 and remoteExec 0.2.3 running on
> CentOS7.1.

It's stored in the database in Foreman. If you go to the Smart Proxy's page
and click "Refresh" under the actions it will refresh the key.

If you'd like, you can file an issue in our tracker, we should probably make
this more obvious, perhaps using the new Smart Proxy status widgets.

http://projects.theforeman.org/projects/foreman_remote_execution/issues/new

··· ----- Original Message -----

Thanks!

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

3

Yes, that worked - thanks!
And yes, this needs to be more obvious, at least documented. Konstantin Orekhov

··· From: Stephen Benjamin To: foreman-users@googlegroups.com Sent: Monday, April 18, 2016 1:56 PM Subject: Re: [foreman-users] How to update remoteExecution SSH key properly? and where?

----- Original Message -----

From: “‘Konstantin Orekhov’ via Foreman users” foreman-users@googlegroups.com
To: “Foreman users” foreman-users@googlegroups.com
Sent: Monday, April 18, 2016 3:34:06 PM
Subject: [foreman-users] How to update remoteExecution SSH key properly? and where?

Hi, folks!

I can’t figure out where remoteExecution plugin keeps the old version of
SSH pub key - I’ve replaced the old id_rsa and id_rsa.pub, updated
/etc/foreman-proxy/settings.d/remote_execution_ssh.yml with a proper path
to new id_rsa file, restarted foreman-proxy, foreman-tasks and
httpd/foreman, but both host YAML and templates for the hosts still show me
the old public key.

The strangest part is that Foreman remoteExec API
https://localhost:8443/ssh/pubkey shows me the correct, new public key.

What am I missing? I’m on Foreman 1.10.1 and remoteExec 0.2.3 running on
CentOS7.1.

It’s stored in the database in Foreman. If you go to the Smart Proxy’s page
and click “Refresh” under the actions it will refresh the key.

If you’d like, you can file an issue in our tracker, we should probably make
this more obvious, perhaps using the new Smart Proxy status widgets.

http://projects.theforeman.org/projects/foreman_remote_execution/issues/new

Thanks!

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to a topic in the Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/rDjhYmcQSvI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.