-
Notifications
You must be signed in to change notification settings - Fork 313
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
client-options "verify_certs:false" seems to be ignored #472
Comments
Can you please paste the respective snippet from your log file when the client is created? It should look similar to the one below:
Can you please also paste the output of |
I think I know the root cause. I have pushed a change which hopefully fixes this issue. It is contained in Rally 0.10.1. Can you please upgrade to Rally 0.10.1 and retry? |
Your fix solved the bug. ;) |
Thanks for the quick verification @suckowbiz! The reason was that we did not copy the client options but modified it. So the next time a client was created, it was done based on a modified version of the client options which missed a few properties. Fixed in c6198fe. |
I seem to be getting this same problem with esrally 1.4.1 and 2.0.0 |
@gittygoo Would you mind moving this observation in https://discuss.elastic.co/tags/c/elastic-stack/elasticsearch/6/rally? We also use |
I find that the extra quotation marks can be problematic in some cases. I tried to run the elastic rally in a k8s job.
The correct parameter syntax should be like this: (without any double quote mark)
This may not be an issue if you run the rally in a terminal. |
Rally version (get with
esrally --version
):0.10.0
Invoked command:
Configuration file (located in
~/.rally/rally.ini
)):JVM version:
OS version:
Debian GNU/Linux 8 (jessie)
Description of the problem including expected versus actual behavior:
Expected: Rally runs as 0.9.4 did.
Actual: Rally fails with CERTIFICATE_VERIFY_FAILED exception.
Steps to reproduce:
Provide logs (if relevant):
Describe the feature:
The text was updated successfully, but these errors were encountered: