VM / vApp operations fail on VMware Cloud Director with InternalServerErrorException and NO_FEASIBLE_PLACEMENT_SOLUTION due to stale reservation entries
search cancel

VM / vApp operations fail on VMware Cloud Director with InternalServerErrorException and NO_FEASIBLE_PLACEMENT_SOLUTION due to stale reservation entries

book

Article ID: 432070

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

When attempting to migrate Virtual Machines or performing operations in VMware Cloud Director, the task fails with a placement error. This occurs even when the target datastores have sufficient free space and threshold settings (Yellow/Red) on Cloud Director are configured correctly.

The following error is observed in the logs or UI:

com.vmware.vcloud.api.presentation.service.InternalServerErrorException: The operation failed because no suitable resource was found. Out of 1 candidate hubs: 
    1 hubs eliminated because: No valid storage containers found for VirtualMachine "xxxx-xxxx-xxxx-xxxx". All available storage containers were filtered out as being invalid.   Rejected hubs: resgroup-yyy
Storage containers were rejected for the following reasons: 
    3 storage containers rejected because: Threshold would be violated.   Rejected storage containers: <name of datastores>

Caused by: com.vmware.pbm.placement.PlacementException: PlacementException NO_FEASIBLE_PLACEMENT_SOLUTION
    at com.vmware.vcloud.placement.engine.impl.PlacementSolverImpl.constructPlacementException(PlacementSolverImpl.java:138)
    at com.vmware.vcloud.placement.engine.impl.PlacementSolverImpl.ensureHubAvailability(PlacementSolverImpl.java:750)

 

Environment

VMware Cloud Director 10.x

Cause

A product issue exists where the reservation table in the VCD database receives entries during catalog librarysync attempts but fails to clear them, leaving stale entries. These stale reservations lead the placement engine to incorrectly calculate available space, resulting in the "Threshold would be violated" rejection despite physical space availability.

 

Resolution

This issue is currently under review by Broadcom Engineering for a fix in a future release. 

Workaround:

To resolve the immediate placement failure, you must manually remove the stale entries from the VCD database. Please contact Broadcom support for additional information. 

Additional Information

Powered by Wolken Software