Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-1309

CCMA: Migration plan stuck in ready status due to MissingAttachments preflight failure.

    XMLWordPrintable

Details

    • Severity 3 - Minor

    Description

      Issue Summary

      When running space migration using CCMA, all the checks run fine however plan gets stuck in Ready status.
      The migration assistant shows the "Migration in Progress" but all configurations in the migration (users and spaces) are on status Ready.

      This is reproducible on Data Center:

      Steps to Reproduce

      1. Install the CCMA 3.x version.
      2. Create a migration, click on continue and fix later for missing attachment check
      3. The migration assistant shows "Migration in Progress" and all configurations included in the migration will be Ready status.

      Expected Results

      The migration should be successful as all the preflight checks are green.

      Actual Results

      The below exception is thrown in the atlassian-confluence.log file:

      ERROR [Caesium-1-4] [agent.service.check.AsyncCheckExecutor] error Couldn't execute check of type MissingAttachments with id f361ab5523e91f3415e8a44e96a540e01cc4957d
java.lang.IllegalArgumentException: Failed to find checkResult for executionId: f361ab5523e91f3415e8a44e96a540e01cc4957d and checkType: MissingAttachments
	at com.atlassian.migration.agent.service.check.CheckResultsService.lambda$null$5(CheckResultsService.java:76)
	at java.base/java.util.Optional.orElseThrow(Optional.java:408)
	at com.atlassian.migration.agent.service.check.CheckResultsService.lambda$saveCheckResult$6(CheckResultsService.java:76)
	at com.atlassian.migration.agent.store.tx.PluginTransactionTemplate.lambda$on$0(PluginTransactionTemplate.java:10)
	at com.atlassian.migration.agent.store.jpa.impl.DefaultPluginTransactionTemplate.on(DefaultPluginTransactionTemplate.java:36)
	at com.atlassian.migration.agent.store.tx.PluginTransactionTemplate.on(PluginTransactionTemplate.java:9)
	at com.atlassian.migration.agent.store.tx.PluginTransactionTemplate.write(PluginTransactionTemplate.java:28)
	at com.atlassian.migration.agent.service.check.CheckResultsService.saveCheckResult(CheckResultsService.java:73)
	at com.atlassian.migration.agent.service.check.AsyncCheckExecutor.lambda$executeChecker$9(AsyncCheckExecutor.java:233)
	at com.atlassian.migration.agent.logging.LoggingContextBuilder.execute(LoggingContextBuilder.java:127)
	at com.atlassian.migration.agent.service.check.AsyncCheckExecutor.executeChecker(AsyncCheckExecutor.java:220)
	at com.atlassian.migration.agent.service.check.AsyncCheckExecutor.runJob(AsyncCheckExecutor.java:180)
	at com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.doRunJob(JobRunnerWrapper.java:117)
	at com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.lambda$runJob$0(JobRunnerWrapper.java:87)
	at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContextInternal(VCacheRequestContextManager.java:84)
	at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContext(VCacheRequestContextManager.java:68)
	at com.atlassian.confluence.impl.schedule.caesium.JobRunnerWrapper.runJob(JobRunnerWrapper.java:87)
	at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:134)
	at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:106)
	at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:90)
	at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:435)
	at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJob(CaesiumSchedulerService.java:402)
	at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:380)
	at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:66)
	at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:60)
	at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:35)
	at java.base/java.lang.Thread.run(Thread.java:829)

      Workaround

      Follow the below steps to skip the missing attachments check:

      1. Stop the migration plan if it is still in the ready state.
      2. Navigate to*_ ${CONFLUENCE_URL}/admin/dark features.action_*
      3. Add the dark feature flags: migration-assistant.disable.missing-attachments-check. Please note that the missing attachment check will be skipped thus missing attachments report will not be generated.
      4. Enable/Disable the CCMA plugins.
      5. Create and run the migration plan.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MIG-1220 Migrate data using CCMA stalls due to MissingAttachments error

          • Highest - Our top priority issues
          • Closed
          relates to

          MOVE-128017 Loading...

          Activity

            People

              Unassigned Unassigned
              54bf2707b706 Deepak Pandey
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: