The VM reconfiguration failed with the error: "vim.fault.ConcurrentAccess".

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• When reconfiguring a VM, it fails with the error  "vim.fault.ConcurrentAccess"

• In vCenter var/log/vmware/vpxd/vpxd.log you see entries similar to:
  
  [YYYY-MM-DDTHH:MM:SS] error vpxd[06192] [Originator@6876 sub=vpxLro opID=l03mnvva-9189476-auto-5gyn9-h5:71438938-71-01] [VpxLRO] Unexpected Exception: N3Vim5Fault16ConcurrentAccess9ExceptionE(Fault cause: vim.fault.ConcurrentAccess
--> )
--> [context]zKq7AVECAQAAAAp/JQEodnB4ZAAA2uc3bGlidm1hY29yZS5zbwAA64gsAHN7LQBB+DKBpesHAWxpYnZpbS10eXBlcy5zbwCBT/wHAQFP+eoC2wZxdnB4ZACCZeReAQK0yHsC8Mp7AmES8wKuFfOC7f8vAYK4Dy0BgvJjLAGCQ4IsAYJhiCwBgpurYAGC3KxgAYIKvGABgm3pXwGCPEJgAYJKtSoBguu1KgECWDT0Am039ALsN/SBAfUFAYKgqGEBgpurYAGC3KxgAYIKvGABgm3pXwGCOJNgAQCXWiMAP7AjAJhzNwOHfwBsaWJwdGhyZWFkLnNvLjAABO81D2xpYmMuc28uNgA=[/context]

[YYYY-MM-DDTHH:MM:SS] info vpxd[06192] [Originator@6876 sub=vpxLro opID=l03mnvva-9189476-auto-5gyn9-h5:71438938-71-01] [VpxLRO] -- FINISH lro-217249861

[YYYY-MM-DDTHH:MM:SS]info vpxd[06192] [Originator@6876 sub=Default opID=l03mnvva-9189476-auto-5gyn9-h5:71438938-71-01] [VpxLRO] -- ERROR lro-217249861 -- vm-####-- vim.VirtualMachine.reconfigure: vim.fault.ConcurrentAccess:
--> Result:
--> (vim.fault.ConcurrentAccess) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "com.vmware.cdrs.placeVm.concurrentAccess",
-->          arg = (vmodl.KeyAnyValue) [
-->             (vmodl.KeyAnyValue) {
-->                key = "threadID",
-->                value = 8464
-->             }
-->          ],
-->          message = <unset>
-->       }
-->    ]
-->    msg = ""

 

Environment

VMware vCenter Server 7.x

Cause

When a DRS recommendation is generated for a specific VM but not applied—such as when DRS is set to manual or partially automated mode—the VM's reconfiguration workflow becomes blocked by the pending DRS recommendation.

This can be verified by navigating to:
Cluster > Monitor > vSphere DRS > Recommendations.

 

Resolution

Currently, there is no fix available for the issue.

Workaround:
Remove VM/HA Rules for the problematic VM or apply the DRS recommendation.

To remove the DRS rule follow the below steps,

• Access vSphere Web Client: Log in to the vSphere Web Client and navigate to the cluster where the VM affinity rule is defined.
• In the cluster's settings, find the "VM/Host Rules" 
• Select and Edit/Remove the Rule:
• Identify the specific affinity rule you want to remove.
• Click "Edit" or "Delete" to modify or remove the rule.
• Disable the Rule (if editing):
  • If you're editing the rule, you can uncheck the "Enable Rule" option.
• Click "OK" to save the changes.
  • If you're deleting the rule, confirm the deletion by clicking "OK".