User and groups are not migrated to the new cwd tables upon upgrade
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
While upgrading JIRA from a version prior 4.3 to a newer version, users and groups are not migrated to the new Crowd embedded tables (cwd_*) causing the login to fail.
No specific errors appear in the atlassian-jira.log
Cause
The root cause of this issue is usually related to a previous failed upgrade and the database was not totally restored to the original state before the upgrade attempt.
Resolution
Always back up your data before performing any modification to the database. If possible, try your modifications on a test server.
- Shutdown JIRA instance;
Execute this query and take note of the 'id' value;
SELECT * FROM propertyentry e, propertystring n WHERE e.id = n.id AND e.property_key = 'jira.version.patched'Update the table propertystring with build number '589' using the following statement;
UPDATE propertystring SET propertyvalue = '589' WHERE id = <ID_from_previous_query>- Restart JIRA;
If JIRA is integrated to LDAP, be sure that the osuser.xml file which contain the LDAP settings is located into '$JIRA_INSTALL/atlassian-jira/WEB-INF/classes' before restart the instance.