- From: consiliens <
>
- To:
- Subject: [chef] Re: Chef-solo Fails on client.pem
- Date: Sun, 16 May 2010 16:47:31 -0600
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=HdrU7RUmT3zxp3fmqGoG3ZSKxBRP+4HB0RBCDdJIv+TbC/kMOUCsgDpmEsj1oQDGFi RoPN334ObO6YP7uY+KxAI62SQ9cEmr+XsKFlvoXr1jxuxmQqNfVYkoGqNiE23GAYPHyT vcs8j2QfftmWOnuXCfbGaPmCeGpx/fZWPdqhM=
The error is triggered by using the MySQL cookbook. I removed the
cookbook and the rest of the recipes completed without any .pem errors.
/usr/local/lib/ruby/gems/1.8/gems/chef-0.8.16/bin/../lib/chef/rest/auth_credentials.rb:62:in
`load_signing_key': I cannot read /etc/chef/client.pem, which you told
me to use to sign requests! (Chef::Exceptions::PrivateKeyMissing)
Does the mysql::server recipe need to be updated to work on Chef-solo
without client.pem?
On 05/15/2010 08:24 PM, consiliens wrote:
I updated to Chef 0.8.16 and chef-solo completely broke due to
client.pem. The issue is already reported as CHEF-1115.
http://tickets.opscode.com/browse/CHEF-1115
Bootstrapping with bootstrap_server solved the issue. Running a server
defeats the purpose of chef-solo.
How is client.pem generated? The only pem generation I found was in
server_proxy which creates pem files in the certificates folder.
Is there a better work around?
Archive powered by MHonArc 2.6.16.