In this article, we will discuss a common issue that arises while converging a PSC to an embedded one. The error message typically reads “The vCenter Server appliance build number does not match with the vCenter Server appliance configured in the update repository.” We have also included a screenshot of the error.
Table of Contents
PSC Convergence Prerequisites
To resolve this issue, there are several steps that you need to take.
- Check NTP server configurations
- Ensure A and PTR DNS records are correct
- Back up all PSCs and connected vCenters in the SSO domain
- Download the vCenter Server ISO if the server does not have internet access, ensuring that you download the exact same ISO for the version you are running
- Disable vCenter HA before starting to converge the vCenter Server
How to resolve the issue
- To begin, log in to the VAMI page of both the PSC and vCenter and navigate to the Update > Settings section to verify the repository URL. Ensure that it is set to default.
- Once both URLs have been verified, start the convergence process and check whether the issue persists.
- If the issue still exists, log in to both the PSC and vCenter via SSH, and in the appliance shell, run the command below to verify the current and default URLs. You will need to do this for both VC and PSC.
- If you notice that the URLs do not match, use the command provided to match the default URL with the current URL.
update.set --currentURL "default"
- Once this is done, proceed with the convergence of the PSC to the embedded one.
Note: Sometimes, when you log in to VC or PSC, you may directly login to the bash shell instead of the appliance shell. In this case, run the command provided to access the appliance shell.
chsh -s /bin/appliancesh root
By following these steps, you should be able to resolve the issue. If you are still having issues, please leave a comment on this post, and I will be happy to help you. Alternatively, you can connect with me on Twitter for further assistance.