[chef] Re: Upgrade caused chef client to stop

[Bryan McLellan < >]

On Fri, Mar 11, 2011 at 1:29 AM, Ash Berlin 
<
 >
 wrote:
> So last night all my chef clients seem to finally pick up the upgrade to 
> chef 0.9.14 (I guess this is when .14 got pushed to the opscode apt repo 
> which i'm using)

Yup, the 0.9.14 debs were pushed up last night.

http://www.opscode.com/blog/2011/03/11/chef-0-9-14-packages/

> Sadly they didn't upgrade cleanly:

As Dan mentioned, it's a little tricky to have chef upgrade itself.
For most software that gets significant updates, chef included, I
wouldn't have the system update automatically. So when using apt
packages I would use action :install, not :upgrade. This way you're
not surprised by anything in a new release. You can use knife to
upgrade individual environments when you're ready to test and deploy.

A few knife examples for the benefit of the list:

knife ssh 'name:[* TO *]' 'sudo apt-get update ; sudo apt-get install
chef' # all systems

knife ssh 'environment:preprod' 'sudo apt-get update ; sudo apt-get
install chef' # if you've set up an attribute for each enviroment

 knife ssh -E preprod 'name:[* TO *]' 'sudo apt-get update ; sudo
apt-get install chef' # Chef 0.10 environments

Bryan