Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-15815

Updating UPM temporarily disables Jira Software and required bundled plugins

XMLWordPrintable

    • 7.01
    • 119
    • Severity 1 - Critical
    • 5,015
    • Hide
      Atlassian Update – 12 September 2019

      Dear Jira users,

      Thank you for your votes and thoughts on this issue.

      Recently we have been working on improving the apps management in Jira Server by addressing one of the most impactful bugs: JRASERVER-64908.

      From Jira Server 8.2.0 we’ve fixed several issues that caused huge performance degradation in large Jira instances when installing or updating apps.

      After carefully analysing your comments in this ticket, we see that the negative performance impact of installing and updating apps is a major part of this issue. Moreover after the changes made to UPM plugin based on internal tests we see that app downtime is reduced. For example:

      • on Portfolio example restart time decreased significantly, from 4min to 12sec.
      • UPM upgrade time decreased from 10min to 30sec.

      While the described behaviour is expect due to UPM dependency, we believe we largely mitigated the problem described in this ticket, that is why we decided to close it with resolution: answered.

      We are currently thinking about further improvements to Apps management in Jira Server and we would like to get more clarity about the problem space. If we will leave this ticket open, we will not be able to judge easily what is the biggest challenge for our customers, what we should prioritise next in this area?

      That is why we have created the following suggestions and would like to hear your voice there or in comments to this issue.

      Our suggestions based on your comments in this issue are:

      https://jira.atlassian.com/browse/JRASERVER-69963

      https://jira.atlassian.com/browse/JRASERVER-69958

      https://jira.atlassian.com/browse/JRASERVER-69959

      https://jira.atlassian.com/browse/JRASERVER-69961

      https://jira.atlassian.com/browse/JRASERVER-69962

      Looking forward for your comments.

      Thank you,
      Product Management Team
      Jira Server and Data Center

      Show
      Atlassian Update – 12 September 2019 Dear Jira users, Thank you for your votes and thoughts on this issue. Recently we have been working on improving the apps management in Jira Server by addressing one of the most impactful bugs: JRASERVER-64908 . From Jira Server 8.2.0 we’ve fixed several issues that caused huge performance degradation in large Jira instances when installing or updating apps. After carefully analysing your comments in this ticket, we see that the negative performance impact of installing and updating apps is a major part of this issue. Moreover after the changes made to UPM plugin based on internal tests we see that app downtime is reduced. For example: on Portfolio example restart time decreased significantly, from 4min to 12sec. UPM upgrade time decreased from 10min to 30sec. While the described behaviour is expect due to UPM dependency, we believe we largely mitigated the problem described in this ticket, that is why we decided to close it with resolution: answered. We are currently thinking about further improvements to Apps management in Jira Server and we would like to get more clarity about the problem space. If we will leave this ticket open, we will not be able to judge easily what is the biggest challenge for our customers, what we should prioritise next in this area? That is why we have created the following suggestions and would like to hear your voice there or in comments to this issue. Our suggestions based on your comments in this issue are: https://jira.atlassian.com/browse/JRASERVER-69963 https://jira.atlassian.com/browse/JRASERVER-69958 https://jira.atlassian.com/browse/JRASERVER-69959 https://jira.atlassian.com/browse/JRASERVER-69961 https://jira.atlassian.com/browse/JRASERVER-69962 Looking forward for your comments. Thank you, Product Management Team Jira Server and Data Center

      Experienced behavior

      Updating UPM causes JIRA Software and required bundled plugins to temporarily disable, resulting in unexpected behavior. JIRA cannot be used properly during this time.

      Steps to reproduce

      1. Install JIRA Software 7.3.4
      2. Update UPM to 2.22.2 or 2.22.3
      3. Access dashboard while UPM is updating

      During UPM update JIRA Software and required bundled plugins will be temporarily disabled: 

      2017-04-12 14:59:42,618 UpmAsynchronousTaskManager:thread-3 INFO tim 899x672x1 1w3t0ih 192.168.56.1 /rest/plugins/1.0/ [c.a.plugin.loaders.ScanningPluginLoader] No plugins found to be installed
2017-04-12 14:59:42,850 UpmAsynchronousTaskManager:thread-3 INFO tim 899x672x1 1w3t0ih 192.168.56.1 /rest/plugins/1.0/ [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1): [com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin], 60 seconds remaining
2017-04-12 15:00:05,056 pool-41-thread-1 INFO tim 900x808x1 1w3t0ih 192.168.56.1 /rest/plugins/self-update/1.0/ [c.a.plugin.loaders.ScanningPluginLoader] No plugins found to be installed
2017-04-12 15:00:06,760 pool-41-thread-1 INFO tim 900x808x1 1w3t0ih 192.168.56.1 /rest/plugins/self-update/1.0/ [c.a.plugin.manager.DefaultPluginManager] Found dependent enabled plugins for plugins '[com.atlassian.upm.atlassian-universal-plugin-manager-plugin]': [com.atlassian.jira-core-project-templates(OPTIONAL), com.atlassian.jira.collector.plugin.jira-issue-collector-plugin(OPTIONAL), com.atlassian.jira.gadgets(OPTIONAL), com.atlassian.jira.jira-core-reports-plugin(OPTIONAL), com.atlassian.jira.jira-issue-link-applinks-common-plugin(OPTIONAL), com.atlassian.jira.jira-issue-link-confluence-plugin(OPTIONAL), com.atlassian.jira.jira-issue-link-remote-jira-plugin(OPTIONAL), com.atlassian.jira.jira-issue-nav-components(OPTIONAL), com.atlassian.jira.jira-issue-nav-plugin(OPTIONAL), com.atlassian.jira.jira-project-config-plugin(OPTIONAL), com.atlassian.jira.jira-projects-issue-navigator(OPTIONAL), com.atlassian.jira.jira-projects-plugin(OPTIONAL), com.atlassian.jira.jira-quick-edit-plugin(OPTIONAL), com.atlassian.jira.jira-share-plugin(OPTIONAL), com.atlassian.jira.jira-software-application(MANDATORY), com.atlassian.jira.jira-view-issue-plugin(OPTIONAL), com.atlassian.jira.mobile(OPTIONAL), com.atlassian.jira.plugin.ext.bamboo(OPTIONAL), com.atlassian.jira.plugins.inline-create.jira-inline-issue-create-plugin(OPTIONAL), com.atlassian.jira.plugins.jira-admin-helper-plugin(OPTIONAL), com.atlassian.jira.plugins.jira-bitbucket-connector-plugin(OPTIONAL), com.atlassian.jira.plugins.jira-development-integration-plugin(OPTIONAL), com.atlassian.jira.plugins.jira-dnd-attachment-plugin(OPTIONAL), com.atlassian.jira.plugins.jira-importers-asana-plugin(OPTIONAL), com.atlassian.jira.plugins.jira-importers-bitbucket-plugin(OPTIONAL), com.atlassian.jira.plugins.jira-importers-github-plugin(OPTIONAL), com.atlassian.jira.plugins.jira-importers-plugin(OPTIONAL), com.atlassian.jira.plugins.jira-importers-redmine-plugin(OPTIONAL), com.atlassian.jira.plugins.jira-importers-trello-plugin(OPTIONAL), com.atlassian.jira.plugins.jira-software-plugin(OPTIONAL), com.atlassian.jira.plugins.jira-transition-triggers-plugin(OPTIONAL), com.atlassian.jira.plugins.jira-workflow-designer(OPTIONAL), com.atlassian.jira.plugins.webhooks.jira-webhooks-plugin(OPTIONAL), com.atlassian.jira.plugins.workflow.sharing.jira-workflow-sharing-plugin(OPTIONAL), com.atlassian.jira.project-templates-plugin(OPTIONAL), com.atlassian.jira.rest(OPTIONAL), com.atlassian.jirafisheyeplugin(OPTIONAL), com.atlassian.labs.hipchat.hipchat-for-jira-plugin(OPTIONAL), com.atlassian.mywork.mywork-jira-provider-plugin(OPTIONAL), com.atlassian.plugins.helptips.jira-help-tips(OPTIONAL), com.pyxis.greenhopper.jira(MANDATORY)].  Disabling...

      Disabled bundled plugins result in unexpected behavior.

      • Example: com.atlassian.jira.gadgets being disabled will result in 500 error when loading dashboards:
      2017-04-12 15:00:17,074 http-nio-8080-exec-8 ERROR      [o.a.c.c.C.[.[localhost].[/].[action]] Servlet.service() for servlet [action] in context with path [] thr
ew exception [java.lang.IllegalArgumentException: Root page 'com.atlassian.jira.gadgets:dashboard-page' does not exist!] with root cause
java.lang.IllegalArgumentException: Root page 'com.atlassian.jira.gadgets:dashboard-page' does not exist!
        at com.atlassian.plugin.webresource.assembler.DefaultWebResourceAssembler$2.requirePage(DefaultWebResourceAssembler.java:189)
        at com.atlassian.jira.web.action.Dashboard.doExecute(Dashboard.java:181)
        at webwork.action.ActionSupport.execute(ActionSupport.java:165)
        at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63)
        at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39)
        ... 6 filtered
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
        ... 56 filtered
        at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
        ... 58 filtered
        at com.atlassian.jira.security.JiraSecurityFilter.lambda$doFilter$0(JiraSecurityFilter.java:80)
        ... 1 filtered
        at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:78)
        ... 36 filtered
        at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)
        ... 10 filtered
        at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
        ... 4 filtered
        at com.atlassian.web.servlet.plugin.LocationCleanerFilter.doFilter(LocationCleanerFilter.java:36)
        ... 29 filtered
        at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25)
        ... 28 filtered
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        at java.lang.Thread.run(Thread.java:745)

      Any problems are temporary. JIRA Software and bundled plugins will re-enable once UPM update is complete. This may take multiple minutes.

      Workaround

      Do not update UPM in production JIRA applications outside of planned maintenance windows. As a best practice test updates to plugins, including UPM, in a test or staging environment prior to updating production.
      See related Best Practices for Managing JIRA Application Add-ons

      Additional details

      UPM update has been tested with JIRA Core, JIRA Software and JIRA Service Desk. Required bundled plugins are only disabled when JIRA Software is present.

      • UPM update after installing JIRA Software onto an existing JIRA installation will not result in this problem unless JIRA has been restarted after installing JIRA Software and before updating UPM.

          Form Name

            [JSWSERVER-15815] Updating UPM temporarily disables Jira Software and required bundled plugins

            Mechee added a comment -

            I also had this error. Rebooting resolved the issue, but if that is always the case then updates to the UPM need to include that fact in the prompt and upgrade instructions. Having it seem to be an innocuous update is misleading.

            Mechee added a comment - I also had this error. Rebooting resolved the issue, but if that is always the case then updates to the UPM need to include that fact in the prompt and upgrade instructions. Having it seem to be an innocuous update is misleading.

            Carl Price added a comment -

            Still got this issue today (9.12.5). Over 20 minutes I waited for this app to update. What's worse though is that it seems to be spearing to other Atlassian plugins. I had this problem with updating "SSO for Atlassian Data Center" and "Jira Service Management" once the Jira Software platform had been updated.

            Carl Price added a comment - Still got this issue today (9.12.5). Over 20 minutes I waited for this app to update. What's worse though is that it seems to be spearing to other Atlassian plugins. I had this problem with updating "SSO for Atlassian Data Center" and "Jira Service Management" once the Jira Software platform had been updated.

            Loc Nguyen (Inactive) added a comment -

            https://getsupport.atlassian.com/browse/SDS-63169

            Loc Nguyen (Inactive) added a comment - https://getsupport.atlassian.com/browse/SDS-63169

            Dawn Fama added a comment -

            We just upgraded to DataCenter license and are experiencing the same issue.

            8.14.1 JS server and JSM 4.14.1 to DC was fine.  When we upgraded to 8.15 and 4.15, it seemed to add a bunch of system add ons and unlock alot of unnecessary languages and we can't seem to run any add on updates while not in safe mode.  We are not a clustered environment.   

            Dawn Fama added a comment - We just upgraded to DataCenter license and are experiencing the same issue. 8.14.1 JS server and JSM 4.14.1 to DC was fine.  When we upgraded to 8.15 and 4.15, it seemed to add a bunch of system add ons and unlock alot of unnecessary languages and we can't seem to run any add on updates while not in safe mode.  We are not a clustered environment.   

            Grazyna Kaszkur added a comment -

            Dear Jira users,

            Thank you for your votes and thoughts on this issue.

            Recently we have been working on improving the apps management in Jira Server by addressing one of the most impactful bugs: JRASERVER-64908.

            From Jira Server 8.2.0 we’ve fixed several issues that caused huge performance degradation in large Jira instances when installing or updating apps.

            After carefully analysing your comments in this ticket, we see that the negative performance impact of installing and updating apps is a major part of this issue. Moreover after the changes made to UPM plugin based on internal tests we see that app downtime is reduced. For example:

            • on Portfolio example restart time decreased significantly - from 4min to 12sec.
            • UPM upgrade time decreased from 10min to 30sec.

            While the described behaviour is expect due to UPM dependency, we believe we largely mitigated the problem described in this ticket, that is why we decided to close it with resolution: answered.

            We are currently thinking about further improvements to Apps management in Jira Server and we would like to get more clarity about the problem space. If we will leave this ticket open, we will not be able to judge easily what is the biggest challenge for our customers, what we should prioritise next in this area ?

            That is why we have created the following suggestions and would like to hear your voice there or in comments to this issue.

            Our suggestions based on your comments in this issue are:

            https://jira.atlassian.com/browse/JRASERVER-69963

            https://jira.atlassian.com/browse/JRASERVER-69958

            https://jira.atlassian.com/browse/JRASERVER-69959

            https://jira.atlassian.com/browse/JRASERVER-69961

            https://jira.atlassian.com/browse/JRASERVER-69962

            Looking forward for your comments.

            Thank you,
            Product Management Team
            Jira Server and Data Center

            Grazyna Kaszkur added a comment - Dear Jira users, Thank you for your votes and thoughts on this issue. Recently we have been working on improving the apps management in Jira Server by addressing one of the most impactful bugs: JRASERVER-64908 . From Jira Server 8.2.0 we’ve fixed several issues that caused huge performance degradation in large Jira instances when installing or updating apps. After carefully analysing your comments in this ticket, we see that the negative performance impact of installing and updating apps is a major part of this issue. Moreover after the changes made to UPM plugin based on internal tests we see that app downtime is reduced. For example: on Portfolio example restart time decreased significantly - from 4min to 12sec. UPM upgrade time decreased from 10min to 30sec. While the described behaviour is expect due to UPM dependency, we believe we largely mitigated the problem described in this ticket, that is why we decided to close it with resolution: answered. We are currently thinking about further improvements to Apps management in Jira Server and we would like to get more clarity about the problem space. If we will leave this ticket open, we will not be able to judge easily what is the biggest challenge for our customers, what we should prioritise next in this area ? That is why we have created the following suggestions and would like to hear your voice there or in comments to this issue. Our suggestions based on your comments in this issue are: https://jira.atlassian.com/browse/JRASERVER-69963 https://jira.atlassian.com/browse/JRASERVER-69958 https://jira.atlassian.com/browse/JRASERVER-69959 https://jira.atlassian.com/browse/JRASERVER-69961 https://jira.atlassian.com/browse/JRASERVER-69962 Looking forward for your comments. Thank you, Product Management Team Jira Server and Data Center

            Jason D Smith added a comment -

            Greg, I think because they'd have to list every version in Jira history

            Jason D Smith added a comment - Greg, I think because they'd have to list every version in Jira history

            Greg Warner added a comment -

            Same problem here. Why are the affects versions not listed?

            Greg Warner added a comment - Same problem here. Why are the affects versions not listed?

            Mohana Sundar J added a comment -

            Our Production had an outage early 1 hour due to updating this buggy UPM plugin. Try to fix this soon as it is was a impact.

             

            Mohana Sundar J added a comment - Our Production had an outage early 1 hour due to updating this buggy UPM plugin. Try to fix this soon as it is was a impact.  

            Piotr Dziedziel added a comment -

            Yea, we have the same situation that after update we need to restart all nodes not a good idea.

            Piotr Dziedziel added a comment - Yea, we have the same situation that after update we need to restart all nodes not a good idea.

            Brad Mace [ATS] added a comment -

            This just locked up our Jira instance for 45 minutes, with no recourse other than a complete restart of Jira. Not great.

            Brad Mace [ATS] added a comment - This just locked up our Jira instance for 45 minutes, with no recourse other than a complete restart of Jira. Not great.

              Unassigned Unassigned
              tevans Tim Evans (Inactive)
              Affected customers:
              84 This affects my team
              Watchers:
              117 Start watching this issue

                Created:
                Updated:
                Resolved: