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] RemoteClusterSecurityReloadCredentialsRestIT testUpgradeFromRcs1 failing #116889

Closed
elasticsearchmachine opened this issue Nov 16, 2024 · 4 comments
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

elasticsearchmachine commented Nov 16, 2024

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:security:qa:multi-cluster:javaRestTest" --tests "org.elasticsearch.xpack.remotecluster.RemoteClusterSecurityReloadCredentialsRestIT.testUpgradeFromRcs1" -Dtests.seed=D400D1689BD93772 -Dtests.locale=mn-Cyrl-MN -Dtests.timezone=Jamaica -Druntime.java=17 -Dtests.fips.enabled=true

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.Exception: Test abandoned because suite timeout was reached.

Issue Reasons:

  • [8.x] 3 failures in test testUpgradeFromRcs1 (0.6% fail rate in 495 executions)
  • [8.x] 3 failures in step openjdk17_checkpart4_java-fips-matrix (20.0% fail rate in 15 executions)
  • [8.x] 3 failures in pipeline elasticsearch-periodic (20.0% fail rate in 15 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 Team:Security Meta label for security team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Nov 16, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@kunal5042
Copy link

Hi, I would like to contribute to this.

@slobodanadamovic slobodanadamovic 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 Nov 20, 2024
@slobodanadamovic
Copy link
Contributor

@kunal5042 Thank you very much for your interest in Elasticsearch.

This is a test failure that's not immediatly actionable and which we need to fix in a timely manner in order to keep our QA and CI build systems happy.

If you are interested in contributing to Elasticsearch, I would suggest to choose from issues labeled with help wanted.

@slobodanadamovic
Copy link
Contributor

Closing as duplicate of #116883 (comment)

@slobodanadamovic slobodanadamovic closed this as not planned Won't fix, can't repro, duplicate, stale Nov 20, 2024
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