Project

General

Profile

Actions
Copy link

Bug #16050

closed

Installer doesn't affect remote execution-related settings

Added by Ivan Necas about 8 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ivan Necas
Category:
-
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
1365956
Pull request:
https://github.com/theforeman/puppet-foreman_proxy/pull/282, https://github.com/theforeman/smart_proxy_dynflow/pull/26, https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/31
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1365956
Description of problem:
The smart_proxy_dynflow_core process expects it's configuration to live in a different directory than the rest of the proxy configs.

This makes changing those settings after installation frustrating, because this is not documented very well.

Version-Release number of selected component (if applicable):
6.2.0

How reproducible:

Steps to Reproduce:
1. Install Satellite 6.2
2. Try and change the REx working directories by changing the config file
3.

Actual results:
Doesn't work (settings are stored in a file that isn't used by smart_proxy_dynflow_core)

Expected results:
Either settings are stored in the file smart_proxy_dynflow_core uses, or smart_proxy_dynflow_core uses a file that is stored in the location the installer uses for config files

Additional info:
Ask Ivan Necas, he knows :)

Related issues 1 (0 open — 1 closed)

Copied to Installer - Bug #16886: Installer doesn't affect remote execution-related settings - cherry-pick request installer to 1.13ClosedDominic Cleal08/10/2016Actions
Actions
Copy link
 #1

Updated by Ivan Necas about 8 years ago

  • Subject changed from Installer doesn't affect remote execution-related settings to Installer doesn't affect remote execution-related settings
  • Target version set to 113
Actions
Copy link
 #2

Updated by Ivan Necas about 8 years ago

  • Status changed from New to Assigned
  • Assignee set to Ivan Necas
  • Target version changed from 113 to 127
Actions
Copy link
 #3

Updated by Ivan Necas about 8 years ago

  • Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/282 added
Actions
Copy link
 #4

Updated by Ivan Necas about 8 years ago

  • Status changed from Assigned to Ready For Testing
Actions
Copy link
 #5

Updated by Ivan Necas about 8 years ago

  • Pull request https://github.com/theforeman/smart_proxy_dynflow/pull/26 added
Actions
Copy link
 #6

Updated by Ivan Necas about 8 years ago

  • Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/31 added
Actions
Copy link
 #7

Updated by Ivan Necas about 8 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link
 #8

Updated by Ivan Necas almost 8 years ago

  • Copied to Bug #16886: Installer doesn't affect remote execution-related settings - cherry-pick request installer to 1.13 added
Actions
Copy link
 #9

Updated by Ivan Necas almost 8 years ago

A workaround should be:

  • configure the settings via installer
  • mkdir /etc/smart_proxy_dynflow_core/settings.d
    ln -s /etc/foreman-proxy/settings.d/remote_execution_ssh.yml /etc/smart_proxy_dynflow_core/settings.d/smart_proxy_remote_execution_ssh_core.yml
    service smart_proxy_dynflow_core restart
Actions
Copy link

Also available in: Atom PDF