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?
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-1115Bootstrapping 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?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello!
On May 16, 2010, at 4:47 PM, consiliens wrote:
Does the mysql::server recipe need to be updated to work on Chef-
solo without client.pem?
Yes. COOK-296 was reported about this issue. The latest github repo
and cookbooks site version contain the fix.
Opscode, Inc
Joshua Timberman, Senior Solutions Engineer
C: 720.334.RUBY E: joshua@opscode.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
iEYEARECAAYFAkvxV6QACgkQO97WSdVpzT2eWgCeNgJe1BZzidTNZk8F1E+RD9cR
yKwAoI9CDxKpVv6/peKVJPUP13mSTih9
=/oZB
-----END PGP SIGNATURE-----