Error: "Failed to reload vm 'vm-######' from path '[########] rtvm-C4-######/rtvm-C4-#######' for vc '1d######'. " when performing a test failover of an encrypted VM in VMware Cloud Direct Availability

Products

• VMware Cloud Director

Issue/Introduction

• When performing a test failover of an encrypted VM we get error,
  Operation canceled due to an unexpected error.
Failed to reload vm 'vm-######' from path '[########] rtvm-C4-######/rtvm-C4-#######' for vc '1d######'
• From the VMware Cloud Director Availability we get below error,
  ERROR - [UI-#############] [task-poller-4] com.vmware.h4.jobengine.JobExecution     : Task 9ac6####-####-####-####-####5aee (WorkflowInfo{type='failoverTest', resourceType='vmReplication', resourceId='C4-####-####-####-####-####c5c1', isPrivate=false, resourceName='####}) has failed
com.vmware.h4.api.error.exceptions.GenericServerException: Operation aborted due to an unexpected error.
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481)
at com.vmware.h4.api.error.GenericServerExceptionProvider.get(GenericServerExceptionProvider.java:125)
at com.vmware.h4.api.error.GenericServerExceptionProvider.get(GenericServerExceptionProvider.java:97)
• In vCenter it fails with below error:
  The specific key, name or identifier '#######' already exists.

 

Environment

VMware Cloud Director 10.6.x
VMware Cloud Director Availability 4.7.x

Cause

This issue occurs when Allow I/O filters are not applied properly in source and destination in vCenter.

Resolution

To resolve this issue, perform the below steps in source and destination:

1. Login to the vCenter, navigate to Policies and Profiles > VM Storage Policies.
2. Edit the Allow I/O filters and save. 

Refer, Assign the I/O Filter Policy to Virtual Machines