vCenter deployment or upgrade Stage 1 fails with the error "Error: Internal error: Failed to connect to remote host due to [No version for VMODL calls]"

Products

• VMware vCenter Server

Issue/Introduction

• While performing a vCenter upgrade, Stage 1 deployment fails at 0%.
• Deployment fails when selecting Destination host as an ESXi or vCenter.
• Installer logs show below entries:
  
  <date><time> - error: Progress Controller: [VCSA ERROR] - Progress callback error
<date><time> - error: Progress Controller: [VCSA ERROR] - Details Internal error: Failed to connect to remote host [vCenter or ESXi FQDN/IP] due to [No version for VMODL calls to <<cs p:081fb2f8, TCP:vCenter or ESXi FQDN/IP:443>, /sdk>]
<date><time> - info: Cancelling the ping timer for session mgmt
  
  
• Connectivity to the destination host (either vCenter or ESXi host) on port 443 is working fine.
• vCenter deployment fails with both CLI and UI methods.
• Any other OVA/OVF deployment from the jump server is working via vCenter and ESXi host UI.

Environment

• VMware vCenter Server 8.x

Resolution

Workaround:

Perform the stage 1 deployment using vCenter OVA. Please follow the below steps:

1. Mount the vCenter ISO to a jump server.
2. Browse to the ISO drive.
3. Go into the vcsa folder.
4. Locate the vcenter.ova file for the vCenter.
5. Login to source vCenter or an ESXi host.
6. Right click on a host or a cluster and select Deploy OVF template.
7. Browse to the local files and select the vcenter.ova file from the mounted ISO.
8. Proceed with the deployment by following the deployment wizard.
9. Once the vCenter VM is deployed, open VAMI page using vCenter IP and proceed with stage 2.

Note: If this issue needs to be investigated further for a resolution, please open a Support Request with Broadcom Support team.