VMware Smart Assurance: 'Pending manager does not exist' error is present in Smarts IP domain log during device discovery process

Products

• VMware

Issue/Introduction

Symptoms:
Below error is thrown during discovery process in VMware Smart Assurance Smarts IP Manager domain logs-

ASL-W-ERROR_RULE_SOURCE-While executing rule set '/opt/InCharge/IP/smarts/rules/discovery/ic-file-importer.asl'
ASL-ERROR_ACTION-While executing action at:
ASL-CALL_STACK_RULE- RuleName: ENTRY, Line: 227
ASL-CALL_STACK_RULE- RuleName: START, Line: 81
ASL-ERROR_INVOKE-While attempting to invoke operation 'create' of object 'MR_Object::ICF-TopologyManager'
ADTM-AD_PENDING_ENULLPENDINGMANAGER-While attempting to get pending manager: Pending Manager does not exist 

Environment

VMware Smart Assurance - SMARTS

Cause

AD_Pending class has been corrupted/manually deleted by the user. A dmctl get on AD_Pending class would return empty resultwhen this error is active. 

$BASEDIR/IP/smarts/bin# dmctl -s <IP Domain Name> -b <broker location> get ICF_TopologyManager::ICF-TopologyManager::PendingManagedBy 

Resolution

Re-create the AD_Pending class by executing following dmctl command:
$BASEDIR/IP/smarts/bin# dmctl -s <IP Domain Name> -b <broker location> put ICF_TopologyManager::ICF-TopologyManager::PendingManagedBy AD_Pending::AD-Pending 


Once the above command is executed, the AD_Pending class and it's instance should be correctly shown in next dmctl get command:
$BASEDIR/IP/smarts/bin# dmctl -s <IP Domain Name> -b <broker location> get ICF_TopologyManager::ICF-TopologyManager::PendingManagedBy
AD_Pending::AD-Pending

Additional Information

Clearing up pending devices by deleting and re-creating AD_Pending::AD-Pending is not a recommended practice and any manual operation on AD-Pending class should be avoided (apart from dmctl gets).