-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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] Plugin installation on OpenSearch 2.0.0 runs into jar hell #2590
Comments
[Work around] Can we remove the library from the security plugin since its included transitively in OpenSearch? |
The above workaround doesn't look working. @Rishikesh1159 Would you please help out? |
Sure @cliu123 I am working on it. I will provide you an update once I find anything. |
Due to some breaking changes in opensearch, security plugin build is failing. So, I cannot reproduce the issue. @cliu123 is working on fixeing build failures in security plugin. Once it is fixed I can resume working on this. |
I believe the repro includes using a build where @cliu123 has fixed the breaking changes you can get a copy from here https://github.com/cliu123/security/tree/bump_opensearch_dependency_to_2.0.0 The issue itself can be seen in the plugin install workflow link, here is the PR Inside the workflow logs there is an error, indicating the service did not start, and there is another task called
If you would like to reproduce locally you can by use the workflow file This is blocking the 2.0.0 release from building, lets please focus attention on this issue and reach out if we are having trouble making progress |
@mch2 will be working on this issue as top priority. Thanks @peternied @cliu123 |
taking a look |
Hi @cliu123, I had to use the tarball pulled by the failed workflow, it looks like there are security build failures against the latest version of the 2.0 branch? What is the desired dependency resolution here? I would suggest unless another version is required security inherits the jackson version from core vs declaring its own. Also this is failing on the validate step after the server is running. I would expect an error during plugin installation for jarHell vs at runtime, is that ignored/obfuscated in the workflow? I don't think there is any change required on OpenSearch here. Plugins should either exclude the inherited jar or inherit the jar and not declare its own version. OS also bumped to version 2.13.2.2 today if there was a requirement for 2.13.2 in security. |
I think we should merge opensearch-project/security#1709 to mitigate this issue (and prevent it from coming up again) |
Describe the bug
Installing security plugin on OpenSearch 2.0.0 fails on jar hell. The following is the error:
Expected behavior
Plugin is installed smoothly.
The text was updated successfully, but these errors were encountered: