[AUTOCUT] Integration Test failed for security: 2.9.0 tar distribution

[opensearch-ci-bot]

The integration test failed at distribution level for component security
Version: 2.9.0
Distribution: tar
Architecture: x64
Platform: linux

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

* Steps to reproduce: See https://github.com/opensearch-project/opensearch-build/tree/main/src/test_workflow#integration-tests
* Access components yml file:
- With security (if applicable)
- Without security (if applicable)

Note: All in one test report manifest with all the details coming soon. See opensearch-project/opensearch-build#1274

[DarshitChanpura]

:integTestRemote task fails in distribution build due to:

  2> java.lang.NoSuchMethodError: 'boolean org.opensearch.common.Strings.isNullOrEmpty(java.lang.String)'

        at org.opensearch.commons.rest.SecureRestClientBuilder.<init>(SecureRestClientBuilder.java:111)

This change comes from common-utils and seems like a stale artifact issue, as this was addressed in 2.9 of common-utils.

2023-07-15 02:22:54 INFO     Copying /var/jenkins/workspace/integ-test@3/tar/builds/opensearch/maven/org/opensearch/common-utils/2.9.0.0/common-utils-2.9.0.0.jar into /usr/share/opensearch/.m2/repository/org/opensearch/common-utils/2.9.0.0/common-utils-2.9.0.0.jar

Reaching out to OpenSearch build team.

[cwperks]

@DarshitChanpura Is this error caused by an outdated default for common-utils referenced in integtest.sh?

#3016

[DarshitChanpura]

I thought so too, but the build seems to be pulling 2.9.0.0 common-utils (see my comments above). It only defaults to 2.2.0.0 if there is no common_utils_version passed. In either case its good to have #3016 merged. I've raised a PR directly to 2.9 to unblock it: #3018

[peternied]

[Triage] This has been merged, closing out this issue.