Not route for cookbook_versions


#1

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


#2

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


#3

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


#4

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


#5

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


#6

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 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 Gheorghiugrig.gheorghiu@gmail.com 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 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 Sloughtertristan.sloughter@gmail.com 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


#7

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 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.comwrote:

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 Gheorghiugrig.gheorghiu@gmail.com 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 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 Sloughtertristan.sloughter@gmail.com 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


#8

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


#9

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


#10

OK, that worked, thanks so much!

On Tue, May 3, 2011 at 11:55 AM, Alex Soto 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 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 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 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 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 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