Skip to content

[CI] FullClusterRestartIT testWatcherWithApiKey {cluster=UPGRADED} failing #124159

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

Closed
elasticsearchmachine opened this issue Mar 5, 2025 · 4 comments · Fixed by #126502
Closed
Assignees
Labels
low-risk An open issue or test failure that is a low risk to future releases :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Mar 5, 2025

Build Scans:

Reproduction Line:

./gradlew ":x-pack:qa:full-cluster-restart:v8.16.6#bwcTest" -Dtests.class="org.elasticsearch.xpack.restart.FullClusterRestartIT" -Dtests.method="testWatcherWithApiKey {cluster=UPGRADED}" -Dtests.seed=24DA0A14101A2BCC -Dtests.bwc=true -Dtests.locale=sms-FI -Dtests.timezone=America/Anguilla -Druntime.java=21

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: version increased: [true], executed: [false]
Expected: is <true>
     but: was <false>

Issue Reasons:

  • [main] 3 failures in test testWatcherWithApiKey {cluster=UPGRADED} (0.4% fail rate in 830 executions)
  • [main] 2 failures in step 9.1.0_bwc-snapshots (1.9% fail rate in 106 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (2.1% fail rate in 95 executions)

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

@elasticsearchmachine elasticsearchmachine added :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) >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 Mar 5, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 failures in test testWatcherWithApiKey {cluster=UPGRADED} (0.4% fail rate in 830 executions)
  • [main] 2 failures in step 9.1.0_bwc-snapshots (1.9% fail rate in 106 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (2.1% fail rate in 95 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Mar 9, 2025
georgewallace pushed a commit to georgewallace/elasticsearch that referenced this issue Mar 11, 2025
@jfreden jfreden 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 Apr 9, 2025
@jfreden
Copy link
Contributor

jfreden commented Apr 9, 2025

Looks like it takes longer than expected for watcher to start (longer than 30 seconds).

@jfreden
Copy link
Contributor

jfreden commented Apr 9, 2025

This appears to be related to:

[2025-03-09T02:23:00,270][INFO ][o.e.t.c.l.DefaultLocalClusterHandle] [suite] Stopping Elasticsearch test cluster 'test-cluster', forcibly: true

Looks like cluster got forceable shutdown. Will unmute the test.

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/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants