Hi,
I experienced the same thing.
When first registering the client/node at the chef-server chef-client
runs fine, but each chef run afterwards, it fails.
The reason is that the data structure sent by the chef-server to the
node was parsed as an object of class Chef::Node with ruby-json 1.7.3-2
and with 1.7.3-3 it is recognized as a hash instead of Chef::Node.
Therefore the NoMethodError is thrown, since the chef sources only
implement a function reset_defaults_and_overrides for the Node class,
not for the Hash class.
After downgrading the ruby-json package to 1.7.3-2 works, chef-client
works again.
I'm not sure if this bug report should also be filed against the chef
package with a higher severity, but since the Debian Ruby Extras
Maintainer take care of both packages, maybe they can decide.
Cheers,
Bastian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
