Details
-
Bug
-
Resolution: Fixed
-
Highest
-
3.12.3
-
3.12
-
Description
Some data was added to a backup by 3.12.3 that made that backup unusable for 3.13. The relevant difference between the two backups is
related to FishEye:
mdoar@svn4:~/bchop> diff old/2008-Sep-08--1347.xml new/2008-Sep-09--0148.xml | grep -i fisheye > <OSPropertyEntry id="10487" entityName="jira.properties" entityId="1" propertyKey="jira.plugin.state-.com.atlassian.jira.ext.fisheye:crucible-issuepanel" type="5"/> > <OSPropertyEntry id="10483" entityName="jira.properties" entityId="1" propertyKey="jira.plugin.state-.com.atlassian.jira.ext.fisheye:crucible-projectpanel" type="5"/> > <OSPropertyEntry id="10484" entityName="jira.properties" entityId="1" propertyKey="jira.plugin.state-.com.atlassian.jira.ext.fisheye:perforceManager" type="5"/> > <OSPropertyEntry id="10485" entityName="jira.properties" entityId="1" propertyKey="jira.plugin.state-.com.atlassian.jira.ext.fisheye:perforceConfig" type="5"/> > <OSPropertyEntry id="10486" entityName="jira.properties" entityId="1" propertyKey="jira.plugin.state-.com.atlassian.jira.ext.fisheye:createjob-function" type="5"/> > <OSPropertyEntry id="10488" entityName="jira.properties" entityId="1" propertyKey="jira.plugin.state-.com.atlassian.jira.ext.fisheye:cruciblecharting" type="5"/>
and importing the second backup produces errors with 3.13 during an attempted import that contained the exception:
earlier/logs/catalina.out:2008-10-14 19:30:49,289 main FATAL [atlassian.jira.upgrade.ConsistencyLauncher] A RuntimeException occurred during ConsistencyLauncher servlet context initialisation - com.atlassian.jira.ext.fisheye.config.RefreshManager doesn't have any satisfiable constructors. Unsatisfiable dependencies: [[interface com.atlassian.jira.ext.fisheye.ChangeSetManager, interface com.atlassian.jira.ext.fisheye.config.FishEyeConfig, interface com.atlassian.jira.ext.fisheye.config.FishEyeInstanceStore, interface com.atlassian.jira.ext.fisheye.config.RepositoryPathStore, interface com.atlassian.jira.ext.fisheye.perforce.PerforceConfig, interface com.atlassian.jira.ext.fisheye.perforce.PerforceManager, interface com.atlassian.jira.ext.fisheye.config.CustomQueryStore, interface com.atlassian.jira.ext.fisheye.config.FishEyeRepositoryStore, interface com.atlassian.jira.ext.fisheye.FishEyeManager]].
This does not occur with the first backup file.
The reason that I have filed this as a blocker is that it stops people from upgrading from 3.12.3 to 3.13. A workaround is to remove the jira-fisheye plugin jar file from a new 3.13 installation.
Attachments
Issue Links
- relates to
-
JRASERVER-15804 Index path is not validated when importing data into a new JIRA instance
- Closed