S3 Cleanup may fail after upgrade to v2.6.0 if there is no worker configuration for the account/region in which S3 Repository resides

• Related Articles

• Cleanup from S3 or S3 copy fails with error: Worker configuration not found

  Issue: When running a Copy to S3 policy, you may receive an error that states Worker configuration not found Or when S3 cleanup runs, you may see similar error in S3 cleanup logs. Solution The error will specify the region and/or account that a ...

• 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.

• S3 Backup may fail after upgrade to v2.6 with the error "Error - Workers could not be launched"

  S3 Backup may fail after upgrade to v2.6 with the error "Error - Workers could not be launched". This issue may happen if subnet is set to "Any" in the worker configuration. The following errors may be logged in the Backup Log: Info - Starting copy ...

• CPM v3.0.x may launch unnecessarily large Cleanup workers, resulting in extra costs

  CPM v3.0.x may launch unnecessarily large Cleanup workers, resulting in extra costs. In order to reduce the costs, please use the following procedure: Connect (via ssh) to the machine running cpm (you will need to execute "sudo -i" to gain the root ...

• N2WS-19169 - Cleanup may fail because of "Can't find mapping for account "

  Issue: Cleanup process may fail because server fails to clean cross-region AMI DR: ERROR: get_account_dict(account_utils.py:114) account PolicyName(user root) not found in account map, even after refresh. ERROR: ...