Empty tag value may result in the error "Instance (or Volume) <ID> wasn't scanned properly"

The error "Instance (or Volume) <ID> wasn't scanned properly" may appear in resource scan log and CPM server log if an instance, or volume is configured with the cpm backup tag key, and the tag value is empty. This message will appear only if the tag value had been previously configured with the name of a policy.

These two errors are related and will appear several seconds apart:

ERROR: scan_resources(.\cpmserver\cpm\backup_tag.py:828) <instanceID>, tag parser error: Empty tag value. Please set policy name, or 'no-backup' to not backup resource (tag: )
ERROR: manage_account_tagged_resources(.\cpmserver\cpm\backup_tag.py:184) Instance <instance ID> wasn't scanned properly (policy <policyName>)

To fix this issue, either configure the instance tag value to the desired policy, or enter no-backup if no policy is desired.

Another option; if tag based backup is no longer desired for the instance, remove the tag key cpm backup.

Related Articles
Error "Policy "Policy_Name" doesn't exist/attached to account" may be printed into CPM server log during the tag scanning operation
The following may be printed into the CPM server log during the tag scanning operation: ERROR: manage_account_tagged_resources(.\cpmserver\cpm\backup_tag.py:336) Policy_Name doesn't exist/attached to account To resolve: Find error in CPM server logs, ...
Instance may be removed from the policy once a tag scan is performed
An instance may be removed from the policy once a tag scan is performed Issue: When there is an instance which is added to two policies - by tag and via web-console, an instance will be removed from the policy in which it was added via GUI. In logs ...
Azure - Error "Policy "Policy_Name" doesn't exist/attached to account" may be printed into server log during the tag scanning operation
The following may be printed into the CPM server log during the tag scanning operation: ERROR: manage_account_tagged_resources(.\cpmserver\cpm\backup_tag.py:336) Policy_Name doesn't exist/attached to account To resolve: Find error in CPM server logs, ...
"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 ...
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 ...

Empty tag value may result in the error "Instance (or Volume) <ID> wasn't scanned properly"

Empty tag value may result in the error "Instance (or Volume) <ID> wasn't scanned properly"

Related Articles

Error "Policy "Policy_Name" doesn't exist/attached to account" may be printed into CPM server log during the tag scanning operation

Instance may be removed from the policy once a tag scan is performed

Azure - Error "Policy "Policy_Name" doesn't exist/attached to account" may be printed into server log during the tag scanning operation

"Cannot attach volume 'vol-xxxx' with Marketplace codes" error may be displayed during CPM upgrade

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"