Failed to enable CCMA

XMLWordPrintable

    • 13
    • Severity 3 - Minor
    • 154

      Atlassian Update – 5th December 2023

      Hi everyone,

      Thank you for raising this bug to our attention, my team and I appreciate the details provided to help us reproduce the bug. Although we're aware of the issue facing customers on MySQL 5.6.X being unable to enable CCMA 3.6.0 being still important to those of you who were involved in the conversations around it, we want to be transparent that we won’t fix the bug as we do not support MySQL versions < 5.7.7 given that:

      • MySQL 5.7 extended support ended on 20th September 2023
      • MySQL 5.6 extended support ended on 28th February 2021 

      We recommend customers to upgrade to MySQL 5.7.7 or above to migrate.

      We will update this thread if there are changes to our roadmap to accommodate this bug. Thank you again for providing valuable feedback to our team!

      We hope that you appreciate our candid and transparent communication.

      Kind regards,

      Confluence Migration Assistant Team

      Issue Summary

      The actual problem is reproducible in our local environment. 
      CCMA 3.6.0 is failed to enable. After the installation of CCMA 3.6.0, I haven't been able to enable the plugin.

      Steps to Reproduce

      1. Install Confluence version : 6.15.2 with MySQL DB version 5.6.51
      2. Install CCMA 3.6.0
      3. Attempt to enable CCMA  

      Expected Results

      Users should be able to enable CCMA 3.6.0 as it meets the environment criteria as outlined in https://marketplace.atlassian.com/apps/1219672/confluence-cloud-migration-assistant/version-history

      Actual Results

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

      Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'configurationService' defined in OSGi resource[classpath:com/atlassian/migration/agent/ServiceBeanConfiguration.class|bnd.id=284|bnd.sym=migration-agent]: Unsatisfied dependency expressed through method 'configurationService' parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'defaultPluginTransactionTemplate' defined in OSGi resource[classpath:com/atlassian/migration/agent/CommonBeanConfiguration.class|bnd.id=284|bnd.sym=migration-agent]: Unsatisfied dependency expressed through method 'defaultPluginTransactionTemplate' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactorySupplier' defined in OSGi resource[classpath:com/atlassian/migration/agent/CommonBeanConfiguration.class|bnd.id=284|bnd.sym=migration-agent]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.migration.agent.store.jpa.SessionFactorySupplier]: Factory method 'sessionFactorySupplier' threw exception; nested exception is javax.persistence.PersistenceException: Failed to update database schema
       
      Caused by: liquibase.exception.LiquibaseException: liquibase.exception.MigrationFailedException: Migration failed for changeset META-INF/db-changelog/52-modify-token-length-on-cloudsite-table.xml::52-modify-token-length-on-cloudsite-table::MPT:
           Reason: liquibase.exception.DatabaseException: Specified key was too long; max key length is 767 bytes [Failed SQL: (1071) ALTER TABLE confluence.MIG_CLOUD_SITE MODIFY containerToken VARCHAR(420)]
      

      Workaround

      Upgrade the database engine to MYSQL DB Version 5.7.7 or higher . 

              Assignee:
              Sarthak Goel
              Reporter:
              Sayeed Islam (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: