Vagrant requires attributes in roles.json that break existing Chef project

Question

I have an existing chef-solo project to which I am trying to add vagrant support. I typically use knife to cook these recipes on EC2 servers using Ubun

Answer 1

This should be fixed in the latest version of Chef. There was a JSON vulnerability that allowed infinite object deserialization. I believe the fix issues for that will also fix the issue you're seeing here as well.

Try out Chef 11 and Vagrant 1.5.6

Answer 2

While I haven't run into this particular problem, I have noticed that Chef, as a moving target, tends to have strange stuff happen like this if you're using the same recipes on different versions of Chef.

Just to eliminate that, the first thing I would try is to make my chef versions consistent. I see that your Vagrant VM is using version 0.10.0 and your EC2 VM is using 0.9.16 - whichever is more important, perhaps you could standardize on that one - e.g. if you're trying to replicate your EC2 system locally, you can recreate your Vagrant base box (or look into making your own, the documentation is pretty good on the Vagrant website) such that it more closely matches what you've got installed on EC2.