-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cookbook_file error gives incomplete list of search locations #1479
Labels
Type: Bug
Does not work as expected.
Comments
Agreed @lindes. This would be a nice to have. Would be cool if you can spare some time to take a stab at this. Let us know if we can give some pointers to get you started on this. |
+1 |
lamont-granquist
added a commit
that referenced
this issue
May 25, 2018
closes #1479 Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using a cookbook_file directive, one of the locations that Chef looks for files is based on the FQDN of the hostname in question, prepended by
host-
. I'd missed thehost-
prepend in my reading of some instructions on this point, and was having a situation where Chef couldn't find the file; in doing so, it presented a list of locations that it had looked, but that list did not include thehost-<FQDN>
subdirectory.The commit that introduced the current messaging is 16a45a4. I believe this should probably be referencing the
preferences
variable, sincepreferences_for_path
seems to be what generates the list of files that are actually checked... But I'm not very familiar with this codebase, and don't have a chef development environment set up just now, so hence submitting a ticket rather than a pull request.Here's an example of the error message, from inside a Vagrant configuration:
I would expect to have an extra line (above the ubuntu-12.04 line), like:
The text was updated successfully, but these errors were encountered: