Error "The requested resource was not found" when migrating VM with VMware Cloud Director Availability

Products

• VMware Cloud Director

Issue/Introduction

• VM migration fails with the error "The requested resource was not found"
• The VM migration starts off with initial Migrating “x%” and counting up as normal. But at some point around 30-40%, it starts syncing again with no warning or error and then it fails.
  
  
• In the /opt/vmware/h4/cloud/log/cloud.log file on the source Cloud Replication Management Appliance, you see messages similar to:

YYYY-MM-DD TIME ERROR - [UI-####-####-####-####] [task-poller-2] com.vmware.h4.jobengine.JobExecution     : Task ####-####-####-#### (WorkflowInfo{type='migrate', resourceType='vmReplication', resourceId='C4-####-####-####-####', isPrivate=false, resourceName='NAME'}) has failedcom.vmware.h4.exceptions.common.NotFoundException: The requested resource was not found        
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:499)        
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)        
at com.vmware.h4.api.error.GenericServerExceptionProvider.get(GenericServerExceptionProvider.java:123)        
at com.vmware.h4.api.error.GenericServerExceptionProvider.get(GenericServerExceptionProvider.java:95)        
at com.vmware.h4.common.task.H4ApiTaskToTaskConverter.toTask(H4ApiTaskToTaskConverter.java:31)        
at com.vmware.task.rest.client.TaskMonitor.lambda$workImpl$0(TaskMonitor.java:214)        
at com.vmware.task.rest.client.TaskMonitor.notifyListener(TaskMonitor.java:234)        
at com.vmware.task.rest.client.TaskMonitor.workImpl(TaskMonitor.java:213)        
at com.vmware.task.rest.client.TaskMonitor.work(TaskMonitor.java:131)        
at com.vmware.h4.cloud.service.ManagerTaskMonitorService.lambda$taskMonitor$0(ManagerTaskMonitorService.java:113)        
at com.vmware.h4.common.mdc.MDCRunnableWrapper.run(MDCRunnableWrapper.java:30)        
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)        
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)        
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)        
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)        
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)        
at java.base/java.lang.Thread.run(Thread.java:840)

Environment

VMware Cloud Director Availability 4.7.1

Cause

After upgrading the replicator still shows the old version and its reporting the error: 
"The request can not be processed, because the HTTP method for the resource is not supported."

Resolution

Rebooting and re-pairing the affected replicator.