Error "Internal Server Expected - Expected completed future, but received future which is still in progress." when reverting snapshot on VMs
search cancel

Error "Internal Server Expected - Expected completed future, but received future which is still in progress." when reverting snapshot on VMs

book

Article ID: 380600

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

Issue / Symptoms:
  • When the revert to snapshot task is initiated in VMware Cloud Director (VCD) the task stays in a running state for some time.
  • VM cannot be powered ON or deleted from Cloud Director.
  • In vCenter server, the task is successfully initiated but there are no other tasks/events related to the snapshot.
  • Snapshot creation and revert works as expected directly from the vCenter server.
  • The issue affects new VMs both created from template, fresh VMs with VMTools installed as well as existing VMs. 
  • The revert task is failing with the error below:  
    Internal Server Expected - Expected completed future, but received future which is still in progress.
  • The snapshot stays present in VCD after it has reverted in vCenter server.

Environment

VMware Cloud Director 10.6.x
VMware Cloud Director 10.5.x

Cause

There is a known issue with the revert snapshot logic when vSAN storage is used.

Resolution

  • For vSAN ESA Datastores, this is currently a known issue and can be verified in the release notes of VMware Cloud Director 10.6.1 and 10.6.1.1

Workaround: None

VMware Cloud Director 10.6.1 Release Notes

VMware Cloud Director 10.6.1.1 Release Notes

  • For vSAN-OSA Datastores, we need to increase the 'vcloud.val.inventory.updateTimeout' value and vm.snapshotRevertTimeoutInSeconds

Steps to increase the 'vcloud.val.inventory.updateTimeout' and vm.snapshotRevertTimeoutInSeconds parameter values:

1. Use the below command to increase the timeout value for vcloud.val.inventory.updateTimeout
/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n vcloud.val.inventory.updateTimeout -v 480
(Default timeout for this property is 300 seconds)
 
2. Use the below command to increase the timeout value for vm.snapshotRevertTimeoutInSeconds
/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n vm.snapshotRevertTimeoutInSeconds -v 600
(Default timeout for this property is 300 seconds)
 
3. Verify that the value is correctly set with this command
/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n vcloud.val.inventory.updateTimeout -l
 
Note: VCD cell restart is not required.
Powered by Wolken Software