Project

General

Profile

Actions

Bug #25970

closed

Remote execution bug again can't send back the report of the remote execution to the foreman

Added by Mario Gamboa about 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

The issue is in the smart_proxy_dynflow_core confguration

  1. Path to dynflow database, leave blank for in-memory non-persistent database
    :database:
  1. URL of the foreman, used for reporting back
    :foreman_url: 'http://localhost:3000'
  1. SSL settings for client authentication against Foreman
  2. :foreman_ssl_ca: ssl/foreman_ca.pem
  3. :foreman_ssl_key: ssl/foreman_key.pem
  4. :foreman_ssl_cert: ssl/foreman_cert.pem

:console_auth: false

  1. Set to true to make the core fork to background after start
  2. :daemonize: false
  3. :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

  1. URL of the foreman, used for reporting back
    :foreman_url: 'https://foreman.server'
  1. SSL settings for client authentication against Foreman
    :foreman_ssl_ca: ssl/foreman_ca.pem
    :foreman_ssl_key: ssl/foreman_key.pem

Related issues 1 (1 open0 closed)

Related to Foreman Remote Execution - Bug #20206: Remote Execution sending error after upgrade katello 3.4.3New07/05/2017Actions
Actions

Also available in: Atom PDF