[AUTOCUT] Gradle Check Flaky Test Report for AwarenessAttributeDecommissionIT #14290
Labels
autocut
Cluster Manager
flaky-test
Random test failure that succeeds on second run
>test-failure
Test failure from CI, local build, etc.
Comments
opensearch-ci-bot
added
>test-failure
prudhvigodithi
added
the
flaky-test
andrross
added a commit
to andrross/OpenSearch
that referenced
this issue
Jun 14, 2024
The problem is that this test would decommission one of six nodes. The tear down logic of the test would attempt to assert on the health of the cluster by randomly selecting a node and requesting the cluster health. If this random check happened to select the node that was decommissioned, then the test would fail. The fix is to recommission the node at the end of the test. Also, the "recommission node and assert cluster health" logic was used in multiple places and could be refactored out to a helper method. Resolves opensearch-project#14290 Resolves opensearch-project#12197 Signed-off-by: Andrew Ross <andrross@amazon.com>
1 task
andrross
added a commit
to andrross/OpenSearch
that referenced
this issue
Jun 15, 2024
The problem is that this test would decommission one of six nodes. The tear down logic of the test would attempt to assert on the health of the cluster by randomly selecting a node and requesting the cluster health. If this random check happened to select the node that was decommissioned, then the test would fail. The fix is to recommission the node at the end of the test. Also, the "recommission node and assert cluster health" logic was used in multiple places and could be refactored out to a helper method. Resolves opensearch-project#14290 Resolves opensearch-project#12197 Signed-off-by: Andrew Ross <andrross@amazon.com>
opensearch-trigger-bot bot
pushed a commit
that referenced
this issue
Jun 15, 2024
…#14372) The problem is that this test would decommission one of six nodes. The tear down logic of the test would attempt to assert on the health of the cluster by randomly selecting a node and requesting the cluster health. If this random check happened to select the node that was decommissioned, then the test would fail. The fix is to recommission the node at the end of the test. Also, the "recommission node and assert cluster health" logic was used in multiple places and could be refactored out to a helper method. Resolves #14290 Resolves #12197 Signed-off-by: Andrew Ross <andrross@amazon.com> (cherry picked from commit 0d38d14) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
reta
pushed a commit
that referenced
this issue
Jun 15, 2024
…#14372) (#14376) The problem is that this test would decommission one of six nodes. The tear down logic of the test would attempt to assert on the health of the cluster by randomly selecting a node and requesting the cluster health. If this random check happened to select the node that was decommissioned, then the test would fail. The fix is to recommission the node at the end of the test. Also, the "recommission node and assert cluster health" logic was used in multiple places and could be refactored out to a helper method. Resolves #14290 Resolves #12197 (cherry picked from commit 0d38d14) Signed-off-by: Andrew Ross <andrross@amazon.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
harshavamsi
pushed a commit
to harshavamsi/OpenSearch
that referenced
this issue
Jul 12, 2024
…opensearch-project#14372) The problem is that this test would decommission one of six nodes. The tear down logic of the test would attempt to assert on the health of the cluster by randomly selecting a node and requesting the cluster health. If this random check happened to select the node that was decommissioned, then the test would fail. The fix is to recommission the node at the end of the test. Also, the "recommission node and assert cluster health" logic was used in multiple places and could be refactored out to a helper method. Resolves opensearch-project#14290 Resolves opensearch-project#12197 Signed-off-by: Andrew Ross <andrross@amazon.com>
kkewwei
pushed a commit
to kkewwei/OpenSearch
that referenced
this issue
Jul 24, 2024
…opensearch-project#14372) (opensearch-project#14376) The problem is that this test would decommission one of six nodes. The tear down logic of the test would attempt to assert on the health of the cluster by randomly selecting a node and requesting the cluster health. If this random check happened to select the node that was decommissioned, then the test would fail. The fix is to recommission the node at the end of the test. Also, the "recommission node and assert cluster health" logic was used in multiple places and could be refactored out to a helper method. Resolves opensearch-project#14290 Resolves opensearch-project#12197 (cherry picked from commit 0d38d14) Signed-off-by: Andrew Ross <andrross@amazon.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Signed-off-by: kkewwei <kkewwei@163.com>
wdongyu
pushed a commit
to wdongyu/OpenSearch
that referenced
this issue
Aug 22, 2024
…opensearch-project#14372) The problem is that this test would decommission one of six nodes. The tear down logic of the test would attempt to assert on the health of the cluster by randomly selecting a node and requesting the cluster health. If this random check happened to select the node that was decommissioned, then the test would fail. The fix is to recommission the node at the end of the test. Also, the "recommission node and assert cluster health" logic was used in multiple places and could be refactored out to a helper method. Resolves opensearch-project#14290 Resolves opensearch-project#12197 Signed-off-by: Andrew Ross <andrross@amazon.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Flaky Test Report for
AwarenessAttributeDecommissionITNoticed the
AwarenessAttributeDecommissionIThas some flaky, failing tests that failed during post-merge actions.Details
org.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT.testConcurrentDecommissionActionorg.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT.testConcurrentDecommissionActionorg.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT.testConcurrentDecommissionActionorg.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT.testConcurrentDecommissionActionorg.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT.testConcurrentDecommissionActionorg.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT.testConcurrentDecommissionActionorg.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT.testConcurrentDecommissionActionorg.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT.testConcurrentDecommissionActionorg.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT.testConcurrentDecommissionActionorg.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT.testConcurrentDecommissionActionorg.opensearch.cluster.coordination.AwarenessAttributeDecommissionIT.testConcurrentDecommissionActionThe other pull requests, besides those involved in post-merge actions, that contain failing tests with the
AwarenessAttributeDecommissionITclass are:For more details on the failed tests refer to OpenSearch Gradle Check Metrics dashboard.
The text was updated successfully, but these errors were encountered: