BitBucket Server - Error on enabling plugins after upgrade

[Jumail Mundekkat]

Hey there,

We recently updated our BitBucket Server instance from 5.1 to 6.4 and after the upgrade, the only plugin that would successfully enable was Notifyr. Every other plugin would fail with "This app failed to enable. Refer to the logs for more information.".

Heading over to the logs, I run into:

Caused by: java.lang.IllegalStateException: The bundle is uninstalled.
at org.apache.felix.framework.Felix.getBundleResources(Felix.java:1706)
at org.eclipse.gemini.blueprint.util.BundleDelegatingClassLoader.getResources(BundleDelegatingClassLoader.java:186)
at org.springframework.core.io.support.PropertiesLoaderUtils.loadAllProperties(PropertiesLoaderUtils.java:178)
at org.eclipse.gemini.blueprint.extender.internal.support.NamespacePlugins$Plugin.resolve(NamespacePlugins.java:77)
at org.eclipse.gemini.blueprint.extender.internal.support.NamespacePlugins$5.operate(NamespacePlugins.java:209)
at org.eclipse.gemini.blueprint.extender.internal.support.NamespacePlugins$5.operate(NamespacePlugins.java:205)
at org.eclipse.gemini.blueprint.extender.internal.support.LazyBundleRegistry.apply(LazyBundleRegistry.java:159)
at org.eclipse.gemini.blueprint.extender.internal.support.NamespacePlugins.doResolve(NamespacePlugins.java:205)
at org.eclipse.gemini.blueprint.extender.internal.support.NamespacePlugins.resolve(NamespacePlugins.java:169)
at org.eclipse.gemini.blueprint.context.support.TrackingUtil$OsgiServiceHandler.invoke(TrackingUtil.java:106)
at org.eclipse.gemini.blueprint.context.support.DelegatedNamespaceHandlerResolver.resolve(DelegatedNamespaceHandlerResolver.java:55)
... 15 common frames omitted

I've tried the solutions listen in here to no avail. Anyone have any other ideas on how I might get plugins working again?

Thanks,

Jumail 

[Jumail Mundekkat · Accepted solution]

It looks either removing $BITBUCKET_HOME/plugins/.osgi-cache/ or restarting the server (had a stuck process that needed to be killed manually) fixed it!

[Ana Retamal]

Hi Jumail,

When upgrading from one version to another major version, one of the required steps is to check which 3rd party plugins are still compatible with the Bitbucket version you intend to upgrade to. Can you confirm you made that already? After that, you'll have 2 options:

1. You can revert to the previous version from backups and do the analysis above to determine to which version you can safely upgrade to;

or

2. You can keep the existing upgraded instance and search for alternative plugins, which might not necessarily exist. If you go with this option, it might be useful to contact the developers of the existing plugins and ask them if they plan to upgrade those plugins.

For more information, you can read Bitbucket Server upgrade guide.

If you did the checks and the plugins should be supposed to be working but aren't, let us know so we can have a deeper look.

Hope that helps!

Ana

[Jumail Mundekkat]

Hi Ana,

Thanks for your help earlier and your reply.

I did already confirm which plugins were compatible and which ones were not, and attempted to to the update, which disabled all my plugins in the process.

The plugins I was trying to enable were ones that were compatible with the new version of Bitbucket Server I upgraded to, but I've gone ahead and removed all the plugins other than the universal plugin manager itself:

Even then, trying to update the universal plugin manager fails with the same stacktrace (except this time for the self-update plugin).