CPM may not retry Tag Scanning if scanning fails due to RequestLimitExceeded
If Tag scanning is triggered and fails due to RequestLimitExceeded,
an alert is generated and no retry is scheduled.
Please search for the below print in the server log:
ERROR: scan_resources(backup_tag.py:<line_number)) Failed getting <resources> in region <region_name>,
exception: Request limit exceeded.
If you face this issue, please upgrade to latest 2.X.X
Reference defect number – N2WS-2235, fixed in v2.3.0e
Tag scan may fail after upgrade to v2.6.0 with the "KeyError: 'config_args'" error, when a resource is tagged with the "no-backup" tag value
Tag scan may fail after upgrade to v2.6.0 with the "KeyError: 'config_args'" error, when a resource is tagged with the "no-backup" tag value The following errors may be printed in CPM Agent logs: ERROR: scan_tags_request(agentapi_requests.py:415) ...
CPM may abort Tag scanning with error "New policy xyz has more than one template”
In case CPM tag scanning is aborted, please open the Scan Log and search for the error “New policy xyz has more than one template tag scanning is running”. If you encounter this error, please upgrade to the latest 2.X.X version Reference defect ...
CPM may fail to add an instance using "Scan Resources”, if policy is created from a template and the "#app-aware" option is added to the tag
When trying to add an instance to a new policy, which is created from a template using the cpm backup tag and value of new policy:existing policy#app-aware, tag scanning may fail with the following error: “Resource tag scan failed". The new policy is ...
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 ...
"Cost Explorer Query Failure" alert in CPM 3.0
After upgrading to CPM 3.0, you may see an Alert in the console which says "Cost Explorer Query Failure". If you view the Alert, you will see an AccessDeniedException: The cause of this alert is due to the CPM role permissions not being updated with ...