elasticsearch::default includes `ark` recipe,as noah already mentioned, loading cookbooks in alphabetically order should matter, as its only compiles the attributes, etc at this phaseOn Tue, Jan 29, 2013 at 5:50 PM, Noah Kantrowitz < " target="_blank"> > wrote:
The "Loading cookbooks" phase is just referring to downloading the cookbooks from the chef server, which I guess it does in alpha order because it makes as much sense as anything else :-)
--Noah
On Jan 29, 2013, at 5:49 PM, Ranjib Dey wrote:
> run list item are not executed alphabetically, they are executed as per the order of assignment in the run list. But this order can be changed, as recipes can internally invoke "include_recipe ".
> Check the recipes, see if you have any include_recipe
>
>
> On Tue, Jan 29, 2013 at 5:33 PM, < " target="_blank"> > wrote:
> Hi, I'm a bit confused about the ordering in the runlist.
>
> I'm trying to set up elasticsearch using the elastic search cookbook from
> https://github.com/elasticsearch/cookbook-elasticsearch
>
> I have a search role looking like this:
>
> name "search"
> description "search"
> run_list(
> "recipe[xml]",
> "recipe[java]",
> "recipe[monit]",
> "recipe[elasticsearch]",
> "recipe[elasticsearch::aws]",
> "recipe[elasticsearch::ebs]",
> "recipe[elasticsearch::data]",
> )
> default_attributes(
> )
> override_attributes(
> "xml" => {"packages" => ["libxml2", "libxml2-dev", "libxslt-dev"]}
> )
>
> From the logs when running the chef-client, I can see:
>
> Run List expands to [xml, java, monit, elasticsearch, elasticsearch::aws,
> elasticsearch::ebs, elasticsearch::data]
>
> But then:
>
> Loading cookbooks [ark, build-essential, chef_handler, elasticsearch, java,
> monit,
> windows, xml]
>
> So for some reason, xml is run after elasticsearch, which obviously blows up,
> because it is trying to install nokogiri, which requires libxml2 etc.
>
> Is there a way to override the order? Is it just being run alphabetically? I'm
> confused :)
>
Archive powered by MHonArc 2.6.16.