-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Highest
-
None
-
Affects Version/s: JCMA - 1.12.23
-
Component/s: Apps - Migration Assistant
-
None
-
Severity 2 - Major
-
Issue Summary
When upgrading or downgrading JCMA versions 1.12.23, 1.12.25 this may incorrectly re-trigger app migrations in already completed plans
Steps to Reproduce
- Run a migration with apps on JCMA 1.12.22
- Let the app migration settle
- Upgrade to JCMA 1.12.23
- App migrations will incorrectly try to start on the previous migration plan
Expected Results
App migrations should not start when upgrading JCMA
Actual Results
You can see app migrations trying to start from the log line
2025-02-20 05:36:42,444 JCMA-MigrationEventBus-pool-1-thread-66 INFO [jira.migration.app.AppMigrationTrigger] Obtained lock for migrationId: 95405616-f054-443d-ad79-8d7db0bee6f2 2025-02-20 05:36:42,444 JCMA-MigrationEventBus-pool-1-thread-66 INFO [jira.migration.app.AppMigrationTrigger] migrationId 95405616-f054-443d-ad79-8d7db0bee6f2 was not found in cache 2025-02-20 05:36:42,444 JCMA-MigrationEventBus-pool-1-thread-66 INFO [jira.migration.app.AppMigrationTrigger] Saving migrationId 95405616-f054-443d-ad79-8d7db0bee6f2 into cache
Workaround
You have two options
- Don't upgrade to 1.12.23 and 1.12.25 until we have released a fix
- Delete the plans with settled app migrations in database in `AO_6FF49D_PLAN_ENTITY` and `AO_6FF49D_MIGRATION_ENTITY` tables