The place where I'd have to add that is on the machine I'm bootstrapping, no?I still don't understand clearly what changed - I mean - this was working not that long ago...On Wed, Jan 2, 2013 at 6:11 PM, Daniel DeLeo < " target="_blank"> > wrote:On Wednesday, January 2, 2013 at 2:38 PM, Maven User wrote:
I tried to specify the version of chef to install in the bootstrap command (10.16.4) and that didn't solve the issue either.Daniel - the bug you mention - do I _have_ to upgrade my client from 10.12.0 to 11.X to get this all working again?
On Wed, Jan 2, 2013 at 5:24 PM, Maven User < " target="_blank"> > wrote:Help me figure out what I've changed that would all of a sudden be causing this pain :-(If I specify the bootstrapping version, will that also solve this?Hmmm- more history...Previously, we were specifying the distribution we wanted to use (ubuntu12.04-gems), but the moneta issue broke this for us, so via this mailing list, we solved this by upgrading my cookbooks and taking out the distribution flag to the bootstrap command.
Assuming the bug I referenced is your problem, then the core of the issue is that you're creating encrypted data bags on ruby 1.8-1.9.2 and reading them on ruby 1.9.3. You can work around the issue by adding this code to your chef/config.rb or in the cookbook that reads the encrypted data bag item:YAML::ENGINE.yamler = 'syck' if RUBY_VERSION > '1.9'A longer discussion of the format change in encrypted data bag items, the implications of the change, and compatibility is here:Since Chef 11 client is not released as an alpha yet, I'd recommend using the workaround for now.--Daniel DeLeo
Archive powered by MHonArc 2.6.16.