Upgrade vSphere Replication 6.X to 8.X "Failed to connect to VR appliance" after entering source appliance root password on step 18. Upgrade option on console.

Products

• VMware Live Recovery
• VMware vSphere ESXi

Issue/Introduction

Symptoms:
vSphere Replication 6.1.2.2 upgrade to 8.1.1 is failing . Upgrade. Failed to Connect to VR Appliance [vrappliance.fqdn].


hms-boot.log of new VR 8.1.1 Appliance

Failed to connect to VR appliance [vrappliance.fqdn]
(vmodl.fault.SystemError) {
   faultCause = null,
   faultMessage = null,
   reason = Missing non-optional return value
}
    at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.checkNonOptionalValueProvided(ResponseImpl.java:247)
    at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:229)
    at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:156)
    at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:53)
    at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:226)
    at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:106)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:629)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:610)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:360)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:311)
    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:184)
    at com.sun.proxy.$Proxy37.findAllByDnsName(Unknown Source)
    at com.vmware.hms.config.vix.VixRemoteExecutor.search(VixRemoteExecutor.java:691)
    at com.vmware.hms.config.vix.VixRemoteExecutor.findHmsVm(VixRemoteExecutor.java:626)
    at com.vmware.hms.config.vix.VixRemoteExecutor.<init>(VixRemoteExecutor.java:142)
    at com.vmware.hms.apps.util.upgrade.Vr81MigrationUpgradeWorkflow.connectToVrAppliance(Vr81MigrationUpgradeWorkflow.java:447)
    at com.vmware.hms.apps.util.upgrade.Vr81MigrationUpgradeWorkflow.lambda$compileUpgrade$1(Vr81MigrationUpgradeWorkflow.java:1201)
    at com.vmware.hms.apps.util.upgrade.Vr81MigrationUpgradeWorkflow.run(Vr81MigrationUpgradeWorkflow.java:519)
 

Environment

VMware vSphere Replication 8.x
VMware vSphere Replication 6.x

Cause

In the vSphere Replication Appliance VAMi. The Network tab will show the VRHostname as the DNS shortname instead of its full fqdn.  The vSphere web client will show this on the VR Appliance VM's, summary tab.

The new VR Appliance 8.1.1 will be looking for the full fqdn of the original VR Appliance, that you set in the wizard.

Resolution

Ensure you have DNS configured correctly with forward and reverse lookup for the PSC, vCenter and VR Appliance.

Log into the original vSphere Replication VAMi page https://VRApplianceIP:5480 

Select Networking tab. Change the VR Appliance's Hostname from shortname to full fqdn.

Enter password for your account.

Perform a Save and Restart to update the vCenter.

Proceed with Upgrading to 8.1.1.


Workaround:
none

Additional Information

Impact/Risks:
none