Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Instant clone provisioning fails.The broker log contains entries similar to: 2019-02-20T17:41:23.279+09:00 ERROR (10F4-0F24) [CloneNgvcVmPO] Cloning of VM test123 has failed: Fault type is UNKNOWN_FAULT_FATAL - Unknown error 2019-02-20T17:41:23.279+09:00 DEBUG (10F4-0F24) [CloneNgvcVmPO] Cloning of VM test123 has failed: Fault type is UNKNOWN_FAULT_FATAL - Unknown error : com.vmware.daas.cloneprep.common.CPException: Unknown error at com.vmware.daas.cloneprep.workflowengine.Task.executeNextAction(Task.java:500) at com.vmware.daas.cloneprep.workflowengine.WorkflowEngine.processReadyQueue(WorkflowEngine.java:886) at com.vmware.daas.cloneprep.workflowengine.WorkflowEngine.run(WorkflowEngine.java:651) at java.lang.Thread.run(Thread.java:748) Further down in the log file, you see vCenter connectivity errors: 2019-02-05T17:31:49.151+09:00 ERROR (1004-2154) <WFE-09> [VcSubsystem25] Retry because VC operation failed with error: com.vmware.vdi.logger.Logger.error(Logger.java:92) javax.xml.ws.WebServiceException: Could not send Message. at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:150) at com.sun.proxy.$Proxy190.reconfigVMTask(Unknown Source) com.vmware.daas.cloneprep.workflowengine.ActionLink.execute(ActionLink.java:216) at com.vmware.daas.cloneprep.workflowengine.Task.executeNextAction(Task.java:478) at com.vmware.daas.cloneprep.workflowengine.WorkflowEngine.processReadyQueue(WorkflowEngine.java:886) at com.vmware.daas.cloneprep.workflowengine.WorkflowEngine.run(WorkflowEngine.java:651) at java.lang.Thread.run(Thread.java:748) Caused by: java.net.SocketException: SocketException invoking https://vc001:443/sdk: Software caused connection abort: socket write error
This issue occurs when the SSL handshake with vCenter Server is timing out.
Identify the bottleneck causing the delay in the handshake timeout.
To resolve this issue increase the SSL handshake timeout.Please refer to After renewing a ESXi Host Certificate, directly connecting to the host using browser gives non secure connection status (60216) for specifics on backing up and editing /etc/vmware/rhttpproxy/config.xmlWith your config, You will see lines similar to the below - if there is no line on handshakeTimeoutMs , you can manually add this line.<config> <vmacore> <rootPasswdExpiration>false</rootPasswdExpiration> <ssl> <doVersionCheck> false </doVersionCheck> <useCompression>true</useCompression> <libraryPath>/lib/</libraryPath> <handshakeTimeoutMs>20000</handshakeTimeoutMs> <---- change here to 120 000 (2 minutes) <sslOptions>50479104</sslOptions> </ssl> <!-- enable plugin loading --> <loadPlugins> false </loadPlugins> ... </vmacore>...</config> Restart rhttpproxy service with this command: service-control --restart rhttpproxy