Open sherenator opened 7 years ago
It looks like Cheffish.default_chef_server is supposed put config[:node_name] and config[:client_key] underneath the key "options", but for whatever reason, the "options" key gets dropped.
Relevant gist: https://gist.github.com/gregsher88/f979b4d7c2c88c48023c6052d6e5b496
I am receiving a 401 error when trying to precreate chef objects as part of a chef-provisioning run.
I have followed instructions for using knife-acl to define a provisioners group as described in the chef-provisioning readme, however the issue persists.
I am able to create nodes successfully with knife using the same node_name and client_key.
A minimal example leveraging only the relevant portions of cheffish runs without any issue: https://gist.github.com/gregsher88/0a794ee6f4f5ea678c765f67e69689af
A gist of the code being used to provision is here: (https://gist.github.com/gregsher88/3a3bcb819db812eb48aabb415d109adb)
client.rb
corresponding nginx log entry for 401 error
/var/log/opscode/nginx/access.log:158.218.180.110 - - [24/Jul/2017:16:09:58 +0000] "GET /organizations/command/nodes/2elastic-dev-0 HTTP/1.1" 401 "0.014" 5 "-" "Chef Knife/13.2.20 (ruby-2.4.1-p111; ohai-13.2.0; i386-mingw32; +https://chef.io)" "127.0.0.1:9462" "401" "0.014" "13.2.20" "-" "-" "-" "-" 403
C:/chef/cache/chef-stacktrace.out