General discussion about Chef

[chef] Chef-solo Fails on client.pem


Chronological Thread 
  • From: consiliens < >
  • To:
  • Subject: [chef] Chef-solo Fails on client.pem
  • Date: Sat, 15 May 2010 20:24:08 -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=itpjY94xSkAWJqWFeyq0v6szuNw/MwlzQZ6KPI7b60a71H6T1wmU/Qi62Om4IswrE1 k/SwObCh2JJbUVnzQFZv4Xjv/e0KzrRDG7C4P6IwqnQ7sqU6DCvf6JEvEGaMfMJlFQIR nBP9z+sJuxy4vlgiK51kASfw6nVShIFXFIThg=
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.

§