Space migration via CCMA fails with NPE on Confluence Server 7.14.0 and later

XMLWordPrintable

    • Severity 2 - Major

      Issue Summary

      Space migration via CCMA fails with NPE on Confluence Server 7.14

      Steps to Reproduce

      1. Install Confluece DC 7.14 version
      2. Import the XML space export in the confluence server.
      3. Create a migration plan and run the migration.
      4. The migration of space fails with the below error and NPE observed in the Confluence server log file.
      Failed to export [cloudId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,fileId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,spaceKey=XXXXXX]

      Expected Results

      Migration is successful

      Actual Results

      The below exception is thrown in the xxxxxxx.log file:

      Failed to export [cloudId=1d5d253f-87ec-42ff-9043-362fe347bacc,fileId=3fbd0bf0-c4aa-49d6-a42f-e9cc4010458b,spaceKey=NORMA]

      – stepConfig:

      {"spaceKey":"XXX","fileId":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","cloudId":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"}
      cloudId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx planName: Test Migration stepType: CONFLUENCE_EXPORT stepId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx planId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx cloudUrl: https://xxxxxx.atlassian.net taskName: Migrate space XXXXXXX taskId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxjava.lang.NullPointerException
      at com.atlassian.migration.agent.export.SpaceNoAttachmentsXmlExporter.configureXmlExporter(SpaceNoAttachmentsXmlExporter.java:83)
      at com.atlassian.migration.agent.export.SpaceNoAttachmentsXmlExporter.doExportImpl(SpaceNoAttachmentsXmlExporter.java:76)
      at com.atlassian.migration.agent.export.SpaceNoAttachmentsXmlExporter.lambda$doExport$1(SpaceNoAttachmentsXmlExporter.java:71)
      at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(Unknown Source)
      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at java.base/java.lang.Thread.run(Unknown Source)h3. Workaround

      This issue only exists for Conf Server versions 7.14.0 and above.

      A possible workaround might be to downgrade Confluence to 7.13.x

            Assignee:
            Kenny MacLeod
            Reporter:
            Byron Walker
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: