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

JCMA Preflights: preflight check fails with an error "We couldn't check for entities with public access"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • None
    • JCMA - 1.12.13, JCMA - 1.12.14
    • Viper SI - India
    • 15
    • Severity 2 - Major
    • 134

      Issue Summary

      The JCMA preflight check fails with an error "We couldn't check for entities with public access" on newer versions (1.12.13, 1.12.14) of JCMA.

      Steps to Reproduce

      1. Create new migration plan and run the checks.
      2. It fails with an error.

      Expected Results

      The checks should pass.

      Actual Results

      The below exception is thrown in the atlassian-jira-migration.log file:
      SQL Server:

      2024-12-01 12:22:45,346 JCMA-ExecutorService-pool-2-thread-313 ERROR username 689x18907x1 1ft1iac xxx.xxx.110.49:90856,0:0:0:0:0:0:0:1 /rest/migration/latest/stats/plan [migration.preflight.reports.PreMigrationReportsService] An error occurred during getting preflight checks result
java.util.concurrent.ExecutionException: com.querydsl.core.QueryException: Caught SQLServerException for select "AO_D9132D_ISSUE_SOURCE"."ID", "AO_D9132D_ISSUE_SOURCE"."CONVERSION_FACTOR", "AO_D9132D_ISSUE_SOURCE"."PLAN_ID", "AO_D9132D_ISSUE_SOURCE"."SOURCE_TYPE", "AO_D9132D_ISSUE_SOURCE"."SOURCE_VALUE" from "dbo"."AO_D9132D_ISSUE_SOURCE" "AO_D9132D_ISSUE_SOURCE" where 1 = 2
.
.
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid objectname 'dbo.AO_D9132D_ISSUE_SOURCE'.

      Postgres:

      2024-11-29 05:06:50,265 JCMA-ExecutorService-pool-2-thread-205 ERROR admin 306x786170x1 admin xx.1xx.xx.xx /rest/migration/latest/check/987347fdf7f7d87bf1749aee511bd08edc036a99 [jira.migration.preflight.AsyncCheckExecutor] Pre-flight execution error occurred for check type AnonPermission
java.util.concurrent.ExecutionException: com.querydsl.core.QueryException: Caught PSQLException for select "AO_D9132D_ISSUE_SOURCE"."ID", "AO_D9132D_ISSUE_SOURCE"."CONVERSION_FACTOR", "AO_D9132D_ISSUE_SOURCE"."PLAN_ID", "AO_D9132D_ISSUE_SOURCE"."SOURCE_TYPE", "AO_D9132D_ISSUE_SOURCE"."SOURCE_VALUE" from "public"."AO_D9132D_ISSUE_SOURCE" "AO_D9132D_ISSUE_SOURCE" where 1 = 2
.
.
Caused by: org.postgresql.util.PSQLException: ERROR: relation "public.AO_D9132D_ISSUE_SOURCE" does not exist

      MySQL:

      2024-11-26 09:57:48,712 JCMA-ExecutorService-pool-2-thread-26 ERROR admin 597x10813x2 oplimn 1xx.1xx.xxx.81,1xx.xx.xx.xx /rest/migration/latest/check/24337c807dd9115edc098794a8b8525b845e0c57 [jira.migration.preflight.AsyncCheckExecutor] Root cause error com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'jiradb.AO_D9132D_ISSUE_SOURCE' doesn't exist
.
.
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'jiradb.AO_D9132D_ISSUE_SOURCE' doesn't exist

      Workaround

      Contact Atlassian support.

        1. Public_access_Preflightcheck_error.png
          Public_access_Preflightcheck_error.png
          184 kB

              e700d61161a9 Anubhav Jaiswal
              421a2e06c4a8 Jyoti Verma
              Votes:
              3 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: