When attempting to upgrade VMware Cloud Foundation (VCF) to version 9.1.0.x, the upgrade pre-checks fail for Management or Workload domains. In the SDDC Manager or VCF Operations UI, upgrade options for NSX, vCenter, and ESXi appear grayed out with the following error:
Detailed pre-check results indicate that components are "not upgradable" and "not interoperable":
Cannot upgrade to VCF version 9.1.0.0 for domain [domain-id] in a compatible way: not upgradable: NSX_T_MANAGER 4.2.4.0.0.25410638 -> NSX_T_MANAGER 9.1.0.0.25318225, VCENTER 8.0.3.00900-25413364 -> VCENTER 9.1.0.0.25370922, ESX_HOST 8.0.3-25429389 -> ESX_HOST 9.1.0.0.25370933; not interoperable: ESX_HOST 9.1.0.0.25370933 -> VCENTER 8.0.3.00900-25413364.
Affected Configurations: This restriction impacts environments with the following configurations:
This failure is caused by an intentional "Back-in-Time" upgrade restriction.
A back-in-time scenario is defined as an upgrade path that would result in the deliberate regression of code and security fixes. VMware Cloud Foundation prevents upgrading a software component to a build that is chronologically older than the version currently installed.
Although VCF 9.1.0 is a higher major version, the specific builds for vCenter, ESXi, and NSX were released after the VCF 9.1.0.x software baseline was finalized. Because the installed environment contains security patches and fixes not yet present in the VCF 9.1.0.x bundle, the system blocks the upgrade path to prevent a regression in the environment's state.
VMware Cloud Foundation 9.1.1.0 has been released with an updated Bill of Materials (BOM) that includes component build versions chronologically newer than the previous 9.1.0.0 restriction baseline. This effectively resolves the "Back-in-Time" upgrade block for environments running vSphere 8.0 Update 3j and later, NSX 4.2.4 and later, VMware Cloud Foundation 9.1.0.x.
Correlating VMware VCF versions