Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-71927

Zero Down Time (ZDU) upgrades are not listed in System Info->Upgrade history

XMLWordPrintable

      Problem

      Zero Downtime Upgrade process in Jira DC 7.x and 8.x is not adding the target version information in the System Info -> Upgrade history

      Environment

      Jira Data Center 7.x and 8.x

      Steps to Reproduce

      • Install Jira Data Center 7.x or 8.x
      • Upgrade Jira DC to a newer version (following the document Upgrading Jira Data Center with zero downtime
      • Under System Info > Last Upgrade click in the link "Get more upgrade history details" 

      Expected Results

      Target version should be added in the Upgrade History
      (Database table upgradeversionhistory)

      Actual Results

      Target version is not added in the Upgrade History
      (Database table upgradeversionhistory)

      Workaround

      The SQL query below can be used to insert the missing values in the table "upgradeversionhistory"
       The query was created for PostgreSQL and syntax may vary to other database vendors
      Replace the '<UPGRADEDATE>','<TARGETBUILD>','<TARGETVERSION>' for the proper values

      INSERT INTO upgradeversionhistory (id, timeperformed, targetbuild, targetversion)
VALUES ((SELECT MAX(id)+1 FROM upgradeversionhistory),'<UPGRADEDATE>','<TARGETBUILD>','<TARGETVERSION>');

            [JRASERVER-71927] Zero Down Time (ZDU) upgrades are not listed in System Info->Upgrade history

            Paul Baumann added a comment -

            The issue was appearing on our Datacenter instance when upgrading from 9.4.14 to 9.4.18 and the bug is ongoing since then even after upgrade to LTS 9.12.x.

            So the bug isn't resolved. The workaround is only a workaround but not persistent.     

            Paul Baumann added a comment - The issue was appearing on our Datacenter instance when upgrading from 9.4.14 to 9.4.18 and the bug is ongoing since then even after upgrade to LTS 9.12.x. So the bug isn't resolved. The workaround is only a workaround but not persistent.     

              Unassigned Unassigned
              bsilva@atlassian.com Bruno
              Affected customers:
              11 This affects my team
              Watchers:
              14 Start watching this issue

                Created:
                Updated: