Importing virtual machine with Advanced Cross vCenter vMotion fails due to SSLVerifyFault
search cancel

Importing virtual machine with Advanced Cross vCenter vMotion fails due to SSLVerifyFault

book

Article ID: 420129

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • Host's SSL certification cannot be verified correctly when ESXi is selected for importing virtual machine.

Environment

VMware vCenter Server 7.x
VMware vCenter Server 8.x

Cause

Changing the vCenter Server PNID from lowercase to uppercase will cause an SSL trust mismatch if the operation fails.
When importing virtual machine is executed on the vCenter Server, this SSL trust mismatch subsequently causes the failure of the destination ESXi's SSL certificate verification with the following error: vim.vm.check.ProvisioningChecker.checkRelocate: vim.fault.SSLVerifyFault.

In the /var/log/vmware/vpxd/vpxd.log file:

yyyy-mm-ddThh:mm:ss.fffZ info vpxd[31703] [Originator@6876 sub=Default opID=####-###-###-ct-h5:#####-##] [VpxLRO] -- ERROR session[#####-####-###-####-###############]##############-###-##-##-####-- ProvChecker -- vim.vm.check.ProvisioningChecker.checkRelocate: vim.fault.SSLVerifyFault:
--> Result:
--> (vim.fault.SSLVerifyFault) {
-->    faultCause = (vmodl.MethodFault) null, 
-->    faultMessage = <unset>, 
-->    selfSigned = false, 
-->    thumbprint = "##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##"
-->    msg = ""
--> }

Resolution

Fix SSL trust mismatch with lsdoctor tool and then import virtual machine again.

For more information, see Using the 'lsdoctor' Tool.