Thanks for responding.
Yes the default recipe does include teo other recipes from the same cookbook.
I do know that the recipes work because when I do a Chef run with this cookbook on a Vagrant VM, the cookbook executes successfully. I’m attempting to deploy this cookbook to a node in my dev environment.
I’ve checked in the /etc/chef directory and can see the two pem files(i.e validation.pem and client.pem). Is there anywhere else you suggest I might start from to troubleshoot this?
Sent from iCloud
On May 08, 2015, at 09:15 AM, Daniel DeLeo firstname.lastname@example.org wrote:
On Friday, May 8, 2015 at 8:56 AM, ANGELA EBIRIM wrote:
I would really appreciate some assistance with this…
I’m trying to get a particular cookbook to run on a Ubuntu node. The node is brand new and the first thing I did just after spinning up an instance in AWS, did a chef-client on the command line (which should identify this node to the Chef server) and then did a chef run -r “recipe[cookbook_name::default]”.
I received the following:-
Starting Chef Client, version 11.14.6
resolving cookbooks for run list: [“cookbook_name::default”]
Converging 0 resources
Running handlers complete
Chef Client finished, 0/0 resources updated in 3.269889693 seconds
Can you please tell me why the default recipe isn’t being run?
cookbook_name::default recipe will be run, unless it uses an
include_recipe statement to pull in other recipes. Setting dependencies at the cookbook level will make chef pull them in for the chef-client run (as you can see in your logs), but the run list (and include statement) controls which recipes actually get run.
Sent from iCloud