Skip to content

[CI] DocsClientYamlTestSuiteIT test {yaml=reference/cat/allocation/cat-allocation-example} failing #121976

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 Feb 6, 2025 · 3 comments · Fixed by #124684
Assignees
Labels
:Delivery/Build Build or test infrastructure needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Feb 6, 2025

Build Scans:

Reproduction Line:

./gradlew ":docs:yamlRestTest" --tests "org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT.test {yaml=reference/cat/allocation/cat-allocation-example}" -Dtests.seed=1F1FBD4F9AF5F043 -Dtests.locale=tt-Cyrl-RU -Dtests.timezone=America/Cayenne -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [reference/cat/allocation:22]: field [$body] was expected to match the provided regex but didn't
Expected: shards \s+shards.undesired \s+write_load.forecast \s+disk.indices.forecast \s+disk.indices \s+disk.used \s+disk.avail \s+disk.total \s+disk.percent \s+host      \s+ip        \s+node    \s+node.role\s* \s+1                \s+0                 \s+0.0                  \s+\d+(\.\d+)?[tgmk]?b         \s+\d+(\.\d+)?[tgmk]?b    \s+\d+(\.\d+)?[tgmk]?b     \s+\d+(\.\d+)?[tgmk]?b    \s+\d+(\.\d+)?[tgmk]?b           \s+\d+ \s+127.0.0.1 \s+127.0.0.1 \s+.+\s*
     but: was "shards shards.undesired write_load.forecast disk.indices.forecast disk.indices disk.used disk.avail disk.total disk.percent host      ip        node   node.role\n     2                0                 0.0                43.1kb       43.4kb     8.3gb     50.5gb     58.9gb           14 127.0.0.1 127.0.0.1 node-0 cdfhilmrstw\n"

Issue Reasons:

  • [main] 3 failures in test test {yaml=reference/cat/allocation/cat-allocation-example} (0.3% fail rate in 998 executions)
  • [main] 2 failures in step part-1-entitlements (8.0% fail rate in 25 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (0.4% fail rate in 458 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 Feb 6, 2025
elasticsearchmachine added a commit that referenced this issue Feb 6, 2025
…=reference/cat/allocation/cat-allocation-example} #121976
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.x

Mute Reasons:

  • [8.x] 2 failures in test test {yaml=reference/cat/allocation/cat-allocation-example} (0.2% fail rate in 870 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:Delivery Meta label for Delivery team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Feb 6, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 failures in test test {yaml=reference/cat/allocation/cat-allocation-example} (0.3% fail rate in 998 executions)
  • [main] 2 failures in step part-1-entitlements (8.0% fail rate in 25 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (0.4% fail rate in 458 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Feb 18, 2025
…=reference/cat/allocation/cat-allocation-example} #121976
@slobodanadamovic slobodanadamovic self-assigned this Mar 12, 2025
jfreden pushed a commit to jfreden/elasticsearch that referenced this issue Mar 13, 2025
The .security index is created asynchronously on a cluster startup. This
affects some of the docs YAML tests in a way that they need to account
for the existence of the .security index or wait for the index to be
created and green. This PR disables the feature for docs YAML tests.
Disabling the feature in docs YAML tests will solve the flakiness
without affecting the coverage.

Resolves elastic#122343 Resolves
elastic#121748 Resolves
elastic#121611 Resolves
elastic#121345 Resolves
elastic#121338 Resolves
elastic#121337 Resolves
elastic#121288 Resolves
elastic#121287 Resolves
elastic#121867 Resolves
elastic#122335 Resolves
elastic#122681 Resolves
elastic#121976 Resolves
elastic#123094 Resolves
elastic#123192 Resolves
elastic#122983 Resolves
elastic#124671 Resolves
elastic#124103
slobodanadamovic added a commit to slobodanadamovic/elasticsearch that referenced this issue Mar 13, 2025
The .security index is created asynchronously on a cluster startup. This
affects some of the docs YAML tests in a way that they need to account
for the existence of the .security index or wait for the index to be
created and green. This PR disables the feature for docs YAML tests.
Disabling the feature in docs YAML tests will solve the flakiness
without affecting the coverage.

Resolves elastic#122343 Resolves
elastic#121748 Resolves
elastic#121611 Resolves
elastic#121345 Resolves
elastic#121338 Resolves
elastic#121337 Resolves
elastic#121288 Resolves
elastic#121287 Resolves
elastic#121867 Resolves
elastic#122335 Resolves
elastic#122681 Resolves
elastic#121976 Resolves
elastic#123094 Resolves
elastic#123192 Resolves
elastic#122983 Resolves
elastic#124671 Resolves
elastic#124103

(cherry picked from commit cac356a)

# Conflicts:
#	muted-tests.yml
slobodanadamovic added a commit to slobodanadamovic/elasticsearch that referenced this issue Mar 13, 2025
The .security index is created asynchronously on a cluster startup. This
affects some of the docs YAML tests in a way that they need to account
for the existence of the .security index or wait for the index to be
created and green. This PR disables the feature for docs YAML tests.
Disabling the feature in docs YAML tests will solve the flakiness
without affecting the coverage.

Resolves elastic#122343 Resolves
elastic#121748 Resolves
elastic#121611 Resolves
elastic#121345 Resolves
elastic#121338 Resolves
elastic#121337 Resolves
elastic#121288 Resolves
elastic#121287 Resolves
elastic#121867 Resolves
elastic#122335 Resolves
elastic#122681 Resolves
elastic#121976 Resolves
elastic#123094 Resolves
elastic#123192 Resolves
elastic#122983 Resolves
elastic#124671 Resolves
elastic#124103

(cherry picked from commit cac356a)

# Conflicts:
#	muted-tests.yml
slobodanadamovic added a commit to slobodanadamovic/elasticsearch that referenced this issue Mar 13, 2025
The .security index is created asynchronously on a cluster startup. This
affects some of the docs YAML tests in a way that they need to account
for the existence of the .security index or wait for the index to be
created and green. This PR disables the feature for docs YAML tests.
Disabling the feature in docs YAML tests will solve the flakiness
without affecting the coverage.

Resolves elastic#122343 Resolves
elastic#121748 Resolves
elastic#121611 Resolves
elastic#121345 Resolves
elastic#121338 Resolves
elastic#121337 Resolves
elastic#121288 Resolves
elastic#121287 Resolves
elastic#121867 Resolves
elastic#122335 Resolves
elastic#122681 Resolves
elastic#121976 Resolves
elastic#123094 Resolves
elastic#123192 Resolves
elastic#122983 Resolves
elastic#124671 Resolves
elastic#124103

(cherry picked from commit cac356a)

# Conflicts:
#	muted-tests.yml
elasticsearchmachine pushed a commit that referenced this issue Mar 13, 2025
)

The .security index is created asynchronously on a cluster startup. This
affects some of the docs YAML tests in a way that they need to account
for the existence of the .security index or wait for the index to be
created and green. This PR disables the feature for docs YAML tests.
Disabling the feature in docs YAML tests will solve the flakiness
without affecting the coverage.

Resolves #122343 Resolves
#121748 Resolves
#121611 Resolves
#121345 Resolves
#121338 Resolves
#121337 Resolves
#121288 Resolves
#121287 Resolves
#121867 Resolves
#122335 Resolves
#122681 Resolves
#121976 Resolves
#123094 Resolves
#123192 Resolves
#122983 Resolves
#124671 Resolves
#124103

(cherry picked from commit cac356a)

# Conflicts:
#	muted-tests.yml
elasticsearchmachine pushed a commit that referenced this issue Mar 13, 2025
)

The .security index is created asynchronously on a cluster startup. This
affects some of the docs YAML tests in a way that they need to account
for the existence of the .security index or wait for the index to be
created and green. This PR disables the feature for docs YAML tests.
Disabling the feature in docs YAML tests will solve the flakiness
without affecting the coverage.

Resolves #122343 Resolves
#121748 Resolves
#121611 Resolves
#121345 Resolves
#121338 Resolves
#121337 Resolves
#121288 Resolves
#121287 Resolves
#121867 Resolves
#122335 Resolves
#122681 Resolves
#121976 Resolves
#123094 Resolves
#123192 Resolves
#122983 Resolves
#124671 Resolves
#124103

(cherry picked from commit cac356a)

# Conflicts:
#	muted-tests.yml
elasticsearchmachine pushed a commit that referenced this issue Mar 13, 2025
)

The .security index is created asynchronously on a cluster startup. This
affects some of the docs YAML tests in a way that they need to account
for the existence of the .security index or wait for the index to be
created and green. This PR disables the feature for docs YAML tests.
Disabling the feature in docs YAML tests will solve the flakiness
without affecting the coverage.

Resolves #122343 Resolves
#121748 Resolves
#121611 Resolves
#121345 Resolves
#121338 Resolves
#121337 Resolves
#121288 Resolves
#121287 Resolves
#121867 Resolves
#122335 Resolves
#122681 Resolves
#121976 Resolves
#123094 Resolves
#123192 Resolves
#122983 Resolves
#124671 Resolves
#124103

(cherry picked from commit cac356a)

# Conflicts:
#	muted-tests.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants