Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1371674 - Remote execution does not obey remote-working-dir setting for foreman-proxy configuration
Summary: Remote execution does not obey remote-working-dir setting for foreman-proxy c...
Keywords:
Status: CLOSED DUPLICATE of bug 1365956
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-30 18:41 UTC by Craig Donnelly
Modified: 2021-06-10 11:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-19 11:19:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Craig Donnelly 2016-08-30 18:41:20 UTC 
Description of problem:
Environments where we are not able to use '/var/tmp' for example because of security concerns where people have configured noexec or otherwise are required to change the remote directory used for remote execution scripts.
When running:

# satellite-installer --foreman-proxy-plugin-remote-execution-ssh-remote-working-dir "<directory>"

This does correctly update the configuration file located at: /etc/foreman-proxy/settings.d/remote_execution_ssh.yml

However, this configuration change is ignored by Satellite and all jobs are still created in the default location of '/var/tmp'.

Version-Release number of selected component (if applicable):
Satellite 6.2.1:
rubygem-smart_proxy_remote_execution_ssh-0.1.2-2.el7sat.noarch
tfm-rubygem-smart_proxy_remote_execution_ssh_core-0.1.2-1.el7sat.noarch

How reproducible:
100%

Steps to Reproduce:
1. Run # satellite-installer --foreman-proxy-plugin-remote-execution-ssh-remote-working-dir "<directory>" (for example /tmp)
2. Run a job against a host.
3. Look at new directory.


Actual results:
Job will not be present in newly configured remote-working-directory.
If you check /var/tmp, foreman-* job folder and script will be present.

Expected results:
Need to use the special configuration specified via satellite-installer to change directory.

Additional info:
This likely also affected the local-working-dir configuration as well.
Note You need to log in before you can comment on or make changes to this bug.