I had an issue (self inflicted) where i needed to remove the two secondary Cells from vCloud Director deployment.
After removing the two cells i’d broken, i proceeded to deploy two new secondary cells with the same version as my primary cell.
I’m using signed certificates for all my 3 cells, and they’re unique to each cell (no wildcard).
When you’ve deployed a Secondary VCD cell and browse to :5480 it simply asks for the vCloud Director Transfer NFS, super simple!
Problem was that when the setup ran, it would fail when it came to adding the self-signed certificates to the java keystore. It uses the root password to do this, problem is it uses the root password that was supplied initially when the primary cell was deployed, not the current one.
The fix is to deploy the cell appliance with the same root password you used when you initially deployed the primary cell, then use https://docs.vmware.com/en/VMware-Cloud-Director/10.5/VMware-Cloud-Director-Install-Configure-Upgrade-Guide/GUID-F52309A2-1E55-434F-B25B-21CC42F49AC6.html after deployment to change it.
INFO: connecting to primary database
WARNING: –upstream-node-id not supplied, assuming upstream node is primary (node ID: 8062)
INFO: standby registration complete
NOTICE: standby node “sfo-vcd01b” (ID: 20253) successfully registered
Configuring VCD from response file (/opt/vmware/vcloud-director/data/transfer/responses.properties).
2023-08-08 12:20:45 | setupvcd.sh | Configuring VCD from response file (/opt/vmware/vcloud-director/data/transfer/responses.properties).
2023-08-08 12:20:45 | setupvcd.sh | According to responses.properties, user http certificate is not on the NFS share. Overriding http cert location to: /opt/vmware/vcloud-director/etc/user.http.pem
Cryptographic error: Password provided was incorrect for the supplied private key
2023-08-08 12:20:48 | setupvcd.sh | [ERROR] Failed to configure vCD. Check /opt/vmware/vcloud-director/logs for details. Aborting.
2023-08-08 12:20:48 | configure-vcd.sh | [ERROR] setupvcd script failed to execute.
2023-08-08 12:20:48 | cleanup-vcd.sh | Starting cleanup script.
This has been reported to VMware Engineering and they are working on remedying this.