elasticsearch::test doesn't work in ec2 with chef server about elasticsearch HOT 6 CLOSED

Looks like knife cookbook upload doesn't actually upload all the files, I don't see the tests/ directory in the opscode management console

from elasticsearch.

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 run_list I guess it should be uploaded and run -- never tried this with Chef server though.)

from elasticsearch.

No, that is what I'm saying, I did add it to the run_list and they didn't run.

from elasticsearch.

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...

from elasticsearch.

@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?
2/ Can you please explain why and how you want to use the included tests with EC2?

from elasticsearch.

1. Using the most recent version of the cookbook, the tests do run locally (Before, I was having problems getting them to run at all even locally).

2. I just expected that the tests would run the same way with EC2.

from elasticsearch.