Functional test in HasParentTest intermittently fails due to a lack in ES configuration #1306
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The alternative would be to enable it for all tests and use the default username / password. Like this we also test the authentication. This will probably work well in 5.x. But in 6.0 probably random passwords will be introduced which will make this much more complex. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The problem with the docker image from ES version 5.2.2 is that is shipped with x-pack installed, I disabled security but I forgot to disable monitor which sometimes make this test failing.
At this time it's not possible to remove completely the xpack plugin (except with a workaround) due
to an issue in the official docker ES image : elastic/elasticsearch-docker#36. At the moment I've disabled security and monitoring from the elasticsearch.yml. The problem has been resolved (maybe) in the 5.4, my suggestion is to completely remove the plugin when we will switch to that version.