Details
-
Bug
-
Resolution: Tracked Elsewhere
-
Medium
-
None
-
None
-
None
Description
Summary
When upgrading GreenHopper, it executes com.atlassian.greenhopper.upgrade.GhUpgradeTask003 and a NPE is thrown due to the state of customer data.
Steps to Reproduce
- Restore "dodgy" data.
- Enable plugin.
Expected Results
The plugin enables.
Actual Results
It does not.
The following is displayed in atlassian-jira.log:
2013-08-05 17:45:50,034 http-bio-8090-exec-14 ERROR potatobake 1065x2431x1 b4cq2t 192.168.131.14 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [sal.core.upgrade.PluginUpgrader] Upgrade failed: null java.lang.NullPointerException at com.atlassian.greenhopper.upgrade.GhUpgradeTask003.movePreferencesToSettings(GhUpgradeTask003.java:90) at com.atlassian.greenhopper.upgrade.GhUpgradat com.atlassian.greenhopper.upgrade.GhUpgradeTask003.movePreferencesToSettingseTask003.doUpgrade(GhUpgradeTask003.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597)
Notes
This is caused by a bug in JIRA as tracked in JRA-33557.
Workaround
Refer to our JIRA Login Fails With the Message - User exists but has no unique key mapping KB for the workaround.
Attachments
Issue Links
- is caused by
-
-
- Closed
-
- mentioned in
-
Wiki Page Loading...