RT VM Relocation Fails in VMware Cloud Director Availability Due to Storage Profile Constraint Violation
search cancel

RT VM Relocation Fails in VMware Cloud Director Availability Due to Storage Profile Constraint Violation

book

Article ID: 401416

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

When attempting to relocate a RT virtual machine between clusters using a shared swing / target datastore, the following error may be encountered:

Error:
Unable to relocate VM - Underlying system error: The datastore is not compatible with the virtual machine because of constraint softconstraint-SOFT_CONSTR_STORAGE_PROFILE violation.

This issue prevents the RT VM from being relocated as intended.

Environment

VMware Cloud Director Availability 4.x

VMware Cloud Director 10.x

Cause

This error typically occurs when the target datastore (in this case, the swing / target datastore) is not associated with a storage policy compatible with the VM’s current storage requirements.

More specifically:

  • The target datastore is not associated with the required storage policy (also known as a storage profile).

  • VMware Cloud Director enforces storage policy constraints, so it blocks relocation operations to incompatible datastores.

  • The swing datastore may not be tagged appropriately or not mapped in the relevant Provider VDC or Organization VDC.

Resolution

To resolve the issue and proceed with the RT VM relocation via VMware Cloud Director Availability.

Step 1. Verify Storage Policy in vCenter

  • In vCenter, confirm that the target datastore is associated with a valid storage policy.
  • If no policy is assigned, create or associate a policy based on your intended use case.

Step 2. Map Storage Policy in VMware Cloud Director

  • In the Provider VDC, ensure that the same storage policy is:
    • Mapped and available.
    • Enabled for the Organization VDC where the VM resides.

Step 3. Confirm target Datastore Availability

  • Ensure that the target datastore is:
    • Mounted and presented to all hosts in both source and destination clusters.
    • Not in a maintenance or disconnected state.

Step 4. Tag Datastore and Update VCD Configuration

  • Navigate to VCD > Provider VDC > Datastores.
  • Confirm the target datastore:
    • Is correctly tagged in accordance with the storage policy.
    • Has its storage policy enabled under the Organization VDC settings.