Elasticsearch Delivery Stats

Oct 13, 2025 by vinooalluri.com 35 views

[CI] SmokeTestIngestDisabledClientYamlTestSuiteIT test {yaml=ingest_mustache/10_ingest_disabled/Test bulk api that contains a single index call with pipeline id fails when node.ingest is set to false} failing

The SmokeTestIngestDisabledClientYamlTestSuiteIT test suite is a crucial component of the Elasticsearch testing framework, designed to ensure the stability and reliability of the platform. However, recent test runs have revealed a critical issue with the test {yaml=ingest_mustache/10_ingest_disabled/Test bulk api that contains a single index call with pipeline id fails when node.ingest is set to false} test case, which is failing consistently. In this article, we will delve into the details of this issue, explore the possible causes, and discuss the necessary steps to resolve it.

The issue was first identified through the Build Scans feature, which provides a comprehensive overview of the test runs. The relevant build scans are:

elasticsearch-periodic-platform-support #6901 / ubuntu-2004-aarch64_checkpart1_platform-support-arm: This build scan reveals a failure in the test {yaml=ingest_mustache/10_ingest_disabled/Test bulk api that contains a single index call with pipeline id fails when node.ingest is set to false} test case.
elasticsearch-periodic-platform-support #6830 / ubuntu-2004-aarch64_checkpart1_platform-support-arm: This build scan also shows a failure in the same test case.

To reproduce the issue locally, you can use the following command:

./gradlew ":qa:smoke-test-ingest-disabled:yamlRestTest" --tests "org.elasticsearch.smoketest.SmokeTestIngestDisabledClientYamlTestSuiteIT" -Dtests.method="test {yaml=ingest_mustache/10_ingest_disabled/Test bulk api that contains a single index call with pipeline id fails when node.ingest is set to false}" -Dtests.seed=4646EF21FEF15A55 -Dtests.locale=ps-Arab-AF -Dtests.timezone=Asia/Baghdad -Druntime.java=23

The issue is applicable to the main branch, and the failure history can be viewed on the Elasticsearch Delivery Stats dashboard.

The failure message is as follows:

org.elasticsearch.client.ResponseException: method [GET], host [http://127.0.0.1:40791], 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":157,"number_of_in_flight_fetch":0,"task_max_waiting_in_queue_millis":34067,"active_shards_percent_as_number":100.0}

The issue reasons are:

2 failures in test test {yaml=ingest_mustache/10_ingest_disabled/Test bulk api that contains a single index call with pipeline id fails when node.ingest is set to false} (0.4% fail rate in 454 executions)
2 failures in step ubuntu-2004-aarch64_checkpart1_platform-support-arm (20.0% fail rate in 10 executions)
2 failures in pipeline elasticsearch-periodic-platform-support (20.0% fail rate in 10 executions)

In conclusion, the SmokeTestIngestDisabledClientYamlTestSuiteIT test suite is experiencing a critical issue with the test {yaml=ingest_mustache/10_ingest_disabled/Test bulk api that contains a single index call with pipeline id fails when node.ingest is set to false} test case. The issue is reproducible locally and has been identified through the Build Scans feature. To resolve this issue, further investigation and debugging are required to determine the root cause and implement necessary fixes.

Based on the analysis, the following recommendations are made:

Investigate the root cause: Further investigation is required to determine the root cause of the issue.
Implement necessary fixes: Once the root cause is identified, necessary fixes should be implemented to resolve the issue.
Verify the fixes: The fixes should be verified to ensure that they resolve the issue and do not introduce any new problems.

By following these recommendations, the SmokeTestIngestDisabledClientYamlTestSuiteIT test suite can be restored to a stable and reliable state, ensuring the quality and integrity of the Elasticsearch platform.
[CI] SmokeTestIngestDisabledClientYamlTestSuiteIT test {yaml=ingest_mustache/10_ingest_disabled/Test bulk api that contains a single index call with pipeline id fails when node.ingest is set to false} failing: Q&A

In our previous article, we discussed the issue with the SmokeTestIngestDisabledClientYamlTestSuiteIT test suite, specifically the test {yaml=ingest_mustache/10_ingest_disabled/Test bulk api that contains a single index call with pipeline id fails when node.ingest is set to false} test case, which is failing consistently. In this article, we will provide a Q&A section to address some of the frequently asked questions related to this issue.

Q: What is the cause of the failure in the test {yaml=ingest_mustache/10_ingest_disabled/Test bulk api that contains a single index call with pipeline id fails when node.ingest is set to false} test case?

A: The cause of the failure is not yet determined. However, based on the failure message, it appears to be related to a timeout issue. Further investigation is required to determine the root cause.

Q: Why is the test {yaml=ingest_mustache/10_ingest_disabled/Test bulk api that contains a single index call with pipeline id fails when node.ingest is set to false} test case failing consistently?

A: The test case is failing consistently because of the timeout issue. The test is waiting for a response from the Elasticsearch cluster, but it is not receiving a response within the specified time limit, resulting in a timeout error.

Q: How can I reproduce the issue locally?

A: You can reproduce the issue locally by running the following command:

./gradlew ":qa:smoke-test-ingest-disabled:yamlRestTest" --tests "org.elasticsearch.smoketest.SmokeTestIngestDisabledClientYamlTestSuiteIT" -Dtests.method="test {yaml=ingest_mustache/10_ingest_disabled/Test bulk api that contains a single index call with pipeline id fails when node.ingest is set to false}" -Dtests.seed=4646EF21FEF15A55 -Dtests.locale=ps-Arab-AF -Dtests.timezone=Asia/Baghdad -Druntime.java=23

Q: What are the applicable branches for this issue?

A: The issue is applicable to the main branch.

Q: Where can I view the failure history for this issue?

A: You can view the failure history for this issue on the Elasticsearch Delivery Stats dashboard.

Q: What are the issue reasons for this failure?

A: The issue reasons for this failure are:

2 failures in test test {yaml=ingest_mustache/10_ingest_disabled/Test bulk api that contains a single index call with pipeline id fails when node.ingest is set to false} (0.4% fail rate in 454 executions)
2 failures in step ubuntu-2004-aarch64_checkpart1_platform-support-arm (20.0% fail rate in 10 executions)
2 failures in pipeline elasticsearch-periodic-platform-support (20.0% fail rate in 10 executions)

Q: What are the next steps to resolve this issue?

A: The next steps to resolve this issue are:

Investigate the root cause: Further investigation is required to determine the root cause of the issue.
Implement necessary fixes: Once the root cause is identified, necessary fixes should be implemented to resolve the issue.
Verify the fixes: The fixes should be verified to ensure that they resolve the issue and do not introduce any new problems.

By following these steps, we can resolve the issue and ensure the quality and integrity of the Elasticsearch platform.