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] LogsdbIndexingRollingUpgradeIT testIndexing {upgradedNodes=2} failing #124830

Closed
elasticsearchmachine opened this issue Mar 13, 2025 · 3 comments · Fixed by #124851
Closed
Labels
low-risk An open issue or test failure that is a low risk to future releases :StorageEngine/Logs You know, for Logs Team:StorageEngine >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Mar 13, 2025

Build Scans:

Reproduction Line:

./gradlew ":qa:rolling-upgrade:v9.0.0#bwcTest" -Dtests.class="org.elasticsearch.upgrades.LogsdbIndexingRollingUpgradeIT" -Dtests.method="testIndexing {upgradedNodes=1}" -Dtests.seed=BC808F086923CB28 -Dtests.bwc=true -Dtests.locale=es-PA -Dtests.timezone=Pacific/Fiji -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: timed out waiting for green state for index [logs-bwc-test] cluster state [{
  "cluster_name" : "test-cluster",
  "cluster_uuid" : "bDRMLq-FTiaBRwWDcOp73Q",
  "version" : 92,
  "state_uuid" : "wJZwpQztSJSWdertfdwIqA",
  "master_node" : "V20gptq2RlyMtqOAmf0Qgw",
  "blocks" : { },
  "nodes" : {
    "V20gptq2RlyMtqOAmf0Qgw" : {
      "name" : "test-cluster-1",
      "ephemeral_id" : "45sNebf6Rr6Vw-t2H7lMQw",
      "transport_address" : "127.0.0.1:39141",
      "external_id" : "test-cluster-1",
      "attributes" : {
        "testattr" : "test",
        "transform.config_version" : "10.0.0",
        "xpack.installed" : "true",
        "ml.allocated_processors" : "32",
        "ml.max_jvm_size" : "536870912",
        "ml.config_version" : "12.0.0",
        "ml.machine_memory" : "101237063680",
        "ml.allocated_processors_double" : "32.0"
      },
      "roles" : [
        "data",
        "data_cold",
        "data_content",
        "data_frozen",
        "data
[truncated]

Issue Reasons:

  • [main] 7 consecutive failures in step 9.0.0_bwc-snapshots
  • [main] 16 failures in test testIndexing {upgradedNodes=2} (1.7% fail rate in 947 executions)
  • [main] 13 failures in step 9.0.0_bwc-snapshots (4.5% fail rate in 286 executions)
  • [main] 2 failures in step 9.1.0_bwc-snapshots (0.7% fail rate in 288 executions)
  • [main] 3 failures in pipeline elasticsearch-intake (4.5% fail rate in 67 executions)
  • [main] 11 failures in pipeline elasticsearch-pull-request (4.7% fail rate in 236 executions)

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

@elasticsearchmachine elasticsearchmachine added :StorageEngine/Logs You know, for Logs >test-failure Triaged test failures from CI labels Mar 13, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 consecutive failures in step 9.0.0_bwc-snapshots
  • [main] 8 failures in test testIndexing {upgradedNodes=2} (0.9% fail rate in 904 executions)
  • [main] 5 failures in step 9.0.0_bwc-snapshots (1.8% fail rate in 276 executions)
  • [main] 2 failures in step 9.1.0_bwc-snapshots (0.7% fail rate in 277 executions)
  • [main] 5 failures in pipeline elasticsearch-pull-request (2.2% fail rate in 228 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:StorageEngine needs:risk Requires assignment of a risk label (low, medium, blocker) labels Mar 13, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-storage-engine (Team:StorageEngine)

@martijnvg
Copy link
Member

This and #124831 and #124833, can be unmuted. These test failed briefly because #124803 was merged and #124787 wasn't.

@martijnvg martijnvg added the low-risk An open issue or test failure that is a low risk to future releases label Mar 14, 2025
@elasticsearchmachine elasticsearchmachine removed the needs:risk Requires assignment of a risk label (low, medium, blocker) label Mar 14, 2025
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 :StorageEngine/Logs You know, for Logs Team:StorageEngine >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants