[chef] RE: Re: 10.16.4 not available for chef-full bootstrap

Chronological Thread 
  • From: Kevin Keane (subscriptions) < >
  • To: < >
  • Subject: [chef] RE: Re: 10.16.4 not available for chef-full bootstrap
  • Date: Wed, 26 Dec 2012 03:29:33 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=sendgrid.info; h=subject :from:to:mime-version:content-type:in-reply-to:references :sender; q=dns; s=smtpapi; b=CCRM5Ds5+lWzZ/nThTqwB0ohViYegBSW/TI u0B6QdASjaPBtAVqlNwsdtC7+s5jbzIAwI/TomlxnOEJo3uFWfi9a9qEHCKuoPwR sctVeLTVlpCRRETFoNX27rwCU6l8GdvjR/2SUbHahwGY5j2RfCq9kmf73CQ9qQef y+FpoTew=

Title: RE: [chef] Re: 10.16.4 not available for chef-full bootstrap
-----Original message-----
From: Daniel DeLeo < >
Sent: Tue 12-25-2012 08:41 am
Subject: [chef] Re: 10.16.4 not available for chef-full bootstrap
To: ;

On Tuesday, December 25, 2012 at 3:27 AM, Erik Hollensbe wrote:

Hey duders,
Just in case you forgot, 10.16.4 never got any omnibus love -- which means standard knife bootstraps with it are pretty grumpy.
Can you share some details? If the problem is that the bootstrap is looking for version 10.16.4 of the omnibus package, you can workaround using the `--bootstrap-version` option.

Instead of 10.16.4, omnibus will install 11.0.0 alpha. That's a pretty substantial change.


Cookbooks that broke for me:


- ntp (bug report COOK-2124)

- nginx (I didn't file a bug report for that one, since I am not familiar enough with it to make a meaningful one beyond "it doesn't work")

- A few of my own cookbooks broke, too.


It's' not unexpected for a new major release, and for that matter for an alpha release. But getting this version when you expect a minor incremental version was a bit of a surprise.


BTW, overall I like Chef 11, I think. The migration was actually not very difficult, it just came as an unplanned surprise.


Archive powered by MHonArc 2.6.16.