[chef] Re: json gem conflict

[Sam Darwin < >]

What's interesting here is that the dependency is not for some 3rd
party package, but for chef itself.    chef-client is using the
route53 recipe, which is using the fog gem, which is using the json
gem.   A new json gem does get installed during the chef run.   But at
the time chef-client started, it wasn't yet there.    Perhaps the
chef-client's ruby process won't re-read and use new gems during that
single chef run.    It simply must run a second time.     not sure if
that's the case.