knife bootstrap scripts should install a specific version of chef

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 0.9.14
  • Fix Version/s: 0.9.16, 0.10.0
  • Component/s: Chef Client
  • Labels:
    None

Description

The default scripts included in knife bootstrap greedily install the latest version of Chef from the preferred source (apt, gems, etc.). This is going to cause unexpected behavior the minute Chef 0.10.0 is released.

On the Opscode Platform, 0.10 clients will work just fine. Against open-source 0.9.x deployments, the 0.10 client will fail to complete a chef-client run.

In order to prevent this, the default behavior of the bootstrap scripts should be to install Chef from the current version used (of knife). You should also be able to pass a version argument to the bootstrap command to (set via config as well) declare the intended version to install on the new node.

A workaround (via custom bootstrap scripts) should also be communicated to the community prior to the 0.10.0 release via a blog post and a message to the mailing list.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Stephen Delano added a comment -

Merged into master and 0.9-stable

Show
Stephen Delano added a comment - Merged into master and 0.9-stable
Hide
Permalink
Neil Bartolome added a comment -

So what is the fix for this ? I'm running into this exact problem now. Our server is 0.9.16 and our nodes are being bootstrapped with chef-client 0.10.0. I am unable to run 'sudo chef-client'.

Ideally I would like to install < 0.9.16 of chef-client on our nodes. Is there a way to do this using 'knife bootstrap' ?

Thanks.

Show
Neil Bartolome added a comment - So what is the fix for this ? I'm running into this exact problem now. Our server is 0.9.16 and our nodes are being bootstrapped with chef-client 0.10.0. I am unable to run 'sudo chef-client'. Ideally I would like to install < 0.9.16 of chef-client on our nodes. Is there a way to do this using 'knife bootstrap' ? Thanks.
Hide
Permalink
jtimberman added a comment -

Neil,

If you are using "knife bootstrap" you can pass "--bootstrap-version 0.9.16". You'll want to make sure the gem in your local system is v0.9.16 as well.

http://lists.opscode.com/sympa/arc/chef/2011-05/msg00019.html

If you're using "knife ec2 server create", the config file setting needs to be used instead:

knife[:bootstrap_version] = "0.9.16"
Show
jtimberman added a comment - Neil, If you are using "knife bootstrap" you can pass "--bootstrap-version 0.9.16". You'll want to make sure the gem in your local system is v0.9.16 as well. http://lists.opscode.com/sympa/arc/chef/2011-05/msg00019.html If you're using "knife ec2 server create", the config file setting needs to be used instead: knife[:bootstrap_version] = "0.9.16"
Hide
Permalink
Neil Bartolome added a comment -

Hi Joshua, thanks for responding.

I've been trying to pass the --bootstrap-version flag in my command but i don't think I'm doing it correctly.

$ knife bootstrap 10.12.40.232 -r 'recipe[chef-client]' -x ubuntu --sudo --bootstrap-version 0.9.16

Error: invalid option: --bootstrap-version

Do I need a newer version of knife ?

$ knife -v
Chef: 0.9.14

Thanks.

Show
Neil Bartolome added a comment - Hi Joshua, thanks for responding. I've been trying to pass the --bootstrap-version flag in my command but i don't think I'm doing it correctly. $ knife bootstrap 10.12.40.232 -r 'recipe [chef-client] ' -x ubuntu --sudo --bootstrap-version 0.9.16 Error: invalid option: --bootstrap-version Do I need a newer version of knife ? $ knife -v Chef: 0.9.14 Thanks.
Hide
Permalink
Neil Bartolome added a comment -

>>Do I need a newer version of knife ?

>>$ knife -v
>>Chef: 0.9.14

Indeed I do. I just read the link you posted and it looks like i need 0.9.16

Show
Neil Bartolome added a comment - >>Do I need a newer version of knife ? >>$ knife -v >>Chef: 0.9.14 Indeed I do. I just read the link you posted and it looks like i need 0.9.16

People

  • Assignee:
    Stephen Delano
    Reporter:
    Stephen Delano
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: