This is going to go over three common errors you may see when trying to install the vCD agent on the host.
The first error message is quite simple:
Failures occurred during prepare of host "ciscol01.r3hx.mlb03.lab.vce.com".
- Cannot complete login due to an incorrect user name or password.
- Cannot complete login due to an incorrect user name or password.
Hopefully this should be pretty clear to you, there is a password mismatch. You are not typing the correct credentials for access to the host. To resolve this, open up SSH access to your host and use the "root" account for login. Try all your known passwords until you have one that works. use the root account and your known password to get the agent installed.
The second error message:
Failures occurred during prepare of host "ciscol02.b3hx1.mlb03.lab.vce.com".
- The vCloud Director operation has timed out.
vCenter Server task (moref: task-21153) failed in vCenter Server 'R3HX-VC' (e2081380-3657-46ea-849f-f4ac439750c5).
- Operation timed out.
This error message means that vCenter could not put the host in maintenance mode to install the host agent. Make sure DRS is enabled and the vMotion network is configured and all hosts can communicate on it. In my case, there was a VM that was outside of vCloud Director's control that was unable to vMotion. I had to power off the VM, and migrate it manually. Once it was off the host, the installation continued.
The third error message:
Failures occurred during prepare of host "ciscol01.b3hx1.mlb03.lab.vce.com".
- javax.net.ssl.SSLException: com.vmware.ssdc.util.crypto.CryptoException: Host certificate thumbprint did not match expected value.
- javax.net.ssl.SSLException: com.vmware.ssdc.util.crypto.CryptoException: Host certificate thumbprint did not match expected value.
- com.vmware.ssdc.util.crypto.CryptoException: Host certificate thumbprint did not match expected value.
- Host certificate thumbprint did not match expected value.
This error message means you have DNS issues. In my case, these hosts were previously added to vCloud, then they mysteriously stopped working. Come to find out, DNS went down and was really broken. To test to make sure its the same root cause, go to your vCloud cell, and try to ping your host via DNS. Did it work? Yes, then i guess it's not a DNS issue. Try removing the hosts from vCloud and re-adding them back in. If pinging via DNS doesn't not work, and pinging via IP does, then you need to add the hosts to your /etc/hosts file on each cell. Once the entries were made in the /etc/hosts file, then the vCD agent installation works.
