Skip to content

[BUG] Plugin installation fails due to jar hell #2324

@stephen-crawford

Description

@stephen-crawford

What is the bug?
When executing the plugin install action on main, the process fails due to Exception in thread "main" java.lang.IllegalStateException: failed to load plugin opensearch-security due to jar hell

This occurs when attempting to install the security plugin into OpenSearch core and results in the following complete error log:


-> Rolled back file:D:\a\security\security\opensearch-security.zip
	at org.opensearch.plugins.PluginsService.checkBundleJarHell(PluginsService.java:681)
	at org.opensearch.plugins.InstallPluginCommand.jarHellCheck(InstallPluginCommand.java:862)
	at org.opensearch.plugins.InstallPluginCommand.loadPluginInfo(InstallPluginCommand.java:830)
	at org.opensearch.plugins.InstallPluginCommand.installPlugin(InstallPluginCommand.java:875)
	at org.opensearch.plugins.InstallPluginCommand.execute(InstallPluginCommand.java:275)
	at org.opensearch.plugins.InstallPluginCommand.execute(InstallPluginCommand.java:249)
	at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:104)
	at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138)
	at org.opensearch.cli.MultiCommand.execute(MultiCommand.java:104)
	at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138)
	at org.opensearch.cli.Command.main(Command.java:101)
	at org.opensearch.plugins.PluginCli.main(PluginCli.java:66)
Caused by: java.lang.IllegalStateException: jar hell!
class: com.fasterxml.jackson.databind.AbstractTypeResolver
jar1: D:\a\security\security\opensearch-3.0.0-SNAPSHOT\lib\jackson-databind-2.14.1.jar
jar2: D:\a\security\security\opensearch-3.0.0-SNAPSHOT\plugins\.installing-17316426811803655475\jackson-databind-2.14.1.jar
	at org.opensearch.bootstrap.JarHell.checkClass(JarHell.java:314)
	at org.opensearch.bootstrap.JarHell.checkJarHell(JarHell.java:213)
	at org.opensearch.plugins.PluginsService.checkBundleJarHell(PluginsService.java:679)
	... 11 more

How can one reproduce the bug?
Steps to reproduce the behavior:

  1. Go to the main branch of the security repo
  2. Make a trivial change to a forked version of the repo.
  3. Wait for the plugin install workflow to fail
  4. See error

What is the expected behavior?
This is a new error after the weekend.

Do you have any additional context?
The action worked as expected on Friday.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingsprint backlogtriagedIssues labeled as 'Triaged' have been reviewed and are deemed actionable.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions