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

[opensearch-ci-bot]

The integration test failed at distribution level for component anomaly-detection
Version: 2.12.0
Distribution: tar
Architecture: x64
Platform: linux

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

* Test-report manifest:*
- https://ci.opensearch.org/ci/dbc/integ-test/2.12.0/9414/linux/x64/tar/test-results/7880/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.

[prudhvigodithi]

Closing this issue as the integ tests pass for the anomaly-detection plugin 2.12.0.
Thanks
@bbarani @peterzhuamazon

[prudhvigodithi]

Re-opening the issue as I have noticed AD integ tests only fail when concurrent search is enabled
https://github.com/opensearch-project/opensearch-build/blob/main/manifests/2.12.0/opensearch-2.12.0-concurrent-search-test.yml#L24-L33
https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/7869/pipeline/99

@minalsha @kaituo

[amitgalitz]

Is this new CI run with concurrent search enabled a new addition in 2.12? This isn't mentioned in the release issue #1079

I ran the integ tests manually since this was never mentioned in the release campaign, was there a way for us to know this was part of the release before today?

@prudhvigodithi @bbarani

[prudhvigodithi]

Hey @amitgalitz the concurrent search integ tests are not new for 2.12.0, they have been running for past few releases. Also the release campaign added is generic process for each plugin level owner to follow up on during the release. Adding @sohami who has more inputs here.
Thanks

[sohami]

We enabled it in the 2.10 timeframe as well and was not seeing any issues and was enabled in December for 2.x branch too. Just yesterday we saw this failure with AD plugin and was working with @kaituo to understand it better. For now we have this tracking issue to understand and fix it next release: opensearch-project/OpenSearch#12331. Until then we are also adding it as a limitation in concurrent search document (here) with a work around.

[prudhvigodithi]

Hey @amitgalitz @sohami do we have an issue tracking the anomaly-detection failure when concurrent search is enabled?
We can close this issue since the anomaly-detection is signed off for the release 2.12.0.
Thank you
@bbarani

[sohami]

@prudhvigodithi Yes it is shared in comment above. Sharing it again: opensearch-project/OpenSearch#12331

[opensearch-ci-bot]

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

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

* Test-report manifest:*
- https://ci.opensearch.org/ci/dbc/integ-test/2.12.0/9441/linux/arm64/tar/test-results/7928/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.

[prudhvigodithi]

The integration tests have passed for anomaly-detection when concurrent search is enabled
https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/7943/pipeline/
https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/7942/pipeline/
@bbarani @sohami @bbarani