[CI] MultiClusterSearchWithSecurityYamlTestSuiteIT #31462
Assignees
Labels
:Security/Authentication
Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)
>test-failure
Triaged test failures from CI
Comments
albertzaharovits
added
>test-failure
|
Pinging @elastic/es-security |
|
Another identical failure, this time on 6.x: |
|
Maybe this was caused by #31241? |
|
@ywelsch Would you take a look at this one? |
ywelsch
added a commit
that referenced
this issue
Jun 27, 2018
Establishing remote cluster connections uses a queue to coordinate multiple concurrent connect attempts. Connect attempts can be initiated by user triggered searches as well as by system events (e.g. when nodes disconnect). Multiple such concurrent events can lead to the connectListener of one event to be called under the thread context of another connect attempt. This can lead to the situation as seen in #31462 where the connect listener is executed under the system context, which breaks when fetching the search shards from the remote cluster. Closes #31462
ywelsch
added a commit
that referenced
this issue
Jun 27, 2018
Establishing remote cluster connections uses a queue to coordinate multiple concurrent connect attempts. Connect attempts can be initiated by user triggered searches as well as by system events (e.g. when nodes disconnect). Multiple such concurrent events can lead to the connectListener of one event to be called under the thread context of another connect attempt. This can lead to the situation as seen in #31462 where the connect listener is executed under the system context, which breaks when fetching the search shards from the remote cluster. Closes #31462
ywelsch
added a commit
that referenced
this issue
Jun 27, 2018
Establishing remote cluster connections uses a queue to coordinate multiple concurrent connect attempts. Connect attempts can be initiated by user triggered searches as well as by system events (e.g. when nodes disconnect). Multiple such concurrent events can lead to the connectListener of one event to be called under the thread context of another connect attempt. This can lead to the situation as seen in #31462 where the connect listener is executed under the system context, which breaks when fetching the search shards from the remote cluster. Closes #31462
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following Rest IntegTest is failing:
with
and does not reproduce locally, looks like a race.
Indeed
_systemuser somehow gets to handle a shard search which is not something he has privileges for and is rightfully rejected.The problem is to see how the
_systemuser assigned to a search request without any Authorization header:x-pack/qa/multi-cluster-search-security/src/test/resources/rest-api-spec/test/multi_cluster/20_info.yml:L64https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_BUILD_JAVA=java10,ES_RUNTIME_JAVA=java10,nodes=virtual&&linux/124/consoleFull
Note: looks similar to #30565
The text was updated successfully, but these errors were encountered: