Error "Incomplete Collection due to failure at stage:SRM" with IllegalStateException: Duplicate key in VCF Usage Meter

Products

• VMware Usage Meter

Issue/Introduction

• After upgrading Usage Meter to version 9.0.x, you see 'Incomplete Collection due to failure at stage:SRM'. 
• On the Notifications page on the UI, you see:

Partial VC collection failure at stage: SRM. Duplicate key ###-vcenter-fqdn (attempted merging values com.vmware.vim##.LicenseAssignmentManagerLicenseAssignment@##### and com.vmware.vim##.LicenseAssignmentManagerLicenseAssignment@#####)

• In the vcenter-collection-error.log, you see:

ERROR --- [collector-main-thread] c.vmware.um.collector.CollectionHelper   : Status (COLLECT_API_ERR) for vCenter server : Partial collection failure: SRM.
ERROR --- [collector-main-thread] com.vmware.um.vccollector.VCCollector    : SRM stage raised exception java.lang.IllegalStateException: Duplicate key <vcenter_fqdn> (attempted merging values com.vmware.vim##.LicenseAssignmentManagerLicenseAssignment@##### and com.vmware.vim##.LicenseAssignmentManagerLicenseAssignment@####)
java.lang.IllegalStateException: Duplicate key <vcenter_fqdn> (attempted merging values com.vmware.vim##.LicenseAssignmentManagerLicenseAssignment@##### and com.vmware.vim##.LicenseAssignmentManagerLicenseAssignment@#####)
        at java.base/java.util.stream.Collectors.duplicateKeyException(Unknown Source)
        at java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Unknown Source)
        at java.base/java.util.stream.ReduceOps$3ReducingSink.accept(Unknown Source)

 

Environment

VCF Usage Meter 9.0.x

Cause

In VCF Usage Meter 9.0.x, the assets name under the  Administration > Licensing > Licenses has to be unique.

Resolution

To resolve this issue, select one of the following methods.

Method 1: Upgrade VCF Usage Meter 9.1 (Recommended)
Upgrade the VCF Usage Meter appliance to version 9.1.0.0 GA or higher.  please refer to the In-Place Upgrade of VCF Usage Meter
In VCF Usage Meter 9.1, the collection-side parsing logic has been improved even if identical asset names exist under vCenter Server licensing. This resolves the collection warning without requiring any modifications to the monitored infrastructure or license settings.

 

Method 2: Modify Asset Names in vCenter (Workaround for VCF Usage Meter 9.0.x)
If you must remain on VCF Usage Meter 9.0, you must ensure that all registered assets have unique names within vCenter:

1.    Login to the vCenter 
2.    Under the Administration > Licensing > Licenses please check the Assets:
3.    Ensure all the Registered Assets have unique name
4.    If the existing license settings are not unique, please refer to the How to Configure License Settings for Your vCenter Server' guide for instructions on modification