Databases
StackOverflow2013
Postsdbo
POChef: Why are resources in an "include_recipe" step being skipped?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POChef: Why are resources in an "include_recipe" step being skipped?
    primarykey
    data
    text
    <p>Chef seems to be processing resources in a strange order, causing my build to fail. My main recipe (<code>mytardis-chef/site-cookbooks/recipes/default.rb</code>) starts like this:</p> <pre><code>include_recipe "build-essential" include_recipe "mytardis::deps" include_recipe "mytardis::nginx" include_recipe "mytardis::postgresql" </code></pre> <p><code>mytardis-chef/cookbooks/build-essential/recipes/default.rb</code> looks like this:</p> <pre><code>case node['platform'] when "ubuntu","debian" %w{build-essential binutils-doc}.each do |pkg| package pkg do action :install end end when "centos","redhat","fedora","scientific" %w{gcc gcc-c++ kernel-devel make}.each do |pkg| package pkg do action :install end end end </code></pre> <p>... (it's an older version of <code>https://github.com/opscode-cookbooks/build-essential/blob/master/recipes/default.rb</code>)</p> <p>At runtime, for reasons I don't understand, this build-essential recipe gets loaded but not executed:</p> <pre><code>[default] Waiting for VM to boot. This can take a few minutes. [default] VM booted and ready for use! [default] Mounting shared folders... [default] -- v-root: /vagrant [default] -- v-csr-3: /tmp/vagrant-chef-1/chef-solo-3/roles [default] -- v-csc-2: /tmp/vagrant-chef-1/chef-solo-2/cookbooks [default] -- v-csc-1: /tmp/vagrant-chef-1/chef-solo-1/cookbooks [default] -- v-csdb-4: /tmp/vagrant-chef-1/chef-solo-4/data_bags [default] Running provisioner: Vagrant::Provisioners::ChefSolo... [default] Generating chef JSON and uploading... [default] Running chef-solo... [Sun, 08 Jul 2012 05:14:32 +0200] INFO: *** Chef 10.12.0 *** [Sun, 08 Jul 2012 05:14:32 +0200] DEBUG: Building node object for lucid32 [Sun, 08 Jul 2012 05:14:32 +0200] DEBUG: Extracting run list from JSON attributes provided on command line [Sun, 08 Jul 2012 05:14:32 +0200] INFO: Setting the run_list to ["recipe[mytardis]"] from JSON [Sun, 08 Jul 2012 05:14:32 +0200] DEBUG: Applying attributes from json file [Sun, 08 Jul 2012 05:14:32 +0200] DEBUG: Platform is ubuntu version 10.04 [Sun, 08 Jul 2012 05:14:32 +0200] INFO: Run List is [recipe[mytardis]] [Sun, 08 Jul 2012 05:14:32 +0200] INFO: Run List expands to [mytardis] [Sun, 08 Jul 2012 05:14:32 +0200] INFO: Starting Chef Run for lucid32 [Sun, 08 Jul 2012 05:14:32 +0200] INFO: Running start handlers [Sun, 08 Jul 2012 05:14:32 +0200] INFO: Start handlers complete. ... [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Loading Recipe mytardis via include_recipe [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Found recipe default in cookbook mytardis [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Loading Recipe build-essential via include_recipe [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Found recipe default in cookbook build-essential [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Loading Recipe mytardis::deps via include_recipe [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Found recipe deps in cookbook mytardis [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Loading Recipe mytardis::nginx via include_recipe [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Found recipe nginx in cookbook mytardis [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Loading Recipe iptables via include_recipe [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Found recipe default in cookbook iptables [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Loading Recipe mytardis::postgresql via include_recipe [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Found recipe postgresql in cookbook mytardis [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Loading Recipe postgresql::server via include_recipe [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Found recipe server in cookbook postgresql [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Loading Recipe postgresql::client via include_recipe [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Found recipe client in cookbook postgresql [Sun, 08 Jul 2012 05:14:33 +0200] INFO: Processing package[postgresql-client] action install (postgresql::client line 37) [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: package[postgresql-client] checking package status for postgresql-client .... [Sun, 08 Jul 2012 05:14:45 +0200] ERROR: gem_package[pg] (postgresql::client line 42) has had an error . make sh: make: not found </code></pre> <p>That is, the build-essential recipe is "found" and "loaded", but it's the postgres recipe that gets "processed" first. And since build-essential (which installs the C compiler) wasn't run, the latter fails.</p> <p>The relevant part of my Vagrantfile looks like this:</p> <pre><code> config.vm.provision :chef_solo do |chef| chef.log_level = :debug chef.cookbooks_path = ["mytardis-chef/site-cookbooks", "mytardis-chef/cookbooks"] chef.roles_path = "mytardis-chef/roles" chef.data_bags_path = "mytardis-chef/data_bags" chef.add_recipe "mytardis" end </code></pre> <p>I was previously using a slightly earlier version of Chef (perhaps 10.10.0?) In that version, build-essential was also not being run, but mytardis::deps was. Now using Chef 10.12.0. Physical machine is OSX, VM is Ubuntu Lucid.</p> <p>So, a few questions:</p> <ol> <li>Why is build-essential not being "processed"?</li> <li>What's the right way to do this? (I didn't write these recipes, and I understand they do or have worked for their author.)</li> <li>Should the site-cookbooks and cookbooks 'shadowing' feature still work? It's supposedly deprecated: <a href="http://tickets.opscode.com/browse/CHEF-2308">http://tickets.opscode.com/browse/CHEF-2308</a> (I tried making a symbolic link under from site-cookbooks/mytardis/recipes/build-essential but no joy).</li> </ol>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSteve Bennett
    1. USSteve Bennett
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POChef: Why are resources in an "include_recipe" step being skipped?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POChef: Why are resources in an "include_recipe" step being skipped?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POChef: Why are resources in an "include_recipe" step being skipped?
      1. USMatt W
      1. VTFavorite
    1. COYou can put Chef::Log.info("I am in #{cookbook_name}::#{recipe_name}") in build-essential/recipes/default.rb and it will print the log message when it loads the recipe. The file created by the exception handler, something like "/var/chef/cache/failed-run-data.json" will also have the entire resource collection of all the resources it loaded, which can aid in debugging whether the resources in the recipe were added.
      singulars
      1. POChef: Why are resources in an "include_recipe" step being skipped?
      1. USjtimberman
    2. COThe cookbook shadowing feature is that where you can overwrite components that exist in a cookbook by putting them in site-cookbooks, not merely having separate cookbooks in both locations.
      singulars
      1. POChef: Why are resources in an "include_recipe" step being skipped?
      1. USjtimberman
    3. COWere you able to solve this?
      singulars
      1. POChef: Why are resources in an "include_recipe" step being skipped?
      1. USPhilippe Gerber
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload