# Not route for cookbook\_versions

**URL:** https://discourse.chef.io/t/not-route-for-cookbook-versions/1826
**Category:** Chef Infra (archive)
**Created:** [May 3, 2011, 4:09pm UTC](https://discourse.chef.io/t/not-route-for-cookbook-versions/1826 "2011-05-03T16:09:20Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![Tristan\_Sloughter](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/tristan_sloughter/32/819_2.png) [@Tristan\_Sloughter](https://discourse.chef.io/u/Tristan_Sloughter)
#### Post date: [May 3, 2011, 4:09pm UTC](https://discourse.chef.io/t/not-route-for-cookbook-versions/1826/1 "2011-05-03T16:09:20Z")

</div>

I have a number of chef nodes that are working fine but this one fails right  
away. When running the chef-client it gets its runlist and expands it and  
then fails with this error:

[Tue, 03 May 2011 11:06:43 -0500] INFO: HTTP Request Returned 404 Not Found:  
No routes match the request: /environments/\_default/cookbook\_versions  
[Tue, 03 May 2011 11:06:43 -0500] ERROR: Running exception handlers  
[Tue, 03 May 2011 11:06:43 -0500] FATAL: Saving node information to  
/var/chef/cache/failed-run-data.json  
[Tue, 03 May 2011 11:06:43 -0500] ERROR: Exception handlers complete  
[Tue, 03 May 2011 11:06:43 -0500] FATAL: Stacktrace dumped to  
/var/chef/cache/chef-stacktrace.out  
[Tue, 03 May 2011 11:06:43 -0500] FATAL: Net::HTTPServerException: 404 “Not  
Found”

Note that knife commands from this node work fine.

Has anyone seen this error and know what it means?

Thanks,  
Tristan

---

<div class="post-metadata">

### Author: ![Edward\_Sargisson](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/edward_sargisson/32/570_2.png) [@Edward\_Sargisson](https://discourse.chef.io/u/Edward_Sargisson)
#### Post date: [May 3, 2011, 4:15pm UTC](https://discourse.chef.io/t/not-route-for-cookbook-versions/1826/2 "2011-05-03T16:15:31Z")

</div>

Environments are new in Chef 0.10.0. The /environments/\_default/  
cookbook\_versions lookup is trying to find some data from the default  
environment.

Has the chef server you're running against been upgraded?

Cheers,  
Edward

On Tue, May 3, 2011 at 9:09 AM, Tristan Sloughter \<  
[tristan.sloughter@gmail.com](mailto:tristan.sloughter@gmail.com)\> wrote:

> I have a number of chef nodes that are working fine but this one fails  
> right away. When running the chef-client it gets its runlist and expands it  
> and then fails with this error:
> 
> [Tue, 03 May 2011 11:06:43 -0500] INFO: HTTP Request Returned 404 Not  
> Found: No routes match the request: /environments/\_default/cookbook\_versions  
> [Tue, 03 May 2011 11:06:43 -0500] ERROR: Running exception handlers  
> [Tue, 03 May 2011 11:06:43 -0500] FATAL: Saving node information to  
> /var/chef/cache/failed-run-data.json  
> [Tue, 03 May 2011 11:06:43 -0500] ERROR: Exception handlers complete  
> [Tue, 03 May 2011 11:06:43 -0500] FATAL: Stacktrace dumped to  
> /var/chef/cache/chef-stacktrace.out  
> [Tue, 03 May 2011 11:06:43 -0500] FATAL: Net::HTTPServerException: 404 "Not  
> Found"
> 
> Note that knife commands from this node work fine.
> 
> Has anyone seen this error and know what it means?
> 
> Thanks,  
> Tristan

---

<div class="post-metadata">

### Author: ![Grig\_Gheorghiu](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/grig_gheorghiu/32/813_2.png) [@Grig\_Gheorghiu](https://discourse.chef.io/u/Grig_Gheorghiu)
#### Post date: [May 3, 2011, 4:39pm UTC](https://discourse.chef.io/t/not-route-for-cookbook-versions/1826/3 "2011-05-03T16:39:39Z")

</div>

I have the exact same issue with all new instances I launch in EC2. As  
part of the bootstrap process I run 'gem install chef' and that brings  
down Chef 0.10 now. I run a Chef 0.9.4 server. I would have thought  
there will be some mechanisms in place to allow 0.10 clients to talk  
to a pre-0.10 server....but I guess I need to look into upgrading my  
server now.

Grig

On Tue, May 3, 2011 at 9:15 AM, Edward Sargisson [esarge@pobox.com](mailto:esarge@pobox.com) wrote:

> Environments are new in Chef 0.10.0. The /environments/\_default/  
> cookbook\_versions lookup is trying to find some data from the default  
> environment.
> 
> Has the chef server you're running against been upgraded?
> 
> Cheers,  
> Edward
> 
> On Tue, May 3, 2011 at 9:09 AM, Tristan Sloughter  
> [tristan.sloughter@gmail.com](mailto:tristan.sloughter@gmail.com) wrote:
> 
> > I have a number of chef nodes that are working fine but this one fails  
> > right away. When running the chef-client it gets its runlist and expands it  
> > and then fails with this error:  
> > [Tue, 03 May 2011 11:06:43 -0500] INFO: HTTP Request Returned 404 Not  
> > Found: No routes match the request: /environments/\_default/cookbook\_versions  
> > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Running exception handlers  
> > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Saving node information to  
> > /var/chef/cache/failed-run-data.json  
> > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Exception handlers complete  
> > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Stacktrace dumped to  
> > /var/chef/cache/chef-stacktrace.out  
> > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Net::HTTPServerException: 404  
> > "Not Found"  
> > Note that knife commands from this node work fine.  
> > Has anyone seen this error and know what it means?  
> > Thanks,  
> > Tristan

---

<div class="post-metadata">

### Author: ![John\_E\_Vincent\_lusis](https://avatars.discourse-cdn.com/v4/letter/j/c89c15/32.png) [@John\_E\_Vincent\_lusis](https://discourse.chef.io/u/John_E_Vincent_lusis)
#### Post date: [May 3, 2011, 4:41pm UTC](https://discourse.chef.io/t/not-route-for-cookbook-versions/1826/4 "2011-05-03T16:41:20Z")

</div>

Wasn't there a new bootstrap option in the new knife to lock the  
client at a given version?

On Tue, May 3, 2011 at 12:39 PM, Grig Gheorghiu  
[grig.gheorghiu@gmail.com](mailto:grig.gheorghiu@gmail.com) wrote:

> I have the exact same issue with all new instances I launch in EC2. As  
> part of the bootstrap process I run 'gem install chef' and that brings  
> down Chef 0.10 now. I run a Chef 0.9.4 server. I would have thought  
> there will be some mechanisms in place to allow 0.10 clients to talk  
> to a pre-0.10 server....but I guess I need to look into upgrading my  
> server now.
> 
> Grig
> 
> On Tue, May 3, 2011 at 9:15 AM, Edward Sargisson [esarge@pobox.com](mailto:esarge@pobox.com) wrote:
> 
> > Environments are new in Chef 0.10.0. The /environments/\_default/  
> > cookbook\_versions lookup is trying to find some data from the default  
> > environment.
> > 
> > Has the chef server you're running against been upgraded?
> > 
> > Cheers,  
> > Edward
> > 
> > On Tue, May 3, 2011 at 9:09 AM, Tristan Sloughter  
> > [tristan.sloughter@gmail.com](mailto:tristan.sloughter@gmail.com) wrote:
> > 
> > > I have a number of chef nodes that are working fine but this one fails  
> > > right away. When running the chef-client it gets its runlist and expands it  
> > > and then fails with this error:  
> > > [Tue, 03 May 2011 11:06:43 -0500] INFO: HTTP Request Returned 404 Not  
> > > Found: No routes match the request: /environments/\_default/cookbook\_versions  
> > > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Running exception handlers  
> > > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Saving node information to  
> > > /var/chef/cache/failed-run-data.json  
> > > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Exception handlers complete  
> > > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Stacktrace dumped to  
> > > /var/chef/cache/chef-stacktrace.out  
> > > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Net::HTTPServerException: 404  
> > > "Not Found"  
> > > Note that knife commands from this node work fine.  
> > > Has anyone seen this error and know what it means?  
> > > Thanks,  
> > > Tristan

---

<div class="post-metadata">

### Author: ![Nathen\_Harvey4](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/nathen_harvey4/32/681_2.png) [@Nathen\_Harvey4](https://discourse.chef.io/u/Nathen_Harvey4)
#### Post date: [May 3, 2011, 4:45pm UTC](https://discourse.chef.io/t/not-route-for-cookbook-versions/1826/5 "2011-05-03T16:45:10Z")

</div>

You can add this to your knife.rb:

bootstrap\_version "0.9.16"

Or include the --bootstrap-version VERSION option when you call bootstrap.

On 5/3/11 12:41 PM, John E. Vincent (lusis) wrote:

> Wasn't there a new bootstrap option in the new knife to lock the  
> client at a given version?
> 
> On Tue, May 3, 2011 at 12:39 PM, Grig Gheorghiu  
> [grig.gheorghiu@gmail.com](mailto:grig.gheorghiu@gmail.com) wrote:
> 
> > I have the exact same issue with all new instances I launch in EC2. As  
> > part of the bootstrap process I run 'gem install chef' and that brings  
> > down Chef 0.10 now. I run a Chef 0.9.4 server. I would have thought  
> > there will be some mechanisms in place to allow 0.10 clients to talk  
> > to a pre-0.10 server....but I guess I need to look into upgrading my  
> > server now.
> > 
> > Grig
> > 
> > On Tue, May 3, 2011 at 9:15 AM, Edward Sargisson[esarge@pobox.com](mailto:esarge@pobox.com) wrote:
> > 
> > > Environments are new in Chef 0.10.0. The /environments/\_default/  
> > > cookbook\_versions lookup is trying to find some data from the default  
> > > environment.
> > > 
> > > Has the chef server you're running against been upgraded?
> > > 
> > > Cheers,  
> > > Edward
> > > 
> > > On Tue, May 3, 2011 at 9:09 AM, Tristan Sloughter  
> > > [tristan.sloughter@gmail.com](mailto:tristan.sloughter@gmail.com) wrote:
> > > 
> > > > I have a number of chef nodes that are working fine but this one fails  
> > > > right away. When running the chef-client it gets its runlist and expands it  
> > > > and then fails with this error:  
> > > > [Tue, 03 May 2011 11:06:43 -0500] INFO: HTTP Request Returned 404 Not  
> > > > Found: No routes match the request: /environments/\_default/cookbook\_versions  
> > > > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Running exception handlers  
> > > > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Saving node information to  
> > > > /var/chef/cache/failed-run-data.json  
> > > > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Exception handlers complete  
> > > > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Stacktrace dumped to  
> > > > /var/chef/cache/chef-stacktrace.out  
> > > > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Net::HTTPServerException: 404  
> > > > "Not Found"  
> > > > Note that knife commands from this node work fine.  
> > > > Has anyone seen this error and know what it means?  
> > > > Thanks,  
> > > > Tristan

---

<div class="post-metadata">

### Author: ![sdelano](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/sdelano/32/35_2.png) [@sdelano](https://discourse.chef.io/u/sdelano)
#### Post date: [May 3, 2011, 4:52pm UTC](https://discourse.chef.io/t/not-route-for-cookbook-versions/1826/6 "2011-05-03T16:52:34Z")

</div>

Hi all,

The `--bootstrap-version` option to knife and the associated Chef::Config  
parameter are only available in knife 0.9.16 and later. Also, by default,  
knife 0.9.16 and later will bootstrap your node with the current version of  
knife that you are using.

If you upgrade your workstation to 0.9.16 you should see the behavior you  
were expecting. If you are using knife 0.10.0, then you will need to provide  
the --bootstrap-version option.

Cheers!

On Tue, May 3, 2011 at 9:45 AM, Nathen Harvey [nharvey@customink.com](mailto:nharvey@customink.com) wrote:

> You can add this to your knife.rb:
> 
> bootstrap\_version "0.9.16"
> 
> Or include the --bootstrap-version VERSION option when you call bootstrap.
> 
> On 5/3/11 12:41 PM, John E. Vincent (lusis) wrote:
> 
> Wasn't there a new bootstrap option in the new knife to lock the  
> client at a given version?
> 
> On Tue, May 3, 2011 at 12:39 PM, Grig Gheorghiu[grig.gheorghiu@gmail.com](mailto:grig.gheorghiu@gmail.com) [grig.gheorghiu@gmail.com](mailto:grig.gheorghiu@gmail.com) wrote:
> 
> I have the exact same issue with all new instances I launch in EC2. As  
> part of the bootstrap process I run 'gem install chef' and that brings  
> down Chef 0.10 now. I run a Chef 0.9.4 server. I would have thought  
> there will be some mechanisms in place to allow 0.10 clients to talk  
> to a pre-0.10 server....but I guess I need to look into upgrading my  
> server now.
> 
> Grig
> 
> On Tue, May 3, 2011 at 9:15 AM, Edward Sargisson [esarge@pobox.com](mailto:esarge@pobox.com) [esarge@pobox.com](mailto:esarge@pobox.com) wrote:
> 
> Environments are new in Chef 0.10.0. The /environments/\_default/  
> cookbook\_versions lookup is trying to find some data from the default  
> environment.
> 
> Has the chef server you're running against been upgraded?
> 
> Cheers,  
> Edward
> 
> On Tue, May 3, 2011 at 9:09 AM, Tristan Sloughter[tristan.sloughter@gmail.com](mailto:tristan.sloughter@gmail.com) [tristan.sloughter@gmail.com](mailto:tristan.sloughter@gmail.com) wrote:
> 
> I have a number of chef nodes that are working fine but this one fails  
> right away. When running the chef-client it gets its runlist and expands it  
> and then fails with this error:  
> [Tue, 03 May 2011 11:06:43 -0500] INFO: HTTP Request Returned 404 Not  
> Found: No routes match the request: /environments/\_default/cookbook\_versions  
> [Tue, 03 May 2011 11:06:43 -0500] ERROR: Running exception handlers  
> [Tue, 03 May 2011 11:06:43 -0500] FATAL: Saving node information to  
> /var/chef/cache/failed-run-data.json  
> [Tue, 03 May 2011 11:06:43 -0500] ERROR: Exception handlers complete  
> [Tue, 03 May 2011 11:06:43 -0500] FATAL: Stacktrace dumped to  
> /var/chef/cache/chef-stacktrace.out  
> [Tue, 03 May 2011 11:06:43 -0500] FATAL: Net::HTTPServerException: 404  
> "Not Found"  
> Note that knife commands from this node work fine.  
> Has anyone seen this error and know what it means?  
> Thanks,  
> Tristan

--  
Stephen Delano  
Software Development Engineer  
Opscode, Inc.  
1008 Western Avenue  
Suite 601  
Seattle, WA 98104

---

<div class="post-metadata">

### Author: ![Tristan\_Sloughter](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/tristan_sloughter/32/819_2.png) [@Tristan\_Sloughter](https://discourse.chef.io/u/Tristan_Sloughter)
#### Post date: [May 3, 2011, 5:14pm UTC](https://discourse.chef.io/t/not-route-for-cookbook-versions/1826/7 "2011-05-03T17:14:32Z")

</div>

Thanks everyone! I should have noticed it was saying it was running 0.10.0.

I've just removed that version and install 0.9.16 and everything is fine.

Thanks again,  
Tristan

On Tue, May 3, 2011 at 11:52 AM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com) wrote:

> Hi all,
> 
> The `--bootstrap-version` option to knife and the associated Chef::Config  
> parameter are only available in knife 0.9.16 and later. Also, by default,  
> knife 0.9.16 and later will bootstrap your node with the current version of  
> knife that you are using.
> 
> If you upgrade your workstation to 0.9.16 you should see the behavior you  
> were expecting. If you are using knife 0.10.0, then you will need to provide  
> the --bootstrap-version option.
> 
> Cheers!
> 
> On Tue, May 3, 2011 at 9:45 AM, Nathen Harvey [nharvey@customink.com](mailto:nharvey@customink.com)wrote:
> 
> > You can add this to your knife.rb:
> > 
> > bootstrap\_version "0.9.16"
> > 
> > Or include the --bootstrap-version VERSION option when you call bootstrap.
> > 
> > On 5/3/11 12:41 PM, John E. Vincent (lusis) wrote:
> > 
> > Wasn't there a new bootstrap option in the new knife to lock the  
> > client at a given version?
> > 
> > On Tue, May 3, 2011 at 12:39 PM, Grig Gheorghiu[grig.gheorghiu@gmail.com](mailto:grig.gheorghiu@gmail.com) [grig.gheorghiu@gmail.com](mailto:grig.gheorghiu@gmail.com) wrote:
> > 
> > I have the exact same issue with all new instances I launch in EC2. As  
> > part of the bootstrap process I run 'gem install chef' and that brings  
> > down Chef 0.10 now. I run a Chef 0.9.4 server. I would have thought  
> > there will be some mechanisms in place to allow 0.10 clients to talk  
> > to a pre-0.10 server....but I guess I need to look into upgrading my  
> > server now.
> > 
> > Grig
> > 
> > On Tue, May 3, 2011 at 9:15 AM, Edward Sargisson [esarge@pobox.com](mailto:esarge@pobox.com) [esarge@pobox.com](mailto:esarge@pobox.com) wrote:
> > 
> > Environments are new in Chef 0.10.0. The /environments/\_default/  
> > cookbook\_versions lookup is trying to find some data from the default  
> > environment.
> > 
> > Has the chef server you're running against been upgraded?
> > 
> > Cheers,  
> > Edward
> > 
> > On Tue, May 3, 2011 at 9:09 AM, Tristan Sloughter[tristan.sloughter@gmail.com](mailto:tristan.sloughter@gmail.com) [tristan.sloughter@gmail.com](mailto:tristan.sloughter@gmail.com) wrote:
> > 
> > I have a number of chef nodes that are working fine but this one fails  
> > right away. When running the chef-client it gets its runlist and expands it  
> > and then fails with this error:  
> > [Tue, 03 May 2011 11:06:43 -0500] INFO: HTTP Request Returned 404 Not  
> > Found: No routes match the request: /environments/\_default/cookbook\_versions  
> > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Running exception handlers  
> > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Saving node information to  
> > /var/chef/cache/failed-run-data.json  
> > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Exception handlers complete  
> > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Stacktrace dumped to  
> > /var/chef/cache/chef-stacktrace.out  
> > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Net::HTTPServerException: 404  
> > "Not Found"  
> > Note that knife commands from this node work fine.  
> > Has anyone seen this error and know what it means?  
> > Thanks,  
> > Tristan
> 
> --  
> Stephen Delano  
> Software Development Engineer  
> Opscode, Inc.  
> 1008 Western Avenue  
> Suite 601  
> Seattle, WA 98104

---

<div class="post-metadata">

### Author: ![Grig\_Gheorghiu](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/grig_gheorghiu/32/813_2.png) [@Grig\_Gheorghiu](https://discourse.chef.io/u/Grig_Gheorghiu)
#### Post date: [May 3, 2011, 6:53pm UTC](https://discourse.chef.io/t/not-route-for-cookbook-versions/1826/8 "2011-05-03T18:53:34Z")

</div>

Is there a way to specify the chef version I want to install when  
doing 'gem install chef'?

On Tue, May 3, 2011 at 9:52 AM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com) wrote:

> Hi all,  
> The `--bootstrap-version` option to knife and the associated Chef::Config  
> parameter are only available in knife 0.9.16 and later. Also, by default,  
> knife 0.9.16 and later will bootstrap your node with the current version of  
> knife that you are using.  
> If you upgrade your workstation to 0.9.16 you should see the behavior you  
> were expecting. If you are using knife 0.10.0, then you will need to provide  
> the --bootstrap-version option.  
> Cheers!
> 
> On Tue, May 3, 2011 at 9:45 AM, Nathen Harvey [nharvey@customink.com](mailto:nharvey@customink.com) wrote:
> 
> > You can add this to your knife.rb:
> > 
> > bootstrap\_version "0.9.16"
> > 
> > Or include the --bootstrap-version VERSION option when you call bootstrap.
> > 
> > On 5/3/11 12:41 PM, John E. Vincent (lusis) wrote:
> > 
> > Wasn't there a new bootstrap option in the new knife to lock the  
> > client at a given version?
> > 
> > On Tue, May 3, 2011 at 12:39 PM, Grig Gheorghiu  
> > [grig.gheorghiu@gmail.com](mailto:grig.gheorghiu@gmail.com) wrote:
> > 
> > I have the exact same issue with all new instances I launch in EC2. As  
> > part of the bootstrap process I run 'gem install chef' and that brings  
> > down Chef 0.10 now. I run a Chef 0.9.4 server. I would have thought  
> > there will be some mechanisms in place to allow 0.10 clients to talk  
> > to a pre-0.10 server....but I guess I need to look into upgrading my  
> > server now.
> > 
> > Grig
> > 
> > On Tue, May 3, 2011 at 9:15 AM, Edward Sargisson [esarge@pobox.com](mailto:esarge@pobox.com) wrote:
> > 
> > Environments are new in Chef 0.10.0. The /environments/\_default/  
> > cookbook\_versions lookup is trying to find some data from the default  
> > environment.
> > 
> > Has the chef server you're running against been upgraded?
> > 
> > Cheers,  
> > Edward
> > 
> > On Tue, May 3, 2011 at 9:09 AM, Tristan Sloughter  
> > [tristan.sloughter@gmail.com](mailto:tristan.sloughter@gmail.com) wrote:
> > 
> > I have a number of chef nodes that are working fine but this one fails  
> > right away. When running the chef-client it gets its runlist and expands  
> > it  
> > and then fails with this error:  
> > [Tue, 03 May 2011 11:06:43 -0500] INFO: HTTP Request Returned 404 Not  
> > Found: No routes match the request:  
> > /environments/\_default/cookbook\_versions  
> > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Running exception handlers  
> > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Saving node information to  
> > /var/chef/cache/failed-run-data.json  
> > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Exception handlers complete  
> > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Stacktrace dumped to  
> > /var/chef/cache/chef-stacktrace.out  
> > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Net::HTTPServerException: 404  
> > "Not Found"  
> > Note that knife commands from this node work fine.  
> > Has anyone seen this error and know what it means?  
> > Thanks,  
> > Tristan
> 
> --  
> Stephen Delano  
> Software Development Engineer  
> Opscode, Inc.  
> 1008 Western Avenue  
> Suite 601  
> Seattle, WA 98104

---

<div class="post-metadata">

### Author: ![Alex\_Soto](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/alex_soto/32/673_2.png) [@Alex\_Soto](https://discourse.chef.io/u/Alex_Soto)
#### Post date: [May 3, 2011, 6:55pm UTC](https://discourse.chef.io/t/not-route-for-cookbook-versions/1826/9 "2011-05-03T18:55:09Z")

</div>

gem install chef -v 0.9.16

try gem install --help for more details  
On May 3, 2011, at 11:53 AM, Grig Gheorghiu wrote:

> Is there a way to specify the chef version I want to install when  
> doing 'gem install chef'?
> 
> On Tue, May 3, 2011 at 9:52 AM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com) wrote:
> 
> > Hi all,  
> > The `--bootstrap-version` option to knife and the associated Chef::Config  
> > parameter are only available in knife 0.9.16 and later. Also, by default,  
> > knife 0.9.16 and later will bootstrap your node with the current version of  
> > knife that you are using.  
> > If you upgrade your workstation to 0.9.16 you should see the behavior you  
> > were expecting. If you are using knife 0.10.0, then you will need to provide  
> > the --bootstrap-version option.  
> > Cheers!
> > 
> > On Tue, May 3, 2011 at 9:45 AM, Nathen Harvey [nharvey@customink.com](mailto:nharvey@customink.com) wrote:
> > 
> > > You can add this to your knife.rb:
> > > 
> > > bootstrap\_version "0.9.16"
> > > 
> > > Or include the --bootstrap-version VERSION option when you call bootstrap.
> > > 
> > > On 5/3/11 12:41 PM, John E. Vincent (lusis) wrote:
> > > 
> > > Wasn't there a new bootstrap option in the new knife to lock the  
> > > client at a given version?
> > > 
> > > On Tue, May 3, 2011 at 12:39 PM, Grig Gheorghiu  
> > > [grig.gheorghiu@gmail.com](mailto:grig.gheorghiu@gmail.com) wrote:
> > > 
> > > I have the exact same issue with all new instances I launch in EC2. As  
> > > part of the bootstrap process I run 'gem install chef' and that brings  
> > > down Chef 0.10 now. I run a Chef 0.9.4 server. I would have thought  
> > > there will be some mechanisms in place to allow 0.10 clients to talk  
> > > to a pre-0.10 server....but I guess I need to look into upgrading my  
> > > server now.
> > > 
> > > Grig
> > > 
> > > On Tue, May 3, 2011 at 9:15 AM, Edward Sargisson [esarge@pobox.com](mailto:esarge@pobox.com) wrote:
> > > 
> > > Environments are new in Chef 0.10.0. The /environments/\_default/  
> > > cookbook\_versions lookup is trying to find some data from the default  
> > > environment.
> > > 
> > > Has the chef server you're running against been upgraded?
> > > 
> > > Cheers,  
> > > Edward
> > > 
> > > On Tue, May 3, 2011 at 9:09 AM, Tristan Sloughter  
> > > [tristan.sloughter@gmail.com](mailto:tristan.sloughter@gmail.com) wrote:
> > > 
> > > I have a number of chef nodes that are working fine but this one fails  
> > > right away. When running the chef-client it gets its runlist and expands  
> > > it  
> > > and then fails with this error:  
> > > [Tue, 03 May 2011 11:06:43 -0500] INFO: HTTP Request Returned 404 Not  
> > > Found: No routes match the request:  
> > > /environments/\_default/cookbook\_versions  
> > > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Running exception handlers  
> > > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Saving node information to  
> > > /var/chef/cache/failed-run-data.json  
> > > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Exception handlers complete  
> > > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Stacktrace dumped to  
> > > /var/chef/cache/chef-stacktrace.out  
> > > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Net::HTTPServerException: 404  
> > > "Not Found"  
> > > Note that knife commands from this node work fine.  
> > > Has anyone seen this error and know what it means?  
> > > Thanks,  
> > > Tristan
> > 
> > --  
> > Stephen Delano  
> > Software Development Engineer  
> > Opscode, Inc.  
> > 1008 Western Avenue  
> > Suite 601  
> > Seattle, WA 98104

---

<div class="post-metadata">

### Author: ![Grig\_Gheorghiu](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/grig_gheorghiu/32/813_2.png) [@Grig\_Gheorghiu](https://discourse.chef.io/u/Grig_Gheorghiu)
#### Post date: [May 3, 2011, 7:46pm UTC](https://discourse.chef.io/t/not-route-for-cookbook-versions/1826/10 "2011-05-03T19:46:22Z")

</div>

OK, that worked, thanks so much!

On Tue, May 3, 2011 at 11:55 AM, Alex Soto [apsoto@gmail.com](mailto:apsoto@gmail.com) wrote:

> gem install chef -v 0.9.16
> 
> try gem install --help for more details  
> On May 3, 2011, at 11:53 AM, Grig Gheorghiu wrote:
> 
> > Is there a way to specify the chef version I want to install when  
> > doing 'gem install chef'?
> > 
> > On Tue, May 3, 2011 at 9:52 AM, Stephen Delano [stephen@opscode.com](mailto:stephen@opscode.com) wrote:
> > 
> > > Hi all,  
> > > The `--bootstrap-version` option to knife and the associated Chef::Config  
> > > parameter are only available in knife 0.9.16 and later. Also, by default,  
> > > knife 0.9.16 and later will bootstrap your node with the current version of  
> > > knife that you are using.  
> > > If you upgrade your workstation to 0.9.16 you should see the behavior you  
> > > were expecting. If you are using knife 0.10.0, then you will need to provide  
> > > the --bootstrap-version option.  
> > > Cheers!
> > > 
> > > On Tue, May 3, 2011 at 9:45 AM, Nathen Harvey [nharvey@customink.com](mailto:nharvey@customink.com) wrote:
> > > 
> > > > You can add this to your knife.rb:
> > > > 
> > > > bootstrap\_version "0.9.16"
> > > > 
> > > > Or include the --bootstrap-version VERSION option when you call bootstrap.
> > > > 
> > > > On 5/3/11 12:41 PM, John E. Vincent (lusis) wrote:
> > > > 
> > > > Wasn't there a new bootstrap option in the new knife to lock the  
> > > > client at a given version?
> > > > 
> > > > On Tue, May 3, 2011 at 12:39 PM, Grig Gheorghiu  
> > > > [grig.gheorghiu@gmail.com](mailto:grig.gheorghiu@gmail.com) wrote:
> > > > 
> > > > I have the exact same issue with all new instances I launch in EC2. As  
> > > > part of the bootstrap process I run 'gem install chef' and that brings  
> > > > down Chef 0.10 now. I run a Chef 0.9.4 server. I would have thought  
> > > > there will be some mechanisms in place to allow 0.10 clients to talk  
> > > > to a pre-0.10 server....but I guess I need to look into upgrading my  
> > > > server now.
> > > > 
> > > > Grig
> > > > 
> > > > On Tue, May 3, 2011 at 9:15 AM, Edward Sargisson [esarge@pobox.com](mailto:esarge@pobox.com) wrote:
> > > > 
> > > > Environments are new in Chef 0.10.0. The /environments/\_default/  
> > > > cookbook\_versions lookup is trying to find some data from the default  
> > > > environment.
> > > > 
> > > > Has the chef server you're running against been upgraded?
> > > > 
> > > > Cheers,  
> > > > Edward
> > > > 
> > > > On Tue, May 3, 2011 at 9:09 AM, Tristan Sloughter  
> > > > [tristan.sloughter@gmail.com](mailto:tristan.sloughter@gmail.com) wrote:
> > > > 
> > > > I have a number of chef nodes that are working fine but this one fails  
> > > > right away. When running the chef-client it gets its runlist and expands  
> > > > it  
> > > > and then fails with this error:  
> > > > [Tue, 03 May 2011 11:06:43 -0500] INFO: HTTP Request Returned 404 Not  
> > > > Found: No routes match the request:  
> > > > /environments/\_default/cookbook\_versions  
> > > > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Running exception handlers  
> > > > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Saving node information to  
> > > > /var/chef/cache/failed-run-data.json  
> > > > [Tue, 03 May 2011 11:06:43 -0500] ERROR: Exception handlers complete  
> > > > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Stacktrace dumped to  
> > > > /var/chef/cache/chef-stacktrace.out  
> > > > [Tue, 03 May 2011 11:06:43 -0500] FATAL: Net::HTTPServerException: 404  
> > > > "Not Found"  
> > > > Note that knife commands from this node work fine.  
> > > > Has anyone seen this error and know what it means?  
> > > > Thanks,  
> > > > Tristan
> > > 
> > > --  
> > > Stephen Delano  
> > > Software Development Engineer  
> > > Opscode, Inc.  
> > > 1008 Western Avenue  
> > > Suite 601  
> > > Seattle, WA 98104
