Error "Socket Read TimeOut" when migrating a VM from unencrypted to encrypted and the destination is ESXi 8.0.
search cancel

Error "Socket Read TimeOut" when migrating a VM from unencrypted to encrypted and the destination is ESXi 8.0.

book

Article ID: 391261

calendar_today

Updated On: 03-20-2025

Products

VMware Cloud Director

Issue/Introduction

  • Cloud to Cloud VM migration fails with the error:

    Socket Read TimeOut
  • In the /opt/vmware/h4/cloud/log/cloud.log file in the destination site we see the migration job start and ultimately fail with the Socket read timeout error:

    DATE TIME ERROR - [UI-########-####-####-########47-QX] [task-poller-1] com.vmware.h4.jobengine.JobExecution     : Task ########-####-####-########05bc (WorkflowInfo{type='migrate', resourceType='vmReplication', resourceId='C4-########-####-####-########e9a8', isPrivate=false, resourceName='donagh-noenc'}) has failed
    com.vmware.h4.api.error.exceptions.client.ReadTimeoutException: Socket read timeout.
            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)
            at com.vmware.h4.common.task.H4ApiTaskToTaskConverter.toTask(H4ApiTaskToTaskConverter.java:33)
            at com.vmware.task.rest.client.TaskMonitor.lambda$workImpl$0(TaskMonitor.java:216)
            at com.vmware.task.rest.client.TaskMonitor.notifyListener(TaskMonitor.java:236)
            at com.vmware.task.rest.client.TaskMonitor.workImpl(TaskMonitor.java:215)
            at com.vmware.task.rest.client.TaskMonitor.work(TaskMonitor.java:133)
            at com.vmware.h4.cloud.service.ManagerTaskMonitorService.lambda$taskMonitor$0(ManagerTaskMonitorService.java:115)
            at com.vmware.h4.common.mdc.MDCRunnableWrapper.run(MDCRunnableWrapper.java:32)
            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)

  • The migration is from an unencrypted source to an encrypted destination.
  • The migration fails when using ESXi 8.0 U3b and it is successful when using ESXi 7.0 U3 is working.

Environment

VMware Cloud director Availability 4.7.3

Cause

The issue is related to the nonencrypted-to-encrypted implementation during the migration.

Resolution

There is no resolution available.

Subscribe to this knowledge article to get updates on this issue.