"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 instance
i-0011001100110011 (device: /dev/xvdg) failed. Reason: Cannot attach
volume 'vol-0231c03d28ae56214' with Marketplace codes as the instance
'i-0011001100110011' is not in the 'stopped' state.
This is an AWS limitation. AWS doesn't allow to attach a root volume of a
instance that has MarketPlace Product Code associated with it to another
instance, unless that instance is stopped. This is not something
CPM has any affect on.
You can see if the volume has a Product Code in its description:
This won't be a problem if you'll try to recover an instance - as the recovered instance will be stopped while the volumes are being attached.
Related Articles
"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 ...File-level recovery may fail with "Reason: In order to use this AWS Marketplace product you need to accept terms and subscribe"
File-level recovery may fail with the following error printed in the CPM logs: ERROR: explore_backup_init(.\cpmserver\cpm\filemanager\views.py:368) File Level Recovery - failed exploring snapshot snap-0123456789abcdef. Reason: Volume ...File Level Recovery may fail with error "The reason could be missing/unsupported file system"
File-level recovery may fail with the following error printed in the CPM logs: Partition Table: gpt Number Start End Size File system Name Flags 1 2097kB 805GB 805GB primary raid INFO: ...File level restore may fail with the "Failed adding share permission" error
File level restore may fail with the "Failed adding share permission" error: ERROR: share_snapshot(.\cpmserver\cpm\aws_utils.py:265) Failed adding share permission to snapshot snap-1234567890abcdef (original volume: vol-abcdef1234567890) Failed. ...File-level restore may fail with the "Could not get CPM instance info" error
File-level restore may fail with the "Could not get CPM instance info" error: The following error is printed in the CPM server log: ERROR: explore_backup_init(.\cpmserver\cpm\filemanager\views.py:317) Could not get CPM instance info ...