Can't update UPM after upgrade from 4.3.2 o 5.11.1

Question

After BitBucket upgrade, I was able to upgrade a 3rd party plugin, but not the UPM. Existing UPM is 2.22.9, available UPM is 2.22.11. Standard logs don't say a word about the failure, but enabling detailed log I see this: 2018-06-11 14:57:12,049 INFO [UpmAsynchronousTaskManager:thread-2] roberto @HEGJ1Nx897x399x0 1wz2ajz 192.168.0.1,192.168.0.70 "POST /rest/plugins/1.0/ HTTP/1.1" c.a.u.c.i.PluginDownloadServiceImpl Downloading plugin artifact from [https://marketplace.atlassian.com/download/apps/23915/version/3000010]... 2018-06-11 14:57:17,611 INFO [UpmAsynchronousTaskManager:thread-2] roberto @HEGJ1Nx897x399x0 1wz2ajz 192.168.0.1,192.168.0.70 "POST /rest/plugins/1.0/ HTTP/1.1" c.a.u.impl.SelfUpdateControllerImpl Extracted self-update plugin to /var/atlassian/application-data/stash/tmp/upm-selfupdate7392906496933242226.jar 2018-06-11 14:57:17,611 INFO [UpmAsynchronousTaskManager:thread-2] roberto @HEGJ1Nx897x399x0 1wz2ajz 192.168.0.1,192.168.0.70 "POST /rest/plugins/1.0/ HTTP/1.1" c.a.u.impl.SelfUpdateControllerImpl Installing self-update plugin 2018-06-11 14:57:17,624 INFO [UpmAsynchronousTaskManager:thread-2] roberto @HEGJ1Nx897x399x0 1wz2ajz 192.168.0.1,192.168.0.70 "POST /rest/plugins/1.0/ HTTP/1.1" c.a.p.loaders.ScanningPluginLoader No plugins found to be installed 2018-06-11 14:57:17,684 INFO [UpmAsynchronousTaskManager:thread-2] roberto @HEGJ1Nx897x399x0 1wz2ajz 192.168.0.1,192.168.0.70 "POST /rest/plugins/1.0/ HTTP/1.1" c.a.p.o.f.UnrecognisedModuleDescriptorFallbackFactory Unknown module descriptor of type rest registered as an unrecognised descriptor. 2018-06-11 14:57:17,689 INFO [UpmAsynchronousTaskManager:thread-2] roberto @HEGJ1Nx897x399x0 1wz2ajz 192.168.0.1,192.168.0.70 "POST /rest/plugins/1.0/ HTTP/1.1" c.a.p.manager.DefaultPluginManager Updating plugin 'com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin' from version '2.22.9' to version '2.22.9' 2018-06-11 14:57:17,701 INFO [FelixDispatchQueue] c.a.p.o.c.f.FelixOsgiContainerManager Unresolved bundle com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin (127) 2018-06-11 14:57:17,701 INFO [FelixDispatchQueue] c.a.p.o.c.f.FelixOsgiContainerManager Uninstalled bundle com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin (127) 2018-06-11 14:57:17,733 DEBUG [UpmAsynchronousTaskManager:thread-2] roberto @HEGJ1Nx897x399x0 1wz2ajz 192.168.0.1,192.168.0.70 "POST /rest/plugins/1.0/ HTTP/1.1" c.a.s.i.p.s.ExtendedDirectoryScanner Plugin file doesn't exist to delete. Ignoring. 2018-06-11 14:57:17,733 INFO [UpmAsynchronousTaskManager:thread-2] roberto @HEGJ1Nx897x399x0 1wz2ajz 192.168.0.1,192.168.0.70 "POST /rest/plugins/1.0/ HTTP/1.1" c.a.p.loaders.ScanningPluginLoader Removed plugin 'com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin' I suppose I could update it manually, but I'd not want to do the same every time. Any clue why this fails? UPDATE The problem isn't with UPM itself. Installing any new plugin succeeds but fails to enable the plugin. However, enabling the plugin manually after installation, succeeds. The same happens with UPM: I found the following plugins: - Atlassian Universal Plugin Manager (2.22.9, installed, enabled) - Atlassian Universal Plugin Manager Self-Update Plugin (2.22.9, installed, disabled) Once manually enabled the Self-Update plugin, it did update UPM. So the question now is: why are installed plugins not enabled? The logs say nothing.

Roberto Cornacchia · Answer

Hi Aaron,

Thanks for your reply.

The plugins I installed are Commit Graph, Power Editor for Bitbucket, Push Email Notifier. But I'm pretty sure the same would happen with any plugin.

My understanding is that the UPM Self-Update Plugin is not one you would normally see. When you ask to update UPM, the UPM Self-Update is downloaded and enabled. When enabled, this updates the UPM, then removes itself.

I no longer see it (I now have the up-to-date UPM), but after it failed I had captured this screenshot. You can see that UPM Self-Update just waited to be enabled. When I did so, it updated UPM and removed itself.

Aaron · Answer

Hello Roberto,

Welcome to Atlassian Community!

Hmm.. That's really weird. I'm sitting here with a 5.11.1 instance with 2.22.11 UPM and I'm able to install plugins and they are enabled by default. What plugins are you installing and I can give it a shot with those specifically. The one thing I find interesting is you mentioned an Atlassian Universal Plugin Manager Self-Update Plugin. That isn't a plugin I can see on my instance. Could you maybe send some screenshots of what you are seeing in terms of that plugin?

Regards,
Aaron Levinson
Dev Tools Support Engineer