Error "Internal Server Error - Undeploy VMs did not complete successfully. Skipping resume VMs phase" when reverting to a VM snapshot in Cloud Director
search cancel

Error "Internal Server Error - Undeploy VMs did not complete successfully. Skipping resume VMs phase" when reverting to a VM snapshot in Cloud Director

book

Article ID: 390316

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • While reverting VMs from snapshot the following errors are displayed : 

    Internal Server Error - Undeploy VMs did not complete successfully. Skipping resume VMs phase

    Internal Server Error - Expected completed future, but received future which is still in progress

  • The Cloud Director logs will show error similar to:

    (com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:<TASK_ACTIVITY_UUID>)
    java.util.concurrent.ExecutionException: java.lang.AssertionError: Undeploy VMs did not complete successfully. Skipping resume VMs phase.
        at com.vmware.ssdc.backend.RevertVAppSnapshotActivity$ResumeVmsPhase.invoke(RevertVAppSnapshotActivity.java:336)
        at com.vmware.vcloud.activity.executors.ActivityRunner.runPhase(ActivityRunner.java:175)
        at com.vmware.vcloud.activity.executors.ActivityRunner.run(ActivityRunner.java:112)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
    Caused by: java.lang.AssertionError: Undeploy VMs did not complete successfully. Skipping resume VMs phase.
        at com.vmware.ssdc.backend.RevertVAppSnapshotActivity$ResumeVmsPhase.invoke(RevertVAppSnapshotActivity.java:334)
        ... 7 more

Environment

VMware Cloud Director 10.6.0.1

Cause

This issue can occur high number of tasks performed in vCenter, which might cause some delay in processing these task updates in Cloud Director.

Resolution

To resolve the issue you will need to increase the timeout of the properties 'vm.snapshotRevertTimeoutInSeconds' and .'vcloud.val.inventory.updateTimeout'

To do that please use the following command 

/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n vm.snapshotRevertTimeoutInSeconds -v 600

Also to  increase one more property 'vcloud.val.inventory.updateTimeout', default timeout for this property is 300 seconds.

/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n vcloud.val.inventory.updateTimeout -v 480

 

To verify that the values are correctly set run the command:

/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n vm.snapshotRevertTimeoutInSeconds -l

 

Note: Cloud Director cell re-start is not required here.