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

JIRA Software not working after Cloud to Server import

XMLWordPrintable

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      Summary

      Importing from JIRA cloud to JIRA server 7.2.4 fails with error 'JIRA software is currently unavailable. This might be because an upgrade task has failed to run or has not yet completed'. 

      Environment

      JIRA Server 7.2.X

      JIRA Cloud 1000.555.0

      Steps to Reproduce

      1. Get backup of cloud instance
      2. Install latest version of jira 7.2.4
      3. Run XML import which completes without error

      Expected Results

      JIRA Software to work.

      Actual Results

      JIRA Software is not available. Restart/reinstall is not helping.

      Workaround

      Set or add a property "GreenHopper.Upgrade.Latest.Upgraded.Version" with value 51.

      Notes

      The root cause is that Cloud export is missing GreenHopper.Upgrade.Latest.Upgraded.Version property which is required by Server. Maybe we are missing a downgrade task that should set the property to 51 which is the last SAL build number.

       

      The symptoms are the same as in https://jira.atlassian.com/browse/JRA-47764 but probably the root causes are different.

            [JSWSERVER-15214] JIRA Software not working after Cloud to Server import

            Deleted Account (Inactive) added a comment -

            Hello

             

            I'm having the problem

            where can i set or add the property (GreenHopper.Upgrade.Latest.Upgraded.Version)

             

            directly in admin console or in property file on the server?

             

            regards

            Deleted Account (Inactive) added a comment - Hello   I'm having the problem where can i set or add the property (GreenHopper.Upgrade.Latest.Upgraded.Version)   directly in admin console or in property file on the server?   regards

            Timothy Harris added a comment -

            Wondering if this is related to my support request? https://support.atlassian.com/servicedesk/customer/portal/20/GHS-69810

            I am seeing

            2017-01-30 11:09:21,177 https-jsse-nio-8443-exec-20 ERROR [o.a.c.c.C.[.[localhost].[/].[action]] Servlet.service() for servlet [action] in context with path [] threw exception [com.opensymphony.module.propertyset.PropertyImplementationException: Failed operation: SetOperation[entityName=ApplicationUser,entityId=10001,propertyKey=user.last.issue.type.id,newType=5,newMapper=TypeMapper[handler=StringPropertyHandler,valueEntity=OSPropertyString]]] with root cause org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "pk_propertyentry" Detail: Key (id)=(30030) already exists.

            and

            org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "AO_60DB71_LEXORANK_pkey"
            Detail: Key ("ID")=(38) already exists.

            This is after I imported a cloud zip to a new running JIRA instance.

             

            Timothy Harris added a comment - Wondering if this is related to my support request? https://support.atlassian.com/servicedesk/customer/portal/20/GHS-69810 I am seeing 2017-01-30 11:09:21,177 https-jsse-nio-8443-exec-20 ERROR [o.a.c.c.C.[. [localhost] . [/] . [action] ] Servlet.service() for servlet [action] in context with path [] threw exception [com.opensymphony.module.propertyset.PropertyImplementationException: Failed operation: SetOperation[entityName=ApplicationUser,entityId=10001,propertyKey=user.last.issue.type.id,newType=5,newMapper=TypeMapper [handler=StringPropertyHandler,valueEntity=OSPropertyString] ]] with root cause org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "pk_propertyentry" Detail: Key (id)=(30030) already exists. and org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "AO_60DB71_LEXORANK_pkey" Detail: Key ("ID")=(38) already exists. This is after I imported a cloud zip to a new running JIRA instance.  

            Bobby Richards added a comment -

            I am having the same problem.  I will comment here and if its too different ill file a new bug.

            I have a xml backup from cloud from 11-18, the restore works fine but users cannot login.  They can however reset password and login.  So I assume hashing problem, but looks correct in mysql.  

            With a dump from the last week until today the restore fails with foreign key constraints and duplicate keys.  Hoping no new cloud updates broke this process, as this is time sensitive for me 

            Bobby Richards added a comment - I am having the same problem.  I will comment here and if its too different ill file a new bug. I have a xml backup from cloud from 11-18, the restore works fine but users cannot login.  They can however reset password and login.  So I assume hashing problem, but looks correct in mysql.   With a dump from the last week until today the restore fails with foreign key constraints and duplicate keys.  Hoping no new cloud updates broke this process, as this is time sensitive for me 

            bmccoy added a comment -

            Yeah avanderschyff and I are discussing.

             

            bmccoy added a comment - Yeah avanderschyff and I are discussing.  

            alex added a comment -

            bmccoy I believe you're across the shenanigans around SAL upgrade tasks etc. ?

            alex added a comment - bmccoy I believe you're across the shenanigans around SAL upgrade tasks etc. ?

              mho@atlassian.com Minh Ho
              spawlak Sebastian Pawlak (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: