-
Notifications
You must be signed in to change notification settings - Fork 271
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
[Bug]: Opensearch fails to start and deploy for 1.2.4 #1477
Comments
@amitgalitz @Zhangxunmt, can you guys take a look. Looks like AD plugin is causing the issue. |
Issue for this error that was opened earlier - opensearch-project/anomaly-detection#359 |
Taking a look |
I think I found the issue, our dependency is being compiled fine and running fine locally and on all github workflows. But after inspecting the pom file made at build, the lang3 dependency is not being bundled with our JAR which makes it so our artifact itself doesn’t work. Basically our runtime classpath contains a different version of this dependency then when we compile. Actively fixing it now and testing it out. |
Thanks @amitgalitz for actively looking into this. |
opensearch-project/anomaly-detection#363. This will fix the issue. After them merge, please work out a build release again for test. @abhinavGupta16 |
@Zhangxunmt After the fix is merged, a build will trigger automatically and you should see a successful build notification on the channel for 1.2.4 (it may take some time). You can then use the docker or tar file to test out of the fix worked. |
Thanks for reporting this issue. Why AD can pass CI:
We plan to pull job scheduler from maven or build locally with latest code to avoid such issue in future. |
opensearch now builds and starts successfully. Please feel free to reopen this issue if the issue persists |
Describe the bug
Opensearch fails to deploy with a missing lib error. The error is consistent with
tar
anddocker
deployment.To reproduce
For docker, run -
For tar -
Expected behavior
No response
Screenshots
No response
Host / Environment
No response
Additional context
No response
Relevant log output
The text was updated successfully, but these errors were encountered: