[chef] Re: Re: Chef bootstrap installation -->gpg key not found on keyserver

[Till Brinkmann < >]

Re,
I´m not sure if it is a point of interest for you (bug tracking)...

I´tried bootstrap installation on debian 6.0.3 several times from scratch (chef-solo).

And if I´m not using ["init_type" : "runit"] the installation fails because of insserv errors. 
If you want I can provide additional information from my research...

greetings Till

Am 10. Januar 2012 16:51 schrieb Till Brinkmann < "> >:

some other thing,

on the opscode wiki there is an alternative way if gpg-key installation fail at first time.....Issues downloading from gnupg.net?

http://wiki.opscode.com/display/chef/Installing+Chef+Client+on+Ubuntu+or+Debian

-->  Add the GPG Key and Update Index

May it´s a good idea to add a line there If gpg fails at this (normal) way, some installation like bootstrap could also fail.

:-) Thanks a lot system bootstrap installation now run without an error

Till

Am 10. Januar 2012 13:17 schrieb Till Brinkmann < " target="_blank"> >:

Bryan, Peter
thanks for your replay it looks like we got a configuration issue in our firewall.
From time to time the firewall blocks the gkd-keyserver response. We use a third party firewall :-/

I tried it some times and now my installation is not in a good state.
First we will fix our firewall to get a 100% response for gpg keyserver and second I will try installation from scratch.
I hope that will work.

Thanks a lot !
Till

Am 9. Januar 2012 18:40 schrieb Bryan McLellan < " target="_blank"> >:

When installing a Chef-server using the chef-solo bootstrap method
[1], the recipe will install gecode from a deb package if you're
running on Debian or Ubuntu. If you're running a release prior to
wheezy or natty, it adds an Opscode apt repository to do so, grabbing
a key for said repository along the way. This is what is failing.

On Mon, Jan 9, 2012 at 10:10 AM, Till Brinkmann
< " target="_blank"> > wrote:

> Executing: gpg --ignore-time-conflict --no-options --no-default-keyring
> --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg
> --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg
> --keyring /etc/apt/trusted.gpg.d//opscode-keyring.gpg --keyserver
> pgpkeys.mit.edu --recv 2940ABA983EF826A
> gpgkeys: key 2940ABA983EF826A not found on keyserver

Now and then we've seen issues with some keyservers responding incorrectly.

I'm curious if you tried a second time and whether it worked this time
or not. As Paul noted, the key is on the keyserver.

We could possibly add a retry here that tries from another keyserver
on failure to prevent this from happening now and then. Perhaps the
keyserver attribute to the apt_repository LWRP in the apt cookbook
could take an array.

Bryan

[1] http://wiki.opscode.com/display/chef/Installing+Chef+Server+using+Chef+Solo