CPM Server may fail to finish configuration when upgrading from v2.1.3 to v2.1.3a using AMI

• Related Articles

• Upgrade using AMI to v2.6.0 from earlier versions may fail with the Configuration Wizard timing out and "Could not upgrade mysql"

  Upgrade using AMI to v2.6.0 from earlier versions may fail with the Configuration Wizard timing out: The following error may be printed in the "config_shell_commands.log" file: upgrade_mysql_db(:60) Could not run mysql5.6 on docker, error=409 Client ...

• CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist" and "Configuration Failed" errors

  CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist"  and "Configuration Failed" errors: The reason for this failure is using wrong AWS Access Key and Secret Key - maybe they belong to the wrong account.

• Upgrade using AMI to v2.6.0 from earlier versions may fail with "Configuration Failed" and "Could not migrate database to version 2.6.0 scheme"

  Upgrade using AMI to v2.6.0 from earlier versions may fail with "Configuration Failed". The following error may be printed in the "config_shell_commands.log" file: perform_shell_commands(:629) Could not migrate database to version 2.6.0 scheme, ...

• Linux scripts may start failing after upgrading to a new CPM version (using AMI) or migrating CPM to a different account/region

  Linux scripts may start failing after upgrading to a new CPM version (using AMI) or migrating CPM to a different account/region. In order to restore scripts' functionality, please run a script from command line, and approve the SSH key by answering ...

• Installation/upgrade to v2.6.0 using the AMI method may fail when using proxy with error 500 displayed

  Installation/upgrade to v2.6.0 using the AMI method may fail when using proxy with error 500 displayed: The following errors may be printed in the cpm_config.log file: ERROR:  list_aliases(kms.py:42)  Failed getting aliases list (region: us-east-1, ...