Skip to content
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] IndicesAndAliasesResolverTests testDataStreamNotAuthorizedWhenBackingIndicesAreAuthorizedViaNameAndRequestThatIncludesDataStreams failing #120018

Closed
elasticsearchmachine opened this issue Jan 11, 2025 · 2 comments
Assignees
Labels
low-risk An open issue or test failure that is a low risk to future releases :Security/Authorization Roles, Privileges, DLS/FLS, RBAC/ABAC Team:Security Meta label for security team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:security:test" --tests "org.elasticsearch.xpack.security.authz.IndicesAndAliasesResolverTests.testDataStreamNotAuthorizedWhenBackingIndicesAreAuthorizedViaNameAndRequestThatIncludesDataStreams" -Dtests.seed=7024DA3D17F912D7 -Dbuild.snapshot=false -Dtests.jvm.argline="-Dbuild.snapshot=false" -Dlicense.key=x-pack/license-tools/src/test/resources/public.key -Dtests.locale=xh-ZA -Dtests.timezone=America/Chihuahua -Druntime.java=23

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: a collection containing ".fs-logs-foobar-2025.01.11-000001"
     but: mismatches were: [was ".ds-logs-foobar-2025.01.11-000001"]

Issue Reasons:

  • [8.x] 2 failures in test testDataStreamNotAuthorizedWhenBackingIndicesAreAuthorizedViaNameAndRequestThatIncludesDataStreams (1.8% fail rate in 114 executions)
  • [8.x] 2 failures in step release-tests (50.0% fail rate in 4 executions)
  • [8.x] 2 failures in pipeline elasticsearch-periodic (50.0% fail rate in 4 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

@elasticsearchmachine elasticsearchmachine added :Security/Authorization Roles, Privileges, DLS/FLS, RBAC/ABAC >test-failure Triaged test failures from CI labels Jan 11, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-security (Team:Security)

@elasticsearchmachine elasticsearchmachine added Team:Security Meta label for security team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jan 11, 2025
@jbaiera jbaiera self-assigned this Jan 12, 2025
@jbaiera
Copy link
Member

jbaiera commented Jan 12, 2025

This looks like these failures should be fixed with #120017 which completed backporting around the time those builds had kicked off. These don't reproduce on 8.x with that change in it, but running on the revision before it does reproduce the failure. The failed builds also list the revision from before the backport commit. I'm going to mark this as resolved since the backport is now complete and we shouldn't see any more of these going forward.

@jbaiera jbaiera closed this as completed Jan 12, 2025
@gwbrown gwbrown added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-risk An open issue or test failure that is a low risk to future releases :Security/Authorization Roles, Privileges, DLS/FLS, RBAC/ABAC Team:Security Meta label for security team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

3 participants