-
-
Notifications
You must be signed in to change notification settings - Fork 599
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
elasticsearch::test doesn't work in ec2 with chef server #41
Comments
Looks like knife cookbook upload doesn't actually upload all the files, I don't see the tests/ directory in the opscode management console |
Hi, the tests shouldn't run in a normal run: I just run them via the Vagrant integration locally. (But if you add the recipe to the node's |
No, that is what I'm saying, I did add it to the run_list and they didn't run. |
Possible, never tried that :) I only run them locally via Vagrant, I believe Chef does some tricks to "clean up" the cookbooks when uploading them... |
@mbaxa Hey, so what should we do about this issue? As I said, the tests are only meant to be run in Vagrant. 1/ Can you verify the situation with the latest cookbook and Chef versions? |
|
The elasticsearch::test doesn't work in the Amazon ec2 and chef server. I can upload the cookbook using
knife cookbook upload cookbook-elasticseach
but when the recipe runs it doesn't find the tests:[2012-12-12T17:38:59+00:00] DEBUG: Will run these tests: []
The text was updated successfully, but these errors were encountered: