You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 14, 2021. It is now read-only.
83 application node['workbench']['app']['home'] do
84 owner 'workbench'
85 group 'workbench'
86
87 git do
88 repository node['workbench']['app']['repo']
89 deploy_key '/etc/id_rsa-workbench_deploy'
90 revision node['workbench']['app']['repo_revision']
91 end
92 end
...and it fails in ssh_wrapper_path from this codebase:
def ssh_wrapper_path
@ssh_wrapper_path ||= ::File.expand_path("~#{user}/.ssh/ssh_wrapper_#{Zlib.crc32(name)}")
end
If I add user 'root' to the git block, it works. (The id_rsa file is only readable by root), though it only works if the user declaration is above the deploy_key declaration.
The strange thing about this is that it only fails on a subset of my hosts.
Now that I've figured out that adding the user fixed it, I'm fine. Leaving this issue here in case anyone is searching for a solution later, or in case ya'll think a docs update is warranted.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For some reason, on a subset of my (essentially identical) hosts, chef fails unless I explicitly provide a :user to the git block:
It's fine when I run the client manually (
sudo chef-client
), but the automated runs fail.The top of the stacktrace:
Where line 89 in my app.rb is:
...and it fails in ssh_wrapper_path from this codebase:
If I add
user 'root'
to the git block, it works. (The id_rsa file is only readable by root), though it only works if the user declaration is above the deploy_key declaration.The strange thing about this is that it only fails on a subset of my hosts.
Now that I've figured out that adding the user fixed it, I'm fine. Leaving this issue here in case anyone is searching for a solution later, or in case ya'll think a docs update is warranted.
The text was updated successfully, but these errors were encountered: