Uploaded image for project: 'SR for Jira - Development'
  1. SR for Jira - Development
  2. SRJIRA-3293

Upgrading Automation for Jira disables the "execute-script-issue-action" module

    Details

    • Type: Bug
    • Status: Done
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 5.4.45, 5.4.47
    • Fix Version/s: None
    • Labels:
    • Sprint:
      SR4J Sprint 87
    • Critical Points:
      7.3

      Description

      There appears to be an issue with the Jira server Scriptrunner module "execute-script-issue-action" which is only enabled when the "Automation for Jira" plugin is installed and enabled.

      The Summary of the problem is:

      If you have automation for Jira installed and then you install Scriptrunner, everything works fine and the "execute-script-issue-action" module is enabled. However, if you then upgrade "Automation for Jira" the "execute-script-issue-action" module will get disabled and you have to disable and enable Scriptrunner to trigger the module to be re-enabled.

      If users do not notice they end up getting warnings like this in the "Automation for Jira" audit log area of the User interface:

      com.onresolve.jira.groovy.groovyrunner.execute-script-issue-action
      Failed to run pluggable rule component most likely because it's not currently installed or enabled

      Tests Performed

      I installed Automation for Jira 4.2.2 and then Script runner 5.4.45. The "execute-script-issue-action" was enabled correctly. I then installed Automation for Jira 5.0.1 and once the install finished, the script runner module "execute-script-issue-action" became disabled.


      Then I tried completely fresh server again. Going from Automation for Jira 4.2.2 to the current latest Automation for Jira using the update button rather than loading a jar file.

      I installed 4.2.2, then I installed Script runner 5.4.45. I checked and the "execute-script-issue-action" was enabled, which it was. Then I upgraded Automation for Jira to 5.1.3 using the update button and the "execute-script-issue-action" became disabled again.


      I also tried this on a fresh system:
      Install Automation for Jira 4.2.2 and then upgraded automation for Jira to 5.0.1.
      Then installed Script runner 5.4.45 and the "execute-script-issue-action" was enabled correctly.
      Then I upgraded Automation for Jira to 5.1.3 using the update button and the "execute-script-issue-action" became disabled again.


      I have even tried starting from Automation for Jira 5.0.1 then installing script runner 5.4.45, the "execute-script-issue-action" was again enabled correctly but as soon as I updated Automation for Jira. the "execute-script-issue-action" module became disabled again.


      So the "execute-script-issue-action" seems to always get disabled after updating Automation for Jira.


       

      log entries you see during the problem:

      2019-02-01 10:56:44,660 UpmAsynchronousTaskManager:thread-4 INFO admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.a.plugin.manager.DefaultPluginManager] Found mandatory, optional and dynamically dependent plugins to re-enable after plugin upgrade 'com.codebarrel.addons.automation': [com.onresolve.jira.groovy.groovyrunner]. Enabling...
       2019-02-01 10:56:44,665 UpmAsynchronousTaskManager:thread-4 INFO admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.a.plugin.manager.DefaultPluginManager] Updating plugin 'com.codebarrel.addons.automation' from version '4.2.2' to version '5.0.1'2019-02-01 10:56:44,667 UpmAsynchronousTaskManager:thread-4 INFO admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.a.plugin.manager.DefaultPluginManager] Disabling com.codebarrel.addons.automation
       2019-02-01 10:56:44,671 UpmAsynchronousTaskManager:thread-4 WARN admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.c.j.p.automation.schedule.RulePollerServiceLauncher] Rule poller stopped
       2019-02-01 10:56:44,671 UpmAsynchronousTaskManager:thread-4 WARN admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.c.j.p.automation.schedule.RuleScheduleServiceLauncher] Unregistering scheduler: com.codebarrel.jira.plugin.automation.schedule.RuleScheduleServiceLauncher.scheduler
       2019-02-01 10:56:44,671 UpmAsynchronousTaskManager:thread-4 WARN admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Shutting down automation-queue-claimer pool...
       2019-02-01 10:56:44,672 UpmAsynchronousTaskManager:thread-4 WARN admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] automation-queue-claimer pool shutdown complete.
       2019-02-01 10:56:44,673 UpmAsynchronousTaskManager:thread-4 WARN admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Shutting down automation-rule-executor pool...
       2019-02-01 10:56:44,673 UpmAsynchronousTaskManager:thread-4 WARN admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] automation-rule-executor pool shut down complete.
       2019-02-01 10:56:44,975 Gemini Blueprint context shutdown thread2 DEBUG admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] ungetService bundle [com.codebarrel.jira.plugin.automation-for-jira]
       2019-02-01 10:56:44,976 UpmAsynchronousTaskManager:thread-4 DEBUG admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] onPluginDisabledEvent removing delegate for [com.codebarrel.addons.automation]
       2019-02-01 10:56:44,979 UpmAsynchronousTaskManager:thread-4 INFO admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.a.plugin.loaders.ScanningPluginLoader] Removed plugin 'com.codebarrel.addons.automation'2019-02-01 10:56:45,340 UpmAsynchronousTaskManager:thread-4 INFO admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (2): [com.codebarrel.addons.automation, com.onresolve.jira.groovy.groovyrunner], 300 seconds remaining
       2019-02-01 10:56:46,341 UpmAsynchronousTaskManager:thread-4 INFO admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (2): [com.codebarrel.addons.automation, com.onresolve.jira.groovy.groovyrunner], 298 seconds remaining
       2019-02-01 10:56:47,344 UpmAsynchronousTaskManager:thread-4 INFO admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (2): [com.codebarrel.addons.automation, com.onresolve.jira.groovy.groovyrunner], 297 seconds remaining
       2019-02-01 10:56:48,344 UpmAsynchronousTaskManager:thread-4 INFO admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1): [com.onresolve.jira.groovy.groovyrunner], 296 seconds remaining
       2019-02-01 10:56:49,607 UpmAsynchronousTaskManager:thread-4 DEBUG admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.a.activeobjects.osgi.OsgiServiceUtilsImpl] Registering service net.java.ao.atlassian.AtlassianTableNameConverter@397c30c3 with interface net.java.ao.schema.TableNameConverter and properties
      {com.atlassian.plugin.key=com.codebarrel.jira.plugin.automation-for-jira}
       2019-02-01 10:56:49,608 UpmAsynchronousTaskManager:thread-4 DEBUG admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.a.activeobjects.osgi.OsgiServiceUtilsImpl] Registering service com.atlassian.activeobjects.config.internal.DefaultActiveObjectsConfiguration@a418da01 with interface com.atlassian.activeobjects.config.ActiveObjectsConfiguration and properties {com.atlassian.plugin.key=com.codebarrel.jira.plugin.automation-for-jira}
      2019-02-01 10:56:49,610 UpmAsynchronousTaskManager:thread-4 DEBUG admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] onPluginModuleEnabledEvent storing unattached <ao> configuration module for [com.codebarrel.addons.automation]
       2019-02-01 10:56:49,638 UpmAsynchronousTaskManager:thread-4 WARN admin 649x554x1 vjz4sc 172.17.0.1 /rest/plugins/1.0/installed-marketplace [c.c.j.p.automation.schedule.RuleScheduleServiceLauncher] Scheduling automation rule scheduler job
      

       

      Workaround

      After Upgrading "Automation for Jira" disable and re-enable Scriptrunner to make sure the "execute-script-issue-action" gets re-enabled as well

       

      Note: "Automation for Jira" mention issues with upgrading here : https://docs.automationforjira.com/upgrade/upgrade-lite-to-pro-server.html#upgrade-troubleshooting 

      "third party add-ons providing these actions were disabled or not registered correctly

       

       

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mclark Matthew Clark
              Reporter:
              mclark Matthew Clark
              Votes:
              4 Vote for this issue
              Watchers:
              21 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: