Error: "The operation failed because no suitable resource was found" deployment error

Products

• VMware Cloud Director

Issue/Introduction

• The VCD user interface displays: 
  
  [ ####-####-####-####-#### ] The operation failed because no suitable resource was found. Out of 1 candidate hubs: 1 hub was eliminated because: Compute requirement not met: [type:HardwareVersion, value:vmx-19]. Rejected hubs: resgroup-#### - PlacementException NO_FEASIBLE_PLACEMENT_SOLUTION.
  
  
• The /opt/vmware/vcloud-director/logs/vcloud-container-debug.log shows a vCenter Server disconnect caused database lock timeout in property_map:
  
  DEBUG    | pc-activity-pool-12094    | CJob                           | updateFailedJob(com.vmware.ssdc.util.LMException) with locale=null | activity=(com.vmware.vcloud.vimproxy.internal.impl.PropertyCollectorReader,urn:uuid:####-####-####-####-####)
com.vmware.ssdc.util.LMException: Error caused vCenter Server disconnect
        at com.vmware.ssdc.backend.vimeventlistener.VirtualCenterListener.onVirtualCenterConnectionStateChanged(VirtualCenterListener.java:108)
        at com.vmware.vcloud.inventory.events.impl.VirtualCenterConnectionChangedEvent.dispatchTo(VirtualCenterConnectionChangedEvent.java:39)
...
Caused by: java.lang.RuntimeException: org.hibernate.exception.GenericJDBCException: could not update: [com.vmware.vcloud.common.model.inventory.PropertyMapModel#####-####-####-####-####]
...
Caused by: org.postgresql.util.PSQLException: ERROR: canceling statement due to lock timeout
  Where: while updating tuple (808,5) in relation "property_map"

Environment

VMware Cloud Director 10.6.1.x

Cause

This issue occurs when the property_map table in the Cloud Director database contains stale inventory metadata or encounters lock contention. The property_map table tracks runtime properties of vSphere Managed Object References (MoRefs). If a synchronization interruption occurs or database locks timeout, VCD cannot accurately match deployment requirements (such as Hardware Version 19) against the current provider resource capabilities.

Resolution

You can resolve this synchronization issue by forcing a refresh of the provider inventory metadata. 

This can be achieved using one of the following methods:

1. Reconnect vCenter: In the VCD Provider Portal, navigate to Resources > Infrastructure Resources > vCenter Server Instances, select the affected vCenter, and click Reconnect.
   
   or
   
   
2. Toggle an ESXi host within the affected cluster into Maintenance Mode and then immediately back out of Maintenance Mode. This action triggers a VCD inventory synchronization that updates the PROPERTY_MAP and PROPERTY_MAP_STATUS tables.