Error: Incomplete Collection "Unable to get vSAN claimedCapacity for cluster domain-xx for vSAN" on Usage Meter 9.0
search cancel

Error: Incomplete Collection "Unable to get vSAN claimedCapacity for cluster domain-xx for vSAN" on Usage Meter 9.0

book

Article ID: 397671

calendar_today

Updated On:

Products

VMware Usage Meter

Issue/Introduction

  • After upgrading Usage Meter to version 9.0, you see 'Incomplete Collection' for vCenter. 
  • On the Notifications page in the Usage Meter UI, you see:
Incomplete collection "Unable to get vSAN claimedCapacity for cluster domain-xx." and "VSAN collection stage completed with warnings."
  • In the /bundle.tar.gz_extracted/var/log/vmware-um-platform/vcenter-collection-error.log, you see:
    ERROR --- [collector-main-thread] c.v.u.v.vsan.VsanCollectionStage         : Error while getting claimed capacity
    com.vmware.um.vccollector.vsan.VsanCollectionException: Unexpected error while getting claimed capacity for cluster with id: domain-xx
            at com.vmware.um.vccollector.vsan.VsanServiceSession.getClaimedCapacity(VsanServiceSession.java:xxx)
            at com.vmware.um.vccollector.vsan.VsanCollectionStage.getClaimedCapacity(VsanCollectionStage.java:xxx)
            at com.vmware.um.vccollector.vsan.VsanCollectionStage.collectClusterUsage(VsanCollectionStage.java:xxx)
            at com.vmware.um.vccollector.vsan.VsanCollectionStage.collectUsage(VsanCollectionStage.java:xxx)
            at com.vmware.um.vccollector.VCCollector.collectStages(VCCollector.java:xxx)
            at com.vmware.um.vccollector.VCCollector.collect(VCCollector.java:xxx)
            at com.vmware.um.vccollector.VCCollector.collect(VCCollector.java:xx)
            at com.vmware.um.collector.CollectionHelper.collectFromServer(CollectionHelper.java:xxx)
            at com.vmware.um.collector.CollectionHelper.collectFromServersWithReporting(CollectionHelper.java:xxx)
            at com.vmware.um.collector.CollectionHelper.collectWithReporting(CollectionHelper.java:xxx)
            at com.vmware.um.collector.SynchronousCollectionExecutor.triggerCollectionFromServer(SynchronousCollectionExecutor.java:xx)
            at com.vmware.um.collector.AbstractCollectorComponent.handleCollectSingleCommand(AbstractCollectorComponent.java:xxx)
            at com.vmware.um.collector.AbstractCollectorComponent.handleCommand(AbstractCollectorComponent.java:xx)
            at com.vmware.um.collector.CollectorComponent.handleCommand(CollectorComponent.java:xx)
            at com.vmware.um.collector.CollectionHelper.processCommand(CollectionHelper.java:xxx)
            at com.vmware.um.collector.AbstractCollector.processCommand(AbstractCollector.java:xxx)
            at com.vmware.um.umcomponent.CommandRunner$CommandExecutionWrapper.execute(CommandRunner.java:xxx)
            at com.vmware.um.umcomponent.CommandRunner.invokeCollector(CommandRunner.java:xxx)
            at com.vmware.um.umcomponent.CommandRunner.lambda$executeCommand$x(CommandRunner.java:xxx)
            at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(Unknown Source)
            at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
            at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.base/java.lang.Thread.run(Unknown Source)
    Caused by: com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Unable to resolve WSDL method name VsanClusterGetClaimedCapacity in vsan.version.version20 (vsan/reserved)
  • Check vSAN version by opening the below URL in the browser. (please replace <vc_ip> with the IP/Hostname of the vCenter appliance)

    https://<vc_ip>/sdk/vsanServiceVersions.xml

    Example output:
    <namespaces version="1.0">
    <namespace>
    <name>urn:vsan</name>
    <version>vSAN 7.0U3</version>
    <priorVersions> .....

Environment

VCF Usage Meter 9.x 

Resolution

This is a known issue in VCF Usage Meter 9.0 that occurs in vSAN versions running below 8.0 Update 3, please refer the VCF Usage Meter 9.0 Release Notes.
 
Plan an upgrade to vSAN version after 8.0 Update 3 as this issue doesn't have any immediate impact on collection or reporting.

Additional Information

Impact: This issue does not affect the correctness of the core vSAN usage report.