Rsync Permission Denied - Subsequent Runs #177

Closed
smdern opened this Issue Jan 23, 2013 · 7 comments

Comments

Projects
None yet
5 participants
@smdern
Contributor

smdern commented Jan 23, 2013

After I run knife solo bootstrap as the root user, I want to switch and use a different user for subsequent runs. I'm running into an issue where rsync can't sync due to permission denied. I've been blowing away the tmp/chef-solo dir and running again, so the new user now owns the tmp/chef-solo dir. I'm pretty sure that any user w/ sudo permission should be allowed to run chef-solo.

Any thoughts?

@smdern

This comment has been minimized.

Show comment
Hide comment
@smdern

smdern Jan 23, 2013

Contributor

I was looking @ def rsync_kitchen and I wonder if it would be good to just set permissions of the directory to 666.. I can't see any reasons why you'd want prevent other people from writing in the tmp directory.

Contributor

smdern commented Jan 23, 2013

I was looking @ def rsync_kitchen and I wonder if it would be good to just set permissions of the directory to 666.. I can't see any reasons why you'd want prevent other people from writing in the tmp directory.

@tmatilai

This comment has been minimized.

Show comment
Hide comment
@tmatilai

tmatilai Jan 23, 2013

Collaborator

The problem is that Chef's cache dir is used by knife-solo to sync its own data. This has already quite a few issues, at least #12, #86, #128 and #145. The last has a on-going work to solve the problem. (The others could maybe be closed?)

The /tmp is already a security problem (#1), and making it world writeable doesn't sound good.

So, sorry. No solution yet. :/

Collaborator

tmatilai commented Jan 23, 2013

The problem is that Chef's cache dir is used by knife-solo to sync its own data. This has already quite a few issues, at least #12, #86, #128 and #145. The last has a on-going work to solve the problem. (The others could maybe be closed?)

The /tmp is already a security problem (#1), and making it world writeable doesn't sound good.

So, sorry. No solution yet. :/

@ifeltsweet

This comment has been minimized.

Show comment
Hide comment
@ifeltsweet

ifeltsweet Jan 27, 2013

Exact same problem. Really want this to be fixed.

Exact same problem. Really want this to be fixed.

@matschaffer

This comment has been minimized.

Show comment
Hide comment
@matschaffer

matschaffer Jan 27, 2013

Owner

If you could try out #145 and report success/failure that would be a big help! Planning to roll that out soon but it may require removing custom solo.rb support.

Owner

matschaffer commented Jan 27, 2013

If you could try out #145 and report success/failure that would be a big help! Planning to roll that out soon but it may require removing custom solo.rb support.

@tmatilai

This comment has been minimized.

Show comment
Hide comment
@tmatilai

tmatilai Jan 30, 2013

Collaborator

I'll close this as there are already a couple of issues for the same problem.

Collaborator

tmatilai commented Jan 30, 2013

I'll close this as there are already a couple of issues for the same problem.

@tmatilai tmatilai closed this Jan 30, 2013

tmatilai added a commit that referenced this issue Apr 6, 2013

Merge pull request #199 from matschaffer/issue/knife-rb-configuration…
…-199

- Generate solo.rb from knife.rb settings. Fixes #86, #125, #128, #177, #197.
- Read protect the uploaded directory. Fixes #1.
- Convert chef-solo-search as a submodule and upgrade it to v0.4.0. Should fix #216.
@benissimo

This comment has been minimized.

Show comment
Hide comment
@benissimo

benissimo Jun 3, 2013

Why isn't /tmp/chef-solo deleted at the end of each run?

Why isn't /tmp/chef-solo deleted at the end of each run?

@matschaffer

This comment has been minimized.

Show comment
Hide comment
@matschaffer

matschaffer Jun 3, 2013

Owner

The intent was to avoid extra time spent transferring cookbooks (since we
use rsync).

The latest prerelease uses $HOME by default which should avoid some of
these issues.

On Monday, June 3, 2013, Ben Ellis wrote:

Why isn't /tmp/chef-solo deleted at the end of each run?


Reply to this email directly or view it on GitHubhttps://github.com/matschaffer/knife-solo/issues/177#issuecomment-18852209
.

-Mat

about.me/matschaffer

Owner

matschaffer commented Jun 3, 2013

The intent was to avoid extra time spent transferring cookbooks (since we
use rsync).

The latest prerelease uses $HOME by default which should avoid some of
these issues.

On Monday, June 3, 2013, Ben Ellis wrote:

Why isn't /tmp/chef-solo deleted at the end of each run?


Reply to this email directly or view it on GitHubhttps://github.com/matschaffer/knife-solo/issues/177#issuecomment-18852209
.

-Mat

about.me/matschaffer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment