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

[Bryan McLellan < >]

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
<
 >
 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