Error "reconfiguring virtual machine: error processing disk changes post-clone: disk.0: ServerFaultCode: NoPermission: RESOURCE (vm-#####:2000), ACTION (queryAssociatedProfile): RESOURCE (vm-####), ACTION (PolicyIDByVirtualDisk)" during clone task
search cancel

Error "reconfiguring virtual machine: error processing disk changes post-clone: disk.0: ServerFaultCode: NoPermission: RESOURCE (vm-#####:2000), ACTION (queryAssociatedProfile): RESOURCE (vm-####), ACTION (PolicyIDByVirtualDisk)" during clone task

book

Article ID: 439982

calendar_today

Updated On:

Products

VMware Cloud Foundation VMware vCenter Server VMware Telco Cloud Infrastructure

Issue/Introduction

  • Virtual machine clone operation using terraform or manual method fails with a ServerFaultCode: NoPermission.|
  • The error explicitly references resources like RESOURCE (vm-<ID>) and actions such as queryAssociatedProfile or PolicyIDByVirtualDisk.
  • The deployment may stall after the VM has been successfully cloned but before it is powered on or customized.

Environment

VCF 4.0
TCI 2.2
vCenter 7.0U3.

 

Cause

  • The vCenter user account or service account used by Terraform lacks the specific Profile-driven storage privileges required to query or update VM Storage Policies (SPBM) during the disk reconfiguration phase.
  • Even if the account is assigned a "Global Administrator" role, these specific Storage Policy Based Management (SPBM) permissions may not be explicitly enabled or correctly propagated from the vCenter root level.

Resolution

Include the necessary Profile-driven storage privileges.

  1. Log in to the vSphere Client with administrative credentials.

  2. Navigate to Administration > Access Control > Roles.

  3. Select the role assigned to the Terraform service account and click Edit.

  4. Ensure the following privileges are enabled:

    • Profile-driven storage > Profile-driven storage view

    • Profile-driven storage > Profile-driven storage update

  5. Navigate to Administration > Access Control > Global Permissions.

  6. Verify that the Terraform service account is assigned the corrected role at the vCenter Root level.

  7. Ensure the Propagate to children checkbox is selected for this assignment to ensure all virtual machine objects inherit the required permissions.

  8. Retry the Terraform deployment.