"Cannot attach volume 'vol-xxxx' with Marketplace codes" error may be displayed during CPM upgrade
The following error message may be displayed when trying to upgrade the CPM instance using a new AMI:
Could not attach volume vol-1234567890abcdef to instance
i-abcdef0123456789. Reason: Cannot attach volume
'vol-1234567890abcdef' with Marketplace codes as the instance
'i-abcdef0123456789' is not in the 'stopped' state.
This error means that you have chosen the wrong volume when selecting the "use existing data volume" option in step 3 of CPM configuration.
The most common mistake is trying to attach the "root" volume (default size 8GB) of the old instance instead of the "cpmdata" volume (default size 5GB)
The correct volume can be identified by its "Name" tag:
To resolve this problem, please follow the upgrade instructions at https://n2ws.com/support/documentation/introduction-to-cpm.html#155 again .
Related Articles
"Cannot attach volume 'vol-xxxx' with Marketplace codes" error may be displayed during the Explore operation
The following error message may be displayed when trying to explore a root volume of an instance that belongs to an AWS Marketplace product: Explore failed: 1. Volume vol-1234567890abcdef created (original: vol-0abcdef123456789). However attach to ...Backup of cpmdata may fail after migration/upgrade with the "The volume '....' does not exist" error
Backup of cpmdata may fail after migration/upgrade with the "The volume '....' does not exist" error: Error - snapshot of independent volume vol-0123456789abcdef failed to start. Reason: The volume 'vol-0123456789abcdef' does not exist This error may ...Error "Account AccountName can't define the cpmdata policy, as it's not the owner of the CPM Server" may be displayed when creating the "cpmdata" policy
Error "Account AccountName can't define the cpmdata policy, as it's not the owner of the CPM Server" may be displayed when creating the "cpmdata" policy. This means that you are trying to create the "cpmdata" policy using an account that isn't the ...CPM configuration may fail with the error: "Could not attach volume %vol-id% to instance %Id% Reason: Invalid value '/dev/sdf' for unixDevice. Attachment point /dev/sdf is already in use"
Issue: CPM configuration may fail with the error: "Could not attach volume %vol-id% to instance %Id% Reason: Invalid value '/dev/sdf' for unixDevice. Attachment point /dev/sdf is already in use" ERROR: done(views.py:181) Could not attach volume ...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, ...