Problem: Remote Execution of SSH Commands Fail with RestClient::NotFound -404
Expected outcome: It Should be executed successfully
Foreman and Proxy versions: 3.1.2
Foreman and Proxy plugin versions: Foreman Remote Execution Version 5.0.6
Distribution and version: CentOS 7
Other relevant data:
I am getting below error when executing remote ssh commands on target hosts.
#####################################
Host,stdout,stderr,debug,Result,Finished
###############################################################
Foreman Proxy logs
##############################################################xproorchestrator05.admiral-eu.com ”]xproorchestrator05.admiral-eu.com ”]xproorchestrator05.admiral-eu.com ”]xproorchestrator05.admiral-eu.com ”]xproorchestrator05.admiral-eu.com ”]xproorchestrator05.admiral-eu.com ”]
################################################################################
Please do post the entire log, not just selected parts.
It is the entire log. Nothing else is there apart from this.
##########################################xproorchestrator05.admiral-eu.com ”]xproorchestrator05.admiral-eu.com ”]xproorchestrator05.admiral-eu.com ”]xproorchestrator05.admiral-eu.com ”]xproorchestrator05.admiral-eu.com ”]xproorchestrator05.admiral-eu.com ”]
The service should be logging since it started. The logs might have been rotated to another, but it should not just vanish
proxy.log (44.9 KB)
If you need any other logs do please let me know
This is the relevant bit
2022-08-03T09:03:43 [W] Error details for Couldn't enable 'ssh': <RuntimeError>: Ssh public key file /var/lib/foreman-proxy/ssh/id_rsa.pub doesn't exist
/opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_remote_execution_ssh-0.5.2/lib/smart_proxy_remote_execution_ssh.rb:20:in `validate!'
/opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_remote_execution_ssh-0.5.2/lib/smart_proxy_remote_execution_ssh/plugin.rb:36:in `block in <class:Plugin>'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:228:in `class_eval'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:228:in `configure_plugin'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:109:in `block in configure'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:109:in `each'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:109:in `configure'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:187:in `each'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:187:in `initialize_plugins'
/usr/share/foreman-proxy/lib/launcher.rb:173:in `launch'
/usr/share/foreman-proxy/bin/smart-proxy:6:in `<main>'
this is the root cause, or at least for now
After fixing the above issue now I am getting the below issue
#######################################
Hey Guys,
One more thing I have an old foreman setup in which this remote execution is working fine and the new one is configures exactly same as the old one. I am attaching the old foreman proxy logs as well.old_foreman_proxy.log (13.4 KB)
There was a thread opened yesterday by you where the main topic was the exact error you’re hitting now. Maybe you didn’t really resolve that?
On a side note, claiming that two foreman instances are configured exactly the same way is a bold claim, even though it might appear so on the surface.
gvde
August 3, 2022, 8:14am
11
That’s exactly the error message from your thread Remote Execution Fails
So this should continue there and you should really fix your SSH keys…
It got resolved with changing the keys. What I really understood from yesterday till now that on new foreman setup dynflow is not working but on old its running.
############## New Foreman Output ###############################
#########################################################
############ Old Foreman Output #########################https://theforeman.org
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
#################################################################################
So if you could help me in this how I could really start dynflow on the new setup
gvde
August 3, 2022, 8:21am
13
A lot has changed between foreman 1.17 and foreman 3.1.
Simply run
# foreman-maintain health check
and it tells you if everything needed is running.
Do not attempt to activate or start deprecated services only because they were running on foreman 1.17…
Looks Like Everything is all good on new foreman
############################################################
[root@xproorchestrator05 smart_proxy_dynflow]#
#####################################################################################
I also found out that dynflow core rubygem is of foreman 2 version is that ok?
[root@xproorchestrator05 smart_proxy_dynflow]# rpm -qa|grep -i dynflowtfm-rubygem-smart_proxy_dynflow_core-0.4.1-1.fm2_6.el7.noarch
gvde
August 3, 2022, 9:53am
16
Well, it depends. You wrote in the other thread that this is a new server. Now it looks like you have upgraded. If you have upgraded from 1.17 to 3.1.2 you do understand that you have to go through all intermediate versions as well? If you install 3.1.2 on a new server it won’t install that rpm.
I have installed it on new server. i never did upgrade. As you could see in my outputs I have 2 server running.
gvde
August 3, 2022, 10:13am
18
Well, then it’s probably still in use, but never been repackaged specifically for 3.1. It’s going to be removed with 3.2 anyway.
Ok now back to my problem of remote execution
gvde
August 3, 2022, 10:46am
20
What problem? You wrote you have resolved the issue, the one here as well as the one in the other thread.
