Validate vMotion Network ConnectivityProgress Messages:Validate vMotion Network ConnectivityError:Message: Validate vMotion Network ConnectivityRemediation Message:Reference Token: #####Cause: Failed to connect to ESX Host <host fqdn> with the specified credentials, Failed to connect to ESX Host <host1 fqdn> with the specified credentials, Failed to connect to ESX <host2 fqdn> with the specified credentials, Failed to connect toESX Host <host3 fqdn> with the specified credentials - Product version VCF 9.0
ERROR [vcf_dm,##########,adec] [c.v.evo.sddc.common.util.SshUtil,####] Unable to create jsch CLI session:com.jcraft.jsch.JSchException: HostKey has been changed: <hostname>
ERROR [vcf_dm,##########,adec] [c.v.e.s.c.u.c.SshCommandExecuter,####] Could not connect to the SSH server @<hostname> for configuration.com.jcraft.jsch.JSchException: HostKey has been changed: <hostname>
ERROR [vcf_dm,##########,adec] [c.v.evo.sddc.common.util.SshUtil,####] Unable to create jsch CLI session:com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused at com.jcraft.jsch.Util.createSocket(Util.java:394) at com.jcraft.jsch.Session.connect(Session.java:215)
VMware Cloud Foundation (VCF) 9.0
The failure is caused by an SSH Host Key mismatch between the SDDC Manager and the ESXi hosts. This happens when the SSH fingerprint stored in the SDDC Manager’s known_hosts does not match the current fingerprint presented by the ESXi host, causing the security handshake to fail and blocking automated configuration tasks.
Regenerate the host keys for the host listed in the logs to fix the SDDC connectivity issue with the host