Client problems with 10.20.0 and 11.2.0


#1

Hi chefs

an interesting problem has cropped up and i’m a bit stumped. The error
is here: https://gist.github.com/anonymous/4771363. This apparently
has started happening in the last week, but I know there have been
hosts that were newly built with 10.20.0 and are working fine.
As a test for this host that i’m working on, i removed 10.20.0 and its
dependent gems and installed 10.12.0 and the client ran as expected
(ie: new client registration and adding an item to the run_list). I
then reinstalled 10.20.0 on top of 10.12.0 and ran right back into
this wall. I can’t help but think there’s something wrong with this
VM and it just needs to be rebuilt, but i’d like to make sure this
isnt a client bug first.


Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.


#2

I’m guessing you installed via gem?

The json gem people released a breaking change in 1.7.6 -> 1.7.7 in response to a DoS vulnerability. I’m presently working on a fix. In the meantime you can uninstall version 1.7.7 of json and install 1.7.6 instead.


Daniel DeLeo

On Tuesday, February 12, 2013 at 9:19 AM, Chris wrote:

Hi chefs

an interesting problem has cropped up and i’m a bit stumped. The error
is here: https://gist.github.com/anonymous/4771363. This apparently
has started happening in the last week, but I know there have been
hosts that were newly built with 10.20.0 and are working fine.
As a test for this host that i’m working on, i removed 10.20.0 and its
dependent gems and installed 10.12.0 and the client ran as expected
(ie: new client registration and adding an item to the run_list). I
then reinstalled 10.20.0 on top of 10.12.0 and ran right back into
this wall. I can’t help but think there’s something wrong with this
VM and it just needs to be rebuilt, but i’d like to make sure this
isnt a client bug first.


Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.


#3

Ah, thanks Daniel. That did it!

Sent from a phone

On Feb 12, 2013, at 9:24 AM, Daniel DeLeo dan@kallistec.com wrote:

I’m guessing you installed via gem?

The json gem people released a breaking change in 1.7.6 -> 1.7.7 in response to a DoS vulnerability. I’m presently working on a fix. In the meantime you can uninstall version 1.7.7 of json and install 1.7.6 instead.


Daniel DeLeo

On Tuesday, February 12, 2013 at 9:19 AM, Chris wrote:

Hi chefs

an interesting problem has cropped up and i’m a bit stumped. The error
is here: https://gist.github.com/anonymous/4771363. This apparently
has started happening in the last week, but I know there have been
hosts that were newly built with 10.20.0 and are working fine.
As a test for this host that i’m working on, i removed 10.20.0 and its
dependent gems and installed 10.12.0 and the client ran as expected
(ie: new client registration and adding an item to the run_list). I
then reinstalled 10.20.0 on top of 10.12.0 and ran right back into
this wall. I can’t help but think there’s something wrong with this
VM and it just needs to be rebuilt, but i’d like to make sure this
isnt a client bug first.


Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.


#4

I uninstalled the 1.7.7 json gem and installed 1.7.6 gem and I still get an
exception when i run any knife commands.

Any thoughts?


/opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chefspec/monkey_patches/provider.rb:6:in
alias_method': undefined methodbuild_from_file’ for class Class' (NameError) from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chefspec/monkey_patches/provider.rb:6:insingletonclass’
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chefspec/monkey_patches/provider.rb:5:in
<class:Provider>' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chefspec/monkey_patches/provider.rb:4:inclass:Chef
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chefspec/monkey_patches/provider.rb:2:in
<top (required)>' from /opt/local/lib/ruby1.9/1.9.1/rubygems/custom_require.rb:55:inrequire’
from /opt/local/lib/ruby1.9/1.9.1/rubygems/custom_require.rb:55:in
require' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chefspec.rb:21:in<top (required)>'
from /opt/local/lib/ruby1.9/1.9.1/rubygems/custom_require.rb:60:in
require' from /opt/local/lib/ruby1.9/1.9.1/rubygems/custom_require.rb:60:inrescue
in require’
from /opt/local/lib/ruby1.9/1.9.1/rubygems/custom_require.rb:35:in
require' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chef/knife/cookbook_create_specs.rb:1:in<top (required)>'
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/knife/core/subcommand_loader.rb:37:in
load' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/knife/core/subcommand_loader.rb:37:inblock in load_commands’
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/knife/core/subcommand_loader.rb:37:in
each' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/knife/core/subcommand_loader.rb:37:inload_commands’
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/knife.rb:119:in
load_commands' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/knife.rb:167:inrun’
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/application/knife.rb:123:in
run' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/bin/knife:25:in<top (required)>'
from /opt/local/bin/knife:23:in load' from /opt/local/bin/knife:23:in

On Tue, Feb 12, 2013 at 12:32 PM, Chris grocerylist@gmail.com wrote:

Ah, thanks Daniel. That did it!

Sent from a phone

On Feb 12, 2013, at 9:24 AM, Daniel DeLeo dan@kallistec.com wrote:

I’m guessing you installed via gem?

The json gem people released a breaking change in 1.7.6 -> 1.7.7 in
response to a DoS vulnerability. I’m presently working on a fix. In the
meantime you can uninstall version 1.7.7 of json and install 1.7.6 instead.


Daniel DeLeo

On Tuesday, February 12, 2013 at 9:19 AM, Chris wrote:

Hi chefs

an interesting problem has cropped up and i’m a bit stumped. The error
is here: https://gist.github.com/anonymous/4771363. This apparently
has started happening in the last week, but I know there have been
hosts that were newly built with 10.20.0 and are working fine.
As a test for this host that i’m working on, i removed 10.20.0 and its
dependent gems and installed 10.12.0 and the client ran as expected
(ie: new client registration and adding an item to the run_list). I
then reinstalled 10.20.0 on top of 10.12.0 and ran right back into
this wall. I can’t help but think there’s something wrong with this
VM and it just needs to be rebuilt, but i’d like to make sure this
isnt a client bug first.


Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.


Thanks,

Mark


#5

Judging by the stack trace, you’ll probably want to get this to the people
involved in writing chefspec.

On Tue, Feb 12, 2013 at 10:02 AM, Mark Pimentel markpimentel22@gmail.comwrote:

I uninstalled the 1.7.7 json gem and installed 1.7.6 gem and I still get
an exception when i run any knife commands.

Any thoughts?


/opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chefspec/monkey_patches/provider.rb:6:in
alias_method': undefined methodbuild_from_file’ for class Class' (NameError) from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chefspec/monkey_patches/provider.rb:6:insingletonclass’
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chefspec/monkey_patches/provider.rb:5:in
<class:Provider>' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chefspec/monkey_patches/provider.rb:4:inclass:Chef
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chefspec/monkey_patches/provider.rb:2:in
<top (required)>' from /opt/local/lib/ruby1.9/1.9.1/rubygems/custom_require.rb:55:inrequire’
from /opt/local/lib/ruby1.9/1.9.1/rubygems/custom_require.rb:55:in
require' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chefspec.rb:21:in<top (required)>'
from /opt/local/lib/ruby1.9/1.9.1/rubygems/custom_require.rb:60:in
require' from /opt/local/lib/ruby1.9/1.9.1/rubygems/custom_require.rb:60:inrescue
in require’
from /opt/local/lib/ruby1.9/1.9.1/rubygems/custom_require.rb:35:in
require' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chefspec-0.9.0/lib/chef/knife/cookbook_create_specs.rb:1:in<top (required)>'
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/knife/core/subcommand_loader.rb:37:in
load' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/knife/core/subcommand_loader.rb:37:inblock in load_commands’
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/knife/core/subcommand_loader.rb:37:in
each' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/knife/core/subcommand_loader.rb:37:inload_commands’
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/knife.rb:119:in
load_commands' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/knife.rb:167:inrun’
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/lib/chef/application/knife.rb:123:in
run' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/chef-11.2.0/bin/knife:25:in<top (required)>'
from /opt/local/bin/knife:23:in load' from /opt/local/bin/knife:23:in

On Tue, Feb 12, 2013 at 12:32 PM, Chris grocerylist@gmail.com wrote:

Ah, thanks Daniel. That did it!

Sent from a phone

On Feb 12, 2013, at 9:24 AM, Daniel DeLeo dan@kallistec.com wrote:

I’m guessing you installed via gem?

The json gem people released a breaking change in 1.7.6 -> 1.7.7 in
response to a DoS vulnerability. I’m presently working on a fix. In the
meantime you can uninstall version 1.7.7 of json and install 1.7.6 instead.


Daniel DeLeo

On Tuesday, February 12, 2013 at 9:19 AM, Chris wrote:

Hi chefs

an interesting problem has cropped up and i’m a bit stumped. The error
is here: https://gist.github.com/anonymous/4771363. This apparently
has started happening in the last week, but I know there have been
hosts that were newly built with 10.20.0 and are working fine.
As a test for this host that i’m working on, i removed 10.20.0 and its
dependent gems and installed 10.12.0 and the client ran as expected
(ie: new client registration and adding an item to the run_list). I
then reinstalled 10.20.0 on top of 10.12.0 and ran right back into
this wall. I can’t help but think there’s something wrong with this
VM and it just needs to be rebuilt, but i’d like to make sure this
isnt a client bug first.


Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.


Thanks,

Mark


#6

Chef 11.4.0 and 10.22.0 are out which fix this JSON issue, blog post
and release notes coming next.

Bryan