Bug #25970
closed
Remote execution bug again can't send back the report of the remote execution to the foreman
Description
The issue is in the smart_proxy_dynflow_core confguration
- Path to dynflow database, leave blank for in-memory non-persistent database
:database:
- URL of the foreman, used for reporting back
:foreman_url: 'http://localhost:3000'
- SSL settings for client authentication against Foreman
- :foreman_ssl_ca: ssl/foreman_ca.pem
- :foreman_ssl_key: ssl/foreman_key.pem
- :foreman_ssl_cert: ssl/foreman_cert.pem
:console_auth: false
- Set to true to make the core fork to background after start
- :daemonize: false
- :pid_file: /var/run/foreman-proxy/smart_proxy_dynflow_core.pid
as you can see the foreman_url is pointing to the localhost that is incorrect must be the point to the foreman server
as workaround
- URL of the foreman, used for reporting back
:foreman_url: 'https://foreman.server'
- SSL settings for client authentication against Foreman
:foreman_ssl_ca: ssl/foreman_ca.pem
:foreman_ssl_key: ssl/foreman_key.pem
Updated by Mario Gamboa over 5 years ago
- Related to Bug #20206: Remote Execution sending error after upgrade katello 3.4.3 added
Updated by Ivan Necas over 5 years ago
What procedure has been followed to set up the instance? Is this manual configuration or an installer has been used?
Updated by Mario Gamboa over 5 years ago
From REX documentation 1.3
foreman-installer --enable-foreman-plugin-remote-execution\
--enable-foreman-proxy-plugin-remote-execution-ssh
mkdir ~foreman-proxy/.ssh
chown foreman-proxy ~foreman-proxy/.ssh
sudo -u foreman-proxy ssh-keygen -f ~foreman-proxy/.ssh/id_rsa_foreman_proxy -N ''
restorecon -RvF ~foreman-proxy/.sshservice httpd restart
service foreman-tasks restart
service foreman-proxy restart
service smart_proxy_dynflow_core restart
That's it
Updated by Justin Sherrill over 5 years ago
- Project changed from Katello to Foreman Remote Execution
- Category deleted (
Orchestration)
Updated by Ivan Necas over 5 years ago
Have the installer finished successfully? When I tested with nighties, everything worked as expected (I'm also not aware of any related changes to this) recently:
foreman-installer --enable-foreman-plugin-remote-execution --enable-foreman-proxy-plugin-remote-execution-ssh --disable-system-checks
Installing Done [100%] [.......................]
Success!
* Katello is running at https://centos7-katello-nightly.example.com
* To install an additional Foreman proxy on separate machine continue by running:
foreman-proxy-certs-generate --foreman-proxy-fqdn "$FOREMAN_PROXY" --certs-tar "/root/$FOREMAN_PROXY-certs.tar"
The full log is at /var/log/foreman-installer/katello.log
[root@centos7-katello-nightly ~]# cat /etc/smart_proxy_dynflow_core/settings.yml
---
# Path to dynflow database, leave blank for in-memory non-persistent database
:database:
:console_auth: true
# URL of the foreman, used for reporting back
:foreman_url: https://centos7-katello-nightly.example.com
# SSL settings for client authentication against foreman.
:foreman_ssl_ca: /etc/foreman-proxy/foreman_ssl_ca.pem
:foreman_ssl_cert: /etc/foreman-proxy/foreman_ssl_cert.pem
:foreman_ssl_key: /etc/foreman-proxy/foreman_ssl_key.pem
# Listen on address
:listen: 0.0.0.0
# Listen on port
:port: 8008
:use_https: true
:ssl_ca_file: /etc/foreman-proxy/ssl_ca.pem
:ssl_certificate: /etc/foreman-proxy/ssl_cert.pem
:ssl_private_key: /etc/foreman-proxy/ssl_key.pem
Updated by Mario Gamboa over 5 years ago
- Status changed from New to Resolved
i just upgrade to the latest version 3.11 and is solved