0

I have this run list: recipe-A, my-recipe.

recipe-A creates /etc/A directory.

my-recipe has these codes:

...
// create '/etc/A/file-1'
...
File.symlink('/etc/A/file-1', '/etc/A/file-2')
...

So, when my-recipe runs, there should be /etc/A directory already, which was created by recipe-A. But I got this error at very first of the chef run:

================================================================================
Recipe Compile Error in ...
================================================================================

Errno::ENOENT
-------------
No such file or directory - (/etc/A/file-1, /etc/A/file-2)

I am sure that recipe-A has not been run when this error message is shown up. But isn't it supposed for recipe-A to run first? Why is Chef checking the existence of /etc/A, which is created by recipe-A while it has not been run? How can I solve this?

tshepang
  • 12,111
  • 21
  • 91
  • 136
Tung Nguyen
  • 1,874
  • 3
  • 18
  • 28

1 Answers1

1

Don't run it as ruby code, use the link resource to create the symlink.

link "/etc/A/file-2" do
  to "/etc/A/file-1"
end

I'm pretty sure that your Ruby code is already executed during the compilation phase of the chef run, that's why the code from the second recipe seems to be executed first.

StephenKing
  • 36,187
  • 11
  • 83
  • 112
  • This works great! Actually it is `link "...file-2" do to "...file-1" end` but I got the idea of using this link resource. Thank you very much! – Tung Nguyen Oct 16 '13 at 18:15
  • Also, there is [another topic here](http://stackoverflow.com/questions/11380485/chef-why-are-resources-in-an-include-recipe-step-being-skipped) which has the answer explaining the cause of this "disrespect" of run order. Chef definitely needs better documentation. – Tung Nguyen Oct 30 '13 at 07:04