Symptoms
A CLI upgrade of vCenter Server to 7.0 U3c or U3d from a source vCenter Server running 7.0U3, 7.0U3a fails with messages similar to the following
Messages indicating that the upgrade failed due to known problematic builds are seen in /var/log/vmware/applmgmt/PatchRunner.log
"patchScript": "/storage/updatemgr/software-updatequrce_8p/stage/scripts/patches/payload/components-script/vcIntegrity", "requirementsResult": { "mismatches": [.."localized": "vCenter upgrade is not allowed if there is any ESXi 7.0 U3 or U3a host(s) in the inventory.","translatable": "vCenter upgrade is not allowed if there is any ESXi 7.0 U3 or U3a host(s) in the inventory."...."localized": "4 ESXi 7.0 U3 or U3a host(s) were found in the vCenter inventory.","translatable": "%(0)s ESXi 7.0 U3 or U3a host(s) were found in the vCenter inventory."
A CLI upgrade of vCenter Server to 7.0 U3c from a source vCenter Server running a version prior to 7.0U3 (i.e. 7.0 U2d and earlier) fails with messages similar to the below
Cause
The CLI upgrade precheck has detected potentially problematic hosts in the environment as detailed in VMware KB 86447 - Upgrading vCenter Server 7.0 fails during precheck with "Host(s) were found in the vCenter Inventory, that are potentially problematic for a vCenter upgrade"
Resolution
This issue is resolved in this release. (i.e. 70U3c to 70U3d). However, if you update from VMware vCenter Server 7.0 Update 3, Update 3a to 7.0 Update 3d, follow the steps in VMware KB 86447
