Skip to content

[CI] SecurityRolesMultiProjectIT testUpdatingFileBasedRoleAffectsAllProjects failing #126223

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

Open
elasticsearchmachine opened this issue Apr 3, 2025 · 5 comments
Assignees
Labels
needs:risk Requires assignment of a risk label (low, medium, blocker) :Security/Security Security issues without another label Team:Security Meta label for security team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":test:external-modules:test-multi-project:javaRestTest" --tests "org.elasticsearch.xpack.security.SecurityRolesMultiProjectIT.testUpdatingFileBasedRoleAffectsAllProjects" -Dtests.seed=7BE81C497538C951 -Dtests.locale=mr-Deva-IN -Dtests.timezone=SystemV/CST6 -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: iterable containing ["monitor"]
     but: no item was "monitor"

Issue Reasons:

  • [main] 2 failures in test testUpdatingFileBasedRoleAffectsAllProjects (1.0% fail rate in 200 executions)

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

@elasticsearchmachine elasticsearchmachine added :Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI labels Apr 3, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 failures in test testUpdatingFileBasedRoleAffectsAllProjects (1.0% fail rate in 200 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Apr 3, 2025
@elasticsearchmachine elasticsearchmachine added Team:Core/Infra Meta label for core/infra team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Apr 3, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-core-infra (Team:Core/Infra)

@rjernst rjernst added :Security/Security Security issues without another label and removed :Core/Infra/Core Core issues without another label labels Apr 7, 2025
@elasticsearchmachine elasticsearchmachine added Team:Security Meta label for security team and removed Team:Core/Infra Meta label for core/infra team labels Apr 7, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@n1v0lg
Copy link
Contributor

n1v0lg commented Apr 8, 2025

@jfreden I'm guessing it's a race condition/insufficient wait in the new test suite you added (lies, it wasn't you and it wasn't very recent) -- do you have cycles to take a closer look?

@n1v0lg
Copy link
Contributor

n1v0lg commented Apr 8, 2025

elasticsearch-pull-request #65900 / part-1 seems suspect -- if I'm reading this correctly it happened on a PR under development.

@n1v0lg n1v0lg self-assigned this Apr 8, 2025
andreidan pushed a commit to andreidan/elasticsearch that referenced this issue Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs:risk Requires assignment of a risk label (low, medium, blocker) :Security/Security Security issues without another label 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