General discussion about Chef

[chef] Roles to JSON broken on Chef-Solo


Chronological Thread 
  • From: consiliens < >
  • To:
  • Subject: [chef] Roles to JSON broken on Chef-Solo
  • Date: Fri, 16 Jul 2010 14:01:45 -0600
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=wYV5Rt2IyLQdIDQJkMJCf2uorC0CuRsHOCcYg5u/vn3E9Be3Tdmb2knwTbWvTSWUVO 86M8bgs4UvtjEYR7rdL5lWuA03GZOLVf0OC00W/JNc7qyIW2a7AvrPl1JgHcDBz2F0+8 tUJMaG5j7uS2+Z0RI963EgOVKmWTg2iqLmJxc=
Why does chef-solo require a key to generate a JSON representation of a role for use with chef-solo?

I'm using the command from the wiki. http://wiki.opscode.com/display/chef/Chef+Repository#ChefRepository-rolesorrole\rolename\

rake role[webserver]

/usr/local/lib/ruby/gems/1.8/gems/chef-0.9.6/lib/chef/rest/auth_credentials.rb:62:in `load_signing_key': I cannot read ~/.chef/user.pem, which you told me to use to sign requests! (Chef::Exceptions::PrivateKeyMissing)

Archive powered by MHonArc 2.6.16.

§