[chef] Re: Re: Re: Re: Re: RE: cookbook yum not found

[AJ Christensen < >]

The 'git' cookbook has a dependency on yum that must be provided,
although generally, won't be executed on your Ubuntu system by way of
a case statement or similar. [0]

Cheers,

AJ

[0] git cookbook:
https://github.com/opscode-cookbooks/git/blob/master/metadata.rb#L18

On 19 February 2013 09:43, S Ahmed 
<
 >
 wrote:
> Hi,
>
> No I don't have yum, I'm running this on Ubuntu.
>
>
> On Mon, Feb 18, 2013 at 3:39 PM, Jesse Campbell 
> <
 >
>  wrote:
>>
>> try adding recipe[yum] to your run list.
>>
>> if that works, either you're done, or if you want to help out other folks,
>> try to figure out which recipe has an include_recipe['yum'], as it needs to
>> have the metadata.rb updated to add in a depends 'yum'
>>
>> (you have the yum cookbook downloaded in your cookbooks folder, right?)
>>
>>
>> On Mon, Feb 18, 2013 at 3:32 PM, S Ahmed 
>> <
 >
>>  wrote:
>>>
>>> solo.rb:
>>>
>>> home_dir = File.expand_path(File.dirname(__FILE__) + "/..")
>>> file_cache_path home_dir
>>> cookbook_path [ "#{home_dir}/cookbooks" ]
>>> role_path "#{home_dir}/roles"
>>>
>>> chef.json:
>>>
>>> {
>>> "run_list" : [ "role[base]", "role[webserver]" ]
>>> }
>>>
>>>
>>> base.rb:
>>>
>>> name 'base'
>>> description 'base role that all nodes will have'
>>> run_list "recipe[build-essential]", "recipe[ohai]", "recipe[runit]",
>>> "recipe[openssl]", "recipe[git]", "recipe[apt]", "recipe[java]"
>>>
>>> webserver.rb:
>>>
>>> name 'webserver'
>>> description 'web server role for serving http requests'
>>> run_list "recipe[redis]", "recipe[mysql::server]",
>>> "recipe[mysql::client]"
>>>
>>> override_attributes(
>>>   :mysql => {
>>>     "server_root_password" => "opscode123",
>>>     "server_repl_password" => "opscode123",
>>>     "server_debian_password" => "opscode123"
>>>   }
>>> )
>>>
>>>
>>>
>>> On Mon, Feb 18, 2013 at 3:26 PM, Jesse Campbell 
>>> <
 >
>>>  wrote:
>>>>
>>>> what does your run list look like?
>>>> and the metadata for your cookbook that tries to use yum?
>>>>
>>>> one of the breaking changes in chef 11 was that it no longer adds all
>>>> recipes when running chef-solo, you have to explicitly specify that you 
>>>> want
>>>> it in either metadata.rb or the run list
>>>>    "For Chef Solo users, the new loading logic means that files
>>>> belonging to cookbooks which exist in the
>>>>    cookbook_path but are not in the expanded run_list or dependencies of
>>>> the cookbooks in the
>>>>    expanded run_list will no longer be loaded"
>>>> (see about half way down the page:
>>>> http://docs.opscode.com/breaking_changes_chef_11.html)
>>>>
>>>> -Jesse
>>>>
>>>>
>>>> On Mon, Feb 18, 2013 at 3:10 PM, S Ahmed 
>>>> <
 >
>>>>  wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I'm running my chef-solo on ubuntu 12.04 (worked on previous versions),
>>>>> and I am getting this error:
>>>>>
>>>>> Starting Chef Client, version 11.4.0
>>>>> Compiling Cookbooks...
>>>>> [2013-02-18T20:05:17+00:00] ERROR: Running exception handlers
>>>>> [2013-02-18T20:05:17+00:00] ERROR: Exception handlers complete
>>>>> Chef Client failed. 0 resources updated
>>>>> [2013-02-18T20:05:17+00:00] FATAL: Stacktrace dumped to
>>>>> /home/ubuntu/chef/chef-stacktrace.out
>>>>> [2013-02-18T20:05:17+00:00] FATAL: Chef::Exceptions::CookbookNotFound:
>>>>> Cookbook yum not found. If you're loading yum from another cookbook, 
>>>>> make
>>>>> sure you configure the dependency in your metadata
>>>>>
>>>>> On thing to note, I was using chef 10.16.2 before also.
>>>>>
>>>>> Is there a trace mode that I can figure out exactly which cookbook is
>>>>> giving this error?
>>>>>
>>>>> I'm guessing some recipe has a bug in its ability to figure out I am
>>>>> using ubuntu (which uses apt).
>>>>>
>>>>
>>>
>>
>