"PBM FAULT" error when refreshing storage policies and unable to apply storage profiles.
search cancel

"PBM FAULT" error when refreshing storage policies and unable to apply storage profiles.

book

Article ID: 325459

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • You are unable to refresh storage policies.
  • When you attempt to create a new storage profile, you receive an error similar to:
PbmFault Cause: PbmFault
  • When creating storage policies, properly tagged datastore clusters and datastore objects fail the compatibility check.
  • In the sps.log file, you see the entries similar to:
2017-10-17T15:37:58.354Z [pool-17-thread-1] DEBUG opId=a671a144-c26d-40f7-99ba-cfd71fb5060b com.vmware.sps.pbm.placement.VasaProcessor - VasaProcessor processing matching request...
2017-10-17T15:37:58.375Z [pool-17-thread-1] ERROR opId=a671a144-c26d-40f7-99ba-cfd71fb5060b com.vmware.pbm.placement.impl.PlacementSolverImpl - Exception occurred during compatibility check:
java.util.NoSuchElementException
        at java.util.StringTokenizer.nextToken(Unknown Source)
        at com.vmware.sps.qs.QsQueryTemplate.getMoRefFromQsId(Unknown Source)
        at com.vmware.sps.qs.InventoryServiceImpl.getDatastoreTypes(Unknown Source)
        at com.vmware.sps.pbm.placement.VasaProcessor.process(Unknown Source)
        at com.vmware.sps.pbm.placement.PlacementHubFinderImpl.findMatchingDatastore(Unknown Source)
        at com.vmware.sps.pbm.placement.PlacementHubFinderImpl.findMatchingPod(Unknown Source)
        at com.vmware.sps.pbm.placement.PlacementHubFinderImpl.findMatchingHubInt(Unknown Source)
        at com.vmware.sps.pbm.placement.PlacementHubFinderImpl.findMatchingHub(Unknown Source)
        at com.vmware.pbm.placement.impl.PlacementSolverImpl.checkCompatibility(PlacementSolverImpl.java:230)
        at com.vmware.pbm.placement.impl.PlacementSolverImpl.queryMatchingHub(PlacementSolverImpl.java:99)
        at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at com.vmware.vim.vmomi.server.impl.InvocationTask.run(InvocationTask.java:66)
        at com.vmware.vim.vmomi.server.common.impl.RunnableWrapper$1.run(RunnableWrapper.java:48)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
2017-10-17T15:37:58.375Z [pool-17-thread-1] ERROR opId=a671a144-c26d-40f7-99ba-cfd71fb5060b com.vmware.pbm.placement.impl.PlacementSolverImpl - Exception during queryMatchingHub:
java.util.concurrent.ExecutionException: (pbm.fault.PBMFault) {
   faultCause = null, 


Environment

VMware vCenter Server Appliance 6.0.x
VMware vCenter Server 6.5.x

Cause

The issue occurs if the SDRS cluster has datastores more than 50.

Resolution

To resolve this issue, re-configure the SDRS cluster to include less than 50 datastores.