New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permission Denied when uploading solo.rb #91
Comments
The problem is caused by upload_template having two phases:
Because you are using the On LittleChef's side, what we can do is catch that error and output a proper error message, as "Permission denied" is totally useless for a user encountering the problem. |
Ah, that makes sense. I don't have the means to test that yet, as my computer blew up about an hour after I opened the issue, but I'll try creating a user with a home and post results when I get a chance. |
Tried out creating a new user with a home directory, and it worked perfectly. Thanks! I would recommend a more descriptive error message like you mentioned. |
Committed a partial fix (Ugly error still appears), and filed a bug in fabric (fabric/fabric#629), needed to be able to fix it more nicely on our side. Will leave this open until then |
I'm still getting an error here, but not Permissions. I get the following:
I have tried both directly as root and as a real user chef with sudo permissions. I can see that the template file exists in the home directory with a file name of a long hash, but it appears to fail on moving it to |
Looks like I overlooked #151 |
Thanks @gondoi , I hope the LittleChef 1.5.0 release today fixes your issue. |
I am testing my chef deployments with vagrant, and started out deploying with the vagrant user. I have tried to abstract away the user from vagrant, and am now trying to use a different user, creating when I bootstrap the box.
When I run
fix node:123.123.123.123
using the vagrant user, everything runs perfectly fine, but when I run it using the chef user, (who owns the /etc/chef directory, and can sudo without a password) it fails with the error:This exception is thrown around line 94 of solo.py:
Why does this happen even though the chef user has the correct permissions?
The text was updated successfully, but these errors were encountered: