Bug #12422
closed
Using two different remote users on the single host ends up with permissions issues at the second attemt
Description
The problems is the first time the execution starts, /tmp/foreman-proxy-ssh directory is created, restrictring
it to just the first user, while the second user can't access the directory later.
The solution would be probably to store the data in `~/.foreman-proxy-ssh` on the client, instead of
the share `/tmp` directory
Updated by Stephen Benjamin about 9 years ago
What about using /tmp/foreamn-proxy-<job uuid>? Couldn't you have two jobs running at the same time?
Updated by Stephen Benjamin about 9 years ago
- Has duplicate Bug #12439: No proxy output when using non-root ssh user added
Updated by Stephen Benjamin about 9 years ago
Also affects it if you want to run a command on the foreamn server.
/tmp/foreman-proxy/server is created by foreman-proxy user, so if you're not using root then you can't write to the /tmp/foreamn-proxy/client directory when executing a command on the foreman host itself.
Updated by The Foreman Bot about 9 years ago
- Status changed from New to Ready For Testing
- Assignee set to Stephen Benjamin
- Target version set to 92
- Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/14 added
Updated by Anonymous about 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman_proxy_plugin|5438eefe0524dcdd9d2b5808c4d889cfa1766dfb.
Updated by Stephen Benjamin about 9 years ago
- Target version changed from 92 to 87
- Translation missing: en.field_release set to 107
Updated by Stephen Benjamin about 9 years ago
- Translation missing: en.field_release changed from 107 to 106