-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
None
-
1
-
Severity 3 - Minor
Issue Summary
In some customer environments, migration is stuck at during Users/Groups export. Precisely, AllUserUpload module remains stuck .
The error suggests missing tables from Jira Cloud Migration Assistant plugin.
This occurs when there are multiple versions of JCMA in the folder, which may be causing confusion in the application. Basically, the plugin is bundled when you install Jira, but when you update the plugin, the new plugin jars are stored in the jira-home installed-plugins folder.
Steps to Reproduce
Jira has multiple versions of JCMA in the folder, which may be causing confusion in the application. Basically, the plugin is bundled when you install Jira, but when you update the plugin, the new plugin jars are stored in the jira-home installed-plugins folder.
Expected Results
Migration should get complete.
Actual Results
Migration breaks with the error showing column "NEW_PROTOCOL_JSON" does not exist in the table although it exists.
024-06-04 15:34:09,843+0200 pool-2864-thread-3 ERROR [c.a.j.m.tracking.utils.ThreadUtils] uncaught exception in periodic executor com.atlassian.cache.CacheException: com.querydsl.core.QueryException: Caught PSQLException for select "MIGRATION"."MIGRATION_ID", "MIGRATION"."PLAN_ID", "MIGRATION"."START_MIGRATION_CONTEXT_JSON", "MIGRATION"."IN_PROGRESS_STATUS_JSON", "MIGRATION"."OUTCOME_JSON", "MIGRATION"."APP_OUTCOME_JSON", "MIGRATION"."STARTED_BY", "MIGRATION"."CREATED_TIMESTAMP", "MIGRATION"."UPDATED_TIMESTAMP", "MIGRATION"."PROTOCOL_JSON", "MIGRATION"."USER_MIGRATION_START_TIME", "MIGRATION"."USER_MIGRATION_END_TIME", "MIGRATION"."DATA_MOVEMENT_ID", "MIGRATION"."NEW_PROTOCOL_JSON" from "public"."AO_6FF49D_MIGRATION_ENTITY" "MIGRATION" where "MIGRATION"."OUTCOME_JSON" is null at com.atlassian.cache.memory.DelegatingCache.get(DelegatingCache.java:214 Caused by: com.querydsl.core.QueryException: Caught PSQLException for select "MIGRATION"."MIGRATION_ID", "MIGRATION"."PLAN_ID", "MIGRATION"."START_MIGRATION_CONTEXT_JSON", "MIGRATION"."IN_PROGRESS_STATUS_JSON", "MIGRATION"."OUTCOME_JSON", "MIGRATION"."APP_OUTCOME_JSON", "MIGRATION"."STARTED_BY", "MIGRATION"."CREATED_TIMESTAMP", "MIGRATION"."UPDATED_TIMESTAMP", "MIGRATION"."PROTOCOL_JSON", "MIGRATION"."USER_MIGRATION_START_TIME", "MIGRATION"."USER_MIGRATION_END_TIME", "MIGRATION"."DATA_MOVEMENT_ID", "MIGRATION"."NEW_PROTOCOL_JSON" from "public"."AO_6FF49D_MIGRATION_ENTITY" "MIGRATION" where "MIGRATION"."OUTCOME_JSON" is null at com.querydsl.sql.DefaultSQLExceptionTranslator.translate(DefaultSQLExceptionTranslator.java:50) at com.querydsl.sql.Configuration.translate(Configuration.java:459) Caused by: org.postgresql.util.PSQLException: ERRORE: la colonna MIGRATION.NEW_PROTOCOL_JSON non esiste Position: 435 at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2713) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2401) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:368) at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:498)
Workaround
To remove the JCMA plugin:
- Update the JCMA plugin to the latest version from the UI - v1.11.5;
- Stop Jira;
- Check now how many versions of the plugin are showing up under <JIRA_INSTALL>/atlassian-jira/WEB-INF/atlassian-bundled-plugins/ and under <JIRA_HOME>/plugins/installed-plugins/ ;
- Backup them and remove anything other than jira-migration-plugin-1.11.5.jar from both directories;
- Clear the plugin cache files:
- Delete the <jira_home>/plugins/.bundled-plugins directory (this will be regenerated on restart)
- Delete the <jira_home>/plugins/.osgi-plugins directory (this will be regenerated on restart)
- Delete the contents of <jira_install>/work directory (just the contents, not the folder itself)
- Delete the contents of <jira_install>/temp directory (just the contents, not the folder itself)
- Start Jira application again;
- Now, try opening the app Jira Cloud Migration Assistant.
https://confluence.atlassian.com/jirakb/how-to-clear-jira-s-plugin-cache-1157468195.html
If the problem persists, kindly contact Atlassian Support with the latest support zip with us and let us know the result of the query select * from "AO_6FF49D_MIGRATION_ENTITY" again.
- is cloned from
-
-
- Closed
-