Upgrade Manager 5.3.1 failing SSH connectivity pre-validation check

[jlangmead]

Hi

When running upgrade manager 5.3.1 to upgrade a 2 node cluster, the pre-checks are failing the SSH connectivity tests for both hosts. I have putty installed on the same machine where Upgrade Manager is running and I can connect fine using Putty. So this proves the SSH service is enabled on the host and that the root password I have is also correct.

The only scenario I can think of is that the root password has been changed on the host but the OVC digital vault  not updated. The cluster is not showing any alerts so is it possible the OVCs could have an incorrectly configured root password and this not raise any alerts? Does it use the root password for any day to day tasks that would now fail?

Is there a way to check the root password stored within the digital vault? Or do I need to just overwrite it using the following procedure to ensure it has been configured with the correct password.

> Login using the Administrator@vsphere.local account on OVC
> sudo su
> source /var/tmp/build/bin/appsetup
> dsv-digitalvault-init --hmsuser administrator@vsphere.local --hostip x.x.x.x --hostuser root   >>>press enter
Here 
--hmsuser : vCenter Global Administrator administrator@vsphere.local
--hostip : ESXi IP address
--hostuser : ESXi root user

And then enter the correct root password.

many thanks in advance

[jlangmead]

This turned out to be a firewall restriction - so I guess it's not been able to use SSH connections between the OVC and ESXi hosts a long time. This has now been rectified.