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

App shouldn't disappear when an app server listener cannot be found

XMLWordPrintable

    • 13

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently, if an assessed app server listener cannot be found, the CCMA will simply vanish with the app without any visual indication of what happened. This creates great confusion for the customer who believes they are migrating all the apps they assessed.

      The only indication is a warning in the Server/DC logs:

      WARN [pool-xxxx-thread-x] [agent.service.catalogue.PlatformService] forEach my.App.Key has an automated path but missing a server listener. This app will be ignored during app migration.

            [MIG-1428] App shouldn't disappear when an app server listener cannot be found

            Basile CAVRIL added a comment - - edited

            I had the exact same issue with JCMA and indeed it should absolutly be marked as an error for the migration...
            Maybe it is time to solve a 2023 issue affecting both CCMA and JCMA

            Thanks a lot to Gabriel, his workaround worked

            Basile CAVRIL added a comment - - edited I had the exact same issue with JCMA and indeed it should absolutly be marked as an error for the migration... Maybe it is time to solve a 2023 issue affecting both CCMA and JCMA Thanks a lot to Gabriel, his workaround worked

            Gabriel Muller added a comment -

            This should not be a suggestion, it should be a bug.

            As a user migrating to cloud, you assess the app as needed in cloud, you prepare and install the app in cloud and consent/agree, and then you create a migration plan with your spaces AND apps, run the pre-flight checks and they ALL pass with a green check. You expect the app to be migrated, but if there's any kind of error, you expect the CMA to describe details of the error, preferably during the checks, but if not, at least in the UI in the apps section of the migration plan, and in the Error logs that you can download.

            It is not written in the description, but the Atlassian workaround is:

            As a workaround, you must retry the migration after restarting Confluence server or by Disabling and enabling apps. 

            Gabriel Muller added a comment - This should not be a suggestion, it should be a bug. As a user migrating to cloud, you assess the app as needed in cloud, you prepare and install the app in cloud and consent/agree, and then you create a migration plan with your spaces AND apps, run the pre-flight checks and they ALL pass with a green check. You expect the app to be migrated, but if there's any kind of error, you expect the CMA to describe details of the error, preferably during the checks, but if not, at least in the UI in the apps section of the migration plan, and in the Error logs that you can download. It is not written in the description, but the Atlassian workaround is: As a workaround, you must retry the migration after restarting Confluence server or by Disabling and enabling apps. 

              Unassigned Unassigned
              245bb2463874 Guilherme Menegotto
              Votes:
              4 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: