Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
4.4.3
-
4.04
-
1
-
Severity 1 - Critical
-
Description
The error message does not display if you do this:
Restore internal.xml into 4.4.
(BUG) Now try and restore external.xml into 4.4. It is data with "External User Management" enabled from 4.2. The logs will have an error message "Error: JIRA is unable to migrate the User Directory configuration because external user management is enabled ....", however, the screen will just take you to the login screen. Try to login. Fail with any user.
(BUG) Goto the dashboard. You will get a NPE because the upgrade failed.
java.lang.NullPointerException at com.atlassian.crowd.embedded.core.CrowdDirectoryServiceImpl.storeLdapConnectionPoolConfiguration(CrowdDirectoryServiceImpl.java:308) at com.atlassian.crowd.embedded.core.CrowdDirectoryServiceImpl.initialiseConnectionPoolSystemProperties(CrowdDirectoryServiceImpl.java:291) at com.atlassian.crowd.embedded.core.CrowdDirectoryServiceImpl.getApplication(CrowdDirectoryServiceImpl.java:263) at com.atlassian.crowd.embedded.core.CrowdDirectoryServiceImpl.findAllDirectories(CrowdDirectoryServiceImpl.java:81) at com.atlassian.jira.user.util.DefaultUserManager.getWritableDirectories(DefaultUserManager.java:256) at com.atlassian.jira.user.util.DefaultUserManager.hasPasswordWritableDirectory(DefaultUserManager.java:272) at com.atlassian.jira.bc.security.login.LoginServiceImpl.getLoginProperties(LoginServiceImpl.java:92) at com.atlassian.jira.bc.security.login.LoginServiceImpl.getLoginProperties(LoginServiceImpl.java:108) at com.atlassian.jira.web.action.Dashboard.buildLoginProperties(Dashboard.java:212) at com.atlassian.jira.web.action.Dashboard.getCurrentDashboardState(Dashboard.java:199) at com.atlassian.jira.web.action.Dashboard.doValidation(Dashboard.java:116) at webwork.action.ActionSupport.validate(ActionSupport.java:391) at webwork.action.ActionSupport.execute(ActionSupport.java:162) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:76)
This is probably a bug in that we don't handle errors in the upgrade when doing a restore. The error seems to be correctly reported during a setup restore.