Project

General

Profile

Bug #12422

Using two different remote users on the single host ends up with permissions issues at the second attemt

Added by Ivan Necas over 6 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

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


Related issues

Has duplicate Foreman Remote Execution - Bug #12439: No proxy output when using non-root ssh userDuplicate2015-11-10

Associated revisions

Revision 5438eefe (diff)
Added by Stephen Benjamin over 6 years ago

fixes #11955, #12422 - use /var/tmp and a unique path on clients

Revision 60a06545
Added by Stephen Benjamin over 6 years ago

Merge pull request #14 from stbenjam/12422

fixes #11955, #12422 - use /var/tmp and a unique path on clients

History

#1 Updated by Stephen Benjamin over 6 years ago

What about using /tmp/foreamn-proxy-<job uuid>? Couldn't you have two jobs running at the same time?

#2 Updated by Stephen Benjamin over 6 years ago

  • Has duplicate Bug #12439: No proxy output when using non-root ssh user added

#3 Updated by Stephen Benjamin over 6 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.

#4 Updated by The Foreman Bot over 6 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

#5 Updated by Anonymous over 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#6 Updated by Stephen Benjamin over 6 years ago

  • Target version changed from 92 to 87
  • Legacy Backlogs Release (now unused) set to 107

#7 Updated by Stephen Benjamin over 6 years ago

  • Legacy Backlogs Release (now unused) changed from 107 to 106

Also available in: Atom PDF