Error "Unable to relocate VM" and "NoDiskSpace cannot be cast to PersonaAwareException" while renaming a Virtual Machine in VMware Cloud Director
search cancel

Error "Unable to relocate VM" and "NoDiskSpace cannot be cast to PersonaAwareException" while renaming a Virtual Machine in VMware Cloud Director

book

Article ID: 428934

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

When attempting to rename or perform property changes on a Virtual Machine (VM) in the VMware Cloud Director (VCD) Tenant or Provider portal, the operation fails immediately.

The task details in the VCD UI display the following error stack:

Unable to relocate VM. - class com.vmware.vim.binding.vim.fault.NoDiskSpace cannot be cast to class com.vmware.vcloud.api.presentation.service.PersonaAwareException (com.vmware.vim.binding.vim.fault.NoDiskSpace and com.vmware.vcloud.api.presentation.service.PersonaAwareException are in unnamed module of loader java.net.FactoryURLClassLoader @17d677df)

In the /opt/vmware/vcloud-director/logs/vcloud-container-debug.log , You observe entries indicating a storage threshold breach for the datastore where the VM resides:

| INFO | task-service-activity-pool-382 | ThresholdFilter | Datastore datastore-xxxxx with free space XXXX GB has reached threshold limit of XXXX GB | requestId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx

Environment

VMware Cloud Director 10.6.X

Cause

This issue occurs because the datastore hosting the Virtual Machine has breached the Red Storage Threshold configured in VMware Cloud Director.

Although a rename operation is primarily a metadata update, VCD triggers a ReconfigureVM workflow in the background. This workflow validates the VM's placement compliance against current storage policies.

  1. VCD detects that the datastore's free space is below the configured threshold (e.g., the Red threshold).
  2. The placement engine throws an vim.fault.NoDiskSpace exception.

Resolution

To resolve this issue, ensure the target datastore complies with the configured storage thresholds using one of the following methods:

Method 1: Increase Datastore Capacity

Expand the underlying LUN/Datastore in the vCenter Server to increase the available free space above the VCD threshold limit.

  1. Log in to the vSphere Client.

  2. Navigate to the target datastore and expand its capacity.

  3. Log in to the VCD Provider Portal.

  4. Navigate to Resources > Infrastructure Resources > Datastores.

  5. Right-click the affected datastore and select Refresh Capacity to update the usage statistics immediately.

Method 2: Adjust VCD Storage Thresholds.

Temporarily lower the threshold configuration for the Storage Container associated with the virtual machine to allow operations to proceed.

  1. Log in to the VCD Provider Portal.

  2. Navigate to Resources > Cloud Resources.

  3. In the left panel, select Provider VDCs.

  4. Click on the name of the target Provider VDC.

  5. Select the Storage Containers tab.

  6. Click the name of the affected storage container and click Edit.

  7. Adjust the Red (and optionally Yellow) disk space thresholds to a value lower than the current free space.

  8. Click Save.

After completing either of the above methods, retry the VM rename or any other property change operation.

Additional Information

https://techdocs.broadcom.com/us/en/vmware-cis/cloud-director/vmware-cloud-director/10-6/configure-low-disk-space-thresholds-for-a-provider-vdc-datastore.html

Powered by Wolken Software