VCF customers running on versions 4.x and 5.x who have updated to async patches (such as vCenter 7.0U3t) may encounter issues when attempting to upgrade to VCF 5.2.0.0 or 5.2.1.0.
This issue arises with Async Patch vCenter versions that were released after the target VCF release version, making the upgrade incompatible.
VMware Cloud Foundation 5.x
VMware Cloud Foundation 4.x
The underlying cause is that the security patches applied to vCenter (e.g., 7.0U3t) are newer than the corresponding VCF versions available at the time of the upgrade attempt.
As a result, compatibility checks fail during the upgrade process, preventing the system from progressing to the desired VCF version.
To bypass this issue and successfully upgrade to VCF 5.x, follow these steps:
systemctl restart lcm
For example:
VCF 4.5.2.0 with vCenter Patched to 7.0U3T, Plans to upgrade to VCF 5.2.0.0/VCF 5.2.1.0.
Refer to KB Article for more details on bypassing upgrade compatibility checks:
https://knowledge.broadcom.com/external/article/323368/bypass-sddc-manager-upgrade-compatibilit.html