-
Notifications
You must be signed in to change notification settings - Fork 25k
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
[CI] XDocsClientYamlTestSuiteIT {yaml=en/rest-api/security/clear-cache/line_39} failed #34013
Comments
Pinging @elastic/es-security |
Another test in the same docs file failed in the same way in 6.4 and I suspect the root cause is the same. The repro command is this, although it didn't reproduce locally for me:
The error in the test log is this:
These are the log messages in the server log around the time the error occurred:
The timestamp on the error itself is 2018-09-26T06:05:38,234, so during the period between when the .security-6 was deleted and when it was recreated. So I suspect the problem here is that the docs tests are repeatedly deleting and recreating the .security-6 index without making sure that the test code runs while the index exists. |
We believe this is caused because the tests clean out the security index after each test but don't wait for it to be recreated before the test. I've started working on cleaning up some of the other x-pack test cleanup code and eventually I'll get to security. And when I do, this issue is waiting for me. |
Reproduced again https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+periodic/171/console
|
I ran the tests for this doc page in a loop a couple hundred times and couldn't reproduce. Here's the failures for security docs pages with stack traces that look like the ones here. It seems like there were a handful of them in fall 2018 and none since then |
Build: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-unix-compatibility/os=amazon/20/console
At first I couldn't reproduce with:
Then after a few runs I once saw the following thread dump and a failure locally, but couldn't repeat this so far:
I'm currently not able to log into the machine (ssh timeouts) to look if there are similar things in the cluster logs, the failure I see in the test log is:
The text was updated successfully, but these errors were encountered: