[AUTOCUT] Integration Test failed for anomaly-detection: 2.14.0

[opensearch-ci-bot]

The integration test failed at distribution level for component anomaly-detection
Version: 2.14.0
Distribution: rpm
Architecture: arm64
Platform: linux

Please check the logs: https://build.ci.opensearch.org/job/integ-test/8152/display/redirect

* Test-report manifest:*
- https://ci.opensearch.org/ci/dbc/integ-test/2.14.0/9730/linux/arm64/rpm/test-results/8152/integ-test/test-report.yml

Note: Steps to reproduce, additional logs and other files can be found within the above test-report manifest.
Instructions of this test-report manifest can be found here.

[opensearch-ci-bot]

The integration test failed at distribution level for component anomaly-detection
Version: 2.14.0
Distribution: zip
Architecture: x64
Platform: windows

Please check the logs: https://build.ci.opensearch.org/job/integ-test/8228/display/redirect

* Test-report manifest:*
- https://ci.opensearch.org/ci/dbc/integ-test/2.14.0/9764/windows/x64/zip/test-results/8228/integ-test/test-report.yml

Note: Steps to reproduce, additional logs and other files can be found within the above test-report manifest.
Instructions of this test-report manifest can be found here.

[minalsha]

@dbwiddis could you please take a look at this one? Thanks

[dbwiddis]

@dbwiddis could you please take a look at this one? Thanks

@minalsha There is very little information to go on.

• the arm64 linux failure 2 weeks ago (https://build.ci.opensearch.org/job/integ-test/8152/display/redirect) was a failure to form a cluster after 10 tries. There is a passing test under arm64 linux 20 hours ago (https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/8234/pipeline)
• the x64 windows failure 2 days ago (https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/8228/pipeline) gave no information about why it failed. There is a passing test under x64 windows 19 hours ago (https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/8233/pipeline).

I believe what happened in both cases was a transient failure. I'm not completely clear how these autocut issues work, but it seems the tags get removed when there is a previously tagged failure, and all of the tags have been removed.

As-of 20 hours ago both of the failures have been passing and there is no information or logs available to help debug. I don't think there is anything I can do here.

[minalsha]

Closing this issue since we have passing tests few hours ago as called out by @dbwiddis ^^. Thanks @dbwiddis