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.

Sign up for GitHub

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

Jump to bottom

[CI] IndicesAndAliasesResolverTests testBackingIndicesAreVisibleWhenIncludedByRequestWithWildcard failing #119908

Closed
elasticsearchmachine opened this issue Jan 9, 2025 · 5 comments · Fixed by #119934
Closed

[CI] IndicesAndAliasesResolverTests testBackingIndicesAreVisibleWhenIncludedByRequestWithWildcard failing #119908

elasticsearchmachine opened this issue Jan 9, 2025 · 5 comments · Fixed by #119934
Assignees
@gmarouli @n1v0lg
Labels
:Data Management/Data streams Data streams and their lifecycles low-risk An open issue or test failure that is a low risk to future releases Team:Data Management Meta label for data/management 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.testBackingIndicesAreVisibleWhenIncludedByRequestWithWildcard" -Dtests.seed=50C782C8E01EA132 -Dbuild.snapshot=false -Dtests.jvm.argline="-Dbuild.snapshot=false" -Dlicense.key=x-pack/license-tools/src/test/resources/public.key -Dtests.locale=ig-Latn-NG -Dtests.timezone=Europe/Ulyanovsk -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: is <true>
     but: was <false>

Issue Reasons:

  • [main] 4 consecutive failures in step release-tests
  • [main] 4 failures in test testBackingIndicesAreVisibleWhenIncludedByRequestWithWildcard (1.6% fail rate in 254 executions)
  • [main] 4 failures in step release-tests (100.0% fail rate in 4 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.7% fail rate in 121 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 9, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 4 consecutive failures in step release-tests
  • [main] 4 failures in test testBackingIndicesAreVisibleWhenIncludedByRequestWithWildcard (1.6% fail rate in 254 executions)
  • [main] 4 failures in step release-tests (100.0% fail rate in 4 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.7% fail rate in 121 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Jan 9, 2025
@elasticsearchmachine
Mute org.elasticsearch.xpack.security.authz.IndicesAndAliasesResolver…
3c2f2bf 
…Tests testBackingIndicesAreVisibleWhenIncludedByRequestWithWildcard #119908
@elasticsearchmachine elasticsearchmachine added Team:Security Meta label for security team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jan 9, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@n1v0lg n1v0lg self-assigned this Jan 10, 2025
@n1v0lg
Copy link
Contributor

n1v0lg commented Jan 10, 2025

Same as: #119909 (comment)

@n1v0lg n1v0lg added :Data Management/Data streams Data streams and their lifecycles Team:Data Management Meta label for data/management team and removed :Security/Authorization Roles, Privileges, DLS/FLS, RBAC/ABAC Team:Security Meta label for security team labels Jan 10, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-data-management (Team:Data Management)

@gmarouli gmarouli mentioned this issue Jan 10, 2025
Merged
@gmarouli
Copy link
Contributor

@n1v0lg you are right, the feature flag was blocking the retrieval of the failure indices. Opened: #119934

@gmarouli gmarouli 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 10, 2025
@gmarouli gmarouli self-assigned this Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gmarouli gmarouli

@n1v0lg n1v0lg

Labels
:Data Management/Data streams Data streams and their lifecycles low-risk An open issue or test failure that is a low risk to future releases Team:Data Management Meta label for data/management team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Failure store] Only add failure indices when failure store flag is on. gmarouli/elasticsearch
3 participants
@gmarouli @n1v0lg @elasticsearchmachine