[CI] org.elasticsearch.client.documentation.SecurityDocumentationIT.testGetUsers failing in master since Oct 22 #48440
Labels
:Security/Security
Security issues without another label
>test-failure
Triaged test failures from CI
Comments
dliappis
added
>test-failure
|
Pinging @elastic/es-security (:Security/Client) |
jkakavas
added
:Security/Security
jkakavas
added a commit
that referenced
this issue
Oct 24, 2019
#48440 fails in a strange manner (10 users are returned instead of the expected 9) and this does not replicate locally. Adding this log statement to temporarily help with troubleshooting and resolving the issue.
|
https://gradle-enterprise.elastic.co/s/lwq5a4bcyecfi is a more recent failure. @jkakavas does this have the extra logging you need and if so should we now mute this test? |
|
it does, we can mute it - thanks Relevant log line for troubleshooting: need to figure out where this fellow comes from |
DaveCTurner
added a commit
that referenced
this issue
Oct 25, 2019
ywelsch
pushed a commit
that referenced
this issue
Oct 28, 2019
Now we need to work out why it isn't cleaned up... |
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this issue
Nov 22, 2019
SecurityIT.testGetUser creates a user for testing purposes, but did not delete the user at the end of the test. This could leave the cluster in an unexpected state for other tests. This commit: - Deletes the user at the end of `testGetUser` - Adds the test-name as metadata to the users that are created in `SecurityIT` so that their origin is clear if they do interfere with other tests - Enables SecurityDocumentationIT.testGetUsers on the expectation that the new cleanup step will resolve the unreliability of that test. Relates: elastic#48440
tvernum
added a commit
that referenced
this issue
Nov 28, 2019
SecurityIT.testGetUser creates a user for testing purposes, but did not delete the user at the end of the test. This could leave the cluster in an unexpected state for other tests. This commit: - Deletes the user at the end of `testGetUser` - Adds the test-name as metadata to the users that are created in `SecurityIT` so that their origin is clear if they do interfere with other tests - Enables SecurityDocumentationIT.testGetUsers on the expectation that the new cleanup step will resolve the unreliability of that test. Relates: #48440
|
I found a place that created a test user but didn't clean up after itself. If it turns out not to solve the problem, please re-open this issue and mute the test again. |
jkakavas
pushed a commit
to jkakavas/elasticsearch
that referenced
this issue
Feb 5, 2020
SecurityIT.testGetUser creates a user for testing purposes, but did not delete the user at the end of the test. This could leave the cluster in an unexpected state for other tests. This commit: - Deletes the user at the end of `testGetUser` - Adds the test-name as metadata to the users that are created in `SecurityIT` so that their origin is clear if they do interfere with other tests - Enables SecurityDocumentationIT.testGetUsers on the expectation that the new cleanup step will resolve the unreliability of that test. Relates: elastic#48440
jkakavas
pushed a commit
to jkakavas/elasticsearch
that referenced
this issue
Feb 5, 2020
SecurityIT.testGetUser creates a user for testing purposes, but did not delete the user at the end of the test. This could leave the cluster in an unexpected state for other tests. This commit: - Deletes the user at the end of `testGetUser` - Adds the test-name as metadata to the users that are created in `SecurityIT` so that their origin is clear if they do interfere with other tests - Enables SecurityDocumentationIT.testGetUsers on the expectation that the new cleanup step will resolve the unreliability of that test. Relates: elastic#48440
jkakavas
pushed a commit
to jkakavas/elasticsearch
that referenced
this issue
Feb 5, 2020
SecurityIT.testGetUser creates a user for testing purposes, but did not delete the user at the end of the test. This could leave the cluster in an unexpected state for other tests. This commit: - Deletes the user at the end of `testGetUser` - Adds the test-name as metadata to the users that are created in `SecurityIT` so that their origin is clear if they do interfere with other tests - Enables SecurityDocumentationIT.testGetUsers on the expectation that the new cleanup step will resolve the unreliability of that test. Relates: elastic#48440
jkakavas
added a commit
that referenced
this issue
Feb 6, 2020
SecurityIT.testGetUser creates a user for testing purposes, but did not delete the user at the end of the test. This could leave the cluster in an unexpected state for other tests. This commit: - Deletes the user at the end of `testGetUser` - Adds the test-name as metadata to the users that are created in `SecurityIT` so that their origin is clear if they do interfere with other tests - Enables SecurityDocumentationIT.testGetUsers on the expectation that the new cleanup step will resolve the unreliability of that test. Relates: #48440 Co-authored-by: Tim Vernum <[email protected]>
jkakavas
added a commit
that referenced
this issue
Feb 6, 2020
SecurityIT.testGetUser creates a user for testing purposes, but did not delete the user at the end of the test. This could leave the cluster in an unexpected state for other tests. This commit: - Deletes the user at the end of `testGetUser` - Adds the test-name as metadata to the users that are created in `SecurityIT` so that their origin is clear if they do interfere with other tests - Enables SecurityDocumentationIT.testGetUsers on the expectation that the new cleanup step will resolve the unreliability of that test. Relates: #48440 Co-authored-by: Tim Vernum <[email protected]>
jkakavas
added a commit
that referenced
this issue
Feb 6, 2020
SecurityIT.testGetUser creates a user for testing purposes, but did not delete the user at the end of the test. This could leave the cluster in an unexpected state for other tests. This commit: - Deletes the user at the end of `testGetUser` - Adds the test-name as metadata to the users that are created in `SecurityIT` so that their origin is clear if they do interfere with other tests - Enables SecurityDocumentationIT.testGetUsers on the expectation that the new cleanup step will resolve the unreliability of that test. Relates: #48440 Co-authored-by: Tim Vernum <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Example build failure
https://gradle-enterprise.elastic.co/s/glagjcu63cncy
Reproduction line
It does not reproduce locally or on an OracleLinux 7 CI worker (tried with 20 and 100 iterations).
Example relevant log:
Log excerpt
Frequency
3 times so far in CI
https://build-stats.elastic.co/app/kibana#/discover?_g=(refreshInterval:(pause:!t,value:0),time:(from:now-7d,mode:quick,to:now))&_a=(columns:!(_source),index:e58bf320-7efd-11e8-bf69-63c8ef516157,interval:auto,query:(language:lucene,query:'class:%22org.elasticsearch.client.documentation.SecurityDocumentationIT%22%20AND%20test:%22testGetUsers%22%20AND%20branch:%20%22master%22'),sort:!(time,desc))
The text was updated successfully, but these errors were encountered: