Skip to content

[CI] SmokeTestPluginsClientYamlTestSuiteIT test {yaml=smoke_test_plugins/10_basic/Correct Plugin Count} failing #111632

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
Closed
elasticsearchmachine opened this issue Aug 6, 2024 · 5 comments
Closed

[CI] SmokeTestPluginsClientYamlTestSuiteIT test {yaml=smoke_test_plugins/10_basic/Correct Plugin Count} failing #111632

elasticsearchmachine opened this issue Aug 6, 2024 · 5 comments
Assignees
@nielsbauman
Labels
:Data Management/Health 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

elasticsearchmachine commented Aug 6, 2024 •
edited
Loading

Build Scans:

Reproduction Line:

./gradlew ":qa:smoke-test-plugins:yamlRestTest" --tests "org.elasticsearch.smoketest.SmokeTestPluginsClientYamlTestSuiteIT.test {yaml=smoke_test_plugins/10_basic/Correct Plugin Count}" -Dtests.seed=7C2582D7A3EA97DE -Dtests.locale=bo-Tibt-CN -Dtests.timezone=Europe/Kiev -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.elasticsearch.client.ResponseException: method [GET], host [http://[::1]:42417], URI [_cluster/health?wait_for_events=languid], status line [HTTP/1.1 408 Request Timeout]
{"cluster_name":"yamlRestTest","status":"green","timed_out":true,"number_of_nodes":1,"number_of_data_nodes":1,"active_primary_shards":0,"active_shards":0,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":0,"unassigned_primary_shards":0,"delayed_unassigned_shards":0,"number_of_pending_tasks":150,"number_of_in_flight_fetch":0,"task_max_waiting_in_queue_millis":38103,"active_shards_percent_as_number":100.0}

Issue Reasons:

  • [main] 2 failures in test test {yaml=smoke_test_plugins/10_basic/Correct Plugin Count} (1.0% fail rate in 202 executions)
  • [main] 2 failures in step ubuntu-2404-aarch64_checkpart1_platform-support-arm (50.0% fail rate in 4 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic-platform-support (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 :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI labels Aug 6, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-delivery (Team:Delivery)

@elasticsearchmachine elasticsearchmachine added Team:Delivery Meta label for Delivery team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Aug 6, 2024
@mark-vieira mark-vieira added :Core/Infra/Plugins Plugin API and infrastructure and removed :Delivery/Build Build or test infrastructure labels Aug 7, 2024
@elasticsearchmachine elasticsearchmachine added Team:Core/Infra Meta label for core/infra team and removed Team:Delivery Meta label for Delivery team labels Aug 7, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@mark-vieira mark-vieira mentioned this issue Aug 7, 2024
Closed
@rjernst
Copy link
Member

rjernst commented Aug 9, 2024

Same as #111662, the test passed, but while wiping the cluster the health api timed out, so reassigning to data management.

@rjernst rjernst added :Data Management/Health and removed :Core/Infra/Plugins Plugin API and infrastructure labels Aug 9, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine elasticsearchmachine added Team:Data Management Meta label for data/management team and removed Team:Core/Infra Meta label for core/infra team labels Aug 9, 2024
@dakrone dakrone 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 Oct 29, 2024
@nielsbauman nielsbauman mentioned this issue Dec 20, 2024
Merged
nielsbauman added a commit to nielsbauman/elasticsearch that referenced this issue Feb 12, 2025
@nielsbauman
Log hot threads after cluster cleanup timeout
8887f9e 
In addition to logging the pending cluster tasks after the cluster
health request times out during cluster cleanup in REST tests, we should
log the hot threads to help identify any issues that could cause tasks
to get stuck.

Follow-up of elastic#119186

Relates elastic#111632
Relates elastic#111431
Relates elastic#111662
@nielsbauman nielsbauman mentioned this issue Feb 12, 2025
Merged
nielsbauman added a commit that referenced this issue Feb 13, 2025
@nielsbauman
Log hot threads after cluster cleanup timeout (#122341)
ee3542a 
In addition to logging the pending cluster tasks after the cluster
health request times out during cluster cleanup in REST tests, we should
log the hot threads to help identify any issues that could cause tasks
to get stuck.

Follow-up of #119186

Relates #111632
Relates #111431
Relates #111662
nielsbauman added a commit to nielsbauman/elasticsearch that referenced this issue Feb 13, 2025
@nielsbauman
Log hot threads after cluster cleanup timeout (elastic#122341)
9838a23 
In addition to logging the pending cluster tasks after the cluster
health request times out during cluster cleanup in REST tests, we should
log the hot threads to help identify any issues that could cause tasks
to get stuck.

Follow-up of elastic#119186

Relates elastic#111632
Relates elastic#111431
Relates elastic#111662
nielsbauman added a commit to nielsbauman/elasticsearch that referenced this issue Feb 13, 2025
@nielsbauman
Log hot threads after cluster cleanup timeout (elastic#122341)
f7553be 
In addition to logging the pending cluster tasks after the cluster
health request times out during cluster cleanup in REST tests, we should
log the hot threads to help identify any issues that could cause tasks
to get stuck.

Follow-up of elastic#119186

Relates elastic#111632
Relates elastic#111431
Relates elastic#111662
elasticsearchmachine pushed a commit that referenced this issue Feb 13, 2025
@nielsbauman
Log hot threads after cluster cleanup timeout (#122341) (#122462)
3b66e6f 
In addition to logging the pending cluster tasks after the cluster
health request times out during cluster cleanup in REST tests, we should
log the hot threads to help identify any issues that could cause tasks
to get stuck.

Follow-up of #119186

Relates #111632
Relates #111431
Relates #111662
elasticsearchmachine pushed a commit that referenced this issue Feb 13, 2025
@nielsbauman
Log hot threads after cluster cleanup timeout (#122341) (#122461)
6690c97 
In addition to logging the pending cluster tasks after the cluster
health request times out during cluster cleanup in REST tests, we should
log the hot threads to help identify any issues that could cause tasks
to get stuck.

Follow-up of #119186

Relates #111632
Relates #111431
Relates #111662
@nielsbauman nielsbauman self-assigned this Mar 26, 2025
This was referenced Apr 9, 2025
Merged
Closed
@nielsbauman
Copy link
Contributor

Closing, see #111431 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nielsbauman nielsbauman

Labels
:Data Management/Health 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

No branches or pull requests
5 participants
@dakrone @rjernst @mark-vieira @nielsbauman @elasticsearchmachine