- From: Sam Darwin <
>
- To:
- Subject: [chef] Re: Re: Re: Re: json gem conflict
- Date: Thu, 9 May 2013 12:07:04 +0300
ok, looks like next release of fog will fix this.
On Wed, May 8, 2013 at 9:33 PM,
<
>
wrote:
>
On Wed, 08 May 2013,
>
>
wrote:
>
>
> I just ran into this very same problem starting this week, using the
>
> route53
>
> recipe. Does anyone know of a solution yet? My route53 recipe does this:
>
>
>
> fog = chef_gem "fog" do
>
> action :nothing
>
> end
>
> fog.run_action( :install )
>
>
>
> require 'rubygems'
>
> Gem.clear_paths
>
>
>
>
>
> I see no where else in my recipes where a json gem gets installed by any
>
> chef
>
> resource, in case that might be affecting this.
>
>
>
> To be clear, this is the error my clients are failing with upon birth. A
>
> second chef-client run succeeds :\
>
>
>
> [2013-05-07T19:14:34+00:00] DEBUG: Gem::LoadError:
>
> route53_record[chef-ci-webapp01c.dev.pickameme.com] (resolver::default
>
> line 130) had an error: Gem::LoadError: Unable to activate fog-1.11.1,
>
> because json-1.5.4 conflicts with json (~> 1.7)
>
>
>
Forgot to mention, my clients are chef-10.24.0-1.el6, omnibus.
>
>
kallen
Archive powered by MHonArc 2.6.16.