[chef] Re: RE: Re: Re: Re: Chef.io certificate error causing client install error


Chronological Thread 
  • From: Lamont Granquist < >
  • To:
  • Cc: Justin Franks < >, "Fouts, Chris" < >
  • Subject: [chef] Re: RE: Re: Re: Re: Chef.io certificate error causing client install error
  • Date: Sat, 21 Mar 2015 10:03:09 -0700

" type="cite">

https://docs.chef.io/config_rb_knife.html

 

Where is this documented? That option is not in the list above.

 

Chris

 

From: Lamont Granquist [ ">mailto: ]
Sent: Friday, March 20, 2015 5:11 PM
To: ">
Cc: Justin Franks
Subject: [chef] Re: Re: Re: Chef.io certificate error causing client install error

 


--bootstrap-install-command on the CLI or knife[:bootstrap_install_command] in knife.rb can be used to bypass install.sh entirely and you can dpkg install or rpm install straight from a URL.

On 3/20/15 1:43 PM, Justin Franks wrote:

​ I would like to tell our chef servers to pull the client from out repo and not from a public place. What do I edit on the server?

 


*************************
Justin Franks
Lead Operations Engineer
SaaS, Cloud, Data Centers & Infrastructure
Lithium Technologies, Inc
225 Bush St., 15th Floor
San Francisco, CA 94104
tel: +1 415 757 3100 x3219


From: Christopher Webber ">< >
Sent: Friday, March 20, 2015 1:33 PM
To: ">
Subject: [chef] Re: Chef.io certificate error causing client install error

 

Hey Justin,

 

Sorry you are having issues with this. While we work on a fix for this the workaround is to call --bootstrap-url https://www.opscode.com/chef/install.sh with your knife bootstrap command.

 

Please let me know if you have any questions.

 

— cwebber

 

On Mar 20, 2015, at 13:30, Justin Franks < "> > wrote:

 

Connecting to 10.161.66.83

10.161.66.83 Installing Chef Client...

10.161.66.83 --2015-03-20 20:15:34--  https://www.chef.io/chef/install.sh

10.161.66.83 Resolving www.chef.io... 199.27.79.65

10.161.66.83 Connecting to www.chef.io|199.27.79.65|:443... connected.

10.161.66.83 ERROR: certificate common name “g.ssl.fastly.net” doesn’t match requested host name “www.chef.io”.

10.161.66.83 To connect to www.chef.io insecurely, use ‘--no-check-certificate’.

10.161.66.83 Starting first Chef Client run...

10.161.66.83 bash: line 96: chef-client: command not found​

Errrr... ummm...

 

 


*************************
Justin Franks
Lead Operations Engineer
SaaS, Cloud, Data Centers & Infrastructure
Lithium Technologies, Inc
225 Bush St., 15th Floor
San Francisco, CA 94104
tel: +1 415 757 3100 x3219

 

 





Archive powered by MHonArc 2.6.16.

§