VM creation fails on all hosts with error "Cannot complete file creation operation" after vSAN Cluster shutdown
Article ID: 426852
Updated On:
Products
Issue/Introduction
Symptoms :
After performing a vSAN Cluster shutdown and restart, users are unable to create new Virtual Machines. This affects both proactive vSAN VM creation and standard VM deployment across all hosts in the cluster.
- Proactive vSAN VM creation and Normal VM creation fails on all hosts with following error :
Cannot complete file creation operation.Failed to create object.Reserving folder on host.
Environment
VMware vSAN: 8.x
Cause
The vSAN Cluster shut down process was not carried out correctly and hence the DOMPauseAllCCPs was not reset due to which the vm creation was failed.
Example :
vmkernel.log
2026-01-09T12:12:39.220Z In(182) vmkernel: cpu120:1111111)Config: 725: "DOMPauseAllCCPs" = 1, Old Value: 0, (Status: 0x0)
Resolution
To resolve this issue, manually reset the advanced parameters DOMPauseAllCCPs and IgnoreClusterMemberListUpdates to their default value of 0 on all ESXi hosts within the impacted vSAN cluster.
Step 1: Check current configuration
Run the following commands on each ESXi host to verify the current state:
esxcfg-advcfg -g /VSAN/DOMPauseAllCCPsesxcfg-advcfg -g /VSAN/IgnoreClusterMemberListUpdates
Step 2: Reset parameters to default
If the value returned in Step 1 is 1, run these commands to fix the VM creation issue:
esxcfg-advcfg -s 0 /VSAN/DOMPauseAllCCPsesxcfg-advcfg -s 0 /VSAN/IgnoreClusterMemberListUpdates
Step 3: Validate the fix
Ensure the values are now set to 0:
esxcfg-advcfg -g /VSAN/DOMPauseAllCCPsesxcfg-advcfg -g /VSAN/IgnoreClusterMemberListUpdates
Note: To prevent this issue in the future, always ensure the vSAN Cluster shutdown and restart processes are followed strictly according to official vSAN Cluster shutdown and Restart documentation.
After vSAN Cluster Shutdown & Restart, VMs/objects are inaccessible
Additional Information
Feedback
